Shelly Binding

Maybe this is already known but I couldnt find anything on this.
I have a plus plug S which I upgraded to 1.4.4
Now I cant seem to control the relais anymore. Also the status of thw relais is no longer reported. However the measurements are correctly received by openhab.

I tried enabling debug logging. However I cant find any entries relaited to the relais of this thing.

Iā€™ve also got Shelly Plus Plug Sā€™s with 1.4.4, and they work fineā€¦ :grimacing:

Okay strange I just did an update of Oj from 4.3.0 to 4.3.1 and now its woeking again. Though there was nothing relatwd in the release notes. Guess there was some issue on the websocket not being correctly established or so.

Binding from the add on store or folder??

I had this too.
I restarted openhab. Then it was OK again.
Greets

Only Pro Shellys with 1.4.4 has that problem with Websocket Disconnects.
All my non Pro with 1.4.4 running fine.

@tnemrap Update: got everything set up.
While a good idea, the only channel I see on my pro3m is temperature, and nothing else.

However, I did managed to get the json to add compatibility for the Shelly devices and shared it in the matter thread.

We likely wonā€™t see as many channels through matter as we saw in the Shelly binding though, at least I have a feeling that not everything can be exposed. Letā€™s see how it goes.

But with my 10+ Shelly devices it should be a sizable update to our matter binding :heart:

2 Likes

Iā€™m experimenting with the Shelly Plus RGBW PM and the official Shelly binding.
How can I switch the Shelly on or off?
I tried sending the brightness value 0 but the Shelly doesnā€™t accept that. What other options are there?
If the Shelly is off and I send a value >0, the Shelly switches on.

Have you tried to link a switch item to the dimmer channel?

Yes, I tested that. Without success. :confused:
At the moment Iā€™m making do with sending http-requests.
But I think there must be another solution.

The Plus RGBW PM is currently not supported by the binding.

Why not try the matter bridge with the Shelly plugin? Since itā€™s a dimmer, Iā€™m pretty sure I read that Dan already has the dimmer function working.

Or maybe it was the colorā€¦?

edit:
nope, dimmer, here:

levelcontrol-level	Dimmer	Dimmer	Sets the level of the light	Light

More info here:

and the read me here:

This isnā€™t a ā€œsolutionā€ per se, because the matter protocol isnā€™t exposing nearly as many channels as the shelly binding. not by a long shot. But at least we can help push the matter binding forward by exposing shelly devices there hehe :slight_smile:

Upon second reading, this is an Off topic. If unwelcome I will delete this post, please just let me know and I will do so.

Strange. The binding found the Shelly and suggested it.
I can create and operate the items. The RGBW-values ā€‹ā€‹are also correct.
Only switching it off doesnā€™t work

Thank you very much! Yes, that is also a possibility! Please do not delete it!
My ā€œworkaroundā€ is based on the use of http commands:

sendHttpGetRequest("http://XXX.XXX.XXX.XXX/color/0?turn=on")
sendHttpGetRequest("http://XXX.XXX.XXX.XXX/color/0?turn=off")

@markus7017, maybe this got lost in the pile of new messages? If not, I apologise. :slight_smile:

@markus7017 happy new year!
My (second) em3pro just crashed again and needed to be power cycled. I am now quite certain this is caused by the Shelly binding. The only way Iā€™ve found that reduces or limits this is by disabling the thing in openHAB all together, or isolating the device in my network.

My logs still donā€™t show anything, but Iā€™m not very good at this - another user previously shared his logs with a recurrent/constant call to the device.

It this is related, do you think that maybe there could be a fix?

New stuff for usā€¦ā€¦

3 Likes

Shelly firmware 1.5.0-beta1 with slat support for gen2 2pm. yeah :heart_eyes:
now only datapoint in shelly binding is missing

in your log there is a 404 error present.

"21:22:21.995","DEBUG","org.openhab.binding.shelly.internal.handler.ShellyBaseHandler","shellyplusrgbwpm-ecc9ff4c4570: Unexpected API result: 404/OK"

not sure where this comes from. The first initialization seems ok, then the 404 happens and all subsequent calls fail.

I fixed it the ā€˜easy wayā€™ by getting a rgbw2 (so not the PM/plus)