Aqara door and window sensor: HomeKit + Aqara Home app works

For some reason, Homey is giving me a headache to connect the Aqara door and window sensor.

Step 1: I connect it into the Aqara Home app :white_check_mark:. It automatically also connects it to HomeKit.

Step 2: I press the reset button until it blinks 3 times, like Homey asks. But then the sensor gets deleted in the Aqara Home app.

The app remains in the screen, no matter how often/long I press it. The Homey is standing next to it.

Can anyone help me out with the steps to get the sensor in the Aqara Home app, HomeKit and Homey?

Thanks in advance :pray: !

No “the” sensor please, there are several models, please specify.
Not all are supported.

.

Why? And how? Your phone hasn’t got an onboard zigbee controller.
And,
You can add the sensor to one zigbee controller only.
So, skip step 1 :x:

.

Again, you can add the sensor to one zigbee controller only.
When you put it in pairing mode, it gets removed from the zigbee mesh it was a part of.
.

When it starts to blink, you’ll have to push the pair button every other second, to prevent it from going to sleep mode, until the device is added to Homey.
Keep the sensor very close, like 1cm, to Homey during the pairing process

.

Pick one regarding to zigbee;
With the Homekitty app, you can have your Homey devices available in homekits.

KB info:

According to your description, I assume that you are using an Aqara Hub and connect the door/window sensor to it. Because you can also use the sensor in Apple HomeyKit, you are using Matter as the connection protocol and not Zigbee.
If you also want the door/window sensor to be available in Homey, you also need to add it via Matter (only available with HP23) and not via the Homey Aqara app.

Hi @DirkG, thanks for that! I don’t have a Matter on this one. But I do have the Matter sensor on other doors. So if I understand correctly, you would add all Aqara sensors in Homey first, and then to HomeKit with HomeKitty? Because I added them to HomeKit first and then to Homey, but they stopped working in HomeKit after that.

But I have Aqara Matter sensors on different locations:

Hi @Peter_Kawa, thanks for all that info. At first I was like: I did all that. But then I put my sensor on top of the Homey and then it worked!

Thanks a lot for that tip.

This is my sensor:

1 Like

That’s not what I said or meant.
But if you want to use the “old” door/window sensor without Matter support in Homey and HomeKit, then you have to add the sensor to Homey and then making it available via HomeKitty app in HomeKit. This is the only option.
Actually you connected the “old” sensor to an Aqara Zigbee Hub and then you want to sdd it to Homey via Zigbee. As Peter has already written, this is not possible.

1 Like

One thing to add for readers who have the same issue:

Before clicking continue on this screen, I had to press the button on the sensor and put the sensor on the Homey and wait for 3 blinks of blue dots. After that, I pressed continue.

For some reason, if I press continue and then hold until I had seen the 3 blue dots, that did not work.

Odd, because only the next screen tells us to enable the devices’ pair mode.
I’d nudge Support about this unlogic “logic” if I were you.

Yeah that is really odd! I had a lot of difficulties and it would really help if they could say: keep the device really close and delay what Homey is doing (trying to pick a signal that is already there). But it is odd!

Keeping the device close to Homey during pairing is a bad idea for Aqara devices. That’s why it doesn’t say that you should.

Hmm ok! I’m interested in the “why?”.

It’s kind of weird that you have to too…

Because Aqara devices will “stick” to the router/controller they initially paired with. If that is Homey (because you paired close to Homey) and then move the device away to a different spot in your home, it can end up in a place too far from Homey to make a (stable) connection, and it won’t work or you’ll have issues. Therefore you need to pair it at the spot where you intend to use it.

2 Likes

Thanks for sharing @robertklep!