Shelly pro3em.
I’ve had this issue since months, just check my post history. I’ve been in contact with Shelly, sent all my logs to them for several entire months, replaced the device, no dice.
I have the Shelly disabled in OpenHAB now and I am/was using the matter bridge with great success.
Which version of the plug-in do you use?
The official binding from openHAB 4.3.0.
sad for the binding.
Some things take time… 
Hi, I’m interested with binding for Shelly Wave Pro 3, any help with Shelly Z-Wave devices?
Sorry I am not using the Z-wave devices. Someone knows if the binding is even working with them?
1 Like
For all of us stuck with the Shelly pro3EM, today I noticed that there’s a new beta2 firmware available if you go through the local webui:
I installed it and now we wait to see if it crashes too.
By the way, I updated to the 5.0M1 and I still lack the 3rd meter channel:
I will create a bug in GitHub, it’s so strange that it’s just the one channel missing 
Edit:
Weird things be happening… got my brain confused with the setup of the pro3em, and thought mine should be in triphase. Once I changed to triphase I immediately recognized my error, so I changed it back. As I was curious to see if this had messed with OpenHAB, I checked the Thing and….
It’s correct now…. Not sure why but I’m not complaining.
Note to wait and see if the 1.5.1 also crashes, fingers crossed.
1 Like
No, the bindings does not support the Shelly Wave devices, use the Z-Wave binding instead
Someone installed latest Shelly Firmware 1.5.1? Is the Binding working with the newest Firmware?
Read two posts above @alaub81
My devices are all running 1.5.1, and I haven’t noticed any problems.
1 Like
Perhaps a stupid question, but I saw, that with the new firmware version all devices got a web socket icon in the user right corner. I know, that the battery devices like the shelly H&T have configured the openhab web socket. So my question is, why the other devices, the relais do not need that configuration? Isn’t it better to get informations pushed from the devices, then collecting them?
btw. All my devices are now upgraded to 1.5.1. Looks like everything is more stable now. I saw so many core dumps with the older 1.4.x firmwares in my syslog, but they are gone now. Only thing I realised, is that the BLU Gateway support on the 2PM devices configured as rollerhutter throws so many log entries. I disabled BLU Gateway support on these devices now.
The binding configures the web socket connection automatically and receives status notifications from the device dynamically.
The log entries for BLU Gateway support on 2PM in roller mode here
OK, but on my relais there is nothing configured. Is this a mistake? On my HT devices I see the correct ws URL configured.
this log entry (warning) is comming every 1 to 3 seconds:
361 381.704 1 1|shelly_pm_ade7953.c:565 chip_id:0 meas, retrying setup (attempt 1), pend: 1...
after disabling the oh-blu-scanner.js script, the warnings are gone.
On 2pm devices configured as normal 2 output switch, everything is fine!
try it out, while switching the relays you should see status updates in OH, more or less instantly
The H&T is different, because it goes to sleep mode Therefore it needs an Outbound WebSocket. In this case the device create the WS connection, whereas for devices connected to WiFi this outbound connection is not required.
= all ok
1 Like
No clue what that means, maybe contact Shelly support
Hi i had issues with Shelly EM3 Pro not refreshing items via the binding reliably, as i didn’t recognize the exact topic i made my own.
I have 1.5.1 firmware and OH 4.3.2 and it apeaes i dont get measurements regurally when they change so i made my own integration via MQTT.
As i was discusing the topic with a member he pointed me to chime in on official thread, so i make the noise spread about integration options.
So i welcome anyone to take a look at my MQTT project with Shelly EM3 Pro and Shelly Plus S plug.
Welcome to coment and test it out.
Cheers Matej
1 Like
Hello all,
Is this the last DEV build: myfiles/shelly/org.openhab.binding.shelly-4.3.6-SNAPSHOT.jar at master · markus7017/myfiles · GitHub ?
That’s the one I’ve installed, I’ve delete my Shelly Things, but after that the openhab inbox doesn’t show any of my Shelly appliance, even if I click on the + and then scan for Shelly.
Am I doing something wrong ?
My version of OpenHab is 4.3.5-1
Edit: I’ve found two types of errors:
2025-05-07 11:54:20.887 [WARN ] [core.thing.internal.ThingManagerImpl] - Could not normalize configuration for ‘shelly:shellyplugs:b58617’ because the thing type was not found in registry.
2025-05-07 12:01:12.092 [INFO ] [g.discovery.internal.PersistentInbox] - ThingTypeUID shelly:shellyem for discovery result with ThingUID shelly:shellyem:34945473e8eb not found, retried 20 times, aborting
Update. I’ve tried what the BETA readme says:
stop OH
run "openhab-cli clean-cache"
start OH wait a while until fully initialized
open OH console, run "feature:install openhab-transport-coap"
copy jar to addons folder
run bundle:list on the OH console and make sure, Shelly binding shows up with status active
But I still see these kind of error and nothing in inbox
2025-05-08 19:51:53.253 [INFO ] [g.discovery.internal.PersistentInbox] - ThingTypeUID shelly:shellyem for discovery result with ThingUID shelly:shellyem:34945473e8eb not found, retried 20 times, aborting
Any ideas ?
Update 2: I’ve switched back to v4.3.0. I’ve got back all my Shelly items except for one strange thing, one of my Shelly Door Window BLU (shelly:shellybludw) has lost all his channels except for device#alarm and device#wifiSignal. What could explain that ??
Update 3: this will be my last edit for a while since I’m mostly talking to myself. v4.3.0 works for me but not 4.3.6 or 5.0.0 (error about “normalize configuration” or “discovery result not found”). Lost some channels, was about to that them manually from a previous configuration and a last test of adding/removing the jar fixed the problem. Going to monitor the accuracy of the BLE Door Window I’ve placed recently: one is outside and at a serious distance from the Gateway (BLE Gateway) but it works and the signal is really not bad.
Today I noticed some problem with my Shelly plus 1 with FW 1.6.1
I have had some power down in the garden (water) and therefor the power from the Shelly plus 1 went off. After putting back the fuse, the Shelly bootet, but was not going to become online in the OH 4.3.5. Message in the Thing: “Error Connection” I have had to disable him and enable him, to bring him back to online.
Has some also noticed somthing like that?
What can I to bring him online again, without manuell doing something?
Older Shelly1, oder Shelly 2.5 have not this problem. Only the shelly 1 Plus…
This problem has been already reported in the Shelly forum:
Additionally information… I’m using the AddOn module here for temperature and humidity….
Hi everyone,
I’m seeing an issue with one of my Shelly devices after updating to firmware 1.6.1.
Thing status:
Thing 'shelly:shellyplus1pm:441793cea354' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Unerwarteter Fehler - WebSocket error
This happens frequently, and the device keeps going offline/online intermittently.
Important note: All my other Shelly devices still running on firmware 1.5.1 are working perfectly fine and do not show this issue.
Is anyone else experiencing this with 1.6.1? Could this be a firmware-related problem?
Would appreciate any feedback or suggestions.
Thanks!