Skip to content

Verification Request: homebridge-jci-hitachi-platform #678

Closed
Closed
Verification Request: homebridge-jci-hitachi-platform#678
Labels
request-verificationverifieduse when a plugin meets the criteria - adds the verified badge text

Description

@tasict
tasict
opened on Jan 9, 2024

Plugin Name

homebridge-jci-hitachi-platform

Link To GitHub Repo

https://github.com/tasict/homebridge-jci-hitachi-platform

Link To NPM Package

https://www.npmjs.com/package/homebridge-jci-hitachi-platform

Plugin Icon (Optional)

No response

Activity

  1. tasict
    added
    pendingthe label given to a new verification/icon request
    on Jan 9, 2024

  2. github-actions commented on Jan 9, 2024

    @github-actions
    github-actionsBot
    on Jan 9, 2024 – with GitHub Actions
    Contributor

    ✅ Pre-checks completed successfully.

  3. bwp91 commented on Feb 11, 2024

    @bwp91
    bwp91
    on Feb 11, 2024
    Contributor

    This plugin is also showing the homebridge verified badge on the readme when it is not verified yet

  4. bwp91
    added
    awaiting-user-replyuse after review has started - awaiting user to reply to a comment
    and removed
    pendingthe label given to a new verification/icon request
    on Feb 11, 2024

  5. tasict commented on Feb 11, 2024

    @tasict
    tasict
    on Feb 11, 2024
    Author

    Ok,I will remove it and update.

  6. tasict commented on Feb 13, 2024

    @tasict
    tasict
    on Feb 13, 2024
    Author

    @bwp91 Hi, I have modified the code and documentation. Please assist in reviewing the latest version. Thank you.

  7. github-actions commented on Mar 14, 2024

    @github-actions
    github-actionsBot
    on Mar 14, 2024 – with GitHub Actions
    Contributor

    This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

  8. github-actions
    added
    staleused for stale issues
    on Mar 14, 2024

  9. tasict commented on Mar 14, 2024

    @tasict
    tasict
    on Mar 14, 2024
    Author

    @bwp91 Any update?

  10. github-actions
    removed
    staleused for stale issues
    on Mar 15, 2024
  11. bwp91
    added
    currently-reviewinguse for starting a review - adds a comment with the verification list with empty checkboxes
    and removed
    awaiting-user-replyuse after review has started - awaiting user to reply to a comment
    on Mar 16, 2024

  12. github-actions commented on Mar 16, 2024

    @github-actions
    github-actionsBot
    on Mar 16, 2024 – 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 v18 and v20.
      • 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.

    Comment /check to run checks again.

  13. bwp91 commented on Mar 16, 2024

    @bwp91
    bwp91
    on Mar 16, 2024
    Contributor

    Hi @tasict

    I just installed the plugin but have not yet configured it. When I restart Homebridge I get this in the logs (although it does not seem to affect my homebridge).

    [16/03/2024, 18:22:57] ====================
[16/03/2024, 18:22:57] ERROR LOADING PLUGIN homebridge-jci-hitachi-platform:
[16/03/2024, 18:22:57] Error: AWS CRT binary not present in any of the following locations:
        /usr/local/lib/node_modules/homebridge-jci-hitachi-platform/node_modules/aws-crt/dist/bin/linux-arm-glibc/aws-crt-nodejs.node
    at Object.<anonymous> (/usr/local/lib/node_modules/homebridge-jci-hitachi-platform/node_modules/aws-crt/lib/native/binding.js:88:11)
    at Module._compile (node:internal/modules/cjs/loader:1376:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1435:10)
    at Module.load (node:internal/modules/cjs/loader:1207:32)
    at Function.Module._load (node:internal/modules/cjs/loader:1023:12)
    at Module.require (node:internal/modules/cjs/loader:1235:19)
    at require (node:internal/modules/helpers:176:18)
    at Object.<anonymous> (/usr/local/lib/node_modules/homebridge-jci-hitachi-platform/node_modules/aws-crt/lib/native/auth.ts:15:1)
    at Module._compile (node:internal/modules/cjs/loader:1376:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1435:10)
[16/03/2024, 18:22:57] ====================

    I noticed that the installation took a long time and seems to download a load of extra stuff (which is not necessarily an issue by itself).

    I assume all this is from the aws-iot-device-sdk-v2 dependency.

    In my Govee plugin I use aws-iot-device-sdk and tried the -v2 but reverted back due to all the extra stuff that happened during installation. Do you need to use the v2 with your plugin or would it be possible/easy to change to using the original aws-iot-device-sdk?

  14. 50 remaining items

  15. github-actions commented on Apr 11, 2025

    @github-actions
    github-actionsBot
    on Apr 11, 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.2.7 of the plugin.

  16. bwp91 commented on Jul 19, 2025

    @bwp91
    bwp91
    on Jul 19, 2025
    Contributor

    /check

  17. github-actions commented on Jul 19, 2025

    @github-actions
    github-actionsBot
    on Jul 19, 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.2.7 of the plugin.

  18. bwp91
    added
    currently-reviewinguse for starting a review - adds a comment with the verification list with empty checkboxes
    on Jul 19, 2025

  19. github-actions commented on Jul 19, 2025

    @github-actions
    github-actionsBot
    on Jul 19, 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.
  20. bwp91
    added a commit that references this issue on Jul 19, 2025

    verify: homebridge-jci-hitachi-platform

    e7ab231
  21. 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
    currently-reviewinguse for starting a review - adds a comment with the verification list with empty checkboxes
    on Jul 19, 2025

  22. github-actions commented on Jul 19, 2025

    @github-actions
    github-actionsBot
    on Jul 19, 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

  23. bwp91 commented on Jul 19, 2025

    @bwp91
    bwp91
    on Jul 19, 2025
    Contributor

    Hi @tasict really am sorry this has taken so long 😵

  24. bwp91
    closed this as completedon Jul 19, 2025
  25. bwp91
    added a commit that references this issue on Jul 19, 2025

    verify: homebridge-jci-hitachi-platform

    3fdf59d

  26. MarijoVidovic commented on Nov 23, 2025

    @MarijoVidovic
    MarijoVidovic
    on Nov 23, 2025

    Really disappointed that at least update to readme or name did not happen and many users will waste time testing thing plugin

  27. tasict commented on Nov 23, 2025

    @tasict
    tasict
    on Nov 23, 2025
    Author

    Really disappointed that at least update to readme or name did not happen and many users will waste time testing thing plugin

    In fact, many users are using this plugin without any issues. The official firmware hasn't been updated either. If you are experiencing problems, please politely request it, or offer a small donation so I can investigate the issue within my limited timeframe.

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