[Request Device Support] Aqara Curtain motor B1

[cacherocks]

Node Info

Basic cluster 0000

Identify cluster 0003

Windows covering cluster 0102

Analog Output (Basic) cluster 000D

Multistate Output (Basic) cluster 0013

Power Configuration cluster 0001

Node

Description

Works both with the battery and from power supply. Review.

[ebaauw]

It looks like the previous (mains powered) Aqara curtain controller (lumi.curtain), except that this is an end device instead of a router. The REST API plugin exposes a curtain controller as a /lights resource. We probably need to whitelist this device, because Receiver on when idle is false.

I'm a bit worried that the Windows Covering cluster doesn't provide Current Position Lift Percentage. It probably reports the position on the Analog Output cluster. The REST API plugin already picks that up (the lumi.curtain uses both Current Position Lift Percentage and the Analog Output cluster), but for controlling the curtain, only the Windows Covering cluster is used.

Can you check that the Present Value of the Analog Output cluster reports 0 when the curtains are closed and 100 when open?

Can you also check that it responds to the Open, Close, Stop and Go to lift percentage commands from the Windows Covering cluster? Can you set Reversed in Config/Status to change the direction for Open en Close (in case you installed the band to pull the curtains the other way round)?

I'm afraid we need for the API v2 /devices resource scheme to expose the battery percentage; config.battery is available only to /sensors resources.

[cacherocks]

Ok, in the next 2-3 days I will check everything and write the result on all issues.

[cacherocks]

• If the curtains do not move, then the buttons from the cluster do not control them, but receive the answer "success".
• If the curtains are in the process of closing or opening, then the buttons from the cluster control (Open, Close and Stop). Lift value and lift percentage buttons do not work, but they get the answer "success"
• Present Value of the Analog Output cluster changes only from 0.00 to 1.00 during the opening of the curtains and returns to 0.00 again after opening. In the process of closing the curtains 0.00 does not change.
• I can not set the Reversed in Config/Status because Record button is inactive, below is a screenshot. My curtains open from the center to the edges.

- The values of open and closed are preserved from the aqara hub after binding to deconz.

[ebaauw]

• If the curtains do not move, then the buttons from the cluster do not control them, but receive the answer "success".
• If the curtains are in the process of closing or opening, then the buttons from the cluster control (Open, Close and Stop). Lift value and lift percentage buttons do not work, but they get the answer "success"

Odd. Does the curtain controller connect to the RaspBee/ConBee directly, or did it select another parent node?

Present Value of the Analog Output cluster changes only from 0.00 to 1.00 during the opening of the curtains and returns to 0.00 again after opening. In the process of closing the curtains 0.00 does not change.

On the old controller, it changes from 0.00 (closed) to 100.00 (open), after calibrating the controller. Just like Current Position Life Percentage. Does the controller react when you try and write Present Value? Does the Multistate Output report anything?

I can not set the Reversed in Config/Status because Record button is inactive, below is a screenshot.

My bad, it's a read-only attribute. The setting is through Mode.

The values of open and closed are preserved from the aqara hub after binding to deconz.

Do you mean the calibration of the open and close position? Yes, that's handled by the motor itself, "behind" the ZigBee module. On the old model, you need to detach the ZigBee module to access the (other) reset button for the motor and make it re-calibrate.

[cacherocks]

Odd. Does the curtain controller connect to the RaspBee/ConBee directly, or did it select another parent node?

Directly, search and add through "add new light" via Phoscon.

My bad, it's a read-only attribute. The setting is through Mode.

I can set the checkbox and save the Reversed in Mode

Do you mean the calibration of the open and close position?

Yes.

On the old controller, it changes from 0.00 (closed) to 100.00 (open), after calibrating the controller. Just like Current Position Life Percentage. Does the controller react when you try and write Present Value? Does the Multistate Output report anything?

No react, no report.

[deven2020]

Hi

Can you confirm if this works with deconz/conbee 2? I am planning to get one.

Appreciate your feedback.

[freenetwork]

Hello. This curtain is working?

[cacherocks]

Hello. This curtain is working?

Hi
Can you confirm if this works with deconz/conbee 2? I am planning to get one.
Appreciate your feedback.

Hi, unfortunately not, I'm still waiting for B1 support to be added to the deconz. Maybe support will appear in 2.05.67. Like this issue to show the importance of adding support for B1.

[cacherocks]

@ebaauw Should we expect support for Aqara B1 in Deconz 2.05.67?

[ebaauw]

Should we expect support for Aqara B1 in Deconz 2.05.67?

I’m not the person to answer that question. I am just a deCONZ user, who on occasion contributes to this open source

Should we expect support for Aqara B1?

To support the B1, we first need to understand how to control it, i.e. what ZigBee commands make it open, close, and hold the curtains, and how it reports the current curtain position. If it’s not through the Window Covering nor through the Analog Output cluster, I wouldn’t know how.

[freenetwork]

I test zigbee2mqtt and change config from aqara curtain for aqara curtain b1. It is working. But without battery state

I want to say that the control commands work with the previous non-battery version

One problem i cant get responce with current position

[cacherocks]

I want to say that the control commands work with the previous non-battery version

So it will be enough to clone the settings from the old version of the "lumi.curtain" for the new version of the b1 "lumi.curtain.hagl04", good news.

[ebaauw]

Not according to your own tests. We must understand how to control the B1 from the GUI, before we can support it in the API.

[freenetwork]

https://github.com/freenetwork/ZNCLDJ12LM

I capture packets. Controls messages use previous