Support for lumi.curtain.acn002 - Aqara Roller Shade Driver E1 (Europe-version?)

[wisekki]

Finally I received the Aqara Roller Shade Driver E1, but it seems this one doesn't work out of the box with zigbee2mqtt.
I'm using zigbee2mqtt 1.22.0-dev. The device joins the network and is interviewed as:

ZNJLBL01LM - Xiaomi Aqara roller shade companion E1 (EndDevice)

Problem is that it doesn't react to anything and keeps flooding the logs:

'{"battery":null,"last_seen":"2021-11-01T20:07:44+02:00","linkquality":48,"position":0,"running":false,"update_available":null}'

Only thing that changes is the link quality, nothing else.

On the device back it says Model: RSD-M01 and it's manufactured last month 10/2021. So I think this would be a new device perhaps but it joins as ZNJLBL01LM. What can I do?

When googling RSD-M01 the first result goes to Aqara's Europe site of Roller Shade Driver E1.

Information about the device + link

Aqara Roller Shade Driver E1
Model: RSD-M01
https://www.aqara.com/eu/product/roller-shade-driver-e1

data/database.db entry of the device

{"id":12,"type":"EndDevice","ieeeAddr":"0x54ef4410002e066a","nwkAddr":62470,"manufId":4447,"manufName":"LUMI","powerSource":"Unknown","modelId":"lumi.curtain.acn002","epList":[1,242],"endpoints":{"1":{"profId":260,"epId":1,"devId":256,"inClusterList":[0,2,3,4,5,6,9,13,19,258],"outClusterList":[10,25],"clusters":{"genBasic":{"attributes":{"modelId":"lumi.curtain.acn002","manufacturerName":"LUMI","powerSource":0,"zclVersion":3,"appVersion":25,"stackVersion":2,"hwVersion":1,"dateCode":"05-18-2021"}}},"binds":[],"configuredReportings":[],"meta":{}},"242":{"profId":41440,"epId":242,"devId":97,"inClusterList":[],"outClusterList":[33],"clusters":{},"binds":[],"configuredReportings":[],"meta":{}}},"appVersion":25,"stackVersion":2,"hwVersion":1,"dateCode":"05-18-2021","zclVersion":3,"interviewCompleted":true,"meta":{},"lastSeen":1635787960439}

[AndyKassell]

Hi,

I have same issue with same device. It is a supported device but it just doesn't work correctly. I have debug logs turned on also and see it does an OTA request, but yes it is constantly sending this in.

Info MQTT publish: topic 'zigbee2mqtt/Bed 3 Blind', payload 
'{"battery":null,"last_seen":1636097972251,"linkquality":54,"position":20,"running":false,"update_available":null}'
Debug Received Zigbee message from 'Bed 3 Blind', type 'commandQueryNextImageRequest', cluster 'genOta', data '{"fieldControl":0,"fileVersion":3608,"imageType":14976,"manufacturerCode":4447}' from endpoint 1 with groupID 0
Debug Device 'Bed 3 Blind' requested OTA

Whilst the device does not report battery or current position correctly I can control the blind using the controls, however they do not update to reflect the current position you need to do a manual refresh. I have linked a video review below which shows the exact issue starting for the 8 minute mark.

Aqara Blind Driver Unbox + Setup in Home Assistant without a hub

[SchoutenHans]

Hi,

I have same issue with this device. (Model: RSD-M01). Also same problems mentioned by Andy Kassell.

[HenriMatthijssen]

Same here. It would also be nice to see the battery status.

[Koenkk]

Similar to the E1 contact sensor, it might be that this sensor requires a small change in the coordinator firmware to work:

CC2531/CC2530 fws: #9274 (comment)
CC2652/CC1352: #9274 (comment)

[daenny]

Thanks @Koenkk! I had the same problem.

I just tested with latest 1.22.1 HassIO addon and your patched firmware on slaesh's stick and it works!

Except battery reporting is not working. Do you have any idea how to fix that?

[Koenkk]

Could you check if battery works with the following report:

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.curtain.acn002'],
    model: 'ZNJLBL01LM',
    description: 'Aqara roller shade companion E1',
    vendor: 'Xiaomi',
    fromZigbee: [fz.xiaomi_curtain_position, fz.battery, fz.cover_position_tilt, fz.ignore_basic_report, fz.xiaomi_curtain_options, fz.aqara_opple_report],
    toZigbee: [tz.xiaomi_curtain_position_state, tz.xiaomi_curtain_options],
    exposes: [e.cover_position().setAccess('state', ea.ALL), e.battery()],
    ota: ota.zigbeeOTA,
};

