YoLink LoRa Smart Water Level Monitoring Sensor, Wireless Battery-Powered Float Switch Alarm, Sump Pump Alarm, AC Condensate Overflow, Tank Level, Toilet Leak Sensor, 105dB Siren, YoLink Hub Required

Well made and easily installed. Works effectively and support service professional if required.

Useless,

No se puede configurar por tanto no se puede vincular con la app

Wow! Love this brand. I already have some door sensors to prevent the kids sneaking out at night, and now added a high level sump pump sensor. Works like a charm, texts and alerts on my phone and the unit itself beeps in the basement. I would definitely recommend this product for many different applications.

Parfait pour avoir la tête tranquille et être averti en cas de panne de la pompe ! Je n'ai pas eu de problème avec ma pompe depuis l'achat, mais lors de mes tests les avertissements fonctionnaient bien!

First, it’s important to know this is just the same “Water Sensor 2” sensor as YoLink’s rope-style water leak sensor and their remote cable style water leak sensor. During setup, it gets configured as their remote cable sensor, but the alerts are simply inverted, so that it alerts when “dry” rather than “wet”. Where this is important is in how the sensor communicates and behaves. Because the sensor is, at its core, a leak sensor, it tends to get very chatty if the body of water you are monitoring for level with this sensor has any chop, as in, say, a swimming pool (even one that’s not actively in use.) I didn’t mind this, as I turned off the alerts and was simply intending to use this with a Home Assistant automation to selectively trigger and stop an auto-pool-refill function. However, it seems like this extreme chattiness may be having other adverse consequences in how the device interacts with YoLink’s platform. I don’t have confirmation yet, but I suspect my device’s updates are being rate-limited by the upstream servers. This unfortunately results in the sensor becoming “stuck” in either the wet or dry reading, regardless of what the sensor’s float switch position actually is. And when the rate limiting (or whatever the problem is) finally resolves, if the float switch doesn’t again cross over the trigger point, the sensor will remain in whatever erroneous position. This has caused me to overfill my pool a couple times as I did not realize the issue was occurring. So, if you have a glass-smooth water surface, such as in a closed reservoir or a small indoor aquarium, where the float switch is reliably either on or off, this may work for you. But for anything where the sensor may tend to cross back and forth over the trigger point cintinuously, such as with any sort of automations, this may not be the best solution. I am currently in the process of working with YoLink support on the issues I’m having, and I will update this review with the results. To their credit, they are extremely helpful. Already they have sent me a replacement sensor to see if that would correct the issue (but it did not). I am now awaiting their next response after giving them detailed feedback. Update: within a week of my previous review, YoLink support informed me of a new updated firmware they had available that would allow a delayed reporting interval for water level alerts. In the computer programming world, you might call this a “debounce” capability. With this firmware update, I can specify how long the sensor must continuously register a water exhausted warning internally before reporting it in an upstream alert to the servers. After applying this update, and some back and forth with support regarding some behaviors that still seemed to not be quite right, I can now say it seems that the sensor is performing as intended for my needs in monitoring the water level in my outdoor swimming pool. I am of course still closely monitoring it to make sure it doesn’t overfill my pool again, but I am cautiously optimistic that YoLink has, with this update, corrected the issue I was having. I am really impressed with Yolink’s responsiveness and willingness to help me find solutions here. I don’t know if the minor firmware update they made available is something they had in the works already, or something they added at my request, as it was very much aligned to a suggestion I made that might alleviate the issue. Either way, it was rolled out seemingly in response to my troubles in a very short order. Kudos to them! I am raising my review rating to five stars (previously 3 stars) for now. Assuming the sensor continues to perform as it is now, the 5 star rating will be deserved. If not, I will return again with an update.