Thanks! I got the new version but see no difference. Clicking on "Configure" or "Refresh" doesn't seem to do anything. I don't see anything in the "Events". And the log just has a warning of "configure..."
I'm guessing this is because the sensor isn't turning on it's Zigbee radio to check in. Do you think if I get the sensor wet and dry again that it should report the battery again?
When I changed to the generic moisture sensor driver and hit configure it eventually did check in and configure itself properly. It way have been hours later, but it did it. I also haven’t tried the “fixed” driver yet.
OK, I'll just wait. I held down the button and re-paired it, but the logs still don't really show anything. I would have thought if there was a bug with parsing the battery data I would have seen something in the log, but I don't really know that much about Zigbee or how these devices work. I know my Aqara vibration sensors show up in the logs once per hour like clockwork.
Read my linked post. You just need to short press the button to wake it up.
Out of curiosity, when you short pressed the button, did something show up in the event log or anything? I'm not seeing any activity at all. I also tried long pressing it, it went into pairing mode and I redetected it on the Hubitat -> Add Device -> Zigbee page. But still not seeing a battery update or anything.
I don't recall anything in the log. It will log the battery in 18 hours if it is working.
No luck with the new Hubitat version. I have 4 of these sensors, so I just switched 2 of them over to the Generic Zigbee Moisture Sensor driver and short pressed the button. I'll report back tomorrow if any of the 4 start reporting battery.
So I never got any battery reports from the ones I have as Generic Zigbee Moisture Sensor (no temp). I did get one Battery update from one of the ones I switched to Generic Zigbee Moisture Sensor. So I went ahead and switched all 4 over. Then I got an update from one of the other senors.
So I now have 2 out for 4 working. I'm not sure how to debug this. I guess I'll try factory resetting them and reconnecting again. Very frustrating.
I'm seeing the same issue with battery reporting. I paired 8 sensors some 2 weeks ago and some a month ago all using the generic moisture sensor (no temp) driver. None reported any battery levels since an initial reporting when they were installed.
I too updated to 2.3.4.138 and experimented with changing the driver on one to Generic Moisture Sensor. It reported a battery level after about an hour. I am now testing the Generic Moisture Sensor with temperature reporting set to hourly (even though the unit doesn't report temp). We'll see if that triggers a battery check.
I did see that on the device page under State Variables, each of mine has a variable called lastBattery with a value like 1674002676. I determined this value is when the battery level was last reported expressed as the number of seconds since 1/1/1970 midnight GMT.
I'll also mention that using the (no temp) driver may mean the device isn't actually working. I went and put one of the non-reporting ones in water and while it beeped, it didn't notify hubitat. I then did yet another factory reset and repaired to the Zigbee network. It immediately reported the battery and started reporting when it was wet again.
I still have one more device not reporting. I'll need to crawl up in the attic with my laptop to go debug what's going on with that one.
That's interesting; when mine weren't reporting battery with the (no temp) driver, they were still working correctly for reporting when getting wet (I tested them specifically for this).
I have 14 of these, they paired with Generic Zigbee Contact Sensor (no temp). Never had a problem with battery reporting or an event being reported to hubitat. Maybe using that driver may help? Just my two cents.
Your moisture sensors paired as contact sensors?
Yes, over a year ago now. No problems.
I followed the instructions in the linked post and all 8 of mine have been reporting battery levels for a week or so. The only I noticed was that when pressing the button, the led light didn’t blink on most of them.
Checking in with all you Linkind water sensor users. I purchased qty 4 of the model ls21001 sensors. They use AA batteries. Like that they sound and flash a local alarm on the device but also work with Hubitat.
However, mine stop reporting status to the hub within a day of pairing them. No events in the log, no status, etc. But they still work -- if they detect moisture, the devices immediately report to the hub and any corresponding rules or alerts kick-in.
This is a mostly acceptable situation, but would prefer that the devices also check-in periodically so I know they are connected. Anyone else experiencing a similar situation? If yes, is there a solution for getting the Linkind devices to check-in?
Yes, I had four of these that worked quite well, including reporting in regularly, on my old C-4. After I migrated to C-7, which shouldn't even be relevant, they stopped reporting and I'm pretty sure I was using the same driver (I tried several). They still reported wet/dry, but without assurance that the device was actually going to work, I trashed them all.
I reached out to Linkind to see if they had any suggestions, but they wouldn't give me the time of day without providing my Linkind hub ID. In fairness, they are clear that their devices are only supported on their hub.
This thread may have some related comments.
My Linkind Contact and Water sensors are working well on my C4 with 2.3.5.152. AFAIK the Linkind water sensors are no longer availalable.
I have a C8 and C5 hub. I assumed the Linkind sensors would work better with the C5 since my C8 has some issues with older/obscure zigbee devices like iris v1's.
They detect water, work great, and seem to be reliable. But I don't like being "blind" to their status for something as important as a water sensor. I can test them by getting them wet every six months or so but that's not ideal.
Yes, I liked them for what should be extremely long battery life specifically to put them into hard-to-reach nether regions of my crawl space where no one but camel crickets and snakes are comfortable. But if I have to test them manually, there's no point.
Download the Hubitat app
