I just updated to OH 2.5.8. Ran several restarts as usual when updating OH. As I saw several exception on all types of DEV jars in add ons, I decided to remove them for now and check what is working with the release versions after this update. As all of my Shellys are updated to 1.8.x, it looks like there are still problems with this Shelly version and the 2.5.8 release version of the Shelly binding.
So I headed to your Installation link and re-read it is necessary to remove all PaperUI things first. I never did this before and frankly, removing 8 things and approximately 30 items based on them frightens me…
Can you shed some light why this should be done and whether this is just to make a comfortable greenfield situation for the developer binding, or whether this is really mandatory?
You do not need to remove your Items, just the Things. When readding the Things, just give them the same ID (Name) as before. This limits the effort to just 8 Things.
There might be changes in the internal Thing structure and/or channel behaviour, that‘s the reason.
When merged to the release, those changes will be announced as breaking changes.
So nothing to be curious about.
if the channel definitions, translation etc are updated it’s the safe way to delete the things re-discover them. OH keeps Thing/Item linkage separate. This gets restored when the thing is re-discovered, so usually nothing gets lets.
You could keep your things, but maybe don’t get all new channels and maybe this causes side effects, so it’s not a must.
As mentioned before there is a breaking change. I removed channels
lastPower2, lastPower3 for meters
and lastDirectiin for rollers
Those channels don’t get updated anymore if they exist. The reason: Those don’t get updated by Coap, even not in version 2
Hi all,
i have a problem with the shelly bindng and the Shelly 3EM with “device_accumulatedWTotal”.
Sometimes the binding give me the Total without “meter1_totalKWH”. shelly_shellyem3_device_accumulatedWTotal = 37.86 shelly_shellyem3_meter1_totalKWH = 12.055 shelly_shellyem3_meter2_totalKWH = 6.325 shelly_shellyem3_meter3_totalKWH = 31.535
In the graph you can see that this problem comes at different times approx over 30 times a day.
I’ve updated to the DEV binding and rediscovered all things. Now all works fine, excepting the tilt state of my 6 DW2. The tilt is calibrated and shows correct values in the webinterface. This value only updates via CoIP if the DW2 is online with the pressed button and LED is flashing. No update on state changes in standard operation.
I’ve found a new issue (Openhab 2.5.8, DEV-Binnding):
When I install a new Binding, Openhab reinitializing the items. After that it resend the last event:
2020-09-02 21:05:06.118 [hingStatusInfoChangedEvent] - 'shelly:shellyix3:68c63afa940a' changed from ONLINE to UNINITIALIZED
2020-09-02 21:05:06.138 [hingStatusInfoChangedEvent] - 'shelly:shellyix3:68c63afa940a' changed from UNINITIALIZED to UNINITIALIZED (HANDLER_MISSING_ERROR)
2020-09-02 21:05:22.254 [hingStatusInfoChangedEvent] - 'shelly:shellyix3:68c63afa940a' changed from UNINITIALIZED (HANDLER_MISSING_ERROR) to INITIALIZING
2020-09-02 21:05:28.887 [hingStatusInfoChangedEvent] - 'shelly:shellyix3:68c63afa940a' changed from INITIALIZING to UNKNOWN
2020-09-02 21:05:29.231 [me.event.ThingUpdatedEvent] - Thing 'shelly:shellyix3:68c63afa940a' has been updated.
2020-09-02 21:05:29.240 [hingStatusInfoChangedEvent] - 'shelly:shellyix3:68c63afa940a' changed from UNKNOWN to ONLINE
2020-09-02 21:05:29.263 [vent.ChannelTriggeredEvent] - shelly:shellyix3:68c63afa940a:status1#button triggered LONG_PRESSED
2020-09-02 21:05:29.267 [vent.ChannelTriggeredEvent] - shelly:shellyix3:68c63afa940a:status2#button triggered LONG_PRESSED
At this time, nobody has made a click bit it send the event and do the action behind.
do I understand this correctly that I have to delete and re-add all my shelly things if I switch to the dev binding? Is this a high effort? And will this still be required if 2.5.9 has been released? I run more than 30 shellies :-/
I would be nice, if you could short explain, what will be the impact when the next release from OH with 2.5.9 will be go live for all our shelly things.
It would be also not nice to delete 20-30 Things and the attched items. This would be more or less a fresh setup for some of us.
I raised the question on whether it is necessary to go through the deletion / recreation of things here: Shelly Binding From the answers I have seen, it looks like an action recommended to work around issues with changed Thing metadata. It is highlighted in bold - which makes it look mandatory - but I’m still not convinced it is really necessary. A sample never proves anything, but for me it worked to replace the release version by the developer version without the deletion / recreation. But i’m open to be convinced I’m wrong.
As I saw several exception on all types of DEV jars in add ons, I decided to remove them for now and check what is working with the release versions after this update. As all of my Shellys are updated to 1.8.x, it looks like there are still problems with this Shelly version and the 2.5.8 release version of the Shelly binding.
But i’m open to be convinced I’m wrong. 