Verification Request: homebridge-tuya-plus

[adrianjagielak]

Plugin Name

homebridge-tuya-plus

Link To GitHub Repo

https://github.com/adrianjagielak/homebridge-tuya-plus

Plugin Icon (Optional)

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

The homebridge-tuya-plus plugin is a community-maintained continuation of the original, popular but abandoned homebridge-tuya plugin, addding Homebridge 2.0 support, new Tuya protocols and devices, and more.

Compared to the other verified Tuya plugins, it uses LAN-only offline communication with Tuya devices on the network, as opposed to Tuya’s cloud/WAN communication.

For comparison, the currently verified Tuya plugins include:

Legend

✅ - Verified and actively maintained
❌ - Verified but abandoned
⬜ - Unverified plugin

• ❌ homebridge-tuya-platform - the official Tuya Homebridge plugin. It uses Tuya’s cloud/WAN API and appears to be abandoned, with last activity around 3 years ago.

  • ✅ homebridge-tuya-platform-talrhvfork - an actively maintained fork of homebridge-tuya-platform.

  • ✅ @0x5e/homebridge-tuya-platform - an actively maintained fork of homebridge-tuya-platform.

    • ✅ @homebridge-plugins/homebridge-tuya - an actively maintained fork of @0x5e/homebridge-tuya-platform with some fixes.

• ❌ @milo526/homebridge-tuya-web - a plugin that uses Tuya’s web API. Apart from dependency upgrades, it appears to be abandoned, with last real activity around 2 years ago.

• ❌ homebridge-tuya - the original popular LAN-based Tuya plugin, which appears to be abandoned, with last activity around 2 years ago.

  • ⬜ homebridge-tuya-plus - an actively maintained fork of homebridge-tuya . This is the plugin I'm requesting to verify.

[github-actions]

🔴 Failed Checks

• Config Schema JSON: schema is invalid - required should not be a boolean property on individual fields. In JSON Schema, required must be an array at the object level listing required property names. Remove "required": true/false from individual properties and use "required": ["property1", "property2"] at the object level instead.
• Config Schema JSON: does not contain a name schema property

🟢 Passed Checks

• 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: 'preinstall' in scripts is not present
• 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 22
• Package JSON: engines.node property is compatible with Node 24
• Package JSON: engines.homebridge property is compatible with Homebridge 2.0.1
• Package JSON: initializer function found
• NPM Package: has not been deprecated
• GitHub Repo: version in package.json (v3.5.2) matches NPM version (v3.5.2)
• Config Schema JSON: exists and is valid JSON
• Config Schema JSON: contains a valid pluginAlias
• Config Schema JSON: the pluginType is set to 'platform'
• Dependencies: homebridge was not installed as a dependency
• Dependencies: hap-nodejs was not installed as a dependency
• Security: no known vulnerabilities in dependencies
• Security: code patterns flagged for manual review
• Security: no privilege escalation attempts detected
• GitHub Repo: repository is public
• GitHub Repo: repository is not archived
• GitHub Repo: issues are enabled
• GitHub Repo: contains releases

ℹ️ Check Details

• These checks were run against v3.5.2 of the plugin.
• Link to the run workflow: visit →.

📋 Next Steps

• Please action these failures and then comment /check to run the checks again.
• If updating your package.json and config.schema.json files, don't forget to publish a new version to NPM.
• Remember this is an automatic script: if you think something has been marked as a failure in error, let us know with a reply.
• Feel free to ask any questions you have by replying to this issue.

[adrianjagielak]

/check

[github-actions]

🔴 Failed Checks

• Security: Runtime - suspicious file/command access detected in scenario "no config": ip -o link show, ip -o link show
• Security: Runtime - suspicious file/command access detected in scenario "platform only": ip -o link show, ip -o link show
• Security: Runtime - suspicious file/command access detected in scenario "full config": ip -o link show, ip -o link show

🟢 Passed Checks

• 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: 'preinstall' in scripts is not present
• 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 22
• Package JSON: engines.node property is compatible with Node 24
• Package JSON: engines.homebridge property is compatible with Homebridge 2.0.1
• Package JSON: initializer function found
• NPM Package: has not been deprecated
• GitHub Repo: version in package.json (v3.5.3) matches NPM version (v3.5.3)
• Config Schema JSON: exists and is valid JSON
• Config Schema JSON: contains valid JSON Schema
• Config Schema JSON: schema has valid type property
• Config Schema JSON: schema has valid properties for object type
• 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
• Security: no known vulnerabilities in dependencies
• Security: code patterns flagged for manual review
• Security: no privilege escalation attempts detected
• Runtime: homebridge installed successfully
• Runtime: no config - homebridge should start without plugin configuration and plugin should not load
• Runtime: platform only - plugin should start with just platform property
• Runtime: full config - plugin should start with comprehensive configuration
• GitHub Repo: repository is public
• GitHub Repo: repository is not archived
• GitHub Repo: issues are enabled
• GitHub Repo: contains releases

ℹ️ Check Details

• These checks were run against v3.5.3 of the plugin.
• Link to the run workflow: visit →.

📋 Next Steps

• Please action these failures and then comment /check to run the checks again.
• If updating your package.json and config.schema.json files, don't forget to publish a new version to NPM.
• Remember this is an automatic script: if you think something has been marked as a failure in error, let us know with a reply.
• Feel free to ask any questions you have by replying to this issue.

[adrianjagielak]

ip -o link show comes from the @homebridge/ciao lib I think

[adrianjagielak]

/check