Good evening!
I have got myself an aqara wall switch that won’t work with the decoupled mode within homey. It is the H1 single rocker switch with neutral wire. (WS-EUK03). I wanted to migrate this switch over from home assistant (zigbee2mqtt) to homey.
Is this a known problem with aqara switches that decoupled mode doesn’t work?
Also is there anything I can do to make it work?
Kind Regards
Thijs
Hi there,
Is there any way possible that if you set for FP300 the presence detection mode to mmWave radar only that the movement alarm still goes off but then only when the mmwave radar goes on?
This will help make easier integration to the Heimdall app.
By doing this you get 1 device capability. I find the movement alarm way too sensitive, and i cant lower it down because if you change the sensitivity of the sensor you also change this for the presence detection sensor i think…
Disabling the PIR sensor has a serious negative impact on battery life of the device. But I too have problems with the sensitivity of the PIR sensor causing multiple false alarms with Heimdall app. I submitted a suggestion to the app developer to add the option in the app to differentiate between and separately select the motion and presence alarms as triggers, to hopefully solve this shortcoming. I haven’t heard anything back. But maybe if enough people request it, it will get implemented.
It would also be nice if Aqara app could have separate sensitivity settings for the PIR and mmWave radar sensors on the FP300, as the false alarms on the PIR are quite problematic. I find I have to implement workarounds into all my Advance Flows for my multiple FP300s to try and mitigate this problem, without reducing the sensitivity of the mmWave radar also, which causes other problems.
@TedTolboom can you do anything about this? Please
Also @Drako74 what are your fixes? Because i really wanted to see them
It varies from flow to flow, and what I’m trying to achieve… but usually either utilising another sensor, or checking if the FP300’s presence sensor is also activated, or using the Smart Presence app to check if my mobile is connected to my local network. None of them are perfect, or particularly desirable… and I would much rather Aqara fix the problems with the FP300.
Sometimes the FP300’s PIR Is too overly sensitive and prone to large amounts of false positives… other times the FP300 motion and presence sensing gets stuck on, wasting electricity because your devices don’t turn off for hours (or you notice and manually turn them off)… and almost daily one or more of the numerous FP300’s I have around my house need to run a Repair and re-connect it with Homey Pro (2026)
When the single FP2 presence sensor I have in my living room works almost flawlessly… why can’t the FP300’s (of which I have many 
) be equally reliable?
Hello, I am trying to add an aqara fp1e sensor. Every time I’ve tried it, it is getting added as a generic zigbee device. I’ve also read that it is possible that a specific model of the sensor needs to be supported, and that I own a version which maybe is newer and not added yet. @TedTolboom would that be possible?
If anyone has a solution to this problem, or similar problems, what are the fixes you’ve tried?
Extra information: homey pro (2023), aqara fp1e model id: lumi.motion.ac0114
Thank you in advance!
I talked about it with @TedTolboom
He is going to ask also the creators of Heimdall
This is excellent news 
I am extremely pleased to hear… and extremely appreciative you let me know, thank you.
Hi @Neil1, I don’t have an FP1E to try it with, but it is a model that should be supported by the Aqara app:
If you have tried a reset of the device and then add via the Aqara app this specific device, and it still doesn’t work. You should go to the app settings and create a Diagnostic Report to send to the developer, so they can see why it isn’t working for you. You may also want to copy and paste the Diagnostic Report ID in this thread for the developer’s attention.
Im fairly new to all this. Would it work if I used an Aqara hub & linked things to Homey via that? Or do they need to be supported devices to even work that way?
I was wondering if I needed a hub anyway. I have a couple of H2 light switches & the soft buttons can be a bit reluctant to run, I sometimes have to try the button 2 or 3 times before the linked flow kicks in. The switches (& an Innr ZigBee bulb) are connected directly via ZigBee to Homey but, looking at the ZigBee nodes in the developer tools, they all ignore the Homey Bridge that is in the same room & connect to my Homey Pro (2026) in another room. I wondered if that was the cause of the lag.
I’ve powered everything down today - circuit breaker on the light switches, then Bridge, then Homey Pro. Then waited a while before doing the reverse, making sure each device is up & running before the next. Things seemed better but I don’t know if that is a long term fix.
No, the Aqara hub is not yet supported by Homey. Since they use a paid API, I don’t think it will be supported either
Hi Rick,
Sorry to be contrary @smarthomesven, but I have an Aqara Hub M3 and I can totally share Zigbee devices paired with it to Homey via Matter bridge. It doesn’t always support all device functions… but the main functions are supported.
I don’t think all the Aqara hubs support Matter bridge, but sure it is listed in their specs.
Personally I would recommend the Hub M3 if you have multiple Aqara devices, and/or plan to expand your Aqara devices. I’m on the verge of passing 100 Zigbee devices, and my Homey Pro is starting to show signs of struggle… so I plan to share the Zigbee coordinated load between my Homey and Hub M3… all the automations will still be Homey Flows, but a bunch of the Aqara sensors and smart plugs will be Matter bridged from the Hub M3. I have already tested this with a plug, a bulb, a contact sensor, and an FP300 presence sensor (with Light, Temp & Humidity). It’s working well so far.
Also, I too use Innr Zigbee bulbs, and the RC250 buttons. I also have a Homey Pro (2026) downstairs back room, and a Homey Bridge upstairs front room… but also seem to have no devices connecting via the Bridge. They all connect either via a Zigbee bulb or plug, or directly to Homey Pro. I’m hoping reducing the number of Zigbee devices connected to Homey and instead via Matter bridge from Aqara Hub M3 will help resolve that problem.
I have been having the exact same issue. It definitely seems like a Homey integration issue. I assume you were not able to fix this?
My devices are paired to my Homey Pro directly over Zigbee.
@TedTolboom here’s my diagnostic code if it helps fix the FP300 reporting issues.
95b6c188-aed8-47e2-b4c1-8948358e927c
I have a few aqara battery temperature/humidity sensors and a tilt sensor, they all seam to work ok. when i open the aqara app in the homey phone app all the devices show up.
but in developer in the zigbee device section the devices show as unknown and homey thinks they are router devices.
Have you been able to get this working within Homey (without the hub?). T2 sounds like a great option to automate my gate but if I cant (properly) control the Dry Contact pulse option it is no option.
@TedTolboom @kasteleman @Robin @kasteleman Is it possible to to get this working?
Any plans to add new Aqara devices? W600 thermostat and w100 climate sensor?
Hi,
thanks for the great app and integrations, but will there be an integration for the vibration sensor: lumi.vibration.agl01?
Thanks a lot for all the hard work!!!
I’ts the T1 version, know that this model is currently not supported but wanted to know if it will be. THhanks for the answer
Hi, unfortunately not. I intended the same, but no luck.
