So, I updated my device to new firmware version like 3 days ago. I moved from 0.5xx to 0.6xx, I can’t remember the exact numbers in the official schematics, but my HA lists it as 0x0000412a. I connect using Zigbee network, and in the last 3 days since I updated, I’m having issues with my device. It stops responding, and it doesn’t seem to be a problem with my network itself, because the device doesn’t flash hen I press the button to wake it. It’s completely unresponsive until I hold the button for 5 seconds (even pressing the button 10+ times has no effect), when it goes into pairing mode, after re-pairing it, it works for about another day, and then it happens again.
2 Likes
@erpatr3 Hey there! Thanks for sharing the details about your FP300 firmware update issue. That sounds frustrating when a device becomes unresponsive after an update, especially when it keeps recurring every day or so.
Based on similar Zigbee device troubleshooting experiences, here are some steps you can try:
Quick Troubleshooting Steps:
-
Upgrade gateway and app - Make sure both your Zigbee gateway and Aqara Home App are on the latest versions, then try re-adding the device.
-
Check device distance - The distance between your FP300 and gateway might be causing weak signals. Try moving the device closer to the gateway during pairing.
-
Power cycle the device - For your FP300, you’re already doing the right thing with the 5-second hold to reset. Just to confirm: pressing and holding the reset button for 5 seconds should reset network settings and re-enter pairing mode.
-
Check gateway device limit - Verify if your gateway has reached its maximum number of connected devices, which could cause connection drops.
-
Try different gateway - If you have another gateway available, attempt connecting the FP300 to that one to rule out gateway-specific issues.
Important Note: Since this appears to be a firmware-specific issue (0.5xx to 0.6xx), and the problem recurs even after re-pairing, this might need deeper investigation from the product team.
If the problem persists after trying these steps, I’d recommend reaching out to Aqara support with a short video showing the issue. This will help them better understand and investigate the firmware-specific behavior.
Contact the Aqara Home App Customer Service Team (Profile> Help & Feedback > Customer Service) or scan the QR code:
This will be more efficient. If you do not have an Aqara Home account, please click here to create a ticket.
This information comes from community discussions and user experience summaries and may vary by environment. Please verify carefully.
Hope this helps get your FP300 back to stable operation! Feel free to update us on how it goes.
Home Assistant? Read this:
https://www.reddit.com/r/smarthome/comments/1ttf4n4/comment/op59gfk/
In Zigbee2MQTT, you can look at the “last_seen” attribute to track when it went quiet. You could also set up a Z2M alert in HA to send a notification as soon as it drops for tracking frequency of the drop.
I’m actually using ZHA with a custom quirk. It worked normally until the last update. Ever since then, the pir and presence seem to stop reacting after ~24 hours after I paired the device. I just checked, and when I turn the light on, the luminance is reacting. But presence/pir was last detected an hour ago.
LQI is 235-255, RQI is -50 to -40dBm and on the map, it seems to be connected to the closest light switch as usual - another Aqara, which is nearby, and it always worked. When I turn the light on, the “last seen” is updated, but when I walk in, trying to make the presence triggered, it doesn’t. Changing any settings isn’t synced to the device, even if I make it react by turning the light on and off and waiting for the reaction.
On rare occasions when it would stop responding on the old firmware, pressing the button once would fix the issue, and the device would respond to it by flashing blue, now pressing the button has no reaction, which makes me think this is a firmware issue, not quirk or coordinator/network. Hitting “reconfigure” doesn’t work either, or more precisely, it shows as “success” after a while, but the clusters aren’t populated.
When it stops responding, holding the button for exactly 5 seconds doesn’t always work - I needed to hold it longer, or try 2-3 times. Once I powercycle the device, pressing the button makes it immediately flash blue light again, and I can change settings.
And then reconfiguring populates:
2 Likes
Hey, that 24-hour pattern is a really useful data point — and your signal numbers are excellent (LQI 235-255, RSSI -50 to -40), so this definitely isn’t a network or mesh issue.
What you are describing matches a known bug in the current FW release. I would:
- Escalate to Aqara Support (support@aqara.com), they are usually really quick to get back with me (within 8-10 hours normally).
- You could downgrade to FW 5841 but it had false positive issues that 6542 were supposed to fix.
- Set up a Home Assistant “work-around”. Another user set an automation to run every 8 hours to restart his devices. I think a cleaner approach would be to have HA watch for devices that drop out or have long presence states and just restart those devices.
Nice troubleshooting work!
1 Like
I replaced my quirk with an updated version, and luck had it that last night I had a blackout, we’ll see if it stops working tonight or not. I will e-mail the support directly if it goes down again.
2 Likes
I am facing a similar issue with my FP300 sensors in Home Assistant after updating from FW 5841 to FW 6542. Everything works fine for 24 hours, almost to the dot, then the occupancy and PIR sensors cease responding completely. The temp/humidity/illuminance sensors still work and update though, most likely because they don’t belong to the same cluster. The only solution is to re-pair (hold for >5s) with ZHA, but only for it to seize up again in another 24 hours.
I suspect something broke in the manufacturer-specific cluster 0xFCC0 which is where the occupancy and PIR reside. It’s almost like the sensor has an independent 24-hour countdown to self-cripple itself after being paired to a system.
@Outburstin could you share how one could perform a downgrade to FW 5841?
Definitely not due to a weak signal.
In my case, I replaced my quirk with the current suggested one (ZHA)… and the same day I had a blackout, so HA had a hard reset, and ever since then, it works normally, for some reason…
1 Like
I have never performed a downgrade myself but I had read in another forum topic where a user wanted to downgrade and Aqara had asked them to reach out to Aqara Customer Service.
2 Likes