homebridge-shelly-2pm-plus

[tomas-kulhanek]

homebridge-shelly-2pm-plus

[bwp91]

thanks for the changes!

not sure if this suits your use case for the IP address config field, but there exists a format: 'ipv4' property you can use for a little bit more guidance in the plugin config screen for users.

https://developers.homebridge.io/#/config-schema#format

Will show a warning in the config screen if any entered value does not seem a valid IP

[tomas-kulhanek]

@bwp91 thanks!
I modified the format and released a new version.

[github-actions]

✅ Pre-checks completed successfully.

[bwp91]

Hi @tomas-kulhanek

Please update your readme with a valid config for your plugin (it at least needs to include the "platform" property, and in the case of your readme example, it would be good to see a 'base, minimal' config as well as one that shows a config for a vacuum cleaner with room cleaning as you have written in your current readme

---

screenshot:

---

[bwp91]

Comment number two:

I have installed the plugin on my local homebridge with the following config:

        {
            "platform": "Shelly2PMPlus",
            "_bridge": {
                "username": "0XXX",
                "port": XXX
            }
        }

I get the following message in the log

[11/07/2023, 01:49:51] [homebridge-shelly-2pm-plus] Initialize of plugin was failed TypeError: this.config.watch is not iterable

which is great that the plugin 'stops' and is one of the main things about verified plugins, but I wonder if a more helpful explanation for the user would help.

This is outside the plugin verification criteria but if you are sorting out the above anyway 😁

[tomas-kulhanek]

Hi @bwp91
OMG 🤦 , I have information about a vacuum cleaner there, and it's an electronic voltage switch 😁

I edited it incl. platform definition in the configuration and I treated the type error for watch straight away

[github-actions]

• - 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 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.
• - GitHub releases 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.js v16 and v18.
• - 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.

---

Everything Looks Good!

[github-actions]

Congratulations! Your plugin has been verified.

You can now add the Verified by Homebridge badge to your plugin's README:

[![verified-by-homebridge](https://badgen.net/badge/homebridge/verified/purple)](https://github.com/homebridge/homebridge/wiki/Verified-Plugins)

Your plugin is now also eligible to display a ❤️ Donate button on its tile in the Homebridge UI. See https://github.com/oznu/homebridge-config-ui-x/wiki/Developers:-Donation-Links for instructions.

If for any reason in the future you can no longer maintain your plugin, please consider transferring it to our unmaintained plugins repo. We can take ownership until another willing developer comes along.

Thank you for your contribution to the Homebridge Community.
https://homebridge.io