module.exports = definition;

See https://www.zigbee2mqtt.io/advanced/support-new-devices/01_support_new_devices.html#instructions how to use it, make sure you are on z2m 1.22.0

[daenny]

Thanks for your help! I get the following issue:

[23:00:48] INFO: Handing over control to Zigbee2mqtt Core ...
> zigbee2mqtt@1.22.0 start
> node index.js
(node:1445) UnhandledPromiseRejectionWarning: ReferenceError: ota is not defined
(Use `node --trace-warnings ...` to show where the warning was created)
(node:1445) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:1445) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

I went on and removed the line with ota and I got some state update with battery 🎉 :

Zigbee2MQTT:info  2021-11-11 23:03:22: MQTT publish: topic 'zigbee2mqtt/Entrance Roller Rechts', payload '{"battery":0,"last_seen":"2021-11-11T22:03:22.425Z","linkquality":102,"position":100,"running":false,"voltage":1297}

And the state is shown as:

{
    "battery": 0,
    "last_seen": "2021-11-11T22:03:22.425Z",
    "linkquality": 102,
    "position": 100,
    "running": false,
    "voltage": 1297
}

However, I think the battery which is included is a LiPO, which should have ~3.7V-4.2V. But it's definitely an improvement.

[Koenkk]

And with:

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.curtain.acn002'],
    model: 'ZNJLBL01LM',
    description: 'Aqara roller shade companion E1',
    vendor: 'Xiaomi',
    fromZigbee: [fz.xiaomi_curtain_position, fz.battery, fz.cover_position_tilt, fz.ignore_basic_report, fz.xiaomi_curtain_options],
    toZigbee: [tz.xiaomi_curtain_position_state, tz.xiaomi_curtain_options],
    exposes: [e.cover_position().setAccess('state', ea.ALL), e.battery()],
    ota: ota.zigbeeOTA,
    configure: async (device, coordinatorEndpoint, logger) => {
        const endpoint = device.getEndpoint(1);
        await reporting.bind(endpoint, coordinatorEndpoint, ['genPowerCfg']);
    },
};

module.exports = definition;

??

Note: wait one day to make sure device reports the new voltage.

[HenriMatthijssen]

Tried it out with patched firmware for CC2652R and above change (directly in file 'xiaomi.js') and this is definitely an improvement. Progress is instantly shown now. However I have inverted my roller and this is not taken into account yet (position should be (100 - position)).

Battery still shows N/A. I also see battery not reported in the logging:

info 2021-11-13 13:19:31: MQTT publish: topic 'zigbee2mqtt/Rolgordijn Keuken', payload '{"linkquality":99,"position":86,"running":false}'

State shows:

{
    "linkquality": 105,
    "position": 86,
    "running": false
}

[Koenkk]

@HenriMatthijssen

• Does it show battery?
• How did you invert the roller? (through configuration.yaml?)

[HenriMatthijssen]

See above, It shows N/A for Battery.

I have inverted the roller on the device itself (pressing reset button 3 times in a row).

[Koenkk]

@HenriMatthijssen

• does battery reporting work with Support for lumi.curtain.acn002 - Aqara Roller Shade Driver E1 (Europe-version?) #9447 (comment) ?
• you have to make z2m aware that your covers is inverted, see the invert_cover option: https://www.zigbee2mqtt.io/devices/ZNJLBL01LM.html#options

[SchoutenHans]

@Koenkk ,
I have two Aqara Roler Shade drivers E1. I'm running the docker-compose version 1.22 on a Raspberry Pi 4.
Also I installed the CC2652/CC1352: #9274 (comment) Firmware.

My Rolers working fine. The position is updated after you modify the position.
The battery value is in the payload.
Zigbee2MQTT:info 2021-11-14 17:47:28: MQTT publish: topic 'zigbee2mqtt/Blind-3', payload '{"battery":0,"last_seen":1636908448351,"linkquality":72,"position":0,"running":false,"voltage":1297}'

The voltage reported is 1297mv. The Battery stay's at 0% after more that 24 hours.
State
{
"battery": 0,
"last_seen": 1636908221702,
"linkquality": 75,
"position": 0,
"running": false,
"voltage": 1298
}
I don't now if the voltage is ok. I read some ware that the device has a 7,4V 1000ma battery.
So, it's working with the 1.22 docker compose version and the firmware update of the CC2652 Slaesh stick

