Verification Request: homebridge-ring-smoke-detectors

[simplytoast1]

Plugin Name

homebridge-ring-smoke-detectors

Link To GitHub Repo

https://github.com/simplytoast1/Ring-Smoke-Detectors

Plugin Icon (Optional)

https://notifyicons.pingie.com/icons/mmzbbg7l-9n7299p8.png

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

🟠 No (please explain in the more information box at the end)

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

This plugin exposes Kidde/Ring smart smoke and CO detectors (hubless WiFi models) to HomeKit via Homebridge. These devices are not supported by the existing verified homebridge-ring plugin because they require a direct WebSocket connection that bypasses the Ring hub requirement.

The plugin includes a custom settings UI for Ring authentication (email/password/2FA) and device management (rename, show/hide per device).

[github-actions]

🔴 Failed Checks

• Dependencies: homebridge was installed as a dependency
• Dependencies: hap-nodejs was installed as a dependency

🟢 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 20
• 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 1.11.2
• Package JSON: initializer function found
• NPM Package: has not been deprecated
• GitHub Repo: version in package.json (v1.2.1) matches NPM version (v1.2.1)
• 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
• Security: no known vulnerabilities in dependencies
• Security: no unsafe code patterns detected
• 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 v1.2.1 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.

[simplytoast1]

Updated to v1.2.2 — removed peerDependencies that was causing homebridge and hap-nodejs to be installed as plugin dependencies.

[simplytoast1]

/check

[github-actions]

🟢 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 20
• 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 1.11.2
• Package JSON: initializer function found
• NPM Package: has not been deprecated
• GitHub Repo: version in package.json (v1.2.2) matches NPM version (v1.2.2)
• 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: no unsafe code patterns detected
• 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: minimal required - plugin should start with minimal required configuration
• Runtime: full config - plugin should start with comprehensive configuration
• Runtime: network resilience - plugin should handle network failures without crashing
• 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 v1.2.2 of the plugin.
• Link to the run workflow: visit →.
• External HTTP requests detected:
  • 📡 https://oauth.ring.com/oauth/token
    Methods: POST | Count: 8 | Scenarios: full config, minimal required, network resilience

📋 Next Steps

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

[dgreif]

@simplytoast1 there has been a lot of progress on dgreif/ring#1674. I'd be happy to see support for these devices land in the main homebridge-ring plugin, rather than spinning it out into a separate plugin. I likely won't have time to implement it myself in the near future (and I don't own the devices), but I'd be happy to take a PR. It sounds like @tsightler is getting close to a good implementation over on the other issue.

Regarding the verified plugin request, I don't believe this is the right course of action. We generally try to keep a single plugin per platform when possible, and this splits support for Ring into a second plugin. Let's instead work together to make homebridge-ring support these devices 🙏

[simplytoast1]

For sure.. My thinking was the Ring plugin can't possibly support every "works with Ring" product out there and wanted to support a speciality subset of devices but I really want to be a good citizen and hear what you are saying!