I commented on your post in the app-thread. Hope they can fix it soon. I guess they read this forum and can prioritize stabilizing existing devices before adding new features and devices. 
I bought another aqara sensor today, i already have one for over a year, and i now have this issue with no contact with the sensor after successfully pairing directly to homey. The sensor i have that works fine has product-ID lumi.sensor_magnet.aq2 and the new one has product-ID lumi.magnet.agl02. Dnt seem like anybody has found a way to fix this yet? Try to return the sensor and buy another brand?
Pleas use the app thread [APP] Aqara & Xiaomi Smart Home - Simplify your life with a smarter home - #6245 by philipostli
for your questions.
Hi N0rdic
You seem to be having exactly the same issues as me. Yours is a motion sensor T1?
So I am curious. What model Homey do you have?
I have now upgraded to Homey Pro 2023. The âAqara Door and Windows sensor T1â is no longer a problem
Hi guys,
I am new to Homey Pro (2023) and started to integrate my devices in Homey. I added a lot of Aqara door sensors (T1) with Product-ID: lumi.sensor_magnet.aq2.
All of them working properly.
Now I bought other 3 pcs. to complete my installation Product-ID: lumi.magnet.agl02. What should I say, as mentioned many times here, this parts not working.
Aqara app:
all working as expected (status, battery, contact)
Homey Pro (2023):
All connected, but none report status (contact, batteryâŚ) nothing.
Any new insights?
I have the latest Aqara App installed on Homey Pro (2023).
Not sure whether relevant: The aq2 is the non-T1 version, the alg02 the T1 version. Did you add them using the corresponding driver/device tile in the Homey Aqara app? There is a driver for the T1 and non-T1.
to my knowledge it does not matter which âtileâ you use when you add a zigbee device. Homey will use the correct device driver.
My problems with the aqara door T1 devices were on my old Homey pro. After migrating to Pro 2023, all my aqara door sensor work nicely.
@Ernie Have you tried âinterviewingâ your problem device?
1 Like
In that case I donât understand why these different âtilesâ are provided for, to my knowledge they only exist for you to pick the right one (so the app installs the correct driver)?
Again, with a disclaimer, my understanding 
âŚ
The reason to pick a tile is so the homey app can provide you with the instructions on how to pair it.
When I add a zigbee device, I usually choose the âZigbeeâ icon from the âTechnologiesâ section of the âNew Device dialogâ. Homey figures the rest.
1 Like
@SunBeech: tried both, same result 
Did you try interviewing the device?
@ArnarS: could you please explain, what you exactly mean with âinterviewingâ the device. THX
The post is a bit old, but explains âinterviewingâ
Homey developer URL (zigbee) is: Homey Developer Tools
There you get a list of all your zigbee devices. Locate your device and hit the 3dot menu and you can interview it.
Press it once and wait. It will take some time, but you should get a result looking like this:
but it can be tricky with enddevices. they dont necessarily respond (worth the try)
Thank you , will investigate.
Everyday we learn something new, thanks!
Your understanding is correct, Homey will pick the right driver after pairing, based on internal device identifiers.
Thatâs why you can also use the generic Zigbee âdeviceâ for pairing any Zigbee device, as long as the proper app is installed.
The reason you can pick a specific tile is because the developer can then add specific instructions for that particular device, which are shown during the pairing process.
1 Like
Interesting. I was not aware of that. Good to know 
.
The tricky part using that approach, is your comment ââŚas long as the proper app is installed.â.
If I understand you correctly, the device will not pair (or at best as a generic Zigbee device) if you havenât pre-installed the dedicated app.
The benefit of selecting/searching for the specific device when pairing, is that Homey will install the dedicated app (that includes the selected device), if you havenât installed it earlier (e.g. when it is your first device of a brand).
Yes, it will pair as a generic device in that case.
Tried to switch to âinterviewingâ mode, but it seems, that the T1 does not respond.
Allways get a timeout message. Have pressed the reset butten to wake up the T1, but no response.
This is valid for both types of T1 sensors.
So guess there are still changes in the Aqara app necessary to get this devices running properly.