p.s. you have to rejoin the roler again after updating the firmware on the CC2562 stick.

Regards,
Hans Schouten

[daenny]

Yes, I think something is different in the voltage reporting. It's a 7.4V two cell lipo (according to https://notenoughtech.com/home-automation/aqara-roller-shade-driver-e1-zigbee2mqtt/). I also get voltage reading in the range of 1260-1330 at the moment with:

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 ota = require('zigbee-herdsman-converters/lib/ota');
const e = exposes.presets;
const ea = exposes.access;

const definition = {
    zigbeeModel: ['lumi.curtain.acn002'],
    model: 'ZNJLBL01LM',
    description: 'Aqara roller shade companion E1',
    vendor: 'Xiaomi',
    fromZigbee: [fz.xiaomi_curtain_position, fz.battery, fz.cover_position_tilt, fz.ignore_basic_report, fz.xiaomi_curtain_options, fz.aqara_opple_report],
    toZigbee: [tz.xiaomi_curtain_position_state, tz.xiaomi_curtain_options],
    exposes: [e.cover_position().setAccess('state', ea.ALL), e.battery(), e.battery_voltage()],
    ota: ota.zigbeeOTA,
};

module.exports = definition;

The value does update and change. Battery stays at 0. which makes sense, as all other battery templates expects at least a 3V battery if I read (https://github.com/Koenkk/zigbee-herdsman-converters/blob/cc45f434e7b867b404a7c2c4c005925b19163427/lib/utils.js#L132) correctly.

[HenriMatthijssen]

Using above from @daenny I now get Voltage reporting. Further with setting invert_cover option the position seems reported fine now.

I get for state :

{
    "battery": 0,
    "linkquality": 93,
    "position": 0,
    "running": false,
    "voltage": 1301
}

However battery percentage is still not correctly shown (as 0%).

[Koenkk]

Then the only thing left here is to define a calculation to convert the voltage to battery (%). This is done by zigbee2mqtt here: https://github.com/Koenkk/zigbee-herdsman-converters/blob/8f2aed87bdfd3215de72cd10e761dd2e8504ae77/converters/fromZigbee.js#L5534

Which boils down to:

• Figure out the highest and lowest possible voltage
• Define a new option/calculation in https://github.com/Koenkk/zigbee-herdsman-converters/blob/8f2aed87bdfd3215de72cd10e761dd2e8504ae77/lib/utils.js#L132
• Change https://github.com/Koenkk/zigbee-herdsman-converters/blob/8f2aed87bdfd3215de72cd10e761dd2e8504ae77/converters/fromZigbee.js#L5534 to return {battery: batteryVoltageToPercentage(voltage, model.model === 'ZNJLBL01LM' ? 'NEW_OPTION_NAME' : '3V_2100'), voltage: voltage};

[wisekki]

Thanks for the great work! I've been sick and wasn't able to participate. After a lot of repairing I was finally able to actually move the roller shades up and down :) but that's about it. So what do I need to do in order to get it work better? Flash the slaesh's stick? And modify scripts?

[redphx]

I have the Aqara Hub. Aqara app shows the battery at 55%. I tried to use the code above to get the voltage value but it didn't work. Z2M loaded the custom script but the exposed values are still the same (no voltage property, battery is null). I'm new to Z2M so not sure if I did anything wrong.

[daenny]

I charged my two motor drivers to 100% toady. But the battery voltage is still reported as 1298-1300. So I am afraid that there is some more work left to figure out how to get a proper reading (voltage or percentage).

[Gortosch]

Hello all,
I also have the problem that no battery status is displayed. Everything else works fine. Thanks for this.
Any news on the battery problem yet?

Is there anything I can do to help?

Greetings
Sven

EDIT: I have a conbee II stick with the latest FW.

[xnextx]

+1

[fewdji]

Hi! Battery state not working. Got error:
ERROR (MainThread) [homeassistant.helpers.template] Error parsing value: access to attribute 'update' of 'dict' object is unsafe. (value: {"battery":null,"linkquality":69,"position":0,"running":false,"update_available":null}, template: {{ value_json['update']['state'] == "available" }})

[totalitarian]

Same issue here, all works except battery

[jeroenvdd]

Same issue here, all works except battery

what is your firmware date is it
05-18-2021 ? for the roller

[Gortosch]

Hello,

i have the same issue. My firmware version is 05-18-2021.

Is there anything I can do to help?

