- Raspberry Pi
- Debian, Ubuntu
- CentOS, Fedora, Red Hat
- Arch, Manjaro
- Windows 10 / 11 (Hyper-V)
- Synology DSM 7
- Other Platforms
- Adding To HomeKit
- Change Homebridge Version
- mDNS Options
- Child Bridges
- Remote Access
- Config.json Explained
- Basic Troubleshooting
- iOS App
- HomeKit Glossary of Terms
- How To Update Node.js
- Backup and Restore
- Beta Testing
Clone this wiki locally
Homebridge plugins that are marked as Verified have been reviewed by the Homebridge project team to ensure they meet some basic requirements that encourage best practices and a trouble-free user experience.
Plugins marked as Verified have been tested to ensure they meet the following requirements:
- The plugin must successfully install.
- The plugin must implement the Homebridge Plugin Settings GUI.
- The plugin must 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 contain any analytics or calls that enable the plugin developer to track you.
- The plugin must not throw unhandled exceptions, the plugin must catch and log its own errors.
- The plugin must be published to npm and the source code available on GitHub.
- A GitHub release - with patch notes - should be created for every new version of your plugin.
- The plugin must run on all supported LTS versions of Node.js, at the time of writing this is Node.js v14 and v16.
- The plugin must not require the user to run Homebridge in a TTY or with non-standard startup parameters, even for initial configuration.
- If the plugin needs to write files to disk (cache, keys, etc.), it must store them inside the Homebridge storage directory.
These plugins have been verified by the Homebridge team: