In the summer I purchased one ThirdReality Water Sensor to test. I also put a ThirdReality Zigbee Repeater on every floor of the house, so I believe I have great coverage. After testing the water sensor for a few weeks, I was very happy and ordered 14 more. They sat in the box until the other night when I decided to get them going and finish the project!
I started with 3, and was able to get them all to pair/connect easily, and did a firmware update on the devices. I also added them to the Hubitat Safety Monitor. HOWEVER, when tripped with water (and the device beeps), none of the 4 will trigger the Hubitat Safety Monitor. Of course the original one still will. I’ve checked/rechecked the settings on the original vs the new ones and for the life of me can’t figure out why, and would appreciate a sanity check.
HUB DETAILS: C-5, ver 2.4.0.145
ORIGINAL SENSOR NAME: (working):
WaterSensor-L1-MechanicalRoom
3 NEW SENSOR NAMES: (not working)
WaterSensor-L1-Bath-Sink
WaterSensor-L1-Bath-Toilet
WaterSensor-L2-Bath-Toilet
I would suggest not removing them, but do a reset on the sensors that are not working and then pair them again with the hub. They should connect as a previously connected device. Then after saving them, hit config after checking the settings. See if that works. I hope so.
When troubleshooting device behavior in an app, it's usually most help to start by troubleshooting the device behavior itself. In this case, you'd want to verify that the affected sensors generate "wet" and "dry" values as you expect. To do this, check "Current States" on the device detail page/flyout as you make real-world changes to the device (e.g., expose it to water and then dry it).
This helpful because then you'll know how to continue troubleshooting. If you don't see these states update, no app will be able to see those changes, either. This is the authoritative source of information from the device, at least as far as the hub knows. To fix that, the above solution is one thing you can try (a "Configure" command on a Zigbee device like these is another, though I'm not sure this particular brand responds to those except when awake like it will be during pairing, so that's probably just as easy). In any case, this indicates some sort of problem with the device or possibly driver.
That's my guess as to what you'll find -- but without knowing that for sure, all we can do is guess. If you still have problems and that looks OK, you can start looking into the app, but at least the parts we can see in the screenshots above seem OK.
WOW, thanks for the fast replies (3). So grateful for you taking the time to read my long description and graphics. Even more grateful that this solved it. @StephenH your instructions worked PERFECTLY on all 3 devices. I guess I'll have to do this on the remaining 11 as well, but as long as I know how to get them, so be it. Not sure why this happens, but OK.
@bertabcd1234 I 1000% get what you are saying by starting at the updates coming from the device itself (nothing else downline will work if this doesn't). Problem was I didn't know where to look. I did NOT know that that "flyout" that you described, was updated so INSTANTLY. Watching that and activating them, that is super helpful, and will help with other devices as well, I had no idea, so thanks for teaching me that.
@John_Land Thank you for the suggestion, but thankfully I did NOT need the voodoo process, but good to know for the future.
I have nine of them. They work well but do not report battery correctly. Add them to device activity check and set up a notification for each when they fail to check in. They do so every twelve hours. Battery is good for a year or two.
I have 6 of those sensors in my house. They monitor everything from my hot water tank and sump pump in the basement, to the toilets and sinks on the second floor.
I use that app to check for activity. I found the sensors report hourly, so I have the app configured to report if the last report was more than 1:10 hours.
I also have that app monitor the battery levels, but they never change, so that is a waste of CPU cycles.
I find that these sensors very reliable, and I may miss only 1 single report each month, which is likely due to a Zigbee transmission error, since the sensor does report on the next hour without any intervention by myself.
BTW, I love the Activity Checker app as well. It just takes a little trial and error (or log checking) to learn at what interval each device reports at.