Greetings
Sven

[totalitarian]

Same issue here, all works except battery

what is your firmware date is it 05-18-2021 ? for the roller

05-18-2021

[EloB]

I also have problem with battery. Apart from that I can Open/Close the blind but I've lost the ability to set position. I can still set min/max with 5 button click technic. It was working and I had it connected to HB and was showing of that position feature and suddenly it stopped working. Even if I remove the device from zigbee2mqtt and repair it doesn't reset that functionality. After I setup it again.

Here is an error that I get in log.

Error Publish 'get' 'state' to 'Rullgardin 1' failed: 'Error: Read 0x54ef4410002e1826/1 genAnalogOutput([85], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (no response received)'

[jb123567]

I have two of these, seem to working well, however like others battery is just displaying a question mark. Anything I can do to help? Realistically these devices are the only zigbee devices I need to regularly charge, so it would be great to know when they need it.

[MrNomNom]

The device does not report the position until it has reached the set position or a new position is set but only if the new position will change the motor direction.

I have expressed myself incorrectly. After it has physically reached the targeted position, it still reports a faulty position. Only the subsequent manual retrieval of the position with /get: {state:""} provides the correct result.

I am experiencing same issue. State is "old" everywhere unless I publish to "/get" endpoint, OR click "refresh" icon in zigbee2mqtt device panel (the one named "Exposed" in device info page).

For now I did little hack in node-red, I am publishing to "/get" endpoint every 5 sec to have up to date state everywhere. I hope this is not affecting device battery somehow :D

Ps. looks like this is affecting states of device everywhere throughout home assistant.

[CMDR-Sloma]

I have two of these controllers, but there seems to be a discrepancy with the reported state.

{ "payload": "open", "topic": "cover.livingroom_blinds", "data": { "entity_id": "cover.livingroom_blinds", "state": "open", "attributes": { "current_position": 69, "battery": 90, "charging_status": false, "linkquality": 51, "motor_state": null, "position": 69, "running": null, "update": { "state": "idle" }, "update_available": false, "device_class": "shutter", "friendly_name": "Livingroom blinds", "supported_features": 15 }, "last_changed": "2022-05-02T17:38:27.480556+00:00", "last_updated": "2022-05-02T18:20:49.108138+00:00", "context": { "id": "3aacd6f6f151194f72c4e5874d0b0cd3", "parent_id": null, "user_id": null }, "timeSinceChangedMs": 2583081, "original_state": "open" } }

{ "payload": "closing", "topic": "cover.masterbedroomblinds", "data": { "entity_id": "cover.masterbedroomblinds", "state": "closing", "attributes": { "current_position": 70, "battery": 96, "charging_status": true, "linkquality": 120, "motor_state": "declining", "position": 70, "running": true, "update": { "state": "idle" }, "update_available": false, "device_class": "shutter", "friendly_name": "MasterBedroomBlinds", "supported_features": 15 }, "last_changed": "2022-05-02T16:56:42.255031+00:00", "last_updated": "2022-05-02T18:24:53.747170+00:00", "context": { "id": "11032d29f5f0b75a8c27623fedf2f1ce", "parent_id": null, "user_id": null }, "timeSinceChangedMs": 5326461, "original_state": "closing" } }

It looks that one of them is stuck and always shows status closing with the rest of the attributes: "motor_state": "declining" & "running": true

Anyone knows what is the source of this?

Am I missing something?

I am running the latest zigbee2mqtt add-on released today.

In Lovelace it looks like this (I know this is not important but it reflects current states):

[0ip]

@CMDR-Sloma I had exactly the same problem yesterday with the latest version. Very rare and not predictable. After reaching the target position, the state was not updated at all.

[nielseulink]

It happens only occationaly, but the device report wrong/old position info while stopping. Koenkk/zigbee-herdsman-converters#4163 should fix it.

This has fixed the issue indeed, had to reconnect the device before it took effect. Thanks @invis-z !!

Edit: I noticed an tempature sensor aswell after the reconnect, It's not on the device page. any idea where this is comming from?

[invis-z]

Edit: I noticed an tempature sensor aswell after the reconnect, It's not on the device page. any idea where this is comming from?

The SoC of the device has a temperature sensor, so it is basically the "CPU Temp" of the device. I didn't see any usefullness of the data since the data does not look accruate enough to me to be used as room temperature, so I did not include it in the device defination when I was working on it. It is added by another person in #4201.

[CMDR-Sloma]

I noticed an update release today, does it contain any fixes for this issue?

It looks that one of them is stuck and always shows status closing with the rest of the attributes: "motor_state": "declining" & "running": true

[nielseulink]

I noticed an update release today, does it contain any fixes for this issue?

It looks that one of them is stuck and always shows status closing with the rest of the attributes: "motor_state": "declining" & "running": true

This has allready been fixed, I had te reset the device (remove and add again).

[robertalexa]

Hey guys, for anyone working on this device, does this support motor_speed in z2m? As far as I am aware it does support it on the original aqara hub, but i can't find any info on here about it, and based on what the device exposes it seems it was not yet implemented?

Thanks in advance

[Lyr3x]

Am i the only one having issues with those drivers? They losing the connection on a daily basis and I need to reset them. All operations resulting then in a timeout:

Publish 'set' 'state' to 'Rollo Buero' failed: 'Error: Write 0x54ef4410003e5867/1 genAnalogOutput({"85":{"value":100,"type":57}}, {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Timeout - 18402 - 1 - 15 - 13 - 4 after 10000ms)'

Using zzh! and some of them are quite close to the stick. Other devices in my network do not have such issues. Having currently 4 of them and all lose the connection every other day. I am not sure if it has something to do with z2m or if its all the devices. Feedback would be nice. Currently running on the dev branch

[CMDR-Sloma]

I have two and both are running fine now, every bit of info is reported, and I have no more issues. Earlier update sorted my problem, and I also use zzh! which is located 3-4 meters from the nearest blind controller. I am on a stable branch and my network is pretty robust with nearly 70 devices and many routers (mostly Ikea bulbs and CC2531 sticks). Rock solid.

[Lyr3x]

Thanks for the quick reply. That sounds very good. I think I have then something going on more or less specific to my network.

[notownblues]

Hi all, I've been reading through the comments and some of you have managed to get the sensor to report all the sensors? It's still showing as NA for me with the latest Z2M version. How did you guys manage that?

The open/close state reported is also wrong most of the time.

[Th0rHere]

Just checking if anyone had any luck getting position updates to be automatic instead of needing manual refresh in MQTT. Added my rollers without issue, but ultimately having to manually refresh makes usage less than ideal.

[0ip]

@Th0rHere It works for me. Have you tried deleting the device and adding it again?

[github-actions]

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

[bjeanes]

Thanks for this thread.

After reading through it all, upgrading my Zigbee stick firmware, repairing blind, and configuring the end-stops + direction on the device itself via the button combos (screenshot for below for anyone who no longer has a manual), everything seems to be working correctly for me.

Production date on mine was 01/2022 and I was able to upgrade to latest Aqara firmware using Z2M (unlike my IKEA remotes, which just fail) to 07-20-2022.

I found that inverting the direction in Z2M didn't swap the buttons. But pressing and holding the RESET button on device swapped physical buttons and swapped the direction in Z2M (so I had to un-invert it).

[github-actions]

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

[abenedet78]

Apologies for reopening this thread, but I cannot get this to work with Z2M. I have a Conbee II and I've flashed it with the latest firmware. I have a number of other Aqara and Zigbee products that work flawlessly with Z2M. The error message I get is:

Device '0x54ef4410004a6010' with Zigbee model 'lumi.curtain.acn002' and manufacturer name 'LUMI' is NOT supported, please follow https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html

The model # on the product is RSD-M01 and it was manufactured on 2022.10.

Appreciate any help to get this connected. Significant wifey points if I do!

Thanks in advance.

[akarabach]

motor_speed is not supported, can we reopen the issue ?

[ptrsconsulting]

Just checking if anyone had any luck getting position updates to be automatic instead of needing manual refresh in MQTT. Added my rollers without issue, but ultimately having to manually refresh makes usage less than ideal.

Same issue here. Any tips anyone?

[fir3drag0n]

motor_speed is not supported, can we reopen the issue ?

would be awesome to integrate that

[m1k3f15h]

would be awesome to integrate that

Would be great

[TimBroddin]

Is there any way to make the reporting of position etc work with an ezsp adapter?

[TimBroddin]

Is there any way to make the reporting of position etc work with an ezsp adapter?

If anyone comes here via Google looking for the answer to the question above. In HA: download the Silicon Labs Flasher addon, stop Z2M and run the addon. It will flash the latest firmware, after which reporting should work.

[galdaka]

I flash Sonoff Zigbee Dongle P with latest firmware versión and the problem still exits