Skip to content

Verification Request: homebridge-texecom-full #767

New issue
New issue
Closed
Closed
Verification Request: homebridge-texecom-full#767
Labels
request-verificationverifieduse when a plugin meets the criteria - adds the verified badge text

Description

@K1LL3R234
K1LL3R234
opened on Oct 9, 2024

Plugin Name

homebridge-texecom-full

Link To GitHub Repo

https://github.com/K1LL3R234/homebridge-texecom

Plugin Icon (Optional)

No response

The plugin does not offer the same nor less functionality than that of any existing verified plugin.

🟢 Yes

The plugin successfully installs and does not start unless it is configured.

🟢 Yes

The plugin does not require the user to run Homebridge in a TTY or with non-standard startup parameters, even for initial configuration.

🟢 Yes

The plugin does not contain any analytics or calls that enable you to track the user.

🟢 Yes

If the plugin needs to write files to disk (cache, keys, etc.), it stores them inside the Homebridge storage directory.

🟢 Yes

The plugin does not throw unhandled exceptions, the plugin must catch and log its own errors.

🟢 Yes

More Information

No response

Activity

  1. K1LL3R234
    added
    pendingthe label given to a new verification/icon request
    on Oct 9, 2024

  2. github-actions commented on Oct 9, 2024

    @github-actions
    github-actionsBot
    on Oct 9, 2024 – with GitHub Actions
    Contributor

    🔴 The following checks failed:

    • Package JSON: homepage missing or does not start with https://
    • Package JSON: bugs.url missing
    • Package JSON: 'preinstall' in scripts is not allowed

    🟢 The following checks passed:

    • Installation: successfully installed
    • Package JSON: keywords exist and contain 'homebridge-plugin'
    • Package JSON: 'install' in scripts is not present
    • Package JSON: 'postinstall' in scripts is not present
    • Package JSON: engines.node property is compatible with Node 18
    • Package JSON: engines.node property is compatible with Node 20
    • Package JSON: engines.homebridge property is compatible with Homebridge 1.8.4
    • Package JSON: initializer function found
    • NPM Package: has not been deprecated
    • Config Schema JSON: exists and is valid JSON
    • Config Schema JSON: contains a valid pluginAlias
    • Config Schema JSON: the pluginType is set to 'platform'
    • Config Schema JSON: contains a name schema property
    • Dependencies: homebridge was not installed as a dependency
    • Dependencies: hap-nodejs was not installed as a dependency

    ⚠️ Please action these failures and then comment /check to run the checks again. Let us know if you need any help.

    If updating your package.json and config.schema.json files, don't forget to publish a new version to NPM.

  3. github-actions
    added
    awaiting-changesuse after review has started - awaiting user to make changes to plugin
    and removed
    pendingthe label given to a new verification/icon request
    on Oct 9, 2024

  4. K1LL3R234 commented on Oct 9, 2024

    @K1LL3R234
    K1LL3R234
    on Oct 9, 2024
    Author

    /check

  5. github-actions
    added
    pendingthe label given to a new verification/icon request
    and removed
    awaiting-changesuse after review has started - awaiting user to make changes to plugin
    on Oct 9, 2024

  6. github-actions commented on Oct 9, 2024

    @github-actions
    github-actionsBot
    on Oct 9, 2024 – with GitHub Actions
    Contributor

    🟢 The following checks passed:

    • Installation: successfully installed
    • Package JSON: homepage exists
    • Package JSON: bugs.url exists and seems a valid URL
    • Package JSON: keywords exist and contain 'homebridge-plugin'
    • Package JSON: engines.node property is compatible with Node 18
    • Package JSON: engines.node property is compatible with Node 20
    • Package JSON: engines.homebridge property is compatible with Homebridge 1.8.4
    • Package JSON: initializer function found
    • GitHub Repo: repository is public
    • GitHub Repo: repository is not archived
    • GitHub Repo: issues are enabled
    • GitHub Repo: contains releases
    • NPM Package: has not been deprecated
    • Config Schema JSON: exists and is valid JSON
    • Config Schema JSON: contains a valid pluginAlias
    • Config Schema JSON: the pluginType is set to 'platform'
    • Config Schema JSON: contains a name schema property
    • Dependencies: homebridge was not installed as a dependency
    • Dependencies: hap-nodejs was not installed as a dependency

    🎉 All checks passed successfully, nice work! Your plugin and/or icon will now be manually reviewed by the Homebridge team.

  7. bwp91
    added
    request-verification
    on Oct 12, 2024

  8. bwp91 commented on Dec 29, 2024

    @bwp91
    bwp91
    on Dec 29, 2024
    Contributor

    /check

  9. github-actions commented on Dec 29, 2024

    @github-actions
    github-actionsBot
    on Dec 29, 2024 – with GitHub Actions
    Contributor

    🔴 The following checks failed:

    • Package JSON: engines.node property is not compatible with Node 22

    🟢 The following checks passed:

    • Installation: successfully installed
    • Package JSON: homepage exists
    • Package JSON: bugs.url exists and seems a valid URL
    • Package JSON: keywords exist and contain 'homebridge-plugin'
    • Package JSON: engines.node property is compatible with Node 18
    • Package JSON: engines.node property is compatible with Node 20
    • Package JSON: engines.homebridge property is compatible with Homebridge 1.8.5
    • Package JSON: initializer function found
    • GitHub Repo: repository is public
    • GitHub Repo: repository is not archived
    • GitHub Repo: issues are enabled
    • GitHub Repo: contains releases
    • NPM Package: has not been deprecated
    • Config Schema JSON: exists and is valid JSON
    • Config Schema JSON: contains a valid pluginAlias
    • Config Schema JSON: the pluginType is set to 'platform'
    • Config Schema JSON: contains a name schema property
    • Dependencies: homebridge was not installed as a dependency
    • Dependencies: hap-nodejs was not installed as a dependency

    ⚠️ Please action these failures and then comment /check to run the checks again. Let us know if you need any help.

    If updating your package.json and config.schema.json files, don't forget to publish a new version to NPM.

    These checks were run against v4.2.3 of the plugin.

  10. github-actions
    added
    awaiting-changesuse after review has started - awaiting user to make changes to plugin
    and removed
    pendingthe label given to a new verification/icon request
    on Dec 29, 2024

  11. bwp91 commented on Dec 29, 2024

    @bwp91
    bwp91
    on Dec 29, 2024
    Contributor

    @K1LL3R234 please update the package.json engines.node property to show compatibility with node 22.

    Something like "node": "^18.20.4 || ^20.15.1 || ^22.12.0"

    This is assuming the plugin works on node 22!

  12. K1LL3R234 commented on Jan 3, 2025

    @K1LL3R234
    K1LL3R234
    on Jan 3, 2025
    Author

    I fixed it

  13. 8 remaining items

  14. bwp91
    added
    awaiting-user-replyuse after review has started - awaiting user to reply to a comment
    on Jul 19, 2025

  15. K1LL3R234 commented on Jul 19, 2025

    @K1LL3R234
    K1LL3R234
    on Jul 19, 2025
    Author

    Hi @bwp91 yes that one uses a different protocol of the texecom panel and you need a different device to work with it where mine is simply just rs232 or tcp. If you want further info please let me know and I will provide more info

  16. bwp91 commented on Jul 19, 2025

    @bwp91
    bwp91
    on Jul 19, 2025
    Contributor

    @K1LL3R234 I was testing with a fake IP address in the config, and this caused an unhandled exception which meant the process crashed and restarted. The plugin should catch all errors so that the system does not get into a crash and reboot loop.

    Here is the config I used and logs I saw:

            {
            "name": "Texecom",
            "ip_address": "192.168.0.3",
            "ip_port": 10001,
            "debug": false,
            "_bridge": {
                "username": "0E:80:A5:60:EF:7D",
                "port": 38793
            },
            "platform": "Texecom"
        }

    [1] Error: connect ETIMEDOUT 192.168.0.3:10001
