Driver send IASZone (cluster 0500, att 0x0002) Reporting configuration.
Device response, unsupported command
So this device will only send periodic battery reports, I don’t know how often it will send them, you can see it in the battery graph in the app, 24 hour graph. If the interval between battery events is more than 2 hours then it will be marked offline when 2 hours or so have passed, and it will be marked online when the next battery event or a wet or dry event is received.
In this example battery events received every 6 h.
So… In order to prevent false OFFLINE reporting and back to ONLINE , in case of devices that don’t support IASZone configuration. I suggest a Hub FW update that check , as you suggested, every 6 hours rather than every 2 hours.
@nayelyz , @Aaron or other staff members can you please elevate this issue to development team ?
Sorry, I disagree with you… These devices usually located in a “Hard to Receive” areas like under sinks, under washing machines or on ceiling under HVAC system tubes where the reception is poor. Even the sensor that you showed have poor reception (-74 dBm).
For now my water leakage sensors report battery status every 50min - 60min . If 3 reports will NOT be received (this can be happen statically) the hub will consider this as OFFLINE.
In my own testing, I found these cheap sensors to be made with poor zigbee chips. They rely on a repeater right near them. Not just any repeater, but a tuya repeater. Once I did that, I didn’t have it go offline. However, having to purchase a repeater increases the total cost and now makes it more inconvenient in terms of finding an extra outlet and ensuring the leak sensor is connected thru the tuya repeater and not any other device.
