I have several Aqara water leak sensors installed throughout my house. Recently I’ve started getting “Offline” notices for some of the sensors through Basic Guard. From what I can tell, the offline period is short and temporary: the sensor comes back online on its own shortly after.
My setup: two Aqara hubs, positioned to give good coverage throughout the house. Each leak sensor is connected to whichever hub is physically closest to it.
Has anyone else run into these brief offline notices with their leak sensors? Curious whether this is a known Zigbee/mesh quirk or something specific to Basic Guard’s monitoring. Any insight appreciated.
Hi there.first you should check your internet make the hubs to just use the 5Ghz band because if the jump from an band to another that could lead what you experience also make sure the channels are not set to automatically on the 2.4Ghz the channels are 1,6 and 11MHz see what works best and for 5Ghz chose ether the 80 or 160MHz and see how will goes.if this doesn’t help you need to see the distance between the hub and water leak sensor because if there is an 2/3m with an wall or something that can interfere in zigbee signal could lead to showing the device offline.in this case you need an zigbee bridge like and smart plug or led strip sure both from aqara.and the last thing make sure that your hubs are connected to an stable power supply.
Go to the actual device page in the Aqara app and navigate to the logs. Look and see if those match? I’m guessing they don’t. I’m betting your sensors are fine and the Guarding Log is faulty
I know this will sound strange, but I had a similar problem with my water leak sensors and an M3 hub - sensors constantly reporting guard offline/online, but when looking at the devices, the signal strength and battery were great.
I was ready to throw the whole setup in the trash. I found that I was using a USB power supply that was not rated at 2 AMPS and the Aqara documentation specifically stated it needed 2 AMPS. Replacing the USB power with a higher power dongle solved the problem.
My guess was the M3 had enough power for boot and most functions, but would fail when doing some transmissions or processing.
