Skip to content
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

1.37.0 - Aqara ZNJLBL01LM and Lumi rollers no longer work due to change #7470 #22417

Closed
GoodnessJSON opened this issue May 3, 2024 · 12 comments
Labels
problem Something isn't working

Comments

@GoodnessJSON
Copy link

GoodnessJSON commented May 3, 2024

What happened?

Ever since the 1.37.0 update I get continual errors in my Home Assistant Log as follows:

Logger: homeassistant.components.mqtt.cover
Source: components/mqtt/cover.py:416
integration: MQTT (documentation, issues)
First occurred: 4:15:46 PM (5 occurrences)
Last logged: 4:28:04 PM

Payload is not supported (e.g. open, closed, opening, closing, stopped): pause
Payload is not supported (e.g. open, closed, opening, closing, stopped): rising
Payload is not supported (e.g. open, closed, opening, closing, stopped): declining

This means that my Aqare ZNJLBL01LM (lumi.curtain.acn002) rollers never report an Open or Closed status.

This means that my Home Assistant scenes are currently broken and cannot be edited as the scenes rely upon an accurate 'live' value to be set and then replicated. They are currently stuck in 'Open' in HA MQTT from when it last reported successfully, even though they are in fact closed and show as position 0% indicating they are closed.

I believe this is related to Koenkk/zigbee-herdsman-converters#7470

What did you expect to happen?

For my rollers to use the expected motor states:
open, closed, opening, closing, stopped

instead of pause, rising, declining.

How to reproduce it (minimal and precise)

By opening and closing your roller blinds.

Zigbee2MQTT version

1.37.0

Adapter firmware version

7.3.1.0 build 176 on EZPZ

Adapter

SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2

Setup

Add on for Home-Assistant in HAOS running on x86-64

Debug log

2024-05-03 16:33:02.671 WARNING (MainThread) [homeassistant.components.mqtt.cover] Payload is not supported (e.g. open, closed, opening, closing, stopped): declining
2024-05-03 16:33:05.739 WARNING (MainThread) [homeassistant.components.mqtt.cover] Payload is not supported (e.g. open, closed, opening, closing, stopped): pause
2024-05-03 16:33:05.747 WARNING (MainThread) [homeassistant.components.mqtt.cover] Payload is not supported (e.g. open, closed, opening, closing, stopped): pause
2024-05-03 16:33:05.995 WARNING (MainThread) [homeassistant.components.mqtt.cover] Payload is not supported (e.g. open, closed, opening, closing, stopped): pause
2024-05-03 16:33:11.430 WARNING (MainThread) [homeassistant.components.mqtt.cover] Payload is not supported (e.g. open, closed, opening, closing, stopped): rising
2024-05-03 16:33:12.709 WARNING (MainThread) [homeassistant.components.mqtt.cover] Payload is not supported (e.g. open, closed, opening, closing, stopped): rising
2024-05-03 16:33:13.988 WARNING (MainThread) [homeassistant.components.mqtt.cover] Payload is not supported (e.g. open, closed, opening, closing, stopped): rising
2024-05-03 16:33:14.505 WARNING (MainThread) [homeassistant.components.mqtt.cover] Payload is not supported (e.g. open, closed, opening, closing, stopped): rising
2024-05-03 16:33:14.765 WARNING (MainThread) [homeassistant.components.mqtt.cover] Payload is not supported (e.g. open, closed, opening, closing, stopped): rising
2024-05-03 16:33:15.032 WARNING (MainThread) [homeassistant.components.mqtt.cover] Payload is not supported (e.g. open, closed, opening, closing, stopped): pause
2024-05-03 16:33:15.043 WARNING (MainThread) [homeassistant.components.mqtt.cover] Payload is not supported (e.g. open, closed, opening, closing, stopped): pause
2024-05-03 16:33:15.289 WARNING (MainThread) [homeassistant.components.mqtt.cover] Payload is not supported (e.g. open, closed, opening, closing, stopped): pause
@GoodnessJSON GoodnessJSON added the problem Something isn't working label May 3, 2024
@stigvi
Copy link

stigvi commented May 3, 2024

This means that my Home Assistant scenes are currently broken and cannot be edited as the scenes rely upon an accurate 'live' value to be set and then replicated.

FYI: Scenes can be edited with a text editor. Are they not defined in scenes.yaml or another yaml-file in your system?

@GoodnessJSON
Copy link
Author

GoodnessJSON commented May 3, 2024

This means that my Home Assistant scenes are currently broken and cannot be edited as the scenes rely upon an accurate 'live' value to be set and then replicated.

FYI: Scenes can be edited with a text editor. Are they not defined in scenes.yaml or another yaml-file in your system?

Apparently they get overwritten the moment you open or save anything in the UI as they are held in memory (which sometimes is handy to do when on Mobile). Also, for some reason the motor state factors into the scene and errors out adjusting the blind.

@stigvi
Copy link

stigvi commented May 3, 2024

Apparently they get overwritten the moment you open or save anything in the UI as they are held in memory (which sometimes is handy to do when on Mobile)

That is true. When they are edited in a text editor, you have to go to the developer tools and press the scenes reload button.

@hellcry37
Copy link

This is not regarding scenes, I have this Aqare ZNJLBL01LM (lumi.curtain.acn002) rollers and got same behavior without using scenes

@GoodnessJSON
Copy link
Author

This is not regarding scenes, I have this Aqare ZNJLBL01LM (lumi.curtain.acn002) rollers and got same behavior without using scenes

Yep correct, it's just particularly inconvenient for scenes.

@burmistrzak
Copy link

@GoodnessJSON You'll need at least https://github.com/Koenkk/zigbee-herdsman-converters/releases/tag/v19.34.0 for the hotfix. 🔥

Also make sure no old values for state_opening & Co. are still in your configuration.yaml, just in case.

@barrymossel
Copy link

Same issue for me.

@andyblac
Copy link

andyblac commented May 3, 2024

@GoodnessJSON You'll need at least https://github.com/Koenkk/zigbee-herdsman-converters/releases/tag/v19.34.0 for the hotfix. 🔥

Also make sure no old values for state_opening & Co. are still in your configuration.yaml, just in case.

hope this gets pushed to HA add-on soon.

@burmistrzak
Copy link

burmistrzak commented May 3, 2024

@andyblac You might want to switch to the dev branch, otherwise you'll have to wait a bit for a .1 release.

@GoodnessJSON
Copy link
Author

GoodnessJSON commented May 4, 2024

@GoodnessJSON You'll need at least https://github.com/Koenkk/zigbee-herdsman-converters/releases/tag/v19.34.0 for the hotfix. 🔥

Also make sure no old values for state_opening & Co. are still in your configuration.yaml, just in case.

Thanks for this, when do you think it will make it to the official release? Or how can you get this change?

@burmistrzak
Copy link

@GoodnessJSON You'll need at least https://github.com/Koenkk/zigbee-herdsman-converters/releases/tag/v19.34.0 for the hotfix. 🔥
Also make sure no old values for state_opening & Co. are still in your configuration.yaml, just in case.

Thanks for this, when do you think it will make it to the official release? Or how can you get this change?

Please see my response above. 😉

@Koenkk
Copy link
Owner

Koenkk commented May 4, 2024

I will publish a hotfix release soon!

@Koenkk Koenkk closed this as completed May 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
problem Something isn't working
Projects
None yet
Development

No branches or pull requests

7 participants