Become a verified plugin

[bostrt]

Get labeled as a verified plugin by meeting all these requirements:
https://github.com/homebridge/homebridge/wiki/Verified-Plugins

[bostrt]

• General
  • The plugin must be of type dynamic platform.
    • https://github.com/bostrt/homebridge-bali-blinds/blob/main/src/platform.ts#L10
  • The plugin must not offer the same nor less functionality than that of any existing verified plugin.
    • There are no other plugins for Bali blinds. However, if comparing to a plugin like https://github.com/hjdhjd/homebridge-blinds-cmd they are roughly in feature parity (up, down, stop, battery..)
• Repo
  • The plugin must be published to NPM and the source code available on a GitHub repository, with issues enabled.
    • Available on NPM https://www.npmjs.com/package/homebridge-bali-blinds
    • Available on GitHub https://github.com/bostrt/homebridge-bali-blinds
  • A GitHub release should be created for every new version of your plugin, with release notes.
• Environment
  • The plugin must run on all supported LTS versions of Node.js, at the time of writing this is Node v18 and v20.
    • Testing runs for v18 and 20: https://github.com/bostrt/homebridge-bali-blinds/blob/main/.github/workflows/build.yml#L12
  • The plugin must successfully install and not start unless it is configured.
    • Successfully install (no link to prove) and does not start unless configured: Validate config before launch #12
  • The plugin must not execute post-install scripts that modify the users' system in any way.
    • package.json contains no post scripts: https://github.com/bostrt/homebridge-bali-blinds/blob/main/package.json
  • The plugin must not require the user to run Homebridge in a TTY or with non-standard startup parameters, even for initial configuration.
• Codebase
  • The plugin must implement the Homebridge Plugin Settings GUI.
    • Configuration shema is used: https://github.com/bostrt/homebridge-bali-blinds/blob/main/config.schema.json
  • The plugin must not contain any analytics or calls that enable you to track the user.
  • If the plugin needs to write files to disk (cache, keys, etc.), it must store them inside the Homebridge storage directory.
    • No files are written to disk
  • The plugin must not throw unhandled exceptions, the plugin must catch and log its own errors.
    • Exceptions are generally caught and handled but there is a catch-all at one of the entrypoints into plugin logic: https://github.com/bostrt/homebridge-bali-blinds/blob/main/src/platform.ts#L42-L47