[1]     at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1637:16) {
[1]   errno: -60,
[1]   code: 'ETIMEDOUT',
[1]   syscall: 'connect',
[1]   address: '192.168.0.3',
[1]   port: 10001
[1] }
[1] [7/19/2025, 7:52:52 PM] [Texecom] Child bridge process ended
[1] [7/19/2025, 7:52:52 PM] [Texecom] Process Ended. Code: 1, Signal: null
[1] [7/19/2025, 7:52:59 PM] [Texecom] Restarting Process...
  17. bwp91
    added
    awaiting-changesuse after review has started - awaiting user to make changes to plugin
    and removed
    awaiting-user-replyuse after review has started - awaiting user to reply to a comment
    on Jul 19, 2025

  18. K1LL3R234 commented on Jul 25, 2025

    @K1LL3R234
    K1LL3R234
    on Jul 25, 2025
    Author

    Please /check again

  19. K1LL3R234 commented on Jul 25, 2025

    @K1LL3R234
    K1LL3R234
    on Jul 25, 2025
    Author

    /check

  20. github-actions
    added
    pendingthe label given to a new verification/icon request
    and removed
    awaiting-changesuse after review has started - awaiting user to make changes to plugin
    on Jul 25, 2025

  21. github-actions commented on Jul 25, 2025

    @github-actions
    github-actionsBot
    on Jul 25, 2025 – with GitHub Actions
    Contributor

    🟢 The following checks passed:

    • Installation: successfully installed
    • Package JSON: homepage exists
    • Package JSON: bugs.url exists and seems a valid URL
    • Package JSON: keywords exist and contain 'homebridge-plugin'
    • Package JSON: engines.node property is compatible with Node 20
    • Package JSON: engines.node property is compatible with Node 22
    • Package JSON: engines.homebridge property is compatible with Homebridge 1.11.0
    • Package JSON: initializer function found
    • GitHub Repo: repository is public
    • GitHub Repo: repository is not archived
    • GitHub Repo: issues are enabled
    • GitHub Repo: contains releases
    • NPM Package: has not been deprecated
    • Config Schema JSON: exists and is valid JSON
    • Config Schema JSON: contains a valid pluginAlias
    • Config Schema JSON: the pluginType is set to 'platform'
    • Config Schema JSON: contains a name schema property
    • Dependencies: homebridge was not installed as a dependency
    • Dependencies: hap-nodejs was not installed as a dependency

    🎉 All checks passed successfully, nice work! Your plugin and/or icon will now be manually reviewed by the Homebridge team.

    These checks were run against v4.2.6 of the plugin.

  22. bwp91
    added a commit that references this issue on Jul 26, 2025

    verify: homebridge-texecom-full

    8a82187
  23. bwp91
    added
    verifieduse when a plugin meets the criteria - adds the verified badge text
    and removed
    pendingthe label given to a new verification/icon request
    on Jul 26, 2025

  24. github-actions commented on Jul 26, 2025

    @github-actions
    github-actionsBot
    on Jul 26, 2025 – with GitHub Actions
    Contributor

    Congratulations! Your plugin has been verified!

    You can now add one of the Verified by Homebridge badges to your plugin's README:

    verified-by-homebridge

    [![verified-by-homebridge](https://badgen.net/badge/homebridge/verified/purple)](https://github.com/homebridge/homebridge/wiki/Verified-Plugins)

    verified-by-homebridge

    [![verified-by-homebridge](https://img.shields.io/badge/homebridge-verified-blueviolet?color=%23491F59&style=for-the-badge&logoColor=%23FFFFFF&logo=homebridge)](https://github.com/homebridge/homebridge/wiki/Verified-Plugins)

    Your plugin is now also eligible to display a ❤️ Donate button on its tile in the Homebridge UI. See https://github.com/homebridge/homebridge/wiki/Donation-Links for instructions.

    Interested in getting a @homebridge-plugins/ scope for your plugin? See our Homebridge Scoped Plugins program.

    If for any reason in the future you can no longer maintain your plugin, please consider transferring it to our Homebridge Plugins organization.

    Don't forget to join the official Homebridge Discord server, where plugin developers can get tips and advice from other developers and the Homebridge project team in the #plugin-development channel!

    As a verified plugin, you can request a channel in the Discord server to discuss your plugin with users and other developers. Just ask in the #plugin-development channel.

    Thank you for your contribution to the Homebridge community.

    • The Homebridge Team
  25. bwp91
    closed this as completedon Jul 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    request-verificationverifieduse when a plugin meets the criteria - adds the verified badge text

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions