I found yet another issue with the pro3em Shelly. The total energy consumption channel also does not populate. I hadn’t used this channel in the past and today I finally figured out a use for it… and it doesn’t work 
What is your load power? As far as i remember, the pro3em has some limitations for loads < 30W per phase.
Always always above 100~ watts though. One of the meters (the third) does go down to 10 watts routinely but the others are reading the entire circuit breaker box.
Just double-checked mine. Its upcounting and shows 589,467 kWh. Have still binding 5.2.0.202603190405 (integrated version of OH). Shelly app reading is 589,47 kWh.
Might be related
Hi there again 
It’s been a while, many things recently going on, found no time at all. So I’d be quite interested…
- what’s the state of the binding concerning all the Jetty and connectivity issues?
- Are there any news concerning the OOM error of the BT Gateway script?
- all new - will “The Pill” by Shelly be supported at some day?
Thanks a lot for all your work!
Hello all,
I’m trying to follow the evolutions here but humbly acknowledge that I’m not too sure anymore where to find the latest “stable” dev versions of the binding, if that makes sense?
I am on openHab 5.1.3 (with its associated shelly binding) and have constantly shelly things going offline (by batches, i.e. most of them go back and forth offline to online and vice versa and sometimes stay stuck in offline mode for hours, until I disable and re-enable the thing…
This is more true for “recent” shelly devices.
With all what I read here I have the feeling upgrading the binding could help preventing this from happening. Issue is I’m not too sure about which version I should try. Any recommendation?
Thank you,
This sounds to the websocket error we have had some while ago, which is long fixed also in the offical 5.1.3 shelly binding working very well.
So first I would try to delete one or two existing things with all the relevant items, and create them completely new with the official binding from 5.1.3.
If this should fail, you can try the latest DEV binding, from github, which is this, if I’m right:
5.2.0.202604052251
Ah, yes, very good. I’m trying it (the delete and re-create of the things) right now. I’ll report back here.
Thanks for the hint. I did not consider this because I thought it was more for when sideloading a dev version, but worth trying for sure.
Ok, so, I changed 1 thing, deleted it and re-created it and then reconnect the channels to the items. Just one.
And it seems that the number of “offline → Online” and repeat has reduced drastically. Thanks a lot for the hint. I’m a bit surprised that just doing it for one thing fixed so much, but I’m happy with the effect 
Thanks a lot @scheuerer for your help.
HI all,
I found in the documentation of the Shelly binding that the bluetooth gateway mode needs to be disabled either through the device UI or through the Shelly app to make the oh-blu-scanner.js running properly on the device to make paired Shelly BLU devices visible in OH.
I am running OpenHAB 5.1.1 in a docker container on my NAS.
I am using a Shelly Plus 1 Mini Gen3 as a bluetooth gateway for my Shelly BLU button. My Shelly device is on firmware level 1.7.5-g99…
On that firmware level there is no option to activate or deactivate the gateway function via the UI. Hence, I registered my Shelly Plus 1 Mini device via cloud in the Shelly app and found in the bluetooth settings that the switch to turn off the gateway mode is greyed out and there is a message that since firmware level 1.5.0 the gateway mode is consistently activated and cannot be turned off anymore (see screenshot)
Can you please advise if and how I can now connect my BLU button when the gateway mode cannot be turned off anymore?
I have tried adding it trough the OpenHAB UI and it hangs like expected in CONFIGURATION_PENDING (see screenshot) as the script hangs.
P.S. All my Shelly devices are on a higher firmware level than 1.5.0. This would imply that I cannot attach them to OpenHAB. I cannot believe that this can be true.
Thanks for any hint and support.
Cheers
Justus
Hello all, was the latest DEV binding, going to the new OH 5.1.4?
In the release notes I cannot find it.
I can‘t say, which changes were backported
Any Update on this issue, was the Debug Log not sufficient? Can I provide more information?
BR
Michael
You need to capture a part of the log (where initialization happens or tries to happen) as text, a screenshot is useless. Then, use code fences and paste the snippet inside.
Hey there, it’s been a while and my system setup was shot dead by an update of the Rademacher Smarthomebox introducing much encryption… so I was quite busy.
Did you succeed in cleaning up the websocket connections? Any dev version which would be worth a try in my context?
Did you find some opportunity to investigate the OOM error of the BT Gateway script on Gen3 devices?
I am using this dev binding since a few weeks now: myfiles/shelly/org.openhab.binding.shelly-5.2.0-fixgen2bat.jar at master · markus7017/myfiles · GitHub
Everything is looking good so far on my setup. I also have some gen3 Plugs running, and also enabled the BLU-GW support on one of them. So far so good. Only thing I am seeing is, that my BLU H&T sensors and also my Door Windows sensors are not working stable at the moment. Have to restart the BLU GW Things often, to get updated values from my HT sensors. And also the door windows sensors often tell me that they have the open status, but they don’t. I am still trying to collect data, related to that issues.
(post deleted by author)
I bought a Shelly Gen3 3EM 63T. The device can operate in 3-phase or single-phase mode. In this mode, only 2 channels are displayed instead of 3 after being added to OpenHAB.
Hi, I have 3 Shelly Plug S Gen 3 with Firmware 1.7.3.
They are auto-detected by the binding as “shellyplusplug”, but with missing channels - no power measurements.
Any ideas? Shouldn’t power/energy channels show up and work?
According to the docs, there should be a meter group which is missing here.