Verification Request: homebridge-tuya-smartlife

Plugin Name

homebridge-tuya-smartlife

Link To GitHub Repo

https://github.com/supagroova/homebridge-tuya-smartlife

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

homebridge-tuya-smartlife brings Tuya / Smart Life devices into HomeKit through
device-sharing QR login flow. The plugin's core value is that users can connect their existing Smart
Life account without creating a Tuya developer account or maintaining a 6-month IoT Core trial.

Supported v1 device types:

• Switches and outlets, including multi-gang / multi-socket devices.
• Temperature and humidity sensors.
• Contact, motion, leak, and smoke sensors.
• Basic thermostat support.

Security and privacy notes:

• The browser UI does not receive or store Tuya access or refresh tokens.
• Tokens are persisted under the Homebridge storage directory.
• Default logs do not include Smart Life user codes, QR tokens, access tokens,
  encrypted payloads, or request signatures.
• Debug diagnostics are gated by the plugin debug setting and are redacted.
• The plugin contains no analytics or tracking.

Verification evidence:

• npm package: https://www.npmjs.com/package/homebridge-tuya-smartlife
• GitHub repository: https://github.com/supagroova/homebridge-tuya-smartlife
• GitHub Release: https://github.com/supagroova/homebridge-tuya-smartlife/releases/tag/v1.0.0

Review the verification checklist in this issue first, then inspect the linked GitHub repository, npm package, and v1.0.0 release. Check the submitted installation, configuration, privacy, storage, logging, and error-handling claims against the evidence available there. Done means the checklist is verified or specific missing requirements are identified for the requester.