- 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 be of type dynamic platform.
- The plugin must not offer the same nor less functionality than that of any existing verified plugin.
- The plugin must not execute post-install scripts that modify the user's system in any way.
- The plugin must not contain any analytics or calls that enable you to track the user.
- 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 should be created for every new version of your plugin, with patch notes.
- The plugin must run on all Active LTS versions of Node.js, at the time of writing this is Node v18 and v20.
- 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.

homebridge-spanet #591

Description