[APP] Aqara & Xiaomi Smart Home - Simplify your life with a smarter home

Can you still try to remove this problematic sensor and re-include it based on v1.20?
And see if that resolves your issues.

Thank you, I will try that as well.

Unfortunately also with the community app the problematic FP300 stops reporting lux, hum and temp after 24h (almost like clockwork). Motion and presence continue to work fine. Make me suspect local zigbee issues (or the FP300 firmware, which is fully updated) and not the Homey app(s) per se. Unless both apps have the same issues. I will try to move a zigbee router or two and repair the devices in due course. I re-added one of the other problematic ones to 1.20, but do not expect that to change much (will know for sure in another 24h).

I’m wondering if the FP300’s have the same issue with Thread, or if it is just Zigbee that is unreliable.

I am still having problems with lux readings freezing, presence sensor getting stuck on, and the odd FP300 just stopping responding after a few days and needing a repair.

I have 10 connected via Zigbee to my Homey Pro (2026) half of which I don’t seem to have any problems with, the other half have a variety of the above mentioned issues.

I have one FP300 connected to an Aqara M3 hub via Zigbee and then Matter bridged to my Homey Pro… which so far hasn’t had any issues.

I also have a Lafaer LWR02, which has the same sensors, but connects Matter over Thread. And that has not skipped a beat, working flawlessly in my small en suite that was the most problematic room for my FP300’s with massive amounts of false positive detections, freezing presence, loss of lux, temp & humidity readings.

This seems to point more towards Zigbee on the Homey being at the heart of the problem… in my humble opinion.

Thanks @Drako74 Just to add to your comments I intially tried them plenty on Thread. They generally had less communication issues there, but they also got stuck plenty on false positive presence alarms (core reason why I moved over to zigbee). Frankly I remember that @TedTolboom adressed a bug in the summer some time where the entire device (all sensors) just stopped reporting after 24h in zigbee mode. The bugs I am describing remind a lot of that, but just affects temp, hum and lux readings.

As I understand you do not experience the 24h rhythm that I have with this mare, but more randomly?

There also seem to be similar issues translating over to the w600s and seem reproducable across two different Homey apps. A proper enigma.

Hi Trond,

Yes, I haven’t noticed a similar 24Hr pattern, it does appear more random. But the sensors in the rooms less frequently entered the FP300’s seem stable… but perhaps that’s just because they get used less.

I have my W600 TRV’s connected via Matter o/ Thread and they seem perfectly stable. Or at least as far as I have seen, but the weather has only started getting cold here the last couple weeks… before that it was far too warm to have the central heating on ha ha.

I run HA on a Raspberry Pi 5 purely for Music Assistant really… but I do have a Sonoff Zigbee 3.0 USB dongle, so I might try connecting an FP300 to that and see how stable it is if I Matter bridge that to Homey.

Mine have the exact same fault. Like you say it’s like clockwork. Only way to make it work again is to ”repair sensor” I think. Can you restart yours via maintenance page after those 24h has passed?

Any other non default settings you use? I’m not using PIR, not measuring 0-1M and have set lux to update more frequently.

Yes repair gives you another 24h before the entire cycle starts again. Very frustrating. Settings do not matter much, it happens when you leave them on default or thinker with them. Also commands from Homey going to the devices seem to work when this happens (e.g. set temperatures by cards etc on the w600, they keep working). Core issue seems to be the input that Homey gets from the devices themselves after 24h. Strange thing is that it affects just some of the devices and just some of the sensors (temp, lux, hum) internally on the devices.

Which Homey (hardware) version are the both of you using?

I’m running a Homey Pro (2026) with an upgraded CM4 to 8GB RAM and 16GB eMMC… and a Homey Bridge upstairs to extend the Zigbee, Bluetooth, RF & IR ranges.

Version 1.20.0 has been released to stable (changelog) and version 1.21.0 is now available in the test environment of the app store.

Firmware update issues are being investigated by Athom as this is handled by the Zigbee core.

Changelog v1.21.0

Requires Homey v13.2.0 or newer.

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

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 added.
  • 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.

Hp 2023

I have the same issue with my FP300 as @Trond_Nordfjaern .

After pairing it or using the “Repair Sensor” option, it reports temperature, humidity and light levels for around 24 hours, then stops updating and gets stuck on the last reported values.

It used to also stop reporting movement/presence after around 24 hours, but that issue was fixed with one of the app updates.

I’m using a Homey Pro (2023).

Let me try something in v1.21.1…

Requires some Halloween brewing, so release after the weekend.

Homey PRO 2023

Hi. The try to update firmware on smart plug EU but did not work from V22 to v45.

I removed the device, restart homey, but always error with updating the firmware. Any ideas?

@TedTolboom I think the 24h issue is gone from my FP300s, which is fantastic. I am not completely sure that it is due to app changes or me changing some things in my zigbee routing network (manipulated too many variables in eagerness to get things to work). If anything was done in code for FP300 readings in recent revisions of the app, can those be replicated for W600 which still tends to lose sync of temp on Homey vs what is read on the physical device after about 24h? Would also cross check for this 24h issue across all devices included in the app. It is annoying, complicated to detect and replicate, and needs to die :slight_smile:

FP300 presence detection unreliable since 1.20.0

Homey Pro 13.5.3, Aqara app v1.20.0, 5 x FP300’s over Zigbee on firmwares 0.0.0_5841, 0.0.0_5842, 0.0.0_5234. The in-app firmware update fails as noted in the thread, and the version stays at current.

Presence regularly stays off while the PIR keeps firing. A few examples below

Office: presence off 23:21–03:12, while motion fired 13 times
Bedroom 1: presence off 22:25–04:35, including 25 minutes of continuous motion
Bedroom 2: several motion events, including 15 minutes continuous, without presence

When presence does trigger, it often clears after 20–60 seconds. Before about 1.20.0 Oct it held normally. Could the new “active check” on presence that hasn’t cleared after 15 minutes be resetting it prematurely?

Hi

Update: i fixed it by removing and adding the devices. Luckily it are only 3 devices. Stil I would like to know the probable cause

I just updated to firmware 13.5.3 and now all my aqara devices don’t work anymore. I have three H2 EU (2 button).and one h1 eu. All.dont seem to react. Luckily the are also used by hand.

Is this a know bug and if so, how to fix?

My homey is a 2016 model with firmware 13.5.3 and aqara version 1.20.0

Are you still free from the 24h problems? If so, any more thoughts of what could have been the solution?