Why Won't My Aqara Sensor Trigger Automations Anymore?

Okay, I’ve been scratching my head over this for a few days now and figured I’d throw it out here before I lose my mind. So I’ve got an Aqara motion sensor that was working flawlessly with HomeKit automations—lights turning on when motion’s detected, that sorta thing. Then boom, out of nowhere, it just stops triggering the automations.

The sensor still shows up in the Home app, battery looks fine, and I can even see the motion state change manually. But for some reason, the automation doesn’t fire off anymore. I’ve deleted and re-created the automation, restarted the hub (Aqara M2), even re-paired the sensor. Nada.

I’m kind of new to the whole smart home scene (loving it otherwise!) so maybe I messed something up unknowingly? Anyone else run into this? Is there like a delay issue or stale automation thing I should know about?

Throw me some ideas, anything I should double-check or test? Appreciate it!

1 Like

@AlexaAficionado It sounds like you’re facing a frustrating issue with your Aqara motion sensor not triggering automations anymore. Let’s see if we can work through this together!

Based on the reference information, here are some steps you can try to resolve the issue:

  1. Automation Setup: Since you’ve already tried deleting and recreating the automation, ensure that the correct automation settings are applied. Double-check the triggers and conditions in your HomeKit app.

  2. Sensor and Hub Connection: Make sure the sensor is not placed on a metal surface, as this can interfere with its signal. Also, ensure that the sensor and the Aqara Hub are within a reasonable range to maintain a stable connection.

  3. Battery Check: Although the battery appears fine, it’s worth double-checking. Sometimes a low battery can cause intermittent issues, even if it shows as okay.

  4. Trigger Interval: Aqara motion sensors have a trigger interval where they may not respond immediately after being triggered. Ensure the sensor isn’t in its sleep mode, which could affect triggering automations.

  5. Hub and Sensor Reset: You’ve mentioned resetting the hub and re-pairing the sensor. Ensure that when you reset the sensor, the indicator flashes as expected, and the hub gives a voice prompt—“Normal link confirmed.”

  6. Firmware Updates: Check if there are any firmware updates available for your Aqara Hub or the HomeKit app that might resolve the issue.

If these steps don’t resolve your problem, it might be helpful to share your experience with the community for further insights. Sometimes, other users may have faced similar issues and found unique resolutions. Keep experimenting and feel free to share your progress!

1 Like

Hello,

I’m having the exact same issue. I’m currently talking to their support team, but I don’t think anything will come of it. This app is honestly the worst smart home app I’ve ever used. From what I’ve read on forums, most people use Home Assistant for their automations and don’t do anything within the Aqara app.

The automations worked for a few days—even though I was having some trouble with the thermostats—but then, with no changes made at all, those same automations just stopped triggering. I’ve tried a ton of things, even creating something super simple, but nothing works. It just won’t trigger any automations anymore.

I really regret buying into this ecosystem, but I’m planning to set up a Home Assistant to integrate multiple systems, so I’ll see how it behaves then. Maybe I’ll have more control. Interestingly, everything works perfectly through the Apple Home app.

Hello, welcome to the forum. Please provide a screenshot of the automations that are not working for you.

Hello,

Thank you and nice to meet you.


I also tried a simpler approach: manually adjusting the thermostat, but nothing happened.

Example:

When
Thermostat Bedroom is above 22

Then
Turn off Thermostat.

If needed, I can provide a list of all devices and connections.

Thank you.

Hi, I’m also happy to help.
I have a question right away, is your thermostat model E1 or W600?

This question is asked because E1 has cloud automation when using the condition that you are using (if above the set, if below the set).

I have the W600 connected to the M100 hub. I just received an update for both, and the automations seem to be working now. When I manually adjust the thermostat values, the valve turns on and off as expected.

I hope this solves the main issue, but I’m curious if my second problem is fixed. Over the last few days, even if the thermostat was set to 21°C and the sensor reading was 22.5°C, the thermostat wouldn’t close the valve, and the room kept heating. If automations are working now, I think I can create one to force the thermostat off entirely. Also, adding a hysteresis setting would help prevent the system from frequent cycling.

1 Like

Read the full description of how to switch to Automation 2.0
Be sure to carefully read the explanation in the second part of Lesson 1. This will help you program without errors.

Thank you for the documentation. I’m already using 2.0 and I think I’ve found the issue. Yesterday I received another update for the thermostats, and the two automations for switching the relay on/off are now working. I also added a 30-minute timer for the startup as a sort of protection in case the sensor fails, or to act as a workaround for hysteresis.

However, I’ve noticed there is some built-in hysteresis now; when the temperature was 20.2°C and the thermostat was set to 20°C, the automation didn’t stop until I manually set it to 19.5°C. Still, the logic isn’t quite complete. If the relay doesn’t switch off, the boiler will run continuously for the third radiator (the one without a thermostat) until the water reaches the temperature set on the boiler itself. In practice, it would run non-stop because even though the thermostats close the valves at 20°C, the automation reads that they’ve reached the target temperature. It’s strange.

So, I’m going to try setting them to ‘off’ the moment the Smart Schedule temperature is reached, which should then trigger the boiler relay to stop as well. Thanks for the support and the patience. You really helped me out and gave me the patience not to throw all the equipment out the window! :)))))

1 Like

So I am doing the same with with my house. I have a relay switch which when off turns the Central heating off.

I found the best way to do this is to allow for the radiator to call of heat (turn the relay switch on) if it is not at the set temp.

I then have an automation to check ever hour and turn the relay switch off for the central heating. If any one of my radiators still needs heat the automation to call for heat (turn on the relay switch) happens a minute later. If no radiator needs heat the relay switch stays off. This happens every hour.

Hi, here’s an update after a while. I integrated the Aqara devices into Home Assistant, and the response times and automations really do work. I haven’t had any more issues with the daily schedules or setting the thermostat temperatures. So, the Aqara app is essentially just for updating their devices’ firmware. Other than that, it just takes up space.

However, the Aqara devices never cease to amaze me. I’ve never seen anything worse yet ‘smart’. I was told they have a 2-degree hysteresis, except I wasn’t told that’s only when the devices feel like it. I think the only thing that could give this product a chance is direct valve control from Home Assistant. Besides that, it often happens that one of the radiators is fine, while another one doesn’t produce heat, even if it’s set above the current temperature in both the Aqara app and Home Assistant. It has to be turned off and on again. I think the people in this company care about their customers’ fitness, making them get up more often to check the thermostats or the heating system. Overall, I got used to the problems and that’s it, I can’t change the system now, but I am completely disappointed and wouldn’t recommend these devices to anyone. I set up special notifications for when the boiler starts for nothing but the thermostats won’t open the valve. Oh, and a lot of times I don’t understand why there are different approaches to the same situation. In the same room, if it’s 20 degrees and set to 22, the radiator heats up super fast and everything is fine; under the exact same conditions, it opens the valve too little and only heats part of the radiator, requiring manual intervention to set it to a higher temperature so it opens the valve further. The radiators are bled and cleaned, and the boiler is on the same settings.

I stopped creating support tickets because the answers from the Aqara team are just ‘recalibrate’ and ‘reset’, which I do before contacting them anyway. Otherwise, my only expectations are for future updates, but I’m almost afraid of those too, because I don’t know what else they might mess up… all the best to everyone.