search

Koenkk / zigbee2mqtt

Zigbee 🐝 to MQTT bridge 🌉, get rid of your proprietary Zigbee bridges 🔨
https://www.zigbee2mqtt.io
GNU General Public License v3.0
11.2k stars 1.6k forks source link

ZNJLBL01LM show as Unknown after 1.37.0 #22387

Closed clowncracker closed 1 week ago

clowncracker commented 2 weeks ago

What happened?

After updating to 1.37.0 from 1.36.1, the blinds no longer show Open/Closed, they only show as Unknown.

What did you expect to happen?

I expect the blinds to show Closed or Open, not Unknown.

How to reproduce it (minimal and precise)

Upgrade to 1.37.0 and I get this issue. Downgraded back to 1.36.1 and the state came back.

Zigbee2MQTT version

1.37.0

Adapter firmware version

20220219

Adapter

SONOFF Zigbee 3.0 USB Dongle Plus Gateway

Setup

Add-on on Unraid VM

Debug log

No response

10Thirty commented 2 weeks ago

My ZNJLBL01LM Is also showing the same issue on a UZG-01 with firmware 20240316. I also tried connecting it to an aqara hub to see if there was a newer firmware as #22299 references fw 09-12-2023 but there isn't one available so it could be there is a newer revision that is slightly different or a difference between Chinese and EU ones.

cromelex commented 2 weeks ago

As mention on my comment on https://github.com/Koenkk/zigbee2mqtt/issues/22397

Same issue here. Not sure if this is with Zigbee2MQTT 1.37.0 or Home Assistant 2024.05.0

To be clear, Z2M seems to have all the info, but in Home Assistant the state of the cover.entity is "unknown"

{ "battery": 43, "charging_status": false, "device_temperature": 23, "last_seen": "2024-05-02T11:14:40+01:00", "linkquality": 116, "motor_speed": "medium", "motor_state": "pause", "position": 36, "power_outage_count": 2, "running": false, "state": "OFF" }

image

Looking at some automations I had, the attribute in HASS was previously "position", but now it is "current_position".

Was this changed in 1.37.0 ? That could be the cause of this issue.

The attribute in HASS was previously "position", but now it is "current_position" for the cover.entity. I think this might be the issue.

frops83 commented 2 weeks ago

same problem here, hoping for a fix

Koenkk commented 2 weeks ago

Pushed a fix, let me know if it works.

Changes will be available in the dev branch in a few hours from now.

allistermaguire commented 2 weeks ago

Hi @Koenkk, this is also a similar issue for the ZNCLDJ12LM, line 2626 in src/lib/lumi.ts. Should be 'stopped' and not 'stop'?

if (['ZNCLDJ12LM', 'ZNCLDJ14LM'].includes(model.model)) lookup = {0: 'closing', 1: 'opening', 2: 'stop'};
golles commented 2 weeks ago

Pushed a fix, let me know if it works.

Changes will be available in the dev branch in a few hours from now.

Image koenkk/zigbee2mqtt:latest-dev (Last pushed 41 minutes ago by koenkk) fixes this issue for me!

Dillton commented 2 weeks ago

Hi @Koenkk, this is also a similar issue for the ZNCLDJ12LM, line 2626 in src/lib/lumi.ts. Should be 'stopped' and not 'stop'?

if (['ZNCLDJ12LM', 'ZNCLDJ14LM'].includes(model.model)) lookup = {0: 'closing', 1: 'opening', 2: 'stop'};

Hello @Koenkk I can confirm this for ZNCLDJ12LM. The state for this one is still opening or closing even when the motor is currently stopped. Please push fix for this also. Thanks in advance.

golles commented 1 week ago

Besides everything working fine, the HA log has many entries like WARNING (MainThread) [homeassistant.components.mqtt.cover] Payload is not supported (e.g. open, closed, opening, closing, stopped): pause

There is already a ticket for this btw #22417

