Ah, so that’s only possible if you’re in contact with Shelly, then. How does one do that? 
You can open a ticket:
https://support.shelly.cloud/de/support/tickets/
Since a couple of days my shellies also no longer reliably work with openHAB. Sometimes they don’t react at all, sometimes they do with a delay of about 15 seconds (estimated). I haven’t dug any deeper so far but I think this might be related.
EDIT: actually I think this was more Alexa related… I will observe further…
EDIT: No it’s not just an Alexa thing. It also happens in my local network with a direct OH to Shelly connection.
Cannot see this on a Shelly 1PM with latest firmware:
shelly_notification:162 Status change of switch:0: {"id":0,"aenergy":{"by_minute":[696.778,693.909,691.450],"minute_ts":1742809860,"total":175525.495}}
10:51:00
shos_rpc_inst.c:374 0x3ffe0ab8: duplicate id 'openhab-192.168.1.209'
10:51:14
shos_rpc_inst.c:243 Shelly.GetStatus via HTTP_in POST 192.168.1.209:60568 user admin
10:51:14
shos_rpc_inst.c:243 Shelly.GetStatus via HTTP_in POST 192.168.1.9:34540 user admin
10:51:16
shos_rpc_inst.c:374 0x3ffdf68c: duplicate id 'openhab-192.168.1.184'
10:51:55
shos_rpc_inst.c:243 Shelly.GetStatus via HTTP_in POST 192.168.1.184:48918 user admin
10:51:55
shelly_notification:162 Status change of switch:0: {"id":0,"aenergy":{"by_minute":[700.467,696.778,693.909],"minute_ts":1742809920,"total":175526.195}}
10:52:00
shos_rpc_inst.c:374 0x3ffddc8c: duplicate id 'openhab-192.168.1.209'
10:52:14
shos_rpc_inst.c:243 Shelly.GetStatus via HTTP_in POST 192.168.1.209:52890 user admin
10:52:14
shos_rpc_inst.c:243 Shelly.GetStatus via HTTP_in POST 192.168.1.9:41038 user admin
10:52:17
shos_rpc_inst.c:374 0x3ffde9f0: duplicate id 'openhab-192.168.1.184'
10:52:55
shos_rpc_inst.c:243 Shelly.GetStatus via HTTP_in POST 192.168.1.184:57786 user admin
10:52:55
shelly_notification:162 Status change of switch:0: {"id":0,"aenergy":{"by_minute":[701.697,700.467,696.778],"minute_ts":1742809980,"total":175526.897}}
10:53:00
shos_rpc_inst.c:374 0x3ffde9f0: duplicate id 'openhab-192.168.1.209'
10:53:15
shos_rpc_inst.c:243 Shelly.GetStatus via HTTP_in POST 192.168.1.209:45658 user admin
10:53:15
shos_rpc_inst.c:243 Shelly.GetStatus via HTTP_in POST 192.168.1.9:53452 user admin
10:53:17
shos_rpc_inst.c:374 0x3ffdf68c: duplicate id 'openhab-192.168.1.184'
10:53:55
shos_rpc_inst.c:243 Shelly.GetStatus via HTTP_in POST 192.168.1.184:60212 user admin
10:53:55
shelly_notification:162 Status change of switch:0: {"id":0,"aenergy":{"by_minute":[700.877,701.697,700.467],"minute_ts":1742810040,"total":175527.598}}
10:54:00
shos_rpc_inst.c:374 0x3ffe0ab8: duplicate id 'openhab-192.168.1.209'
10:54:15
shos_rpc_inst.c:243 Shelly.GetStatus via HTTP_in POST 192.168.1.209:43996 user admin
10:54:15
shos_rpc_inst.c:243 Shelly.GetStatus via HTTP_in POST 192.168.1.9:48814 user admin
10:54:17
shos_rpc_inst.c:374 0x3ffdf68c: duplicate id 'openhab-192.168.1.184'
10:54:55
shos_rpc_inst.c:243 Shelly.GetStatus via HTTP_in POST 192.168.1.184:34570 user admin
10:54:55
shelly_notification:162 Status change of switch:0: {"id":0,"aenergy":{"by_minute":[700.467,700.877,701.697],"minute_ts":1742810100,"total":175528.298}}
10:55:00
Runs as expected with 4.3.3 and offical binding.
Just in case: is anyone else using UniFi network equipment like me that has problems with Shelly now?
Yes, I am using UniFi wifi and network infrastructure. But without any new issues. There weren’t any UniFi Updates in the last few weeks for my hardware, so no change there. And also I didn’t do any updates of the new shelly firmware (1.5.1). So no new issues… But I wouldn’t say that everything is working as stable as I would like to have it.
I am trying to figure out at the moment from where my random issues are coming. And also I have switched some shelly devices to mqtt. Just to see if that method is more stable.
I am running openhab 4.3.3 and also the Shelly Binding belonging to that version.
No, you can setup your own syslog server and use that one at the UDP Debug… Shelly is also just using a syslog server. There are plenty of ways to get your own. the simplest way should be to run a docker container. If you guys are interested in such a solution, I can document my syslog setup.
Someone knows, if there is an easy way to monitor the shelly web api, to see when a shelly device is going offline? I need to see that, so I am able to have a look at the debug log of the device to see, what is going wrong. Best way would be to monitor the THING Status, but I did a research of that, and it is not easy to implement. Perhaps someone has an easy solution for that.
I am!
Search for Thing Status Reporter.
I get messages when Things go offline. It is not difficult.
yes and yes.
I’ve got a Unifi setup, but no issues…
yes and yes! It makes me so desperate that I am thinking about ditching openHAB.
Since yesterday functionality seems to be almost back to normal. Only minor delays when switching lights and shutters, Alexa is also working fine again. No idea what caused/causes this 
I had some pretty bad network ratings in my UniFi app though, especially DNS seemed to be a problem. Maybe this is also pi-hole v6 related? However I don’t really see a direct connection here since I use only IP addresses for my Shelly devices in OH, no host names 
Hi all,
i have OH 4.3.3 and I am wondering about support for the gen 3 pm2 as well as the plus rgbw. Both are on the market since a while already. On github there is still a special jar file for the gen3pm2 but I do not know if this is also included in the later builds. I tried also the latest 4.3.5 but could not see any support for the rgbw plus, especially basic command such as on / off. Maybe it is even there but I am missing infos / docu?
Thanks and best
MatzeMuc86
…the plus rgbw…
I solved it this way.
The binding recognizes the RGBW Plus
Which version of the plug-in do you use?
The workaround via http is an idea but sad for the binding.
But unfortunately that is the wrong forum to post, because if I remove the Shelly binding my shelly pro3m never crashes, and as soon as I have the binding back up, it crashes, so it’s an openhab related topic.
I replaced my quite expensive shelly 3pro, and the second one has the same behaviour.
The device gets hard locked, fully crashed, not even the reset button works → This isn’t a shelly app problem, because the device isn’t even accessible locally. It’s completely locked and only a power cycle recovers it.
Are you using a Shelly Pro 3em or a Shelly Pro 3? I have a Shelly Pro 3 running ok, with openhab and the Shelly Binding. But I had issues with my Pro EM 50, I am testing that one just over mqtt at the moment. But it is running only a few days now, and also with the binding it ran up to 1 week and longer. I am using openhab 4.3.3 with official binding and Shellies have version 1.4.4 installed.