You’re welcome.
Must say that untill now, my new HP23 has proven to be very stable. Never lost a beat. The Aqara’s continue to work just fine…
cheered too early. After another boot, the aqara sensors appear with the red triangle. No one worked again. It’s a really big sh*t situation
Share the dev view for Zigbee, just the nodes view, also be sure to submit system diag. report to Athom. Also you are on latest RC, correct? Btw also have plenty of Aqara sensors, in total about~70 Zigbee devices and all works fine except of Xiaomi, which I gave up already month ago
Xiaom and Aqara are the same, so it seems a bigger issue 
as you are facing it as well.
I’m waiting on a response from Atom to provide the diagnostics.
“It’s the app’s fault” 
1 Like
Aqara works for me flawlessly, Xiaomi not but since 1 months I’m hooked directly on Xiaomi Gateway for those few sensors. Without more information from your side, you indeed need to wait for Athom indeed…one of the reaction might be as Robert suggested (which was kind of joke as it can’t be app fault)
The Aqara FP2 sensor uses Wifi not Zigbee and is Homekit compatible.
So I doubt it will be supported by this Aqara Zigbee app.
You could install the FP2 through the official Aqara app to Homekit and via Homey’s experimental Homekit support & install maybe to Homey.
In future the FP2 and also Homey will support Matter through (firmware) updates of both devices.
And I have installed it already to Home Assistant and via Homey’s “Home assistant Community” app to Homey 
1 Like
I have 6 awara humidity devices working fine with my ‘old’ Homey Pro’. I received the new one, and wanted to add them, but I cannot find how.
It’s even worse: this morning I found a way to install them and it worked. Now, later today, I wanted to add the other ones, by I cannot remember how I added them. And I tried everything but don’t find a way.
Anybody?
There is a topic for the Aqara App [APP] Aqara & Xiaomi Smart Home - A different kind of Smart Home solution (Zigbee App)
Please use the Search and existing Topic if possible
I have multiple Xiaomi Wireless Mini Switch, since the upgrade from the “old” Homey to HP23 these are broken. I tried to repair them, remove, re-add, reboot but nothing seems to work.
Sometimes I get 1 working, and when I try to repair / re-add another one, the first one is broken and second one works.
ID: cdc89d21-eda9-4962-aff3-e00d76d971f1
Is this a known problem?
2 Likes
Unfortunately yes (and officially no), please sent report - complain to Athom via Homey Pro — Early Access Status | Homey, together with System Diag (app has nothing to do with that).
There were some successes by moving the devices closer, repeatedly pressing the button etc. - the key is to have “network address” visible on https://tools.developer.homey.app/tools/zigbee - eg. myself, I have one Xiaomi occupancy sensor working since day 1, rest of the “Xiaomi” devices (buttons, contact sensors) I had to move to my old Xiaomi v2 Gateway
I have a problem with my Wireless Switch (2018). Could be since I updatet my HP23 to rc110, but not sure yet:
Flows where a scene (doubleclick) was selected as trigger did not run.
When the flow was inspected, the IF card was broken.
I tried removing and adding the switch again. In that case I can select an IF card “when a scene was activated”, but I cannot select which scene.
Is this a Homey rc110 problem or can something else be wrong?
Anyone else experiencing the same problem?
Hi all, Is there any news on the aqara luminance sensor battery problem? Stil have the problem of the battery’s ho alway go from full tot empty every two hours?
I hope that somewone could give some advice for this problem.
I’m having problems with setting up Aqara H1 wireless double switches to my Homey Bridge.
I have 15 switches and none of them connected from the first try. After I tried to add them I get message that it was not successful and try again.
I was very stubborn and after hours of restarting Homey, pulling out batteries from switches, doing the whole process over and over again … I managed to connect 4 switches and they seem to work okay.
Anyone else experienced similar issues?
Could it be because Homey Bridge is not the first class citizen device?
Is there any way to debug this Aqara app and drivers? It looks like that I could find out was the problem by debugging the app.
2 Likes
My bad i saw H1 rocker supported and didnt notice triple rocker wasnt listed and implemented it. Adding as a zigbee device only allow the first gang function and lose out 2nd and 3rd gang.
Any roadmap for aqara H1 triple rocker?
@TedTolboom I’ve this Aqara B1 Curtain, is it possible to add a ‘Timeline’ tab (feature request) to the apps.
Please add Aqara Mini Switch WXKG20LM
"ids": {
"modelId": "lumi.remote.acn007",
"manufacturerName": ""
},
"endpoints": {
"ieeeAddress": "54:ef:44:10:00:6b:3d:bf",
"networkAddress": 24802,
"modelId": "lumi.remote.acn007",
"manufacturerName": "LUMI",
"capabilities": {
"type": "Buffer",
"data": [
128
]
},
"endpointDescriptors": [
{
"status": "SUCCESS",
"nwkAddrOfInterest": 24802,
"_reserved": 24,
"endpointId": 1,
"applicationProfileId": 260,
"applicationDeviceId": 0,
"applicationDeviceVersion": 0,
"_reserved1": 2,
"inputClusters": [
0,
1,
3,
18,
64704
],
"outputClusters": [
3,
6,
25
]
}
],
"touchlinkGroupIds": [],
"extendedEndpointDescriptors": {
"1": {
"clusters": {
"basic": {
"attributes": [
{
"acl": [
"readable"
],
"id": 0,
"name": "zclVersion",
"value": 3
},
{
"acl": [
"readable"
],
"id": 1,
"name": "appVersion",
"value": 7
},
{
"acl": [
"readable"
],
"id": 2,
"name": "stackVersion",
"value": 2
},
{
"acl": [
"readable"
],
"id": 3,
"name": "hwVersion",
"value": 0
},
{
"acl": [
"readable"
],
"id": 4,
"name": "manufacturerName",
"value": "LUMI"
},
{
"acl": [
"readable"
],
"id": 5,
"name": "modelId",
"value": "lumi.remote.acn007"
},
{
"acl": [
"readable"
],
"id": 7,
"name": "powerSource",
"value": "battery"
},
{
"acl": [
"readable"
],
"id": 13
},
{
"acl": [
"readable",
"writable"
],
"id": 18,
"name": "deviceEnabled",
"value": true
},
{
"acl": [
"readable"
],
"id": 65533,
"name": "clusterRevision",
"value": 1
}
]
},
"powerConfiguration": {
"attributes": [
{
"acl": [
"readable"
],
"id": 32,
"name": "batteryVoltage",
"value": 29
},
{
"acl": [
"readable"
],
"id": 65533,
"name": "clusterRevision",
"value": 1
}
]
},
"identify": {
"attributes": [
{
"acl": [
"readable",
"writable"
],
"id": 0,
"name": "identifyTime",
"value": 0
},
{
"acl": [
"readable"
],
"id": 65533,
"name": "clusterRevision",
"value": 1
}
]
},
"multistateInput": {
"attributes": [
{
"acl": [
"reportable"
],
"id": 85,
"name": "presentValue",
"reportingConfiguration": {
"status": "NOT_FOUND",
"direction": "reported"
}
},
{
"acl": [
"readable"
],
"id": 65533,
"name": "clusterRevision",
"value": 1
}
]
}
},
"bindings": {
"identify": {
"attributes": [
{
"acl": [
"readable",
"writable"
],
"id": 0,
"name": "identifyTime",
"value": 0
},
{
"acl": [
"readable"
],
"id": 65533,
"name": "clusterRevision",
"value": 1
}
]
},
"onOff": {
"attributes": "UNSUP_GENERAL_COMMAND",
"commandsGenerated": "UNSUP_GENERAL_COMMAND",
"commandsReceived": "UNSUP_GENERAL_COMMAND"
},
"ota": {}
}
}
}
}
1 Like
I second that I brought one that is now just collecting dust.
As mentioned by others earlier: I have two Aqara Curtain Drivers E1. When I control them, i.e. open them (value:1.00), the position value gets overwritten by 0.02 (2%) after a number of seconds - rendering the tag useless for use in flows. Any ideas what might be done to fix this?
Hello, when will the new door/window P1 sensor be available? Type MCCGQ13LM?
Thanks in advance
