Skip to content

Verification Request: homebridge-leridian-dynamics #802

New issue
New issue
Closed
Closed
Verification Request: homebridge-leridian-dynamics#802
Labels
request-verificationverifieduse when a plugin meets the criteria - adds the verified badge text

Description

@agilisone
agilisone
opened on Feb 21, 2025

Plugin Name

homebridge-leridian-dynamics

Link To GitHub Repo

https://github.com/agilisone/homebridge-leridian-dynamics

Plugin Icon (Optional)

Hello, this is my first homebridge plugin that I have done. My plugin is based on the homebridge-plugin-template. This plugin both sends and receives http requests to/from a device on the local network.

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

Cheers!

Activity

  1. agilisone
    added
    pendingthe label given to a new verification/icon request
    request-verification
    on Feb 21, 2025

  2. github-actions commented on Feb 21, 2025

    @github-actions
    github-actionsBot
    on Feb 21, 2025 – with GitHub Actions
    Contributor

    🔴 The following checks failed:

    • Package JSON: more keywords apart from 'homebridge-plugin' should exist
    • GitHub Repo: should have issues enabled
    • GitHub Repo: should contain releases
    • Config Schema JSON: does not contain a name schema property

    🟢 The following checks passed:

    • Installation: successfully installed
    • Package JSON: homepage exists
    • Package JSON: bugs.url exists and seems a valid URL
    • 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 18
    • 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.9.0
    • Package JSON: initializer function found
    • GitHub Repo: repository is public
    • GitHub Repo: repository is not archived
    • 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'
    • 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 Feb 21, 2025

  4. agilisone commented on Feb 24, 2025

    @agilisone
    agilisone
    on Feb 24, 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 Feb 24, 2025

  6. github-actions commented on Feb 24, 2025

    @github-actions
    github-actionsBot
    on Feb 24, 2025 – with GitHub Actions
    Contributor

    🔴 The following checks failed:

    • Installation: failed to install [1]
    • Failed to install

    ⚠️ 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.

  7. 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 Feb 24, 2025

  8. agilisone commented on Mar 4, 2025

    @agilisone
    agilisone
    on Mar 4, 2025
    Author

    /check

  9. 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 Mar 4, 2025

  10. github-actions commented on Mar 4, 2025

    @github-actions
    github-actionsBot
    on Mar 4, 2025 – with GitHub Actions
    Contributor

    🔴 The following checks failed:

    • Config Schema JSON: does not contain a name schema property

    🟢 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 18
    • 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.9.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'
    • 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.1 of the plugin.

  11. 22 remaining items

  12. agilisone commented on Mar 25, 2025

    @agilisone
    agilisone
    on Mar 25, 2025
    Author

    That’s an excellent idea! I moved all my validation into a function() but it was not located outside that event. I will make that change as soon as I get home from work.

  13. agilisone commented on Mar 26, 2025

    @agilisone
    agilisone
    on Mar 26, 2025
    Author

    /check

  14. 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 Mar 26, 2025

  15. github-actions commented on Mar 26, 2025

    @github-actions
    github-actionsBot
    on Mar 26, 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.9.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.1.2 of the plugin.

  16. bwp91
    added
    currently-reviewinguse for starting a review - adds a comment with the verification list with empty checkboxes
    and removed
    pendingthe label given to a new verification/icon request
    on Mar 26, 2025

  17. github-actions commented on Mar 26, 2025

    @github-actions
    github-actionsBot
    on Mar 26, 2025 – with GitHub Actions
    Contributor
    • General
      • The plugin must be of type dynamic platform.
      • The plugin must not offer the same nor less functionality than that of any existing verified plugin.
    • Repo
      • The plugin must be published to NPM and the source code available on a GitHub repository, with issues enabled.
      • A GitHub release should be created for every new version of your plugin, with release notes.
    • Environment
      • The plugin must run on all supported LTS versions of Node.js, at the time of writing this is Node v20 and v22.
      • The plugin must successfully install and not start unless it is configured.
      • The plugin must not execute post-install scripts that modify the users' system in any way.
      • The plugin must not require the user to run Homebridge in a TTY or with non-standard startup parameters, even for initial configuration.
    • Codebase
      • The plugin must implement the Homebridge Plugin Settings GUI.
      • The plugin must not contain any analytics or calls that enable you to track the user.
      • If the plugin needs to write files to disk (cache, keys, etc.), it must store them inside the Homebridge storage directory.
      • The plugin must not throw unhandled exceptions, the plugin must catch and log its own errors.
  18. bwp91
    added a commit that references this issue on Mar 26, 2025

    verify: homebridge-leridian-dynamics

    ed4a2da
  19. bwp91
    added
    verifieduse when a plugin meets the criteria - adds the verified badge text
    and removed
    currently-reviewinguse for starting a review - adds a comment with the verification list with empty checkboxes
    on Mar 26, 2025

  20. github-actions commented on Mar 26, 2025

    @github-actions
    github-actionsBot
    on Mar 26, 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.

    If for any reason in the future you can no longer maintain your plugin, please consider transferring it to our Homebridge Plugins organization. We can take ownership until another willing developer comes along.

    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

  21. bwp91 commented on Mar 26, 2025

    @bwp91
    bwp91
    on Mar 26, 2025
    Contributor

    thanks for making those changes!

  22. bwp91
    closed this as completedon Mar 26, 2025

  23. agilisone commented on Mar 27, 2025

    @agilisone
    agilisone
    on Mar 27, 2025
    Author

    Thank you very much for your assistance, your patience, and your excellent suggestions!

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