You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
This plugin is a maintained fork of the original homebridge-freebox-player-delta, modernized for current Homebridge versions.
Version 1.4.0 supports Homebridge 2 and Node.js 22/24. The plugin is implemented as a Dynamic Platform and publishes the Television as an external accessory, following guidance received from the Homebridge team for Television accessories.
The plugin provides Freebox Player Delta/Devialet power control, HomeKit remote control and mute, direct application launching, and automatic active-source detection through the Freebox OS/Player APIs.
Freebox OS authentication data is stored exclusively inside the Homebridge storage directory and is not stored in config.json.
The release is tested through GitHub Actions on Node.js 22 and 24, and production dependencies currently report 0 vulnerabilities with npm audit --omit=dev.
Version 1.4.0 has been published to npm and has a matching GitHub release.
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 have issues enabled
🟢 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.4.0) matches NPM version (v1.4.0)
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: no unsafe code patterns detected
Security: no privilege escalation attempts detected
GitHub Repo: repository is public
GitHub Repo: repository is not archived
GitHub Repo: contains releases
ℹ️ Check Details
These checks were run against v1.4.0 of the plugin.
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.
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.
Thanks for the quick turnaround on the checks — all green now, so I've verified homebridge-freebox-player-delta-hb2 🎉
Nice to see this one picked up again. The original homebridge-freebox-player-delta was verified a long time ago, but I had to remove it from the list when the upstream repo was archived, so there's been no Freebox Player plugin on there for a while. Crediting @securechicken and keeping the GPL-3.0 licence is exactly the right way to handle a fork, so thanks for that.
One small thing going forward — you're already doing it, but please do keep adding notes to each GitHub release. They get shown in the Homebridge UI when someone updates the plugin, so they're genuinely useful to your users.
Activity
github-actions commentedon Aug 31, 2026
🔴 Failed Checks
requiredshould not be a boolean property on individual fields. In JSON Schema,requiredmust be an array at the object level listing required property names. Remove"required": true/falsefrom individual properties and use"required": ["property1", "property2"]at the object level instead.🟢 Passed Checks
homepageexistsbugs.urlexists and seems a valid URLkeywordsexist and contain'homebridge-plugin'keywordsdeclare the supported transports ('supports-hap'and/or'supports-matter')'preinstall'inscriptsis not present'install'inscriptsis not present'postinstall'inscriptsis not presentengines.nodeproperty is compatible with Node 22engines.nodeproperty is compatible with Node 24engines.homebridgeproperty is compatible with Homebridge 2.4.0pluginAliaspluginAliasmatches the platform/accessory registered in codepluginTypeis set to'platform'nameschema propertyhomebridgeis not declared as a runtime/peer/bundled dependencyhap-nodejsis not declared as a runtime/peer/bundled dependencyℹ️ Check Details
v1.4.0of the plugin.📋 Next Steps
/checkon this issue to run the checks again — your request will not move forward until the checks are re-run.package.jsonandconfig.schema.jsonfiles, don't forget to publish a new version to NPM.anthouny commentedon Aug 31, 2026
/check
github-actions commentedon Aug 31, 2026
🟢 Passed Checks
homepageexistsbugs.urlexists and seems a valid URLkeywordsexist and contain'homebridge-plugin'keywordsdeclare the supported transports ('supports-hap'and/or'supports-matter')'preinstall'inscriptsis not present'install'inscriptsis not present'postinstall'inscriptsis not presentengines.nodeproperty is compatible with Node 22engines.nodeproperty is compatible with Node 24engines.homebridgeproperty is compatible with Homebridge 2.4.0typepropertypropertiesfor object typepluginAliaspluginAliasmatches the platform/accessory registered in codepluginTypeis set to'platform'nameschema propertyhomebridgeis not declared as a runtime/peer/bundled dependencyhap-nodejsis not declared as a runtime/peer/bundled dependencyℹ️ Check Details
v1.4.1of the plugin.📋 Next Steps
All checks passed successfully, nice work! Your plugin and/or icon will now be manually reviewed by the Homebridge team.
verify: homebridge-freebox-player-delta-hb2
github-actions commentedon Sep 2, 2026
Congratulations! Your plugin has been verified!
You can now add one of the Verified by Homebridge badges to your plugin's README:
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.
bwp91 commentedon Sep 2, 2026
Hi @anthouny
Thanks for the quick turnaround on the checks — all green now, so I've verified
homebridge-freebox-player-delta-hb2🎉Nice to see this one picked up again. The original
homebridge-freebox-player-deltawas verified a long time ago, but I had to remove it from the list when the upstream repo was archived, so there's been no Freebox Player plugin on there for a while. Crediting @securechicken and keeping the GPL-3.0 licence is exactly the right way to handle a fork, so thanks for that.One small thing going forward — you're already doing it, but please do keep adding notes to each GitHub release. They get shown in the Homebridge UI when someone updates the plugin, so they're genuinely useful to your users.
Thanks for contributing to Homebridge!