burmistrzak commented 1 week ago

Hi @Koenkk, this is also a similar issue for the ZNCLDJ12LM, line 2626 in src/lib/lumi.ts. Should be 'stopped' and not 'stop'?

if (['ZNCLDJ12LM', 'ZNCLDJ14LM'].includes(model.model)) lookup = {0: 'closing', 1: 'opening', 2: 'stop'};

Hello @Koenkk I can confirm this for ZNCLDJ12LM. The state for this one is still opening or closing even when the motor is currently stopped. Please push fix for this also. Thanks in advance.

Quickly fixed that for you. https://github.com/Koenkk/zigbee-herdsman-converters/pull/7483

GoodnessJSON commented 1 week ago

When is this expected to be picked up in the main add-on? Would prefer not to swap to dev if I can help it to avoid any future headaches. Thanks for the incredible work!

burmistrzak commented 1 week ago

When is this expected to be picked up in the main add-on? Would prefer not to swap to dev if I can help it to avoid any future headaches. Thanks for the incredible work!

Well, that's totally up to @Koenkk 🔮, but dev isn't that scary. Running it myself. 😎

Koenkk commented 1 week ago

I will probably do a hotfix release in the coming days, but good that this is fixed now!

Changes will be available in the dev branch in a few hours from now.

clowncracker commented 1 week ago

@Koenkk I just tried using the dev branch and it looks like this issue is fixed, however I've run into another problem. I'm now seeing this in my logs when I only open my blinds partway:

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

Should I open a new ticket or should we reopen this one since it's related to the update?

burmistrzak commented 1 week ago

I just tried using the dev branch and it looks like this issue is fixed, however I've run into another problem. I'm now seeing this in my logs when I only open my blinds partway:

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

Should I open a new ticket or should we reopen this one since it's related to the update?

@clowncracker What's the exact zigbeeModel of your device?

clowncracker commented 1 week ago

I just tried using the dev branch and it looks like this issue is fixed, however I've run into another problem. I'm now seeing this in my logs when I only open my blinds partway: Payload is not supported (e.g. open, closed, opening, closing, stopped): pause Should I open a new ticket or should we reopen this one since it's related to the update?

@clowncracker What's the exact zigbeeModel of your device?

lumi.curtain.acn002

burmistrzak commented 1 week ago

I just tried using the dev branch and it looks like this issue is fixed, however I've run into another problem. I'm now seeing this in my logs when I only open my blinds partway: Payload is not supported (e.g. open, closed, opening, closing, stopped): pause Should I open a new ticket or should we reopen this one since it's related to the update?

@clowncracker What's the exact zigbeeModel of your device?

lumi.curtain.acn002

And the exact commit/version of your Z2M install?

clowncracker commented 1 week ago

I just tried using the dev branch and it looks like this issue is fixed, however I've run into another problem. I'm now seeing this in my logs when I only open my blinds partway: Payload is not supported (e.g. open, closed, opening, closing, stopped): pause Should I open a new ticket or should we reopen this one since it's related to the update?

@clowncracker What's the exact zigbeeModel of your device?

lumi.curtain.acn002

And the exact commit/version of your Z2M install?

1.37.0-dev commit: 358e2ee

burmistrzak commented 1 week ago

@clowncracker Hmm, it's possible that your HA configuration still has the old position values saved/discovered?

The specific model you've mentioned seems to be already fixed.

There's currently only one model that still exposes pause.

fir3drag0n commented 1 week ago

With latest 1.37.0-dev commit: 358e2ee the state is again not showed anymore.

In Z2M it is shown, but in home assistant the state shows as unavailable.

Koenkk commented 1 week ago

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

When is this logged?

clowncracker commented 1 week ago

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

When is this logged?

I'm no longer having this issue. I think that @burmistrzak was correct, I think the status was just cached. Moving the blinds back to closed and then opening them again partway solved the issue.