does this also affect other sensors? As stated before for me, the wall wall switches (h1, h2, non neutral wired) started to behaviour strangely just after release of the security firmware fix of Homey. That could be a coincidence or not. For some reason they are behaving very unreliable.
I have been digging through the code and also checked the sensors connected to my Homeys (where I have full Zigbee communication captures running in parallel).
As it is not affecting all devices, I believe that it is not related to the device driver (as that would be affecting all devices).
There is one thing that could cause your issues, where I also noticed a lack of updates at one of my test devices.
This issue is caused by the Aqara device not completely resetting to default parameters/settings when the device is included at a controller (Homey), specifically if you have connected it to different controllers. On top of that, an Aqara device will typically report it’s lifeline attribute report more frequently during the first 24 hours after inclusion.
So can you check and update (also if the settings appear to be ok) the specific reporting settings for these capabilities that stop reporting after 24 hours. Secure to press the button directly after saving the settings.
I’m curious if this resolves your issues.
Thank you plenty! I have tried this now and also added three additional zigbee routers to the mesh. Let us see if there is any difference in about 24h.
Is this also applicable for wall switches? H1/H2 non neutral. I have 3 H2 switches and one H1. The seem to lose connection of something else. But not all of them. It seems to be random?
I can’t seem the change reporting settings for these devices.
Version 1.20.0 has been released to stable (changelog) and version 1.21.1 is now available in the test environment of the app store and will become the stable version once approved by Athom.
Firmware update issues are being investigated by Athom as this is handled by the Zigbee core.
Aqara v1.21.1
Requires Homey v13.1.0 or newer.
Check your settings
- Dimmer switch H2: power-off memory and dimming phase were swapped. The settings now show what the dimmer
does: check both.- Light switch H2 EU (4 buttons): one power-off memory for both relays (the right relay setting is removed).
- Wall outlet H2 EU: the toggle power-on option is removed (not supported by the outlet).
New devices
- Power Plug H2 EU (RGB) (SP-P05D, Zigbee and Matter): power, energy, child lock and the RGB indicator light
(colour, brightness, power or energy colour scale)- Shutter Switch H2 EU (DS-K02D / DS-K02E): open / stop / close, position, calibration and the wireless buttons
- Power Plug H2 EU (SP-P05E, Zigbee and Matter): as the RGB plug, without the RGB indicator light
- Outdoor Plug H2 EU (SP-P06E, Zigbee and Matter): power, energy, child lock and the indicator light
- Outdoor Plug H2 EU (RGB) (SP-P06E, Zigbee and Matter): as above, with the RGB indicator light
Firmware updates from Homey
- Wall outlet H2 EU
- Light switch H2 EU (2 and 4 buttons)
- Dimmer switch H2
Fixes and improvements
- Light switch H2 EU and Dimmer switch H2: settings follow the device, new Find device, firmware version as in
the Aqara app, pairing instructions as in the Aqara app.- Light switch H2 EU: new load type setting (normal or smart bulb); a locked relay gives a clear message.
- Light switch H2 EU (4 buttons): on/off state, power and energy update reliably.
- Dimmer switch H2: new indicator light setting.
- Thermostats E1, W500 and W600: new external sensor alarm when no external temperature arrived for ~75 minutes.
- Wall outlet H2 EU: firmware version updates after a firmware update.
- Remotes and switches: a button report delivered twice triggers your flows once.
- All devices: updated Zigbee library: no lost reports while a command is pending, no error answers to duplicate
replies.- Wireless mini switch (WXKG11LM): single presses trigger your flows again (broken in v1.21.0). @MarcoRuiter thanks for reporting
Thank you for the update, much appreciated. I hope Athom manage to find a solution soon ![]()
It’s a mahoosive pain in the posterior this not working, when fixes to known problems are available in new firmware.
Hi @TedTolboom, I noticed that since the last few updates of the Aqara app for Homey the battery level of the T1-variant of the Temperature & Humidity Sensor (lumi_sensor_ht.agl02) is always reported as 0%.
I have several of them and they all report 0%. I have replaced their batteries and performed the repair procedure several times over the last few weeks to no avail; also in your latest version (v1.21.1).
I also have a non-T1 version of the sensor (lumi.weather), for which the app reports the battery percentage as expected.
Any idea what could be causing the misreporting on the T1-variant?
Ahhhh so that’s why I keep getting low battery
notifications for my temp & humidity sensor
I kept meaning to change it, but perhaps it’s just misreading
Good news, one of these actions seems to have fixed my issues. All three previous problematic ones (temp, hum, lux) have now been reporting beyond 24h. Will keep an eye on them, but for now it seems like issue solved. Thanks for all help and suggestions regarding this issue.
@TedTolboom Hi, thanks so much for all your work with the app!
I had issues with stuck motion/presence and upgraded my FP300’s to firmware 6542 via Aqara IOS app. After re-pairing in Homey (v1.20.0), temperature, humidity and lux report normally for about 24 hours, then consistently freeze on all 5 sensors. Presence and motion keep working, but now my lux based flows are broken
Any chance you might be able to look into this?
Please have a read back through this thread, it is all about this issue, and how most of us have now solved it within the settings of the FP300’s.
I did and am aware of the suggested fixes. Unfortunately they dont work for me. Tried changing reporting frequency several times, rebooting, changing again, repair. Only reset/repair refreshes the values but they get stuck after a day or so
What about your Zigbee network, number of permanently powered router devices, and possible interference sources (overlapping WiFi channels, sources of RFI/EMI)
If the latest firmware and app versions are working for most FP300’s, except your FP300’s it would suggest a more localised problem rather than the app, if it was the app causing problems the issues would be more widespread surely?
Thanks for your help and suggestion. I have already been down that route unfortunately. WiFi is on 1/6/11 and Zigbee on 25. There are plenty Zigbee routers near my FP300’s and all five are reporting between 0-2% interference in Homey Dev Tools.
I have to respectfully disagree with your logic. My FP300’s have/had been rock solid prior to version 1.20.0. A firmware update fixed the motion/presence issues I (and several others) were having I 1.20.0, but then the reporting of temp/humidity/lux started failing. I think it stands to reason that 1.20.0 could/should at the very least be considered as the cause. I may have missed it, but I’m not seeing any bullet proof fixes in this thread
When you changed the report settings at the problematic sensors (e.g. from optimal to low) did you remember to push the button on the sensors right after saving to wake them up and make sure the settings were saved? That or the fact that I added three zigbee routers strategically in the area of the problematic sensor fixed a very similar problem for me.
Also, I think this was the order I did things.
- Wait till the sensor(s) stop reporting (hum, lux and temp).
- Repair the sensor(s).
- Enter settings for one or two of the affected sensors. Change report setting to e.g. low for both hum, temp and lux.
- Push button to wake sensor right after saving the settings.
- Wait 24h and check if it stops or continues reporting of hum, lux and temp.
If this does not work, it may be an idea to add a couple of cheapish Sonoff smart plugs around the problematic area (e.g. Sonoff S60ZBTPF). Try the cheapest route first (1,2,3,4,5) as it only requires investments from patience and not the wallet. No guarantee, but this worked for me.
I was one of those users having these problems. Doing a reset off the FP300, upgrading it to the latest version 6542 firmware, then resetting all the different sensor reporting intervals to default and as @Trond_Nordfjaern mentioned pressing the button on the FP300 immediately after saving those settings to ensure that they were actually saved to the device resolved the problem for me.
But as was mentioned previously in this thread, I have a pretty even split of router nodes and end device nodes (approximately 40 of each) which gives me quite a strong mesh. @Trond_Nordfjaern added some more router nodes as mentioned, and this also solved the same issues for him. I can’t speak for others, but I am running the latest test release (linked previously in this thread) and so far it has been stable, for the first time in a long time ![]()
![]()
If you have rigorously followed all these steps and you still have problems, it would help the developer of this app greatly if you recreated the issue and then created a Diagnostic Report, making sure to note your email address and the problem it relates to when generating the report… and maybe post the report ID here, where you can provide more detail.
@TedTolboom I’m having excessive Homey “Offline/Online” cycles every few days, which leads me to believe it may be memory-leak related.
Upon inspection, it seems your app is stair-stepping RAM consumption until the Homey Pro (2026) runs out of resources (causing parallel apps to freak out, CPU spike, and crash around the same time).
FlowChecker pumped out a ton of errors around the same time, telling me that all of my Aqara and Eufy flows are broken (they weren’t).
Attached is the resource graph. It spikes around the times of the Homey panics and is only resolved after a hard unplug reboot. This reliably happens every couple of days.
I could be wrong, but perhaps you’d have a better interpretation of the data? Is there anything else you could use from my end to explore this? Thanks.



