Homey Pro 2019 v4.14.15
Aqara 1.7.1
I just bought some Aqaba water leak and vibration sensor. I also read all this topic (aware about the new requirement and blocked due to update needed by athom in zigbee core) and the list of supported devices (EAN not in the list). All these 2 types of sensors are not recognized (unknown zigbee device) or seen as G10 hue light.
Here the EAN number:
Water leak: 6975833352142
Vibration: 6970504212527
Are both of these references affected by the new requirement ? Or there is a workaround ?
In the mean time I reset my zigbee and unplug all devices to see if other brand are interfering (osram, innr and hue).
Thanks for your support.
1 Like
Only one post up from yours refers to a post from the app developer saying that T1 sensor support is delayed. Your water leak sensors is a T1 sensor, so 1 + 1 = 2.
Your vibration sensorās EAN isnāt mentioned in the first post of this thread, so 1 + 1 = 2 again.
Perhaps there is and nobody is sharing it 
(or, more likely: there isnāt, at least with Homey directly).
The water leak is not mentioned as T1 sensor on the box, on the UM neither on the website shop so yes I read this post.
I know the reference is not there and I said that.
My question was if these equipment are or not affected with the same issue as T1.
A simple answer as Yes without this kind of attitude would have been more constructive.
Thanks for your time anyway and thanks for the main developer for his work
Hi,
is there any opputunity to catch the Aqara T2 Relais to Homey. I only can put it as universal Zigbee-device with 1 Channel.
1 Like
In addition, I am working on adding ābasicā support for the T1 LED strip recently released.
āBasicā support will mean being able to control it as a regular (non-addressable) LED strip.
Adding the scenes / a scene editor, similar to the Aqara app has, will require building a scene editor within the requirements / limitations of Homeyās UI. Still the plan to implement this, but will be added in a later update.
So I cannot change its color or temperature, basically only on/off and dim. But in the app I can change the color temperature. But whatās the corresponding Flow card? None of them workā¦ 
I have the Homey pro with and the latest Aqara app installed.
When i want to add my wireless one button switch When I do this it tells me after installation steps that no app is installed and its not working.
I have added some screenshots I hope this can be solved because now i cant use the switches I have.
That means the device isnāt supported (I also canāt find the Product ID in the first post of the thread, which is another indication itās not supported).
Hi Again,
Iāve recently upgraded to the new homey pro (2023) and migrated all my devices, most of it is working very well except for the following:
- lumi.curtain.hagl04 (Aqara Curtain controller B1, firmware 2019)
- lumi.ctrl_neutral2 (Aqara wall switch double - no neutral)
The weird thing is that they work flawlessly after I initially connect them, but at some point (or when the homey inevitably reboots) they (partly) stop working.
The issues Iām facing:
- CURTAINS: The curtain controllers become āunavailableā and show me the ātry to repairā message when clicked, this ātry to repairā flow never really works, it appears to but afterwards the device is still unavailable.
- LIGHT SWITCH: The āmainā left button keeps working as expected, but the āaltā right button loses sync with homey. If I turn it on through homey, the status update times out after 30s and thus homey doesnāt realise the light has turned on. Also pressing the physical (right) switch is not reflected in homey. This missing feedback loop causes my flows to unfortunately break.
The ātry to repairā flow unfortunately also doesnāt work, which means I have to really delete the device and than re-add it to get it to work properly again (at least temporarily). Which is quite annoying because it also causes the flows and integrations (Homekit + Google Home) need to be reconfigured.
Anyone else seeing this issues? Any ideas on how I could possibly fix this? Thanks in advance for any tips!
Some extra info:
Aqara app version: 1.7.1
Homey version 7.5.2 (1357)
Hello,
Is there any idea if and when Aqara Z1 switches will get supported in the app?
Thanks.
No.
Same problem here, bought a few of these sensors but of course, itās not supported yet - the error wasnāt helpful:
āIt seems that you donāt have an app installed for this device, thatās why it has been added as an unknown ZigBee Device. You can change the device name and icon in the deviceās settings.ā
Any idea of how long this might take? Any possible workarounds? Like buying that Aqara hub/gateway?
No idea, or they wonāt be supported?
Hi, I am migrating from a HP-2019 to a HP-2023ā¦ All is working except for any Aqara devices. Trying to use the migration button to re-add or delete them and trying to add them again, no-go.
Is this brand still working with a HP-2023?
I added a few Aqara devices (temp Sensor, plug, water leak sensor) to a HP 2023 without problems using the aqara app.
Iām facing the exact same issue, except mineās a HP 2019 and H1 double (with neutral) switch. Also get the āDevice is unreachableā message with my curtain controller. Donāt see any ātry to repairā prompts though. I noticed this issue first starting when I had a power outtage. Havenāt figured out any fixes apart from removing and readding the devices. Sometimes removing and re-adding doesnāt work either. Would like to hear if anyone out there has a better fix
1 Like
Hi there,
I get the exact same issue with Curtain B1. It goes away suddently after working 2 or 3 days.
I switched from Homey Pro 2019 to 2023 and problem appeared since.
Anyway great thanks for the guys that developped this great app and for the support.
1 Like
Ok, āgladā Iām not the only one with this issue! Any clue if I/we can provide some logs or something to debug and fix this issue?
Hello, Iām using an Aqara H1 wall switch (EU, Neutral). Within the Aqara app, thereās an option to transform the switch to a remote switch (instead of cutting the power to the bulbs). Does this feature also exist in the Aqara Homey App?
Would love support for the Aqara E1 Mini Switch (WXKG20LM).
Interview:
"ids": {
"modelId": "lumi.remote.acn007",
"manufacturerName": "LUMI"
},
"endpoints": {
"ieeeAddress": "54:ef:44:10:00:6b:85:13",
"networkAddress": 58068,
"modelId": "lumi.remote.acn007",
"manufacturerName": "LUMI",
"endpointDescriptors": [
{
"status": "SUCCESS",
"nwkAddrOfInterest": 58068,
"_reserved": 24,
"endpointId": 1,
"applicationProfileId": 260,
"applicationDeviceId": 0,
"applicationDeviceVersion": 0,
"_reserved1": 2,
"inputClusters": [
0,
1,
3,
18,
64704
],
"outputClusters": [
3,
6,
25
]
}
],
"deviceType": "enddevice",
"receiveWhenIdle": false,
"capabilities": {
"alternatePANCoordinator": false,
"deviceType": false,
"powerSourceMains": false,
"receiveWhenIdle": false,
"security": false,
"allocateAddress": true
},
"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"
},
"ota": {}
}
}
}
}
Any clues to if the FP2 will be supported by this app?
