I could use some help! I have a presence sensor FP2. Works great however the backend is problematic in my case.
For some reason, after 2-3 weeks, events doesn’t appear to be sent over to amazon anymore so none of my routines get triggered even tho the aqara app does show the sensor triggering properly. Firmware is latest as of writing this, same for the app etc anyway the app doesn’t really do much at this point as it is only used to confirm that the sensor is working and that aqara’s systems communicates correctly to it, the rest is between aqara’s servers and amazon and this periodically fails every 2-3 weeks and I have to re-link the aqara skill in amazon to restore functionality.
Anyone have similar issue? I don’t see how anything on my end can have an impact at this point but if any of you have any helpful info for fixing this, it would be appreciated!!
On that same note, I decided to try to move this part of the automation to google home and it works so far (only been using it 2 days so can’t tell yet on the long term). I do have one issue. I have programmed it for the sensor to turn on a few lights when motion is detected and then turn them off after 10 seconds when no motion is detected. For some reason, the automation to turn off the lights gets triggered even tho there is motion/presence and both the google home app and aqara shows motion being detected, it still triggers the lights to turn off anyway. Also, google home is slightly slower than amazon but not the end of the world.
Anyone know why the “no motion detected” automation gets triggered even when there is motion?? (this is limited to google home. The same setup does not cause any problems with amazon)
1 Like
@pearsn_david It sounds like you’re encountering a couple of challenges with your Aqara Presence Sensor FP2 and its integration with Amazon Alexa and Google Home. Let’s address these one at a time.
-
Amazon Integration Issue: It seems that you’ve been dealing with a periodic disconnection between Aqara’s systems and Amazon Alexa, causing routines to stop triggering until you re-link the Aqara skill. This might be related to session token expiration or intermittent connectivity issues on the server-side. To potentially mitigate this, ensure that your Aqara Hub is connected properly within the Aqara Home App, and recheck the integration following the path: Profile > Smart Speaker Service > Amazon Alexa. This ensures that all connections are up-to-date and possibly reduces the frequency of re-linking the skill. It’s a known issue that can sometimes occur due to backend server syncs, so you’re not alone in this.
-
Google Home Automation Glitch: Regarding the Google Home automation, where your lights turn off despite motion being detected, this seems to be a timing or logic conflict in the automation setup. The Aqara Presence Sensor FP2 supports various automations, such as detecting presence or absence over specific durations. Ensure the automation settings on Google Home are aligned correctly with the sensor’s capabilities. You might want to extend the duration before triggering the “no motion detected” event or check if there are overlapping or conflicting automations that could be causing the issue.
For both platforms, keeping the firmware updated is beneficial, as newer updates might address these integration issues. If these problems persist, you could consider reaching out to Aqara’s customer support for more tailored assistance. They can provide further insights or updates on server-side fixes that might be in progress.
I hope this helps, and feel free to share any further developments or solutions you come across!
@pearsn_david I’m sorry to hear you’re running into these integration hiccups with your FP2—let’s break this down.
For the Amazon Alexa issue: The reference information doesn’t specifically cover periodic disconnections between Aqara servers and Amazon, but it’s helpful to hear your experience. If others in the community have faced similar problems, sharing their solutions could be really valuable.
For the Google Home automation trigger: Similarly, the available FAQs don’t address why “no motion detected” might fire incorrectly when motion is present. It’s curious that the same setup works on Amazon, which suggests it could be related to how Google Home processes the sensor data.
Since these specific scenarios aren’t covered in the current reference materials, your best bet is to reach out to Aqara Customer Service for further investigation. They can help troubleshoot the backend communication and automation logic. You can contact them via the Aqara Home App (Profile>Help&Feedback>Customer Service) or by clicking here if you don’t have an account.
Hopefully, the community can chime in with their own experiences too—let’s see if others have found workarounds!
@pearsn_david I’m sorry to hear you’re running into these integration hiccups with your FP2—let’s break this down.
For the Amazon Alexa issue: The reference information doesn’t specifically address periodic disconnections where events stop being sent after 2-3 weeks, even with re-linking. It’s good to confirm your firmware and app are up-to-date (which you’ve done), but since this seems to be a backend communication issue between Aqara and Amazon, it might help to check if other users in the community have experienced similar periodic drops. If you have specific suggestions for improvement, feel free to submit feedback via the Aqara Home App (Profile>Help&Feedback>Customer Service) for further assistance.
For the Google Home automation problem: The reference info doesn’t detail why a “no motion detected” trigger might fire incorrectly when motion is present, especially with the FP2. Since the issue is specific to Google Home, it could relate to how the platform interprets presence data from the sensor. Maybe double-check the automation’s “no motion” timeout settings (10 seconds is quite short—could the sensor’s detection interval or Google’s processing delay be a factor?) or ensure the FP2 is properly integrated with Google Home. The community might have insights here—feel free to share more details about your setup, and others might chime in!
Thanks for sharing your experience—it helps the community troubleshoot together. Let us know if you find a workaround!