Skip to content

Verification Request: homebridge-iaqualink-matter #1155

Closed
Closed
Verification Request: homebridge-iaqualink-matter#1155
Labels
request-verificationverifieduse when a plugin meets the criteria - adds the verified badge text

Description

@dean1d
dean1d
opened on Aug 4, 2026

Plugin Name

homebridge-iaqualink-matter

Link To GitHub Repo

https://github.com/dean1d/homebridge-iaqualink-matter

Plugin Icon (Optional)

Image

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

Hi I was working on the plugin for a bit since there was no iaqualink plugin. Then I went to publish it and someone created one 2 months ago that I did not know about. The main difference is mine supports Matter, so I can add it to Alexa as well. Also mine handles a Heat Pump/Pool chiller which theirs does not.

Activity

  1. dean1d
    added
    pendingthe label given to a new verification/icon request
    request-verification
    on Aug 4, 2026

  2. github-actions commented on Aug 4, 2026

    @github-actions
    github-actionsBot
    on Aug 4, 2026 – with GitHub Actions
    Contributor

    🔴 Failed Checks

    • Config Schema JSON: schema is invalid - required should not be a boolean property on individual fields. In JSON Schema, required must be an array at the object level listing required property names. Remove "required": true/false from individual properties and use "required": ["property1", "property2"] at the object level instead.
    • GitHub Repo: should contain releases

    🟢 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: keywords declare the supported transports ('supports-hap' and/or 'supports-matter')
    • 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 22
    • Package JSON: engines.node property is compatible with Node 24
    • Package JSON: engines.homebridge property is compatible with Homebridge 2.2.1
    • Package JSON: initializer function found
    • NPM Package: has not been deprecated
    • GitHub Repo: version in package.json (v0.1.2) matches NPM version (v0.1.2)
    • Config Schema JSON: exists and is valid JSON
    • Config Schema JSON: contains a valid pluginAlias
    • Config Schema JSON: pluginAlias matches the platform/accessory registered in code
    • Config Schema JSON: the pluginType is set to 'platform'
    • Config Schema JSON: contains a name schema property
    • Dependencies: homebridge is not declared as a runtime/peer/bundled dependency
    • Dependencies: hap-nodejs is not declared as a runtime/peer/bundled dependency
    • Security: no known vulnerabilities in dependencies
    • Security: code patterns flagged for manual review
    • Security: no privilege escalation attempts detected
    • GitHub Repo: repository is public
    • GitHub Repo: repository is not archived
    • GitHub Repo: issues are enabled

    🔍 For Manual Review

    The following items were detected and require manual review. We understand that these items may be false positives.

    • Security: uses dynamic require() which could load arbitrary code found in 1 file

    ℹ️ Check Details

    • These checks were run against v0.1.2 of the plugin.
    • Link to the run workflow: visit →.

    📋 Next Steps

    • Once you have fixed these failures, comment /check on this issue to run the checks again — your request will not move forward until the checks are re-run.
    • 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.
  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 Aug 4, 2026

  4. dean1d commented on Aug 4, 2026

    @dean1d
    dean1d
    on Aug 4, 2026
    Author

    Both failed checks have been addressed:

    • Corrected config.schema.json to use an object-level required array.
    • Published npm version and GitHub Release v0.1.3.

    Release: https://github.com/dean1d/homebridge-iAqualink-Matter/releases/tag/v0.1.3

  5. dean1d commented on Aug 4, 2026

    @dean1d
    dean1d
    on Aug 4, 2026
    Author

    /check

  6. 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 Aug 4, 2026

  7. github-actions commented on Aug 4, 2026

    @github-actions
    github-actionsBot
    on Aug 4, 2026 – with GitHub Actions
    Contributor

    🟢 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: keywords declare the supported transports ('supports-hap' and/or 'supports-matter')
    • 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 22
    • Package JSON: engines.node property is compatible with Node 24
    • Package JSON: engines.homebridge property is compatible with Homebridge 2.2.1
    • Package JSON: initializer function found
    • NPM Package: has not been deprecated
    • GitHub Repo: version in package.json (v0.1.3) matches NPM version (v0.1.3)
    • 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: pluginAlias matches the platform/accessory registered in code
    • Config Schema JSON: the pluginType is set to 'platform'
    • Config Schema JSON: contains a name schema property
    • Dependencies: homebridge is not declared as a runtime/peer/bundled dependency
    • Dependencies: hap-nodejs is not declared as a runtime/peer/bundled dependency
    • Security: no known vulnerabilities in dependencies
    • Security: code patterns flagged for manual review
    • 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
    • Runtime: plugin shuts down cleanly within 12s of SIGTERM
    • Runtime: plugin restarts cleanly without port conflicts
    • GitHub Repo: repository is public
    • GitHub Repo: repository is not archived
    • GitHub Repo: issues are enabled
    • GitHub Repo: contains releases

    🔍 For Manual Review

    The following items were detected and require manual review. We understand that these items may be false positives.

    • Security: uses dynamic require() which could load arbitrary code found in 1 file

    ℹ️ Check Details

    • These checks were run against v0.1.3 of the plugin.
    • Link to the run workflow: visit →.
    • External HTTP requests detected:
      • 📡 https://prod.zodiac-io.com/users/v1/login
        Methods: POST | Count: 8 | Scenarios: full config, minimal required, network resilience, platform only

    📋 Next Steps

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

  8. github-actions
    added
    awaiting-final-review
    and removed
    pendingthe label given to a new verification/icon request
    on Aug 4, 2026
  9. bwp91
    added a commit that references this issue on Aug 4, 2026

    verify: homebridge-iaqualink-matter

    6c8bf83
  10. bwp91
    added
    verifieduse when a plugin meets the criteria - adds the verified badge text
    on Aug 4, 2026

  11. github-actions commented on Aug 4, 2026

    @github-actions
    github-actionsBot
    on Aug 4, 2026 – 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://img.shields.io/badge/_-verified-blueviolet?color=%23491F59&style=flat&logoColor=%23FFFFFF&logo=homebridge)](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=flat)](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. github-actions
    removed
    awaiting-final-review
    on Aug 4, 2026

  13. bwp91 commented on Aug 4, 2026

    @bwp91
    bwp91
    on Aug 4, 2026
    Contributor

    Hi @dean1d,

    Thanks for this, and for turning the two failing checks around so quickly.

    You were right to flag the overlap with homebridge-iaqualink in your request — you both talk to the same iAquaLink cloud API, so I did look at it closely. What decided it is that neither plugin is a superset of the other: yours handles the heat pump / chiller with a proper cooling mode, and registers Matter accessories so the equipment can reach Alexa and Google. Neither of those is covered elsewhere, and a chiller is not a small gap.

    Two things I noticed while reading through, both meant as praise rather than requests:

    • redact.ts stripping bearer tokens, JWTs and email addresses out of diagnostics is a nice touch, and rarer than it should be.
    • You have the Matter thermostat feature-gating right (Thermostat.with('Heating') / .with('Cooling')). That one catches people out — get it wrong and the cluster goes missing silently, with no error to tell you why.

    One small ask: there is a GitHub release for v0.1.3, but not for 0.1.1 or 0.1.2. Could you create one for each version going forward, with release notes? They are shown in the Homebridge UI when someone updates, so they are the main way users find out what has changed.

    The plugin is now verified, and I have added it to the Matter Plugins wiki page as well. Thanks for contributing to Homebridge!

  14. bwp91
    closed this as completedon Aug 4, 2026

  15. dean1d commented on Aug 9, 2026

    @dean1d
    dean1d
    on Aug 9, 2026
    Author

    Thank you I really appreciate it. Ill start doing the Git releases like you said. I also added the verified badge.

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