Shelly Binding

[markus7017 (Markus Michels)]

fyi: I’m traveling so can’t work on the binding for the next 2 weeks

Some answers on topics mentioned above:

@alaub81

On Startup I can see these two lines in the log:

2025-09-24 10:18:40.389 [INFO ] [nternal.manager.ShellyManagerServlet] - Shelly Manager gestartet und erreichbar unter http(s)://192.168.50.20:8080/shelly/manager
2025-09-24 10:18:40.770 [INFO ] [nternal.manager.ShellyManagerServlet] - Shelly Manager gestartet und erreichbar unter http(s)://192.168.50.20:8080/shelly/manager

I guess you have 2 instances running, uninstall the binding, run openhab-cli clean-cache and install it again

@ErikDB

12:08:17.322 [WARN ] [org.apache.felix.fileinstall         ] - Error while starting bundle: file:/usr/share/openhab/addons/org.openhab.binding.shelly-5.1.0-SNAPSHOT.jar
org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.shelly [249]
  Unresolved requirement: Import-Package: com.google.gson; version="[2.13.0,3.0.0)"

This indicates that you mixed the 5.0 and 5.1 version.

• Use 5.0.2 SNAPSHOT build for OH 5.0.x and
• the 5.1.0 SNAPSHOT build for OH 5.1 SNAPSHOT

@alaub81

One question, I remember, that you changed the blu devices stuff, In my setup I have often the Problem, that blu door window reported as open or close, even if they are not. Are there any changes on this behavior? I have about 8 BLU GW devices and I know, that this behavior came, because sometimes one device is giving the open command to the binding, just because it was two slow to communicate. So after the other BLU GW devices are reporting door is closed, a delayed device tells openHAB that the door is open.

This requires detailed diagnosis. The binding detects duplicates, but maybe if they are delayed for a longer time…

@alaub81

How are the plans for the awesome new shelly devices? Would like to buy the Shelly Power Strip 4 Gen4. And also the new weather station and the new BLU H&T is very interesting for me.

Power Strip 4 and new BLU devices are already supported by the current DEV builds

@alaub81

Websocket error is gone, but the items are not updating as fast as for example the 1pm devices do. So it takes about 1 Minute that the energy values get updates. I can see the problem only with the pmmini devices at the moment. all others seems to get the updates directly. With MQTT I get the updates within seconds.

If the update takes about 70sec then the NotifyStatus processing doesn’t work and the value is updated by a http poll. Check log to verify.

@chilobo

Unknown API value ‘triphase’ (map data={light=white, rgb=color, rgbw=color, cover=roller, switch=relay}), please create an issue on GitHub

Yes, those will be added with an upcoming PR, for now you should ignore the message

@chilobo

Maybe the jar isn’t available any more?

that’s correct, but is it just the log message or is the initialization failing?