Not really. Seems like one of the FP300 and one of the W600 started to behave properly, but still one of the FP300 and one of the w600 stop reporting lux, hum and temp (temp and valve position for W600) on a 24h cyclus. No idea why two of them suddenly started to behave. Could be due to app upgrades but also moved a zigbee router during the period (manipulated a bit too many variables in the experiment in eagerness to get things to work). I have now tried to change wifi channel to see if zigbee interference there has an effect. Will absolutely report back if it works, but really doubt that interference would cause a systematic problem like this.
What is the firmware version of the W600?
0.0.0_2848
What do you al mean with the 24h problems? Here two of the four aqara devices started to ignore commands. (Timeout) Nothing changed on my side.
Recently i bought the outdoor plug H2 EU, the aqara native app recognises them but in Homey they appear as a random zigbee device, are these going to be supported by Homey?
Thanks in advance.
Curious about any potential outcomes regarding the 24h bug, which is like clockwork. If it is related to backend zigbee in Homey please let us know, because then we know what needs to be done to finally fix this eventually.
Since I paired my most problematic FP300 to an Aqara hub and upgraded its firmware to the below version (that despite many many many attempts in Homey OTA Updates failed miserably) and then reset it and ran a Repair of the Homey device to re-add it to my Homey… it has since worked pretty much flawlessly.
It’s located at the top of my stairs and I use both the motion/presence sensing and lux light sensor to determine if the LED light strip illumination up the stairs should come on or not. The lux light reading used to get stuck with a stale reading regularly before requiring a Repair of the FP300 to get the light to work (or not work) as the Flow intended. I haven’t had to Repair this FP300 for a week+ now. So I’m going to do this same trick with all my FP300’s connected to my Homey via Zigbee now. The new firmware seems to resolve this issue (touch wood)
You could use any method you have available to upgrade the firmware, whether it be the temporary use of something like Aqara’s fairly inexpensive USB hub M100, or HA, or any other means you have at your disposal… or just be patient and wait for the OTA firmware updates on the Homey app to be fixed (but no idea when that might be as it seems to have gone very quiet about that on here)
The point is, the new firmware does seem to improve the performance and reliability of the FP300’s considerably.
Do you use both Zigbee and Thread devices connected to your Homey Pro?
I do, three Matter devices (all routers/Eve smartplugs), 61 zigbee (12 routers a mix of Aqara plugs, Ikea signal repeaters (no bulbs), Datek and Elko, the remaining 49 are various end-devices).
My network is quite different:
77 Virtual devices
1 Infrared (database) devices
2 Group devices
2 Z-Wave devices (0 Router, 2 Battery, 0 Unreachable, 1 Unknown (Bridge ha ha))
87 Zigbee devices (39 Router, 44 End device, 3 Unknown type device (Bridge, Aqara Hub & an ESP32 test project))
1 Homey Bridges
350 Other devices (a mixture of Virtual devices, WiFi devices, Matter o/ WiFi(8), Matter o/ Thread(20), Matter Bridged(8))
520 Total devices
I still only have a relatively small Thread network, but on my Zigbee network my proportion of routers to end devices is more even split (all my lighting is smart bulbs and LED strips, that are permanently powered routers, along with a bunch of INNR, Sonoff & Aqara plugs). And I hope to replace more of the WiFi smart plugs with Zigbee and Thread replacements in the future to further sure up my mesh.
I’ve just started experimenting with ESP32 development boards, for Zigbee routers and smart displays…
I will try to add a couple of more zigbee routers, but to be frank I doubt that it will have any effect to this very systematic 24h issue I am experiencing with (now) 1 of the FP300. Mesh issues would probably cause more random issues than a systemtic 24h stop of reporting on hum, temp, lux (but not for presence and pir which work fine). The WR600 and remaining FP300s with issues magically fixed themselves.
But it could also be argued that having a problem with only one of a number of the same devices that are all using the same code (code that is static and fixed until you update the app, unlike RFI and EMI that can be consistent or vary wildly, but that you can’t easily see) would mean it was equally not the app.
If it is only one of a number of the same type of devices, it is more likely environmental than software. Therefore strengthening your mesh network in the area of the problem sensor would likely help, wouldn’t it?
Thanks. Will for sure try.
There is a small bug that came to life in the latest test .21 version . The battery buttons no longer work on a single keypress . Neither the a button is pressed 1x or the button is pressed with the scene . The 2x 3x en 4x pressed do work .
It’s the lumi.sensor_switch.aq2
Tested on multiple buttons and 2 homeys . Rollback to .20 solves the issue . Switching back to.21 the bug is alive again
An aspect you forget here is that PIR and Presence continue to work throughout. The issue described only affect the remaining sensors not those two.
Earlier (during this summer, june I think I was one of those nagging about these issues also then) the 24h bug also affected pir and presence in zigbee, but was fixed for those two by @TedTolboom in code with great help from Ken_Hansen. I wonder if this could be part of the same pattern?
A hypothesis I have is that the same fix should have been applied to the remaining sensors in the FP300 (and potentially other Aqara devices) as well.
It is really confusing that it is so systematic and still just affects some and not all devices.
But I guess a stronger zigbee network cannot hurt anyway, so will absolutely try that.
I’ve a unique focus on details. Please believe me when I say I did not forget that aspect at all. The FP300 has separate triggers and reporting mechanisms for the two different groups of sensors you mention. And you may wish to double check the settings for the reporting of the three sensors you mention. As I have found on more than one occasion, that the reporting interval has changed, without my express action. I can’t comment on whether that is down to Homey, the Aqara app on Homey, or the FP300 itself (ie it’s firmware) that is too blame. But a number of times I have set one to Optimal or High frequency, only to come back a few days later to find it set to custom.
Whereas the motion and presence sensors just report whenever they are triggered, and only have sensitivity setting, not frequency settings. Also, the other three sensors seem more fire and forget. So likely more prone to intermittent interference or weak signal.
If it was purely a code thing with the Aqara app on Homey, it would far more likely impact all your FP300’s fairly equally. And also equally impact all users FP300’s. Whereas I have seen a marked improvement in FP300 reliability since upgrading to the latest firmware for them (that’s not to say they are performing perfect, but considerably better). And I haven’t witnessed a 24hr drop-out since either, on the 8 of 10 FP300’s I have updated, including my previously most problematic landing & stairs sensor.
I have done quite a lot of testing on this (as the FP300’s had been the bane of my existence for some time) and given this a considerable amount of thought.
This is how discussions should work on a forum. I tend to learn something new by every post you provide. I am not your typical troll either. Simply, just a good discussion by two semi-oldies with the North Sea and some petroleum rigs in between ![]()
Actually did not know that these were two different systems, that change things quite a lot on my interpretation end. I will get a few more zigbee routers and see what happens. Will feed back by any outcome, cheers ![]()
Best
Hi Trond, you are most welcome. And I wholeheartedly agree, forums work a lot better with polite discussions and exchanges of ideas. I really wish everyone saw it that way.
I would also double check those pesky lux, temp & humidity reporting settings… they have caught me off guard way more times than I’d care to admit ha ha ha ![]()
One thing’s for sure, these FP300’s are way more trouble than they are worth
pesky little trouble makers…



