Are you waking the device up before setting the settings, and are you keeping it awake until they are written?
Yes. Also tried after homey (pro early 2023) restart or after disabling other apps like hue.
And how are you keeping the device awake?
How should I?
By pressing the button every two seconds.
I ended up picking up a new Homey Pro 2023 today, and after restoring it from my backup and repairing all the Zigbee devices, that worked perfectly!
I asked, you said âyesâ, so why are you asking?
Battery-operated Zigbee devices are asleep most of the time, they only wake up when something happens (for example motion) or periodically for some housekeeping tasks. They canât be woken up remotely by Homey (because that would defeat the purpose).
So when you change settings for the device on Homey, the device is most likely sleeping and (therefore) not listening to any messages. So you need to wake up the device before sending the settings, and also during the time the settings are being sent (say about 10 to 20 seconds), which is usually done by short-pressing its pairing button every few seconds.
2 Likes
Thx for your advice. I will give that a try.
Please read and follow the advice provided in the advanced settings of the P1 motion sensor:
âBecause this is a sleep end device (SED), short press the button once on the device, to wake it up, before updating these settingsâ
i found a solution that worked on all 3 of my new Aqara T1 Switches (with Neutral), just wanted to post it here if it helps anyone
I have a Homey Pro 2023 and got the error shown in the picture below every time i tried to include the switches, even with the homey placed directly besides them
It seems like Homey is âgiving upâ just a few seconds to early, this is what worked for me, but it requires correct timing
1.Start the search for a new device on Homey
2.Start the pairing process on the switch
3.When it fails, IMMEDIATELY press âretryâ, and if you do that before the switch has ended its pairing process, it will jump out of the inclutsion process on Homey and the switch will have been added.
The error:
3 Likes
This is the same process i did the last few times and sometimes it works and sometimes not, but after some time they stop reporting power (switching still works though).
When is support planned for the Aqara E1 Smart Thermostat ?
1 Like
@TedTolboom.
The link to GitHub repository (under links) donât work - can you provide a new one?
Hello again. I downloaded the 1.8.2 version of the Aqara app, but nothing has happened with my Light switch H1 single rocker with neutral when it comes to power usage monitoring⌠Hope you have some good news soon 
@TedTolboom Is there any plan to add support for the Aqara Dual Relay Module T2 in the Aqara app any time soon?
4 Likes
Good morning
I have exactly the same observation on the power and energy measurement which has been going through 0 for some time.
I turned off the power to the module but it had no effect.
Is there another solution.
Thanks in advance
Let me start with the compliments for this app.
I already have some Aqara products connected to my Homey Pro of 2019 and it works perfectly fine, thanks to the developers!
I bought myself the Aqara smoke detector (Not the homeywell version)
and was wundering if this could be added to the Homey.
I have included the interview of the device.
It would be very nice, if the app could support it.
"ids": {
"modelId": "lumi.sensor_smoke.acn03",
"manufacturerName": "LUMI"
},
"endpoints": {
"endpointDescriptors": [
{
"endpointId": 1,
"applicationProfileId": 260,
"applicationDeviceId": 1026,
"applicationDeviceVersion": 0,
"_reserved1": 1,
"inputClusters": [
0,
1280,
3,
1
],
"outputClusters": [
25
]
}
],
"endpoints": {
"1": {
"clusters": {
"basic": {
"attributes": [
{
"acl": [
"readable"
],
"id": 0,
"name": "zclVersion",
"value": 3
},
{
"acl": [
"readable"
],
"id": 1,
"name": "appVersion",
"value": 19
},
{
"acl": [
"readable"
],
"id": 2,
"name": "stackVersion",
"value": 2
},
{
"acl": [
"readable"
],
"id": 3,
"name": "hwVersion",
"value": 1
},
{
"acl": [
"readable"
],
"id": 4,
"name": "manufacturerName",
"value": "LUMI"
},
{
"acl": [
"readable"
],
"id": 5,
"name": "modelId",
"value": "lumi.sensor_smoke.acn03"
},
{
"acl": [
"readable"
],
"id": 6,
"name": "dateCode"
},
{
"acl": [
"readable"
],
"id": 7,
"name": "powerSource",
"value": "battery"
},
{
"acl": [
"readable"
],
"id": 8,
"name": "appProfileVersion",
"value": 255
},
{
"acl": [
"readable"
],
"id": 9
},
{
"acl": [
"readable"
],
"id": 10
},
{
"acl": [
"readable"
],
"id": 11
},
{
"acl": [
"readable"
],
"id": 13
},
{
"acl": [
"readable"
],
"id": 16384,
"name": "swBuildId",
"value": "2019"
},
{
"acl": [
"readable"
],
"id": 65533,
"name": "clusterRevision",
"value": 1
}
],
"commandsGenerated": [],
"commandsReceived": [
"factoryReset"
]
},
"iasZone": {
"attributes": [
{
"acl": [
"readable"
],
"id": 0,
"name": "zoneState",
"value": "notEnrolled"
},
{
"acl": [
"readable"
],
"id": 1,
"name": "zoneType",
"value": "fireSensor"
},
{
"acl": [
"readable"
],
"id": 2,
"name": "zoneStatus",
"value": {
"type": "Buffer",
"data": [
32,
0
]
}
},
{
"acl": [
"readable",
"writable"
],
"id": 16,
"name": "iasCIEAddress",
"value": "00:00:00:00:00:00:00:00"
},
{
"acl": [
"readable"
],
"id": 17,
"name": "zoneId",
"value": 255
},
{
"acl": [
"readable"
],
"id": 65533,
"name": "clusterRevision",
"value": 1
}
],
"commandsGenerated": [
"zoneStatusChangeNotification",
1
],
"commandsReceived": [
"zoneStatusChangeNotification"
]
},
"identify": {
"attributes": [
{
"acl": [
"readable",
"writable"
],
"id": 0
},
{
"acl": [
"readable"
],
"id": 65533,
"name": "clusterRevision",
"value": 1
}
],
"commandsGenerated": [
0
],
"commandsReceived": [
0,
1,
64
]
},
"powerConfiguration": {
"attributes": [
{
"acl": [
"readable",
"reportable"
],
"id": 32,
"name": "batteryVoltage",
"value": 32,
"reportingConfiguration": {
"status": "UNREPORTABLE_ATTRIBUTE",
"direction": "reported"
}
},
{
"acl": [
"readable",
"writable"
],
"id": 49,
"name": "batterySize",
"value": "CR2"
},
{
"acl": [
"readable",
"writable"
],
"id": 51,
"name": "batteryQuantity",
"value": 1
},
{
"acl": [
"readable",
"writable"
],
"id": 52,
"name": "batteryRatedVoltage",
"value": 30
},
{
"acl": [
"readable",
"writable"
],
"id": 53
},
{
"acl": [
"readable",
"writable"
],
"id": 54,
"name": "batteryVoltageMinThreshold",
"value": 26
},
{
"acl": [
"readable",
"reportable"
],
"id": 62,
"reportingConfiguration": {
"status": "UNREPORTABLE_ATTRIBUTE",
"direction": "reported"
}
},
{
"acl": [
"readable"
],
"id": 65533,
"name": "clusterRevision",
"value": 1
}
],
"commandsGenerated": [],
"commandsReceived": []
}
},
"bindings": {
"ota": {}
}
}
}
}
Ah finally a worthy replacement for the original ones, the honeywell/xiaomi ones are nice but i couldnât find them anymore (only BLE versions). If these can get supported it would be really nice indeed.
This dual relay is also something what I would like to have in Homey Pro. I hope it is going to be implemented soon. Thanks
Hi. I have an Aqara Roller Shade Driver E1. This is connected to Homey only (I do not have an Aqara Hub). The Aqara Roller Shade driver is shown on Homey and I can operate it on Homey without any issues.
The Roller shade driver is also showing on Apple Home app. However, I cannot control the roller shade driver via home app. Anytime I try to operate the blinds via the home app, (e.g. opening) the message âOpeningâ shows on the roller blade icon in the home app until a message saying cannot connect appears.
I have all devices up to date with mode recent firmware and software versions.
Is there any suggestion you may have to help me fix this error?
Many thanks
