Shelly Binding

Add-ons Bindings
,
4076

Great to hear :wink:

4077

I closed the case at Shelly, as my experience is the following (OH 4.1.1) :
I have 3 (5) Shelly plus 2 PM. One since “long time”, firmware 1.3.3, added with the Shelly binding from the store and works just fine.

For other reasons, I installed the Shelly beta binding (and reverting back - more the once).

Purchased two other Shelly Plus 2PM and upgraded to 1.4.2 before adding to OH :

  • not discovered
  • not working (Unexpected error: WebSocket connection closed abnormal)

Therefore, the obvious conclusion was that this problem is related tot the new firmware.

So, I purchased two other Shelly Plus 2PM, upgraded to 1.3.3, and also

  • not discovered
  • not working (Unexpected error: WebSocket connection closed abnormal)

In my humble opinion something goes wrong when the beta binding is installed. Or I am missing something ?

(all in cover mode - Shelly Plus 2PM works justs fine in switch mode).

Any help appreciated.

4078

I assume you restarted the Shelly device in an attempt to trigger the autodiscovery?

4079

Yes.

4080

I have 3 shellyplus2pm in cover mode and fw 1.4.2 in place. All working perfectly and got added without any problems. Maybe there is a particular setting which conflicts with the binding?
changes I have done:

  • password protection is on
  • device name changed before adding to openhab
  • access point and bluetooth is deactivated
  • none of the connectivity options are enabled
  • sntp url set to local time server
4081

For those who have the Shelly plus 2PM working, what version of OH and binding is used ?
(I installed a 4.1.1, did not work, upgraded to 4.2.1) works fine.

4082

I have “only” Shelly plus 1PM working.
OH: 4.2.1-1 on RPI5, RPI4, and RPI3
Shelly Binding: 4.2.1
FW: 1.4.2

4083

I upgraded to 4.2.1 and both Shelly plus 2 PM are discoverd.
(but now my panels are no longer working - which is solved by clearing the cache).