Shelly Binding

use the DEV build, Outdoor plug was just integrated

Make sure you have the latest test dev build. Multiple people reported that the problem is fixed

I noticed that my Shelly Plus2PM always reports a new firmware even if there is only a beta firmware available. Is that on purpose? I usually don’t upgrade to beta firmware. I’m on a dev build (maybe a week old).

I use this dev build:

https://github.com/markus7017/myfiles/blob/master/shelly/org.openhab.binding.shelly-4.3.6-SNAPSHOT.jar?raw=true

I’ve double checked, md5 checksum is the same

I’ve also tried to clearing the cache, but to no avail. Is there anywhere another version?

maybe I need to recompile the 4.3.6 build, stay tuned

does somebody has a Shelly Sense or the original Shelly Bulb? I need the model IDs (output from http://device-ip/shelly)

If you are adding model ids. I mentioned a few month ago, that shelly pro 2 is recognised as unknown. I added it manually as a pro2 and everything is working fine. In the autodicovery the unknown device still appears.

Here is the output of my shelly pro 2:

{"name":null,"id":"shellypro2-a0dd6c9f151c","mac":"A0DD6C9F151C","slot":1,"model":"SPSW-202XE12UL","gen":2,"fw_id":"20250318-152137/1.5.1-g01dd7ff","ver":"1.5.1","app":"Pro2","auth_en":false,"auth_domain":null}

I think, that shelly changed model ids perhaps in newer versions.

Thank you for your great work!

I have a Shelly Bulb Duo. Not sure if this helps you

type: SHBDUO-1

I can also confirm that I have no more websocket errors with the latest DEV build on the Shelly 1 Gen4 with external temperature sensor! Good job!

Here’s my original shelly bulb:

{"type":"SHBLB-1","mac":"DC4F223CC329","auth":false,"fw":"20230913-111639/v1.14.0-gcb84623","discoverable":true,"num_outputs":1}

Hope it helps

this is already fixed, PR is almost done
Currently Iā€˜m adding Plus 1L, 2L, Shutter
The original Pro 4PM (not 4Pro) was also not discovered
Another PR adds the Plus and Pro Dimmers
and another BLU Wall Switch 4 and BLU RC Button 4

Hi, do you have an idea when the official 4.3.6 would come out with this update ?

I wonder after 10 months there is still not a solution. I have seen HomeAssistant does support it, which means it should be technically possible also in openhab. Can someone give me a hint how I can implement in the source code the other 3 keys? Where is the fastest and best way to start?

Doesn’t this post (Shelly Binding - #4594 by markus7017) describe a solution?

Ring the bell: openHAB 5.0 is coming soon

I did a major updated of the DEV Builds

  • Support for Plus & Mini Gen 4, incl. new the Plus 2PM G4 and Plus Strip 4
  • Support for Plus 1L, 2L, Shutter, EM, 3EM-63 (T and W models)
  • Work arounds for firmware 1.6.1+
    • status updates with component id == null
    • Avoid exception on mDNS announcements incl. blanks (firmware 1.6.1+)
  • Discovery refactored - thanks a lot to @jlaur and @lsiepel
  • Devices will now be discovered by model id or service name (this increases the chance that a new hardware revision does not require a binding update)
  • Fix for Plus Pro 2 discovery & init (@alaub81 fyi)
  • Fix for Pro 4PM discovery

BREAKING CHANGES:

  • thing-type shellspro2-relay was renamed to shellypro2
  • thing-type shellyplushtg3 was renamed to shellyplusht (@wborn fyi)

DEV builds are available for 4.3.6 (@tom_il ) and 5.0.0

NOW WE NEED YOUR HELP
Please install the binding and check if all your devices are discovered, initialized and function properly. Even tests look good there could be also side affects - help to harden the binding before 5.0 gets released.


5.0.0-DEV | 4.3.6-DEV | README | READMEbeta
Avdanced Users | Shelly Manager | Bugs/Features | API Doc
Note:

  • The DEV build is always newer than the version in the official Distro or Milestone builds.
  • 5.0.0 build might be newer than 4.3.x

The is more to come, but we hadn’t the time to get that into 5.0

  • Support for Plus (G3, DALI) & Pro Dimmers (1PM/2PM)
  • Support for Shelly BLU Wall Switch 4 & Shelly BLU RC Button 4

Which ids do you mean? One Note: You are very welcome to contribute, just checkout the binding and start working on every fix/extension, I could assist the review.

2 Likes

updated the DEV builds once again to reflect latest merges to the main branch

Updated this morning three system to the build from yesterday. And then just right now to the lastet
version from this morning. All system are up and running with the 4.3.6 binding.
And I cannot see any issue with the websocket / 1.6.1 issue.

Very, very good job @markus7017 . I’m havy impressed, that also the new brinding contains
the new Plus 2PM G4, which is a couple of days on the market. Great!!

Then let’s cross the fingers, that all changes, fixes, etc will work in 5.00 we upgrading from 4.3.6 to 5.0.0 :slight_smile:

I updated to 4.3.6 on openHAB 4.3.5. it’s working now, after rescanning it is recognised as pro2. Thanks! I will now test all other stuff! and also updating from Shelly Firmware 1.5.x to 1.6.2.

Good work so far @markus7017 !!!

First finding with 4.3.6 DEV Build and Shelly Pro3EM (Firmware 1.6.2)

2025-07-14 12:20:28.434 [WARN ] [helly.internal.api2.Shelly2ApiClient] - shellypro3em-9454c5ba76b8: Unknown API value 'triphase' (map data={light=white, rgb=color, rgbw=color, cover=roller, switch=relay}), please create an issue on GitHub

I deleted the old thing and added it from auto discovery again. Values are shown correctly. It seems just this warning message.

Should we open tickets, or do you want to have the issues here in the forum?