Hi Markus
Im currently on 5.0.0.202506220739 and everything looks fine. Because all worked, I never tried with newer releases.
I’m on holiday until 20/7, I’m afraid…
I surely will do testing on 5M4 soon. Could you provide is a deadline by when you expect us to provide results? Currently very busy but I like to contribute
I’ll update to the latest build tonight and will have a look. Right now I don’t seem to be having any issues.
is there a newer build than the one from 14th of July? I am running 4.3.6.202507140648 binding.
5.0M4 has already been released and should match the last DEV build.
quote from the announcement site:
With this milestone we have reached the feature freeze - from here on, we plan to only merge bug fixes (unless there are strong reason for anything else). Please help us to identify any bigger issues that might still exist in the code base to make sure that the final release is as stable as possible.
Talking about the GA release, there is a slight adaption to the earlier announced schedule for personal timing reasons: While the RC1 is still planned for July 18, the GA release will be postponed by one day to July 21 - I hope you are ok to wait one day more for it. 
—-
I think a bugfix has to be posted for review latest Thursday morning.
I tried the latest snapshot build with a Plug S Gen 3 today and it still worked!
@alaub81 please try this build: https://github.com/markus7017/myfiles/blob/master/shelly/org.binding.shelly-4.3.6-SNAPSHOT-fixminipm.jar?raw=true
- check for minipm with status updates
- check device log for dual id message
I have finally checked with 5.0M4 but to be honest not very intensive. What I can say is that the device status does not constantly switch between Online and Offline like it is seen in OH 4.3.5. I’ve been using 2 devices ShellyPlus2PM.
I just updated to this build. All things came online, I will watch for any anomalies. I do have the following devices in my setup right now:
- shelly1
- shellyplugs
- shellydimmer2
- shellybludw
- shellydw2
- shelly25-relay
- shelly25-roller
- shellyplus2pm-roller
- shellyuni
So far I only noticed that the shellyplus2pm still reports beta firmware as new while other devices only report stable releases as new firmware.
Hi @markus7017
Thanks again for this fast fixing.
duplicate errors still appear, now they are looking like that:
Jul 16 03:10:57 shelly-sd-usv shellyplusplugs-b48a0a1c6420 10887 32255.998 1 1|shos_rpc_inst.c:376 0x3ffda000: duplicate id 'oh:shelly:shellyplusplug:b48a0a1c6420'
perhaps that message belongs to my setup. Any ideas what to do to find out, why I get these warnings?
The pmmini gen3 is working now (with 1.5.x and 1.6.2 firmware). I can see the power values updating and the thing stays online.
The shelly 3em warning is still there, but I think, that’s not included in your fix:
2025-07-16 03:01:04.958 [WARN ] [helly.internal.api2.Shelly2ApiClient] - Shelly Wallbox: Unknown API value 'triphase' (map data={rgbw=color, rgb=color, light=white, switch=relay, cover=roller}), please create an issue on GitHub
I will have an eye on all my other devices running with that build. Again, thank you, very good job!
with this DEV build I got a strange thing. Only one of my Shelly Plug Plus is in the thing auto discovery as new device with a new id, called “usv” instead of I think the shelly unique id.
I configured it as new thing, but the power values are only %.0f and not as all other %.2f. I deleted my old one:
and after a while it shows up also in the THING auto discovery. So I rolled back to that one, which is working. Why the same plug s is also recognized now by the binding? With the DEV Build from the 14th of July it was fine. Could that belonging to your duplicate warning fix?
here is the GetStatus Output of that device:
{"ble":{},"cloud":{"connected":true},"mqtt":{"connected":true},"plugs_ui":{},"switch:0":{"id":0, "source":"init", "output":true, "apower":88.9, "voltage":229.2, "current":0.688, "aenergy":{"total":1197685.531,"by_minute":[1504.765,1488.676,1497.614],"minute_ts":1752645000},"temperature":{"tC":33.7, "tF":92.6}},"sys":{"mac":"B48A0A1C6420","restart_required":false,"time":"07:50","unixtime":1752645000,"last_sync_ts":1752643437,"uptime":1567,"ram_size":253936,"ram_free":129748,"ram_min_free":115164,"fs_size":393216,"fs_free":114688,"cfg_rev":42,"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.25","status":"got ip","ssid":"IOt","rssi":-60},"ws":{"connected":false}}
I’ll look into that later, nothing changed in this release
The interesting part: The NotifyStatus has an id field and src / dst. I changed the code to use a random value for id and derive the src from the thing id. I would expect that the device complains on the id field, but obviously the constraint is the src/dst field. Does not make sense to me, I need to think about that.
Tell me if you need more informations! Or if I should open a GitHub issue.
Not a huge issue anyway, just noticed the inconsistency
Is that permanently or only during discovery?
Is that reproducible?
Did you configured a device name in the device’s setup UI?
If so
- Does the device name has one or more blanks?
- Could you try to remove the “Shelly” act the beginning
it is permanently, exactly every minute.
yes it is reproducible. device name was “shelly-usv” I changed it to it’s real device name “shelly-sd-usv” and it’s gone in the auto discovery and also scanning for new device wasn’t showing it. Very interesting! Thank you!
outdoor plug g3 is now regconized! thank you for your effort!
@markus7017 I can get the Shelly Plus Uni to work. But the Shelly 1 Gen 4 is not listed as a target type. Thanks for your work on this.
did you tried the discovery? Plus 1 maps to shellyplus1 independent from plus, g3 or g4