@mike.maxwell I checked the events on the device and it shows this - all the events since I initially paired it at 20:54. Just now (22:32) I hit Refresh, Configure, and Refresh, and now it shows 100% (right after pressing the button on the device).
And I'm happy to report the four devices on today's non-activity report are once again reporting battery %. I'll have more definitive information after tomorrow's AM activity report.
Interesting. I was showing 200% so I hit Configure and Refresh. It did change to 100% but that was six hours later .. I guess when it happened to check in.
apparently...
But at lease in this case its contingent on the firmware version...
Also it appears that some are lk, and some LK as the manufacturer.
So the next hot fix should fix those with LK as the manufacturer
The sonoff will need to be re-included to function correctly.
Just factory reset it, then include it again (don't delete it from hubitat)
The TP-Link should report properly after the next hotfix.
@mike.maxwell Did something else change in the Generic Zigbee Moisture Sensor (no temp) driver in 2.3.4.116? Since I updated to that from .115, none of my 8 Linkind Water Sensors have reported battery. They were doing it about every 16 hours. They all stopped since I upgraded to .116 yesterday evening (at 11-30 21:16).
4 of these devices have been doing the update-every-16 hours for 9 months now. I use Device Activity Check to let me know if I haven't heard from them in 24 hours, and tonight they all triggered.
I on 2.3.4.116 and have 3 Linkind Water Sensors that are reporting battery using the "Generic Zigbee Moisture Sensor" driver with temperature reporting = disabled.
ok, I switching one of my new ones to that. But this has been working fine for 9 months until I switched to .116.
And I know it's .116 - only 7 of them came up into tonight's report, because the 8th did it's last battery update just 15 minutes before upgraded to .116 (so it was still within 24 hours). But it's missed it's battery update since.
I had no issues for two years (other than one device reporting 200% battery) with seventeen Linkind Contact Sensors, six using the Generic Zigbee Contact (no-temp) driver, eleven with the standard version with temperature = disabled.
After installing 2.3.4 the devices using the (no-temp) driver version all stopped reporting battery. It was simply easier for me to change the driver, that thankfully fixed the non-reporting issue, than to factory reset and re-pair the devices.
Any future issues with these Linkind devices and I will follow @mike.maxwell 's configure advice. They are "sleepy" devices so the factory reset is perhaps the only reliable method of doing a configuration.
Just re-join them. As @mike.maxwell said don't delete the existing device. Add new Zigbee device, press and hold the button until the LED flashes to pair. It will go thru the join/configure process but using the existing device entry so nothing in HE needs to change.