Verification Request: homebridge-dummy-cmd-switch

[YPyltiai]

Plugin Name

homebridge-dummy-cmd-switch

Link To GitHub Repo

https://github.com/YPyltiai/homebridge-dummy-cmd-switch

Plugin Icon (Optional)

No response

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

There are a few dummy switch plugins but none of them allow running CMD commands on click. The CMD command plugins are no longer maintained either and commonly offer regular on/off switches, which don't make sense either for the use case.

This plugin merges the idea of having dummy momentary switch with being able to run CMD commands on click and is very lightweight to solve just that specific use case.

Technically parts of the functionality are available elsewhere but I couldn't find plugin that solves this use case end-to-end, so built a small new one.

Thanks!

[github-actions]

🔴 The following checks failed:

• Package JSON: more keywords apart from 'homebridge-plugin' should exist
• Config Schema JSON: the pluginType is not set to 'platform'

---

🟢 The following checks passed:

• Installation: successfully installed
• Package JSON: homepage exists
• Package JSON: bugs.url exists and seems a valid URL
• 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: 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 v0.1.0 of the plugin.

[YPyltiai]

/check

[github-actions]

🔴 The following checks failed:

• Package JSON: more keywords apart from 'homebridge-plugin' should exist
• Config Schema JSON: the pluginType is not set to 'platform'

---

🟢 The following checks passed:

• Installation: successfully installed
• Package JSON: homepage exists
• Package JSON: bugs.url exists and seems a valid URL
• 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: 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 v0.1.0 of the plugin.

[YPyltiai]

Added keywords https://github.com/YPyltiai/homebridge-dummy-cmd-switch/blob/main/package.json#L6 but didn't want to re-publish just for those alone.

Is it 100% required to be "Platform"? Given the narrow use case - wanted to keep it lightweight, so it has less configs and setup complexity. I don't expect it to grow way beyond the original use case explained in first comment.