Skip to content

Verification Request: homebridge-cmdswitch3 #1287

Open

Description

@jakemike1

Plugin Name

homebridge-cmdswitch3

Link To GitHub Repo

https://github.com/jakemike1/homebridge-cmdswitch3

Plugin Icon (Optional)

cmdSwitch3 plugin icon

Download the 100×100 PNG. Original cmdSwitch3 artwork: a command prompt inside an ON switch.

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

cmdSwitch3 is a maintained Homebridge 2 dynamic-platform fork of luisiam/homebridge-cmdswitch2 for Linux and macOS. The original Apache-2.0 licence and attribution are retained.

Published release: homebridge-cmdswitch3 1.0.0 on npm, with GitHub stable release notes. npm latest points to 1.0.0, matching GitHub's package.json; the beta tag remains on 1.0.0-beta.6. Testing instructions, migration guidance and issue reporting are public.

Stable release scope: 1.0.0 promotes the tested beta.6 runtime unchanged. Command execution, switches, dimming, sequential commands, accessory identities, Settings UI assets, schema/defaults and dependency versions are identical to beta.6. The release changes only version/publishing metadata, documentation and issue-template wording.

Distinct functionality: command switches plus native Lightbulb dimmers using HB_BRIGHTNESS, restoration of the last confirmed brightness, and optional FIFO command ordering across the platform, including state reads. It also preserves cmdSwitch2's name-derived identities and configuration semantics through an explicitly managed migration; installation alone does not take over another plugin's accessories.

We compared it with verified homebridge-script2, which already offers script switches, timeouts, sequencing and shared reads. Its documented interface does not include native brightness or cmdSwitch2 identity migration. cmdSwitch3 is not a superset: script2 also offers file-watched state and optional early acknowledgement. We welcome the team's assessment of this distinction.

Local shell and SSH support: documentation and the Settings UI cover service-account SSH setup, verified host keys, non-interactive authentication, remote switches, momentary actions and dimming. With opt-in strictState: true, switch-state exit 0 means ON, exit 1 means confirmed OFF, and other exits (including SSH error 255) report an error while retaining the last confirmed state. A documented helper maps remote utility failures to error 2. SSH uses the host's existing client, service-account configuration and credentials; no credential fields or connection manager are added.

Implementation: no runtime dependencies, installation hooks, telemetry or separate UI server. The custom Settings UI and JSON schema support switches/dimmers, sequential commands and opt-in quiet logging that retains errors. Plugin-owned state stays in Homebridge accessory context. Missing configuration stays inactive; invalid configuration/cache and unexpected startup/state-publication failures stop the affected platform with sanitized diagnostics and retained cached accessories. Command deadlines, output limits, stream failures, failed writes and shutdown are regression-tested. User-configured commands run with the Homebridge service user's permissions.

Passing CI, including native Linux ARM64: all nine jobs at the 1.0.0 release commit passed before publication, covering Linux x64, native Linux ARM64 and macOS on Node 22, 24 and 26. Each job runs 78 tests, syntax/shared-validator checks, formatting and an offline packed-install/HAP check. Local macOS ARM64 build, formatting and packaged-install checks also pass.

Release and CI commit: 9e453f503ec030a06824848999ec8ee5b12ff959. The downloaded npm 1.0.0 registry archive matches the tested 16-file package byte-for-byte (SHA-256 f56fb43f6e7c7e19c385e122cb15368250b86d219964c023ad70d55ab8f18163). Byte comparisons also confirm that the runtime, UI and schema match beta.6 and dependency versions are unchanged.

Real-world use and remaining coverage: the maintainer has confirmed beta.6 installed and working in everyday Raspberry Pi switch and automation use, including local heating and hot-water command helpers. Physical dimming, sequential use across multiple installations and diverse command scripts still need broader community coverage. Native Ubuntu ARM64 CI does not establish universal Raspberry Pi or Debian compatibility. Synthetic migration tests preserve six switches' and a dimmer's HAP identities across cache restoration; they do not establish universal migration safety. This release intentionally supports Homebridge 2 only.

Verification status: the previous Homebridge automated result passed on beta.3; it is not a 1.0.0 result. The scanner's environment-access flag in command-runner.js remains for manual review and is not a confirmed vulnerability. Final Homebridge team review remains pending; publishing a stable release does not itself confer verification approval.

Activity

  1. github-actions commented on Oct 22, 2026

    @github-actions
    Contributor

    🔴 Failed Checks

    • GitHub Repo: version mismatch - NPM has v1.0.0-beta.2 but GitHub package.json has v1.0.0-beta.3

    🟢 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.4.0
    • Package JSON: initializer function found
    • NPM Package: has not been deprecated
    • 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: 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
    • 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: accesses environment files in command-runner.js

    ℹ️ Check Details

    • These checks were run against v1.0.0-beta.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.
  2. 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 Oct 22, 2026
  3. jakemike1 commented on Oct 22, 2026

    @jakemike1
    Author

    The npm distribution tags are now aligned: both latest and beta point to 1.0.0-beta.3, matching the version in GitHub's package.json. This remains a public beta and the GitHub release remains marked as a prerelease; no package contents were changed.

    The existing nine-job CI run is passing, including native Linux ARM64 on Node 22, 24 and 26.

    /check

  4. 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 Oct 22, 2026
  5. github-actions commented on Oct 22, 2026

    @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.4.0
    • Package JSON: initializer function found
    • NPM Package: has not been deprecated
    • GitHub Repo: version in package.json (v1.0.0-beta.3) matches NPM version (v1.0.0-beta.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: 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: full config - plugin should start with comprehensive configuration
    • 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: accesses environment files in command-runner.js

    ℹ️ Check Details

    • These checks were run against v1.0.0-beta.3 of the plugin.
    • Link to the run workflow: visit →.

    📋 Next Steps

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

  6. jakemike1 commented on Nov 17, 2026

    @jakemike1
    Author

    Stable 1.0.0 is now published on npm, with GitHub release notes. I have updated the submission above.

    npm latest is 1.0.0, matching GitHub's package.json; beta remains 1.0.0-beta.6. The stable release promotes the beta.6 runtime, UI, schema and dependency versions unchanged.

    All nine CI jobs at the release commit passed: 78 tests per job across Linux x64, native Linux ARM64 and macOS on Node 22, 24 and 26, plus formatting and packaged-install/HAP checks. The published npm archive matches the tested package byte-for-byte. The submission and testing guide retain the remaining coverage limitations.

    Please rerun the automated checks against 1.0.0. I understand that final manual review, including the existing scanner flag, remains pending.

    /check

  7. github-actions commented on Nov 17, 2026

    @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.5.0
    • Package JSON: initializer function found
    • NPM Package: has not been deprecated
    • GitHub Repo: version in package.json (v1.0.0) matches NPM version (v1.0.0)
    • 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: 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: full config - plugin should start with comprehensive configuration
    • 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: accesses environment files in command-runner.js

    ℹ️ Check Details

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

    📋 Next Steps

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

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

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions