Plugin Name

homebridge-easy-mqtt

Link To GitHub Repo

https://github.com/mpatfield/homebridge-easy-mqtt

Plugin Icon (Optional)

No response

The plugin does not offer the same nor less functionality than that of any existing verified plugin.

🟠 No (please explain in the more information box at the end)

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-mqttthing and homebridge-mqtt do seem to offer similar functionality, but development has ceased and many important issues have been ignored for years.

homebridge-easy-mqtt is intended be a simple-to-use replacement that uses modern homebridge patterns and up-to-date dependencies.

I respect not wanting verified plugins that duplicate functionality, but is there a process by which plugins are "de-verified" after an extended period of inactivity to make way for more up-to-date variants? It seems like having a plugin marked as verified that is many years old and uses dependencies that are error-prone and possibly even security risks is not great.

No hard feelings if you reject my request to verify homebridge-easy-mqtt. I just wanted to at least start a conversation about the verification process.

Thanks!