home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
73.71k stars 30.84k forks source link

In all ver HA after 2024.7.0 don't working tuya cover (curtains) and thermostats (head) from MQTT (Z2M) #124882

Open diemon24 opened 2 months ago

diemon24 commented 2 months ago

The problem

After updated Core 2024.7.0 and 2024.8.3 my covers and thermostats don't working. In MQTT this devices unavailable. But it's working in Z2M and if downgrade HA ver to 2024.5.5. I deleted this device from MQTT integration, renamed in Z2M i see don't working device in ver after 2024.7.0. I don't think what this problem with MQTT integration or Z2M, this problem I see only after update HA ver.

My other 100 devices working in all ver HA. Problem only this 2 type devices.

Zigbee2MQTT 1.39.1 commit: [e132316] zStack3x0

image image

all ver after 2024.7.0

this device in HA 2024.8.3 IMG_7819

IMG_7820

this device in HA 2024.5.5

image image image image

its working

image

What version of Home Assistant Core has the issue?

2024.8.3

What was the last working version of Home Assistant Core?

2024.5.5

What type of installation are you running?

Home Assistant Core

Integration causing the issue

MQTT

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

diemon24 commented 1 month ago

Please, have you reported when it will be fixed?

home-assistant[bot] commented 1 month ago

Hey there @emontnemery, @jbouwh, @bdraco, mind taking a look at this issue as it has been labeled with an integration (mqtt) you are listed as a code owner for? Thanks!

Code owner commands Code owners of `mqtt` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign mqtt` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


mqtt documentation mqtt source (message by IssueLinks)

jbouwh commented 1 month ago

Hi @diemon24 , there were no recent changes to the mqtt cover component. To reproduce I need the configs (in json) not screenshots including the payload that are send/received.

With these steps we need the expected result and the actual result.

diemon24 commented 1 month ago

Hi @diemon24 , there were no recent changes to the mqtt cover component. To reproduce I need the configs (in json) not screenshots including the payload that are send/received.

With these steps we need the expected result and the actual result.

Thanks for your reply. I think the problem is in MQTT topics. What json files do you need and where can I get them so you can investigate the problem in more detail?

jbouwh commented 1 month ago

Thanks for your reply. I think the problem is in MQTT topics. What json files do you need and where can I get them so you can investigate the problem in more detail?

That might be the issue indeed. Some characters are not allowed in MQTT topics. May be you can try to update those.

jbouwh commented 1 month ago

If the covers are discovered, but are not responding, then try to see when payloads are send from Home Assistant. To see these in the HA core logs, you might need to turn on debug logging for homeassistant.components.mqtt.

diemon24 commented 12 hours ago

If the covers are discovered, but are not responding, then try to see when payloads are send from Home Assistant. To see these in the HA core logs, you might need to turn on debug logging for homeassistant.components.mqtt.

Thank you. I will try to do it soon.