Shelly Binding

[markus7017 (Markus Michels)]

@Kim_Andersen

Shelly Pro 2:
It keeps on telling me there is a new firmware, even though the Shelly app says its running the latest.

The switch is ON if there is a new release OR a new beta firmware

@Kim_Andersen

Shelly EM3:
Yesterday I added the channel #totalkWh - It returns 0.0 kWh

Do you mean on the device level? This is auto-computed from the meter channel. Did you linked them too?

@Hundertvolt1

The Shelly binding (OH 5.1.0) floods the devices with multiple and parallel Shelly.GetConfig requests via HTTP

Please add you observations here:

[Shelly] 1 Gen 3 - Many Shelly.GetConfig requests

I need an OH DEBUG or TRACE log to see why GetConfig() is called frequently
please also attach the device debug log

@Baschtlwaschtl

Now if I switch a Shelly 1 without openhab (ie from hardware-switch or shelly app) the item in openhab isnt synced.. It looks like with the 60sec poll it gets in sync again.

Do you see an exception in OH log? Enable DEBUG
Please create an issue here

openhab/openhab-addons

[markus7017 (Markus Michels)]

@jweschulte

I was wondering if it has been confirmed that the jetty warning (below) is caused by the Shelly Binding and if a root cause / remedy has been identified?

Please report your observations here: [shelly] `jetty.util.thread.QueuedThreadPool` - Stopped without executing or closing null- Eventual OOM Crash · Issue #19902 · openhab/openhab-addons · GitHub
and try this build (should also work on 5.1): myfiles/shelly/org.openhab.binding.shelly-5.2.0-SNAPSHOT-refcleanup.jar at master · markus7017/myfiles · GitHub

[Hundertvolt1 (Nico Steinhardt)]

@markus7017

@Hundertvolt1

The Shelly binding (OH 5.1.0) floods the devices with multiple and parallel Shelly.GetConfig requests via HTTP

Please add you observations here:

I did, including a lucky catch which even immediately caused a reboot

I short, I found that the Shelly binding autodetects my Plug S Gen3 again and again at a rate of about twice a minute, sometimes it’s detected three times in parallel, even if it already has a Thing created, but it also queries unconfigured devices without a Thing, even if it’s already in the inbox.

[markus7017 (Markus Michels)]

let‘s continue in the GitHub Issue

[scheuerer]

OH5.1 and Shelly PlugS GEN3 - Powervalue not more updated.

Hello @markus7017: Today I found out, that my Shelly PlugS GEN3, with FW 1.7.1
was not more able to report the current Power value to my OH 5.1 system.
The Binding which is in use is the production binding.

What was working?

• The Shelly was active and I was able to log on him via WEB-UI
• The value for power was shown, and I was able to switch hin on/off
• On my OH5.1 I was also able to switch him on/off
• The channel “Stromverbrauch” was not more updated.
  
  

After a setting the Item offline and Online, the issue was gone and the current power was shown (see picture)
I have two other OH 5.1 systems with the same configuration, on that value was NOT offline. On thoose system the value was shown.

Not a big stuff, but I switch the Item on and off based on the power value automaticly, and when the value is not show, it will be not switch on and off.

[Kim_Andersen]

@markus7017

The switch is ON if there is a new release OR a new beta firmware

There is no new release. The switch is still on.
I have no idea where to look for beta firmwares.

@markus7017

Do you mean on the device level? This is auto-computed from the meter channel. Did you linked them too?

The channel just state 0.00 kWh.
The meter channels are linked and state fine.

[markus7017 (Markus Michels)]

@scheuerer

Shelly PlugS GEN3, with FW 1.7.1
was not more able to report the current Power value to my OH 5.1 system.
The Binding which is in use is the production binding.

If you have a DEBUG log of the situation I could have a log, otherwise it’s guess work.

[markus7017 (Markus Michels)]

I’m currently focusing on bug fixes and various issues are already in the working.

Please check Shelly Issues if “your issue” is listed and marked “work in progress”. If so the comments for a special build and give it a try (usually they are based on the main branch and include only a single fix/change). If not, feel free to create an issue.

I’m still need more input on jetty.util.thread.QueuedThreadPool - Stopped without executing or closing null. Do you see this error in the openhab.log. If so, please join the discussion in the issue and provide input. The root cause might be a bad design in Shelly Manager, which is fixed in between, but I can’t verify this. If you see the error use the special build included in this issue and give some feedback.

I’ll continue with the most important bugs before adding new features or devices. Best you could do is support on testing and report results. Thanks in advance

[alaub81 (Andreas)]

@markus7017

I’m still need more input on jetty.util.thread.QueuedThreadPool - Stopped without executing or closing null. Do you see this error in the openhab.log. If so, please join the discussion in the issue and provide input.

Is this fix also in the latest dev builds? I know that I saw the messages, but not when it was at least.

[scheuerer]

Thanks for the tipp @markus7017
Next time if this should happens, I will enable the debug mode from the binding, and will try to trace the situation.

Thanks in advanced.

[MathiasK (Mathias Karrasch)]

not sure if I missed it but has there been a fix for this

2026-01-09 08:53:52.778 [WARN ] [helly.internal.api2.Shelly2ApiClient] - shellypro3em-08f9e0e9509c: Unknown API value ‘triphase’ (map data={switch=relay, cover=roller, rgbw=color, rgb=color, light=white}), please create an issue on GitHub

Still get it on OH 5.1

[ErikDB (Erik)]

Read the message a bit higher and check GitHub

[alaub81 (Andreas)]

Hi @markus7017 I got some new Shelly BLU H&T Display ZB. Is there a chance that you will add them to the binding? I know you are busy with bug fixing, but perhaps it is not such a big deal. Otherwise, meanwhile I will try to build a mqtt blu script. Just tell me. Also I can open up a ticket on GitHub for that.

cheers

Andreas

Edit: Just added one as a normal Blu HT … seems to work, only the illumination channel is missing.

[markus7017 (Markus Michels)]

@alaub81

Is this fix also in the latest dev builds? I know that I saw the messages, but not when it was at least.

Please try this build: https://github.com/markus7017/myfiles/blob/master/shelly/org.openhab.binding.shelly-5.2.0-SNAPSHOT.jar?raw=true

[markus7017 (Markus Michels)]

@MathiasK

not sure if I missed it but has there been a fix for this

it’s on the list

[ErikDB (Erik)]

@markus7017, if this is true, is it not unnecessary to delete things when updating a DEV jar?

[Matthias_Kaufmann (Matthias)]

Anything planned / possible for dimmer gen 4?
Thanks!

[dk8pn (Willi Konrath)]

Your device should be Matter compatible. The Matter binding is probably a very good alternative to the Shelly binding for you.

[Nadahar (Nadar)]

It’s a bit sad to see people migrating Shelly devices since Matter is more complicated, has unreasonable requirements like IPv6, and most likely is more limited in what it can actually do. But, with the current state of the Shelly binding, it might be the most realistic path to a working solution within a reasonable timeframe.

[Matthias_Kaufmann (Matthias)]

Same opinion. If Gen 4 is supported by the shelly binding, matter should be a workaround but not the solution. I used MQTT instead - have it working anyhow and was much easier. Anyhow: Also MQTT should not be the solution if we have official shelly binding with native integration.