Well drats. I just found this thread after posting a new one for the same issue.
I'm currently on 2.3.4.114. I reset and repaired one of the MS100 motion sensors and hit configure but still get the same behavior.
please post the data section of driver details for both of the misreporting, thanks...
This is one of them. The other one just shows endpointId: 01
Data
endpointId: 01
application:
inClusters: 0000,0001,0003,0500,FF89
manufacturer: TP-Link
model: MS100
outClusters: 0019
softwareBuild:
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.
2 Likes
Sweet! Thank you!
@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.
E.g., this should have updated at 5AM:
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.
They will need to have configure run on them
1 Like
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.
2 Likes
You don't even need to rejoin them. Just open the device page, press Configure, then go to the physical device and press the button to wake them up.
This doesn't work for all devices. For instance, the Linkind leak sensors do nothing when you press the button.
Mike,
So my MS100 sensors are good now, but the Sonoff after I re-paired and ran configure on it dropped down to 7% where it sat all night. This morning it's back up to 200%. 
Well, when I pressed Configure and then hit the button, they did light up the red LED and make me think they were doing something. But the update has not taken effect as they only sent 1 battery value. I'll try resetting and re-pairing them.
1 Like
I installed four of the Linkink water leak sensors several days ago and all reported battery for a day or two, then stopped. I updated to .116 during that time, so it sounds like I have the issue being discussed here.
As these sensors are located in the nether regions of my crawl space that are difficult to access, I'm looking for a solution that doesn't require physical access to the device. Are you saying that switching to standard driver (which I supposed is generic Zigbee water leak) fixed it for you without touching the device?
Yes, but I was writing about my Linkind Contact sensors.
I also have 3 Linkind water sensors on the standard ZigBee moisture driver with temperature disabled that continue reporting battery % with no issue on 2.3.4
1 Like
I changed the driver to Generic Zigbee Moisture Sensor (and disabled temp) on one of the Linkind leak sensors and it reported battery again a few hours later. It had been silent since .116 was installed (which happened 2022-12-02 02:15:46.272 PM EST). This was without touching the device itself.
1 Like
Those refresh (and configure) commands are likely futile with a sleepy zigbee device, unless you somehow manage to catch the device during some other reporting event.
When I switched my Linkind Contacts to the standard driver they took 3 to 12 hours before reporting battery %.
Pleased you have that water sensor reporting battery % again.
I am seeing this on the same driver, Hub FW 2.3.4.117, using Third Reality contact sensors. They are brand new and came with firmware 18 which I upgraded both of them to v31 right away.
This is over the course of a couple of days, some days it logs 100% other days 200%
@mike.maxwell if this is of any use, pressing refresh and configure got these debug logs.
I am not yet a ZigBee expert but it looks like it is reporting it two different ways. Attribute 21 is reporting C8 (200) and attribute 20 is reporting 20 (32 in decimal, perhaps 3.2 volts)?
I think I saw another old thread once with similar issues another TR device, not sure if it was ever sorted out.
UPDATE: I went to check the device data and most of the info was missing from the Basement contact (it was there when I first paired it). I just tried resetting and re-pairing it twice as well, it is still not populating. Not sure if this means anything?
Basement (originally just endpoint was there until I pressed firmware update button):
Closet:
1 Like
