Verification Request: homebridge-concert

[tbaur]

Plugin Name

homebridge-concert

Link To GitHub Repo

https://github.com/tbaur/homebridge-concert

Plugin Icon (Optional)

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

Homebridge plugin for AudioControl Concert XR receivers (e.g. XR-8S). Dynamic platform exposing power/standby, volume-preset, and source-preset HomeKit switches over the LAN IP control port.

No existing verified plugin covers AudioControl Concert hardware (verified AVR plugins target other brands such as Denon/Yamaha/Anthem).

• Published on npm as homebridge-concert@1.0.0
• Dynamic platform (pluginAlias: Concert), config.schema.json for the Settings UI
• Zero runtime dependencies; Homebridge is a devDependency only
• Invalid/missing config disables the platform without crashing Homebridge
• TCP connect/poll failures are caught and logged (no unhandled rejections)
• Plugin icon is the AudioControl brand mark, used for this AudioControl-specific plugin (see assets/logo.png)

[tbaur]

This request was opened via the GitHub CLI, which could not apply the issue-form labels (request-verification / pending) — collaborators without triage permission cannot add labels on this repo, and those labels are required for the Plugin Checks workflow to run.

Could a maintainer please add request-verification (and pending) so the automated checks can execute? Happy to comment /check once the label is present.

Thanks!

[tbaur]

Tried a few ways @bwp91 -- should have used the form :)

[tbaur]

/check

[github-actions]

🔴 Failed Checks

• Package JSON: keywords must include at least one of 'supports-hap' or 'supports-matter' — see Declaring Supported Transports

🟢 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: '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 (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: 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: no unsafe code patterns detected
• 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

ℹ️ Check Details

• These checks were run against v1.0.0 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.

[tbaur]

Fixed: supports-hap is now on the published package (homebridge-concert@1.0.1). The keyword was on GitHub earlier but had not been released to npm yet.

/check