verified Verification Request: homebridge-texecom-full

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

Oct 09 '24 06:10 K1LL3R234

🔴 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.

Oct 09 '24 06:10 github-actions[bot]

/check

Oct 09 '24 08:10 K1LL3R234

🟢 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.

Oct 09 '24 08:10 github-actions[bot]

/check

Dec 29 '24 13:12 bwp91

🔴 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.

Dec 29 '24 13:12 github-actions[bot]

@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!

Dec 29 '24 13:12 bwp91

I fixed it

Jan 03 '25 18:01 K1LL3R234

/check

Jan 03 '25 18:01 K1LL3R234

🟢 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.node property is compatible with Node 22
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

🎉 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.5 of the plugin.

Jan 03 '25 18:01 github-actions[bot]

/check

Jul 19 '25 14:07 bwp91

🟢 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.5 of the plugin.

Jul 19 '25 14:07 github-actions[bot]

Hi @K1LL3R234 I noticed that there is already a verified plugin - https://github.com/garethflowers/homebridge-texecom-connect - I wondered how your plugin is different from this? Is it a different Texecom product? thanks!

Jul 19 '25 14:07 bwp91

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

Jul 19 '25 17:07 K1LL3R234

@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...

Jul 19 '25 18:07 bwp91

Please /check again

Jul 25 '25 07:07 K1LL3R234

/check

Jul 25 '25 07:07 K1LL3R234

🟢 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.

Jul 25 '25 07:07 github-actions[bot]

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](https://badgen.net/badge/homebridge/verified/purple)](https://github.com/homebridge/homebridge/wiki/Verified-Plugins)

[![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 :heart: 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

Jul 26 '25 16:07 github-actions[bot]