Shelly Binding

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 :confused:

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 :slight_smile:

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.