search

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
71.31k stars 29.86k forks source link

loss of connection on the automations with all the equipment that has buttons, whether Lidl or IKEA by Zigbee2MQTT #110493

Closed IncendioMoussy closed 7 months ago

IncendioMoussy commented 7 months ago

The problem

HELLO, You have reported a bug for some time now, I have a loss of connection on the automations with all the equipment that has buttons, whether Lidl or IKEA. I did the investigations, in Zigbee2MQTT, ie receives the information from the Zigbee network, which is transmitted MQTT, We see on the device via MQTT that there is an activity, but I notice two things, in MQTT: 1 the one hand, if we want to add automation it says that the device has no possibility. 2 the information is not transmitted to the automation in connection with its equipment. I can very easily fix the problem by renaming the device from Zigbee2MQTT. I have not been able to determine the factor that leads to this result. But often these suites caused Home Assistant to freeze, and I had to restart HA.

From Device :

STYRBAR remote control (E2001/E2002) SOMRIG shortcut button (E2213) Silvercrest smart wireless door bell button (HG06668) Livarno Lux switch and dimming light remote control (FB20-002) Livarno Lux switch and dimming light remote control (FB21-001)

Original in french

Bonjour, Je signale un bug depuis quelques temps j'ai une perte de liaison sur les automations avec tous les équipements qui ont des boutons que ce soit Lidl ou IKEA. J'ai fait les investigations, dans Zigbee2MQTT, ie reçoit bien les informations du réseau Zigbee, qui sont bien transmis MQTT, On voit sur le périphérique via MQTT qu'il y a une activité, mais je constate deux choses, dans MQTT, d'une part que si on veut ajouter une automation il dit que le périphérique n'a aucune possibilité. Et les informations ne sont pas transmises à l'automation en lien avec ses équipements. Je peux très facilement résoudre le problème en renommant le périphérique depuis Zigbee2MQTT. je n'ai pas pu déterminer le facteur qui mène à ce résultat. Mais souvent ces suites un gel d'Home Assistant, et que j'ai dû redémarrer HA.

System Information

version core-2024.2.1
installation_type Home Assistant OS
dev false
hassio true
docker true
user root
virtualenv false
python_version 3.12.1
os_name Linux
os_version 6.1.74-haos
arch x86_64
timezone Europe/Paris
config_dir /config
Home Assistant Community Store GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok GitHub API Calls Remaining | 4995 Installed Version | 1.34.0 Stage | running Available Repositories | 1457 Downloaded Repositories | 35
Home Assistant Cloud logged_in | false -- | -- can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | ok
Home Assistant Supervisor host_os | Home Assistant OS 11.5 -- | -- update_channel | stable supervisor_version | supervisor-2024.01.1 agent_version | 1.6.0 docker_version | 24.0.7 disk_total | 916.2 GB disk_used | 219.2 GB healthy | true supported | true board | generic-x86-64 supervisor_api | ok version_api | ok installed_addons | File editor (5.8.0), Mosquitto broker (6.4.0), FTP (5.0.1), Samba share (12.3.0), Silicon Labs Multiprotocol (2.4.4), Zigbee2MQTT (1.35.3-1), Matter Server (5.1.2), OpenThread Border Router (2.4.5), Advanced SSH & Web Terminal (17.1.0)
Dashboards dashboards | 27 -- | -- resources | 19 views | 27 mode | storage
Recorder oldest_recorder_run | 4 février 2024 à 05:09 -- | -- current_recorder_run | 13 février 2024 à 17:48 estimated_db_size | 32544.80 MiB database_engine | sqlite database_version | 3.44.2

What version of Home Assistant Core has the issue?

2024.2.1

What was the last working version of Home Assistant Core?

2024.2.1

What type of installation are you running?

Home Assistant OS

Integration causing the issue

No response

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

home-assistant[bot] commented 7 months ago

Hey there @emontnemery, @jbouwh, 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 7 months ago

Make sure your device triggers are unique. Check the MQTT logs. This is not an issue with Home Assistant or the MQTT integration. Duplicate of #109885

jbouwh commented 7 months ago

Possible related to https://github.com/Koenkk/zigbee2mqtt/issues/21158

Probably fixed with Zigbee2Mqtt 1.35.3.

Closing as this is not an issue with Home Assistant Core