Skip to content

Strange problem with motion detection triggered automations

Strange problem with motion detection triggered automations

Recently I had a strange problem with the reliability of the automations determined by the motion detection. I have the following motion detection devices: * 3 Aqara motion sensors * 4 cameras (mixed marks) All motion events trigger occupancy switches, which in turn trigger lights and timers. This worked pretty well for a while, but I started to have inconsistent results that I can’t explain from the Aqara sensors. Example: I can enter the bedroom and HomeKit * will * record movement from both the Aqara sensor and the camera sensor. * Automation * based on motion detection Aqara * will not * trigger, however, while automation for motion detection camera * will *. This is confusing. I can “test” the automation and it works as expected, triggering the occupation (or any other automation I try). It will not always fail, only sometimes and often several times in a row (I wave, I start the movement, I wait 1 minute, I try again). I would understand if HomeKit wouldn’t record the detected motion at all, but since it’s clear that the motion is recorded, I don’t understand why it doesn’t trigger automations based on it. I don’t know how to fix this. I removed and added the devices again, placed the Aqara hub in every socket in the house (apparently it has an excellent wifi connection) and added additional switches to improve the Zigbee signal. Again, however, HomeKit * records motion events, it just doesn’t always trigger * automations *. This seems to be limited to Aqara detectors, but I can’t say for sure that I don’t notice that other automations are failing. Anyone have any thoughts on how to fix this?