As per the title and apologies if this is a known quantity.
I have noticed since upgrading to OH 3.0.0, from 2.5.4 I believe, that my 4 original Nano dimmers no longer send updates when I use the physical wall switch.
This also applies to 3 original nano switches.
I have since installed the latest firmware upgrade, still no change. Tried both hail cc and basic. Also tried the trick with forced broadcast on wattage change
I haven’t excluded and included yet, as I didn’t feel like unscrewing the wall plates today.
Newer dual nano and brand new single nanos all work as expected.
Strangely, the same items have meta tags for Google Home and report correctly there.
Not really expecting a solution as such, just putting it out there for discussion and to see if anyone else is experiencing the same.
Try deleting the device Things from OH (NOT exclude) and rediscover / add them to get the latest settings.They will keep the same thingid so your Items and rulte will not break.
I did that with one dimmer and one regular, but it doesn’t appear to have helped. I suspect I did this a few times previously also
The only thing it’s really doing here to me is making my overview UI page kind of … not representative of what’s on and what’s off! Not a deal breaker, by any means.
I have noticed that it doesn’t update when the light status is altered via rules/scripts. When I use my Wallmote to turn on/off the bedroom lights from bed it doesn’t update then either. I do think you’re on the right track, my thoughts are also along the lines of it being some garbage data left over from the previous version.
I found out yesterday that the OH3 binding database was about 3 weeks behind the OH2 export due to some repo changes. A PR was merged last night to update to the version in the 2.5 binding. The next snapshot build will have the updates. Perhaps missing database updates are part of the issue.
Awesome, I will likely do a clean install and try again with the snapshot. I assume going fresh with the updated database will solve. I was hoping a z-w-ave 7 hub would get certified for ANZ frequency before I rebuilt, but that looks unlikely.
Part of my original issue that sent me on this path was plugging in my aetoec zstick5 plus into an rpi4 as an “upgrade” to a faster control hub. Didnt realise that the silly stick isn’t compatible with rpi4.
Admittedly it’s an old stick and this problem has been addressed.
Well - until Chris gets to NZ, he doesn’t really know so much about the local scene . However I’m sure that it’s the same in NZ as anywhere else in the world, and the Aeotec sticks are normally a pretty good bet. Currently all sticks use pretty much the same hardware and almost exactly the same firmware, so the reality is there is little difference.
. However I’m sure that it’s the same in NZ as anywhere else in the world, and the Aeotec sticks are normally a pretty good bet. Currently all sticks use pretty much the same hardware and almost exactly the same firmware, so the reality is there is little difference.