-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Aqara T1 switches dont report power anymore #11480
Comments
Try updating your coordinator firmware and repair the device (the devices are now expected to be in "xiaomi" mode which require this firmware) |
Thanks for the reply. is there any chance i can get the old converter from somewhere to write a external converter without updating the coordinator? im not happy with doing that at this point. i have 114 devices connected and down want to screw things up. |
I reverted back to the old z2mqtt version and it is working again. I dont understand why updates always have to break stuff that works perfectly... |
@z-x-f could you add back the standard power converters for Aqara devices? (Koenkk/zigbee-herdsman-converters#3292) However I'm not sure if that introduces flipping in precisions |
I think it is better to use an external converter, if you are not going to update the firmware of the coordinator. |
@sygys following external converter should do it: const fz = require('zigbee-herdsman-converters/converters/fromZigbee');
const tz = require('zigbee-herdsman-converters/converters/toZigbee');
const exposes = require('zigbee-herdsman-converters/lib/exposes');
const reporting = require('zigbee-herdsman-converters/lib/reporting');
const extend = require('zigbee-herdsman-converters/lib/extend');
const e = exposes.presets;
const ea = exposes.access;
const definition = {
zigbeeModel: ['lumi.switch.n0acn2'],
model: 'DLKZMK11LM',
vendor: 'Xiaomi',
description: 'Aqara single switch module T1 (with neutral)',
fromZigbee: [fz.on_off, fz.xiaomi_power, fz.aqara_opple],
toZigbee: [tz.on_off, tz.xiaomi_power, tz.xiaomi_switch_type, tz.xiaomi_switch_power_outage_memory, tz.xiaomi_led_disabled_night, fz.metering, fz.electrical_measurement],
exposes: [e.switch(), e.power().withAccess(ea.STATE_GET), e.energy(), e.temperature().withAccess(ea.STATE),
e.voltage().withAccess(ea.STATE), e.power_outage_memory(), e.led_disabled_night(), e.switch_type()],
configure: async (device, coordinatorEndpoint, logger) => {
await device.getEndpoint(1).write('aqaraOpple', {'mode': 1}, {manufacturerCode: 0x115f, disableResponse: true});
},
ota: ota.zigbeeOTA,
};
module.exports = definition; |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days |
I have the same issue of power not being reported at all. I tried the external converter above, but const fz = require('zigbee-herdsman-converters/converters/fromZigbee');
const tz = require('zigbee-herdsman-converters/converters/toZigbee');
const exposes = require('zigbee-herdsman-converters/lib/exposes');
const reporting = require('zigbee-herdsman-converters/lib/reporting');
const extend = require('zigbee-herdsman-converters/lib/extend');
const zigbeeOTA = require('zigbee-herdsman-converters/lib/ota/zigbeeOTA');
const e = exposes.presets;
const ea = exposes.access;
const definition = {
zigbeeModel: ['lumi.switch.n0acn2'],
model: 'DLKZMK11LM',
vendor: 'Xiaomi',
description: 'Aqara single switch module T1 (with neutral)',
fromZigbee: [fz.on_off, fz.xiaomi_power, fz.aqara_opple],
toZigbee: [tz.on_off, tz.xiaomi_power, tz.xiaomi_switch_type, tz.xiaomi_switch_power_outage_memory, tz.xiaomi_led_disabled_night, fz.metering, fz.e
exposes: [e.switch(), e.power().withAccess(ea.STATE_GET), e.energy(), e.temperature().withAccess(ea.STATE),
e.voltage().withAccess(ea.STATE), e.power_outage_memory(), e.led_disabled_night(), e.switch_type()],
configure: async (device, coordinatorEndpoint, logger) => {
await device.getEndpoint(1).write('aqaraOpple', {'mode': 1}, {manufacturerCode: 0x115f, disableResponse: true});
},
ota: zigbeeOTA,
};
module.exports = definition; In the end, nothing changed, though. Still no power is being reported. If there is anything I can help with to make this work, I'm more than happy try stuff out or deliver logs or something! |
It all started when the z2mqtt update messed up the setup for me. The problem is that the coordinator firmware needs te be updated to the latest version for the t1 switch to work properly again. I really don't understand why every update seems to break more then it fixes. I decided to just stop updating z2mqtt. The only reason for this is that updates made by koenk seems to keep breaking already working devices forcing to upgrade coordinators and God knows what that can only mess more things up. If everything works just stop updating z2mqtt. There is absolutely no reason to update a perfect working setup. Especially not z2mqtt in which updates tend to have absolutely no value to existing systems and only mess things up |
Which version of zigbee2mqtt are you using? I don't know how to downgrade it on Hassos, but I'm eager to check it out! |
Not sure if downgrading will help I posted this issue a while back after which someone replied that the coordinator firmware needed to be upgraded. I'm using a zigbee to Ethernet coordinator from tube's website it uses a CC2652P2 zigbee chip. This thing can be upgraded to the latest firmware. But reading your post I start to wonder if upgrading will fix it. Because if you use an USB stick I don't think that this is the problem. I use an external converter that does work by the way. |
I just upgraded the Zigbee2Mqtt coordinator firmware on my stick to this version: https://github.com/Koenkk/Z-Stack-firmware/tree/master/coordinator/Z-Stack_3.x.0/bin Edit:
Is it any different from the ones above, could you share it? |
try this:
|
This works with my T1's You will have to look which exact model you have and change these. on the places where it says 'n0agl1' also check if the model is the same. I had some trouble with these too. i ended up cutting power to these switches to make it work. Also check if you have the same model. If you get this working i advise to stop updating z2mqtt. there is like i said no reason to update a well working system. unless you add devices that dont work out of the box. But maybe its even better to download the external converter for those devices. this way the system you have will keep working. These updates are most of the time terrible. |
After the firmware update alone didn't fix it, I just tried to re-add the device into the network. After the device got interviewed correctly, it doesn't seem to be working at all. The values/states that worked (On/off, temperature, e.g.) are recognized, but not working. It looks like the connection get's dropped after the interview. I tried the same with your converter, with similar results. I'll try to downgrade the coordinator later and repeat the process. :( |
I downgraded the coordinator to https://github.com/Koenkk/Z-Stack-firmware/blob/467eee408c37c3c4bee956877e2f7aabf9b007e4/coordinator/Z-Stack_3.x.0/bin/CC2652RB_coordinator_20220103.zip (the previous version) and removed your external converter. This seems to have fixed the issue: I can control the switch and can read values for power, energy and temperature! I have no insight in how these firmwares are built - is there a place to check for changes between 20220103 and 20220219? |
Why ist it closed? The Problem is still there. And the custom converter doesn't work either. :-( |
Hello, with the same problem I try to install the converter. At Z2M restart I have this error:
And Z2M doesn't start anymore. The converter I get is the one listed above:
|
This converter works with latest release and fixed the power not reporting problem for me.
|
How and where do I need to put this code? I have 2 Aquara T1 switches with nog power usage.
|
last line is missing. See post above. |
module.exports = definition; <---- this line is missing !! You have to put this file (with the last line missing) into the
Then restart ZigbeeToMqtt addon (Parameters/addon/Zigbee2Mqtt restart) and then click on the button in py post just above. It should work. May be you will have to wait a few. |
thanks, works now. Reconfiguration did the trick. |
Confirmed too: Latest Firmware with this custom converter worked for me as well! Thanks a lot @petravic @Kiezelke @jmcollin78 ! |
Resolved: for anyone reading this due to the error below, use the converter from here #11480 (comment) making sure to add the modules.export as stated. Hi Any ideas? Edit: Thank |
What happened?
After updating to version 1.23.0-1 all 3 of my aqara T1 switches (Xiaomi DLKZMK11LM) stopped reporting power usage and energy (kwh and watts) temperature and controlling the switch keep working.
i tried re-pairing the devices but that give me this error:
error 2022-02-18 18:52:09: Failed to configure '0x54ef44100009be5b', attempt 1 (Error: Bind 0x54ef44100009be5b/1 genOnOff from '0x00124b00237e0705/1' failed (AREQ - ZDO - bindRsp after 10000ms)
at Timeout._onTimeout (/app/node_modules/zigbee-herdsman/src/utils/waitress.ts:64:35)
at listOnTimeout (internal/timers.js:557:17)
at processTimers (internal/timers.js:500:7))
What did you expect to happen?
I expected them to work properly and give me power and energy after the update
How to reproduce it (minimal and precise)
No response
Zigbee2MQTT version
1.23.0-1
Adapter firmware version
20210120
Adapter
cc2652p2
Debug log
error 2022-02-18 18:52:09: Failed to configure '0x54ef44100009be5b', attempt 1 (Error: Bind 0x54ef44100009be5b/1 genOnOff from '0x00124b00237e0705/1' failed (AREQ - ZDO - bindRsp after 10000ms)
at Timeout._onTimeout (/app/node_modules/zigbee-herdsman/src/utils/waitress.ts:64:35)
at listOnTimeout (internal/timers.js:557:17)
at processTimers (internal/timers.js:500:7))
The text was updated successfully, but these errors were encountered: