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.
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 
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?
Second finding with 4.3.6 DEV Build and Shelly PM mini gen3:
After Updating to Shelly Firmware 1.6.2 Things are getting offline and online again with the web socket error in the UI. Channels are not getting updates. Devices with old firmware are working fine with this DEV Build.
No errors or warnings in the openhab.log file.
If you need more details, just tell me.
Third finding with 4.3.6 DEV Build and all Shelly devices:
I am still getting these Warnings from my shelly devices.
shellypmminig3-54320459a06c 236900 4243235.127 1 1|shos_rpc_inst.c:374 0x3fcce154: duplicate id 'openhab-192.168.1.20'
I know there was a discussion a few month ago. And also I read in some release notes, that this error should be fixed now. Perhaps only in the 5.x release? Perhaps someone can tell me.
yes, it‘s a warning
fix will be included in next dev build
I ran a test over night and thing „survived“ withoit reconnects. However, I have no load attached, so don’t get updates.
please provide a TRACE log and output from http:device-ip/rpc/Shelly.GetStatus
where?
do you have one or more OH instances attached to this device? I could try to use a random numbet.
Did anybody else did some testing with the current builds? Any positive feedback as well as issues are welcome to harden the 5.0 release.
yes, I tested all my devices with the 4.3.6 DEV Build what I can say is, that with 1.5.x and 1.6.2 firmware the following devices are working fine on my side:
Shelly 1pm mini gen3
Shelly Plus 1PM Mini
Shelly Plug S
Shelly 1 mini gen3
Shelly Plus H&T
Shelly H&T gen3 → Things had to be newly created
Shelly Plus 1
Shelly Plus Smoke
Shelly Flood
Shelly Pro EM 50
Shelly Plus 2 PM - Switch Mode
Shelly Plus 2 PM - Covering Mode
Shelly Pro 3
Shelly Pro 2 → Things had to be newly created
Shelly Pro 1
BLU DW
BLU Motion
BLU H&T
no, just one instance, one docker container, one openHAB process. Shall I open a bug ticket?
Will have a look on this again and will provide both.
So I played around a bit. Devices with no load are working, seems that only on an update, the THING is getting offline with this message:
here is the status output of the shelly pm mini gen3:
{"ble":{},"bthome":{"errors":["bluetooth_disabled"]},"cloud":{"connected":true},"mqtt":{"connected":true},"pm1:0":{"id":0, "voltage":238.2, "current":0.040, "apower":3.5 ,"freq":50.0,"aenergy":{"total":35311.345,"by_minute":[0.000,0.000,0.000],"minute_ts":1752559800},"ret_aenergy":{"total":0.000,"by_minute":[0.000,0.000,0.000],"minute_ts":1752559800}},"sys":{"mac":"34B7DA8A1C3C","restart_required":false,"time":"08:10","unixtime":1752559830,"last_sync_ts":1752558593,"uptime":60005,"ram_size":255872,"ram_free":127188,"ram_min_free":112116,"fs_size":1048576,"fs_free":626688,"cfg_rev":21,"kvs_rev":0,"schedule_rev":0,"webhook_rev":0,"btrelay_rev":0,"available_updates":{"beta":{"version":"1.7.0-beta3"}},"reset_reason":3,"utc_offset":7200},"wifi":{"sta_ip":"192.168.60.93","status":"got ip","ssid":"IOt","rssi":-63,"sta_ip6":["fe80::36b7:daff:fe8a:1c3c"]},"ws":{"connected":false}}
and the tracelog, I hope I filtered in a right way:
shellypmminigen3-trace.log (5.8 KB)
Tell me if you need more informations.
Hello and thank you for the DEV version, great job.
I also tested my Shelly devices with version 4.3.6 DEV BUILD. The devices are all running software version 1.6.2.
I can NOT find any warnings or errors in my OH logs.
(In the standard version, websocket warnings kept popping up.)
Here are the few devices I tested:
- Plus1
- 1PM Gen 3
- Plus 2PM
- 1 Mini Gen 3
Best,
Tom
That is specific to the Pro 3EM, because it supports 2 device profiles: triphase and monophase. Those values were not implemented so the binding outputs a warning.
@gravedigger @soylent81 @DrRSatzteil @alaub81 @alexxio @tom_il @lsiepel
Same question to you