I have installed a vibration sensor and then I get the message that my battery is almost empty. Strange, because a new battery gives the same result, almost empty.
What could be the cause of this and how to solve it?
** i have put a other (already number 5) battery and that one is working
I have this message when its cold outside. Just ignore it, voltage goes up when its warm again
Same issue here with the Aqara curtains B1, following migration to HP2023 . The curtains is just in front of the HP2023 so i guess this is not related to zigbee signal.
I can remove it and reinstall it and it is back againā¦ but it goes away after 2 or 3 days. Very annoying to repair flow each time. Never had any issue with HP2019.
If somebody has some ideas, it is really welcome. Many thx
Please add Support for Aquara Cube Pro T1 / CPT-R01
Thanks,
Thomas
"ids": {
"modelId": "lumi.remote.cagl02",
"manufacturerName": "LUMI"
},
"endpoints": {
"ieeeAddress": "54:ef:44:10:00:7a:33:c7",
"networkAddress": 6093,
"modelId": "lumi.remote.cagl02",
"manufacturerName": "LUMI",
"endpointDescriptors": [
{
"status": "SUCCESS",
"nwkAddrOfInterest": 6093,
"_reserved": 18,
"endpointId": 1,
"applicationProfileId": 260,
"applicationDeviceId": 259,
"applicationDeviceVersion": 0,
"_reserved1": 1,
"inputClusters": [
0,
3,
6
],
"outputClusters": [
0,
3
]
}
],
"deviceType": "enddevice",
"receiveWhenIdle": false,
"swBuildId": "2019",
"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": 25
},
{
"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.remote.cagl02"
},
{
"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"
]
},
"identify": {
"attributes": [
{
"acl": [
"readable",
"writable"
],
"id": 0,
"name": "identifyTime",
"value": 0
},
{
"acl": [
"readable"
],
"id": 65533,
"name": "clusterRevision",
"value": 1
}
],
"commandsGenerated": [
"identifyQuery.response"
],
"commandsReceived": [
"identify",
"identifyQuery",
"triggerEffect"
]
},
"onOff": {}
},
"bindings": {
"basic": {
"attributes": [
{
"acl": [
"readable"
],
"id": 0,
"name": "zclVersion",
"value": 3
},
{
"acl": [
"readable"
],
"id": 1,
"name": "appVersion",
"value": 25
},
{
"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.remote.cagl02"
},
{
"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"
]
},
"identify": {
"attributes": [
{
"acl": [
"readable",
"writable"
],
"id": 0,
"name": "identifyTime",
"value": 0
},
{
"acl": [
"readable"
],
"id": 65533,
"name": "clusterRevision",
"value": 1
}
],
"commandsGenerated": [
"identifyQuery.response"
],
"commandsReceived": [
"identify",
"identifyQuery",
"triggerEffect"
]
}
}
}
}
}
Please search before posting.
I did. Maybe you can provide a link for what I should have found. There are 3 types of the cube and this one is not supported.
Hi,
i have been trying to add the Smart plugg EU into my Homey PRO.
on/off works well, but energy measurments are at ā0ā.
now, I have searched the forum (Xiaomi Aqara Smart Plug (EU) not monitoring energy?)
that solution does not help me, i have also tried to connect it to Aqara M2 for updating.
i have executed an interview in the developer page, i have deleted the device entirely and connected it as a homey zigbee device as well and no change.
to eliminate possible issue with device i did try to connect again to M2, and check if measurments are visible there, and they are.
Does anyone here have any other hints i can try?
A few weeks back there was experimental 10.1.4-rc.2 available which adds a workaround for certain Aqara devices that will only report to Aqara Zigbee controllers according to changelog.
Homey Pro (Early 2023) Changelog | Homey
Now the stable 10.1.4 is available for everyone and there is still no 1.8.0, not even the test version available.
Does it mean, that the workaround is not working, or you just missed it?
Thanks for any updates.
I wish there would be any ā¦ I realized this problem 1 month ago ? That time, repair helped. Now I checked it again and seems itās not reporting values again (also a pity it does have only watts, not voltage, current etc.) I believe it has something to do with latest v10.1.4
Strange, I have 4 of them and all are working fine (even energy measurements). Before 10.1.4 and even now after.
Product ID: lumi.plug.maeu01
Would you know which firmware they have, just by any chance ?
There is nothing next to Firmware version.
Thank you, rightā¦that would be possible only with eg. Zibee2MQTT but as it works for you, itās not worth it.
Iām not the app developer. But I can probably answer your questions: no, the developer didnāt miss it (in fact, Iām sure they collaborated with Athom to implement this workaround), but it still takes time to implement the drivers for the missing devices, and, like many other apps, this app is being developed by someone that has a regular job.
It doesnāt exist, and I would find this option also really useful.
Iām currently considering moving my zigbee network to home assistant just to enable this future. Have everything setup just to find out that this feature is broken in the latest version of Zigbee2MQTT 
will have to be patientā¦
app request: It would be great if the new aqara T2 relay would also be supported.
please find the module in the link below.
Dual Relay Module T2 - Aqara
Couldnāt have said it better 
The workaround has currently been implemented for Homey Pro 2023. The team is currently working on the workaround for Homey Pro 2016 - 2019 and Homey Bridge. So hold on tight @hubo , weāre working around the clock to have the devices working as soon as possible 
I am using the Homey Pro 2023, so for me it is everything ready for the mentioned Aqara 1.8.0 app release, but there is not even the test version yet. From the previous what have been written here, I get a feeling that the 1.8.0 is just waiting for that workaround to be released. The workaround is released and still no Aqara 1.8.0 or any news about it.
I would patiently wait, even when the 1.8.0 was announced to be released at the end of August, but the last news are from 21 October, before the workaround was experimentally released as a part of 10.1.4-rc.2 and now the workaround is released to everyone as of part of the stable release 10.1.4 and there is still no new information about the 1.8.0, like if there is some other issue or whatās going on.
So, if anybody got some updates, please let us know.
