Skip to content

Verification Request: homebridge-easy-mqtt #851

New issue
New issue
Closed
Closed
Verification Request: homebridge-easy-mqtt#851
Labels
request-verificationverifieduse when a plugin meets the criteria - adds the verified badge text

Description

@mpatfield
mpatfield
opened on Jul 16, 2025

Plugin Name

homebridge-easy-mqtt

Link To GitHub Repo

https://github.com/mpatfield/homebridge-easy-mqtt

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

homebridge-mqttthing and homebridge-mqtt do seem to offer similar functionality, but development has ceased and many important issues have been ignored for years.

homebridge-easy-mqtt is intended be a simple-to-use replacement that uses modern homebridge patterns and up-to-date dependencies.

I respect not wanting verified plugins that duplicate functionality, but is there a process by which plugins are "de-verified" after an extended period of inactivity to make way for more up-to-date variants? It seems like having a plugin marked as verified that is many years old and uses dependencies that are error-prone and possibly even security risks is not great.

No hard feelings if you reject my request to verify homebridge-easy-mqtt. I just wanted to at least start a conversation about the verification process.

Thanks!

Activity

  1. mpatfield
    added
    pendingthe label given to a new verification/icon request
    request-verification
    on Jul 16, 2025

  2. github-actions commented on Jul 16, 2025

    @github-actions
    github-actionsBot
    on Jul 16, 2025 – with GitHub Actions
    Contributor

    🔴 The following checks failed:

    • GitHub Repo: should contain releases

    🟢 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: '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.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
    • 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 v1.0.0 of the plugin.

  3. github-actions
    added
    awaiting-changesuse after review has started - awaiting user to make changes to plugin
    and removed
    pendingthe label given to a new verification/icon request
    on Jul 16, 2025

  4. mpatfield commented on Jul 16, 2025

    @mpatfield
    mpatfield
    on Jul 16, 2025
    Author

    /check

  5. github-actions
    added
    pendingthe label given to a new verification/icon request
    and removed
    awaiting-changesuse after review has started - awaiting user to make changes to plugin
    on Jul 16, 2025

  6. github-actions commented on Jul 16, 2025

    @github-actions
    github-actionsBot
    on Jul 16, 2025 – with GitHub Actions
    Contributor

    🟢 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: '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.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 v1.0.0 of the plugin.

  7. bwp91 commented on Aug 30, 2025

    @bwp91
    bwp91
    on Aug 30, 2025
    Contributor

    /check

  8. github-actions commented on Aug 30, 2025

    @github-actions
    github-actionsBot
    on Aug 30, 2025 – with GitHub Actions
    Contributor

    🟢 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: '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.homebridge property is compatible with Homebridge 1.11.0
    • 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
    • Runtime: homebridge installed successfully
    • Runtime: no config - homebridge should start without plugin configuration
    • 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

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

  9. bwp91
    added a commit that references this issue on Aug 30, 2025

    verify: homebridge-easy-mqtt

    d372004
  10. bwp91
    added
    verifieduse when a plugin meets the criteria - adds the verified badge text
    and removed
    pendingthe label given to a new verification/icon request
    on Aug 30, 2025

  11. github-actions commented on Aug 30, 2025

    @github-actions
    github-actionsBot
    on Aug 30, 2025 – with GitHub Actions
    Contributor

    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

    [![verified-by-homebridge](https://badgen.net/badge/homebridge/verified/purple)](https://github.com/homebridge/homebridge/wiki/Verified-Plugins)

    verified-by-homebridge

    [![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 ❤️ 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

  12. bwp91 commented on Aug 30, 2025

    @bwp91
    bwp91
    on Aug 30, 2025
    Contributor

    sorry this took so long @mpatfield

  13. bwp91
    closed this as completedon Aug 30, 2025

  14. mpatfield commented on Sep 1, 2025

    @mpatfield
    mpatfield
    on Sep 1, 2025
    Author

    @bwp91 no problem at all! I appreciate you accepting my request.

    What are your thoughts on this? Perhaps there is a better channel to have this discussion?

    I respect not wanting verified plugins that duplicate functionality, but is there a process by which plugins are "de-verified" after an extended period of inactivity to make way for more up-to-date variants? It seems like having a plugin marked as verified that is many years old and uses dependencies that are error-prone and possibly even security risks is not ideal.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    request-verificationverifieduse when a plugin meets the criteria - adds the verified badge text

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions