Device trigger broken in automations

[Chartreusito]

The problem

All my automations using Device triggers on zigbee devices are broken. The triggers are now all reported as "Unknown trigger" as seen below

If i try to update the trigger i'm only able to select update/availability/battery related ones as seen below

The problem is similar for 4 different types of zigbee buttons/switches of different brands. I'm using the latest version of zigbee2mqtt. Restarting zigbee2mqtt does not resolve the issue. Restarting HA used to sometimes fix it on core-2023.11.x but it now fails everytime to bring the triggers up.

I can replace the device triggers with MQTT triggers so that it works but i'd much rather prefer it to be fixed.

What version of Home Assistant Core has the issue?

core-2023.12.0

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Automation

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

alias: rideaux_fermeture_totale
description: >-
  Fermeture de tous les rideaux à l'aide du bouton gauche de la télécommande
  styrbar
trigger:
  - platform: device
    domain: mqtt
    device_id: a3e810b43de5027c4f380c5922d6ee05
    type: action
    subtype: arrow_left_click
    discovery_id: 0x94deb8fffe4563ea action_arrow_left_click
  - platform: state
    entity_id:
      - sensor.telecommande_rideaux_maison_action
    attribute: arrow_left_click
  - platform: mqtt
    topic: zigbee2mqtt/telecommande_rideaux_maison/action
    payload: arrow_left_click
condition:
  - condition: and
    conditions:
      - type: is_not_open
        condition: device
        device_id: 521513d87ece85fb4c1710b914ce3677
        entity_id: 21cbcbf878fa4acdeb7add470a57e839
        domain: binary_sensor
      - type: is_not_open
        condition: device
        device_id: a9e369e57f879c948cbd9adb7924d205
        entity_id: a48aa99efb8ac8a7f70c51273e8bad33
        domain: binary_sensor
      - type: is_not_open
        condition: device
        device_id: eae3a7d06b620433850a5e91aba398eb
        entity_id: 4bb502c4ef6a235854d55d41bbd3f4eb
        domain: binary_sensor
      - type: is_not_open
        condition: device
        device_id: 96f968dd53290b4230a480965c78aeb7
        entity_id: b9517db67e02911186344fff8a10f579
        domain: binary_sensor
      - type: is_not_open
        condition: device
        device_id: 22bba1f1f82a0f79250a9d3458505c40
        entity_id: 9c6595c9fd470bebbf0c457f7d8a646e
        domain: binary_sensor
      - type: is_not_open
        condition: device
        device_id: dbc3ade41369e306f4f1a45066e2f0a0
        entity_id: 1eba89199d397bc70bd998ca463e3223
        domain: binary_sensor
      - type: is_not_open
        condition: device
        device_id: fcd20871fdc338d0257232885b000d74
        entity_id: 54dbc6cbde647959384c24dad4553ea4
        domain: binary_sensor
      - type: is_not_open
        condition: device
        device_id: b66fcad94c708d96afb6f9130ecdff33
        entity_id: ec583f8e1c435725bcd16e1b99b6223e
        domain: binary_sensor
action:
  - service: cover.close_cover
    data: {}
    entity_id: all
mode: single

Anything in the logs that might be useful for us?

No response

Additional information

No response

[elektrinis]

Have you resolved this? I have a similar issue, with z2m as well:

• All trigger IDs have been cleared.
• All device/entity IDs have been cleared.

I have tried to copy-paste the automation from a backup, but device IDs are not recognized. I had to recreate all of automations manually. And I have some really complex ones, it was a huge task. There seems to be a change in how automations work, as previously entity IDs were human-friendly, and now they are in hex.

I'm not totally sure when this happened: after update to HA 2023.12, or after z2m stopped working due to me trying to update sonoff stick firmware. Whatever the reason is, the fact that my automations got actually edited is alarming.

[Calimerorulez]

I've got the same problem. Running HA 2023.12 and 2024.2.

[Chartreusito]

I ended up switching to MQTT Trigger Baring z2m related issue, the trigger handling as been flawless since.

[jbouwh]

I believe this is a Z2M issue. Iam closing this one. Please update Z2M to at least version. 1.35.3. If that does not help open an issue for Z2M instead of HA Core.