Thx, that works better.
Can I use this in production ? The docs seem to indicate it could be unstable - will the fix become available in a release soon ?
We are working to merge some PRs, which hopefully make it into the 5.0 release.
Between releases I’m fixing bugs, enhancive features or additional devices like Gen4 series. You could use those so you don’t need to wait until next official release.
And you should use the DEV build to do testing and report bugs, which can be fixed before the next release is published.
I updated the DEV build (5.0 and 4.3.6) to include support for Shelly PlugS Gen3, Shelly Plus Outdoor Plug and amazon Shelly Plug. Thanks @wborn for implementation.
3 x under OH4.3.5 the DEV 4.3.6 binding installed, without an problems so far…
No WebSocket issue more
Please continue with the implementation of new shelly devices @markus7017 and thanks for you development work!!
I have update the firmware of my ShellyPlus2PM from version 1.5.1 to 1.6.2 without having found this topic in advance and now facing issues as well.
I am now wondering there is the possibility to downgrade the firmware back to 1.5.1 in general using the respective firmware file for the time being and if someone has downloaded and can share the firmware version 1.5.1 for ShellyPlus2PM file?
Thanks for the fixes and the update. I’m new to OH, although have 30+ years of Windows based line of business development experience. So might dive into the code base to see if there is anything I can do to help.
Hi, I have a shelly outdoor (running openhab 4.3.5). I’ve tried the current build 4.3.6.202507011114
Unfortunately, the outdoor plug shows up as an unknown shelly device and it’s also not listed as a selectable device type when trying to add it manually. Any advice?
I’ve moved to “openHAB 5.0.0-SNAPSHOT - Build #4718” but firmware 1.6.2 bugs do continue. ShellyPlus2PM is constantly switching form Online to Offline and vice versa showing “Unexpected error: WebSocket error” in the logs.
I noticed that my Shelly Plus2PM always reports a new firmware even if there is only a beta firmware available. Is that on purpose? I usually don’t upgrade to beta firmware. I’m on a dev build (maybe a week old).
If you are adding model ids. I mentioned a few month ago, that shelly pro 2 is recognised as unknown. I added it manually as a pro2 and everything is working fine. In the autodicovery the unknown device still appears.