Xiaomi ZNJLBL01LM no longer reports Open or Closed just Opening and Closing #15873
Comments
|
Same here, from the MQTT log in HA Same Zigbee2MQTT version, but ConbeeII adapter. |
|
Can you provide the debug log when closing and opening the track? |
|
Sure. This opening: This is closing: I hope I've filtered out all lines correctly; but I have about 150 MQTT devices.... :-) |
|
I have the same problem : The following warning seems to be related to the above, as it started to appear only after the latest update: Also, I don't know why the same devices behave differently, both on the same firmware both work, but only one of them fully reports additional information. Any suggestions to fix other controller? Master: Livingroom blinds: Relevant debug lines from Zigbee2MQTT: |
|
Quick update, I repaired the other controller, and it reports all parameters as the first one. The main issue still stands. |
|
I could not open/close my 2 blinds through HA (automations). My logs don't show anything that hasn't been already shared here before. Btw, the release notes don't mention any changes to ZNJLBL01LM |
|
This might be caused by #15555 , reverted this now. Can you check if the latest dev works OK now? Changes will be available in the dev branch in a few hours from now. (https://www.zigbee2mqtt.io/advanced/more/switch-to-dev-branch.html) |
|
The current |
|
I have the ZNCLDJ11LM model and the state is also broken. In HA it always shows as open, in Z2M frontend it has no state. Attributes work fine and open and close command work as well, just the state that is broken. I updated to the latest dev build and that also seemed to fix my model. Reporting here incase other come across the same issue that have my model. |
|
Just tried 1.29.0-dev commit: 15ccf94 and can confirm that it is working as expected again. |
|
Same issue for ZNCLDJ12LM. Hopefully this will be pushed to master asap. |
|
Great, I'll make a new hotfix release version soon (1.29.1) |
|
Is someone willing to help me fix this? |
|
@10Thirty @Xitro01 @ASNNetworks @golles @CMDR-Sloma @buhito81 can you check if your Xiaomi cover still works correctly in the latest dev branch? (https://www.zigbee2mqtt.io/advanced/more/switch-to-dev-branch.html) |
Yes, they do. |
|
@buhito81 sorry, the changes were not available yet, can you check again in 1 hour from now? |
edit: re-installed and got 1.29.1-dev (commit #9c4abb6) now. My model (ZNCLDJ11LM) is now again broken unfortunately with this latest dev build. It's different broken than before the hotfix btw. It now is always set as closed in HA, while position attribute is working as intended. I attached logs as well. I logged when the curtain was in closed state. I opened the curtain, waited and then closed again. To clarify: latest stable build with the hotfix (1.29.1-1) did fix my model. |
|
I don't understand how can this happen. The changes I made now are not supposed to break anything as they only apply when there's the 'moving' property. |
With my model the running and motor_state has never worked. Even though it exposes running and motor_state, those variables are always N/A with my model in the frontend. |
|
This is very similar to the issue I've reported previously in #15116 |
|
Can someone please post the payload of the MQTT message published from z2m when the cover is stopped and while moving, and also the discovery message published from z2m to home assistant? |
|
Hmm.. I updated to 1.29.1 last evening, and now my Zigbee2mqtt periodic crach. "Zigbee2MQTT:debug 2023-01-09 05:22:06: lumi.curtain.acn002: unknown key 13 with value 3870" Value 3870 is Firmware version. But all Binds works (start, stop, up and down), untill crach.
|
Yes correct, stable 1.92.2 fixed it (but the dev build that was made after 1.92.2 broke it again). |
|
@ASNNetworks @cmiguelcabral Can you check this change #16324? |
It is just the same thing in a different order.
I don't think I understand what you mean, I did not change anything related to null values or other stuff, only added the same logic to use when there is a moving property... |
Hi, I don't think the new PR is online yet. I just re-installed dev build, but it's different commit and still bugged. |
You need to checkout the PR and build the image yourself. |
You can checkout from my fork. Make sure you have Node v.14 or above installed. git clone [email protected]:Drafteed/zigbee2mqtt.git z2m-test
cd z2m-test
git checkout ha-moving-fix
npm iCopy your configuration to z2m-test/data/ and start z2m: npm run start |
I'm running Z2M add-on on Home Assistant OS. I don't think I can install this, since I'd need an add-on right? |
Then let's just wait for the changes to the dev branch. |
|
I find it really hard to understand how can this break those Xiaomi blinds. `{% if not value_json.${motorState.property} %}` +
` ${stoppedState} {% else %} {{ value_json.${motorState.property} }} {% endif %}`;For this: `{{ ${stoppedState} if not value_json.${movingState.property} ` +
`else value_json.${movingState.property} }}`;But they should behave the same as the second one it's just an inline version of the former one. |
Let`s try: {% set value_json = {"moving": None} %}
{% if not value_json.moving %} stopped {% else %} {{ value_json.moving }} {% endif %}Result: Now, yours: {% set value_json = {"moving": None} %}
{{ stopped if not value_json.moving else value_json.moving }}Result: |
|
Ah... I see. |
|
If you do: {% set value_json = {"moving": None} %}
{{ "stopped" if not value_json.moving else value_json.moving }}Result: |
|
I know, but I preferred the previous option, since you don’t have to fence second-level quotes: discoveryEntry.discovery_payload.value_template =
`{{ "${stoppedState}" if not value_json.${movingState.property} ` +
`else value_json.${movingState.property} }}`;discoveryEntry.discovery_payload.value_template = `{% if not value_json.${motorState.property} %}` +
` ${stoppedState} {% else %} {{ value_json.${motorState.property} }} {% endif %}`; |
|
In my blinds the 'moving' property never gets 'null', so it never failed here. Anyway, we don't need any of that if using your solution. |
I think we need to add a test to catch this. |
Is there a way to get a notification when the next dev branch has been released? I just re-installed again but is still on commit #7639ce4. |
|
@ASNNetworks Changes available in latest-dev build. Please test this. |
Just installed commit #2f0a2ce, works great with my motor! 🙌 🫶 |
|
I just started using Z2M, on the latest version (1.31.2) and using the latest firmware available for these (10-09-2022). |
|
No one else is still seeing this error? |
For me, this issue was resolved earlier this year. I only see opening/closing when the curtain is actually moving. Else I see open or closed. My ZNJLBL01LM is on firmware date |
|
And you're using the -P stick? Or - E? |
I'm using a zzh stick |
|
I'm on Conbee II, firmware 0x26720700, issue is still very much there. |
|
Is there any news? |
|
I've come here having literally just purchased this unit. It appears to work from zb2mgtt but the statuses don't update in HA and it appears to be open permanently. Temperature doesn't report, running and status is all n/a Anyone still seeing similar? |
|
Same here for a long time |
|
Did you try flashing your controller? I am going to try that shortly. |
What happened?
After updating to 1.29 this morning my Aqara E1 motor no longer reports to home assistant that it has opened or closed instead staying on opening or closing long after the motor has stopped running.
I have tried removing and re-adding the motor and also updated the coordinator to the latest firmware but it has made no difference.
In zigbee2mqtt in the state tab shows "state": "OFF", no mater the position of the blind unless you hit the stop button from which point on it will show "state": "STOP", even when the motor is running
What did you expect to happen?
No response
How to reproduce it (minimal and precise)
No response
Zigbee2MQTT version
1.29.0
Adapter firmware version
20221226
Adapter
Slaesh CC2652RB
Debug log
No response
The text was updated successfully, but these errors were encountered: