I will clarify with Aqara directly… but my impression is that the online version is the one that is able to be linked to one-another and the offline version is not.
I only have the SD-S01E available. In the current Zigbee implementation, you can trigger the siren from Homey, therefore linking the smoke alarm (or intrusion alarm) to the smoke alarms siren…
Not sure if the SD-S01D has the same option or only reports the smoke alarm.
All the version SD-S01D units I’ve come across are marked with Zigbee connectivity, same as the ones I have at home. I’ll double-check the back panel today. It looks like at some stage versions E and D versions ended up being functionally the same, both running Zigbee despite Aqara documentation still distinguishing them as online/offline models…
I checked the model of my smoke detectors and it is indeed SD-S01D with zigbee connectivity.
And it seems that I can trigger the siren with flows in Homey.
It might be that in the Aqara hub the E and D models differ in available functions, and the E version can be linked with others smoke detectors, but in Homey it doesn’t seem to make any difference?
Please H2 support asap…
Yes, I fully support this. I’ve bought quite a few Aqara H2 switches and H2 Dimmer Switches — excellent quality — but I still can’t use them with Homey Pro. The sooner this is supported, the better. Any idea when it might be available?
@TedTolboom you mentioned v1.16.0 with H2 dimmer and switches support, but we are still on v1.14.0 ?
I’ve just released v1.15.0 to the app store (pending final approval from Athom).
This version includes support for the following new multi-protocol Aqara devices:
Support for these devices has been added based on both (!) the Matter and Zigbee protocols.
Matter is only support through the Homey Pro 2023 platform and is supported “out of the light / sensor box”. Matter based drivers can be identified with the matter symbol in the lower right corner of the icon (and in the devices name).
The LED light implementation does not differ between Matter or Zigbee.
The FP300 presense sensor implementation within Zigbee provides the full options, including distinction between presence and motion alarm and more advanced control over the behavior of the sensor (range, reporting interval etc.).
Flashing the Zigbee protocol firmware
To be able to add these devices based on the Zigbee protocol, it requires to flash the device with the Zigbee protocol firmware through the Aqara Home app (iOS / Android).
As also clearly indicated in the inclusion instructions of the Zigbee devices.
No Aqara Hub is required for this action.
In the Aqara Homey app, the new devices are automatically discovered by Bluetooth and an option is shown to continue with Thread (matter) protocol, or to flash to the Zigbee protocol.
The flashing of this Zigbee protocol firmware is quite straight forward.
Once flashed with the Zigbee protocol firmware, it can be added to Homey as any other Zigbee devices.
Dank je Ted
Thank you for the FP300 implementation!
I played all evening with it and it seems to be a lot more responsive than set up through the aqara hub. Although it seems more predictable with the “adaptive sensitivity” set to off and “AI interference detection” set to on (at least for me). But all in all, I’m very happy.
Just a few bugs I noticed throughout the day, not showstoppers, but still I think I should mention:
- The status indicator on the device icon lights up only if the motion sensor is triggered, not the presence (on both “any alarm” and “presence alarm” setting). Nevertheless, the room is correctly marked as “active”;
- The detection range only sometimes works in increments of 0.3, mostly only in steps of 0.6, but it’s a guessing game until finding an accepted value… maybe a simple slider can be implemented here?
- some setting values snap to numbers with 16 decimals (setting the range to 1.8 snaps to 1.7999999999999998 after coming back to the settings, same for temp and humidity reporting interval) ;
That’s all I noticed for now.
Thank you again!
Same here, in Flows I just don’t understand the difference between motion notification, motion alert and presence alert. Why not simply “motion” and “presence”? And when should you use which one?
I understand that it’s a combination of a motion sensor and a presence sensor, so it first detects motion, and then presence remains active until no person is in the room anymore? So it’s possible that the presence sensor still detects people while the motion sensor no longer does.
How is this implemented, and is the simplest option, turning on the lights when someone is present and off when they leave, easily managed using zone activity in a flow?
These are just a few questions I have after playing with the sensor for a while. The indicator next to the icon in Homey doesn’t give me any clarity.
The indicator currently appears to be bugged: it lights up only when motion is detected, not when presence is detected. However, the zone where the sensor is installed still shows as ‘active’ even if the indicator itself isn’t lit.
In your flows, you can base your automation on whether the zone becomes active or inactive. It doesn’t matter if the sensor activates the zone through motion detection or presence detection - the result is the same.
Separated flow cards by ‘motion’ or ‘presence’ is probably only useful if you set the sensor to use only one of the methods and not both (PIR and mmwave) combined.
Hi, who can help me with the Aqara E1 wall switch without a neutral wire (QBKG39LM)? The Aqara app doesn’t recognize this switch.
Thanks. I noticed when testing with the distance function it reports correct. But when limiting the sensing distance in the setting and walking outside of that range it still triggers.
Hi!
Adding a Door and window sensor T1 is no problem, it gets picked up by the Homey Pro (Early 2019). But it will not trigger any of the cards.
I have tried with other magnets from older Door and window sensors, and vice versa - but no change in status.
Anyone experiencing the same issue?
Are you sure it’s not added as “unknown zigbee device”?
This only supports lights, plugs & switches, no sensors.
Hi Peter, it’s not supported, so how can it be used in HOMEY?
thanks for the feedback
Strange. Retested it in my setup (based on the app store version), and the device icon is turning on, based on the setting used.
I can only use a numerical value here (as per Homey’s SDK). As indicated in the help text, the step size is 0.3.
This is a known issue, being clarified with Athom. Shouldn’t affect the operation of the device though.
Will check this one.. seems to be off indeed.
You can try to add it as generic zigbee device. If it doesn’t function, you can share the device details here an request for support for that model.
