Why doesn't HA show the device connected via zigbee and Zigbee2MQTT?

[belamy (Ralph)]

I have a 4-button switch connected to HA via zigbee: Tuya TS0044 control via MQTT | Zigbee2MQTT Tuya TS0044 control via MQTT | Zigbee2MQTT
Everything worked fine for 2 years and recently stopped working.
I removed the switch from zigbee2mqtt, paired it again.
In Zigbee2mqtt everything works fine, pressing each button is displayed in the Zigbee2Mqtt panel but there is no switch on the HA device list.
If I go to HA->Developer Tools->Device STATES the device is not on the list.
I also checked MQTT Explorer and the data reaches the MQTT broker:
in the branch: zigbee2mqtt/Switch-4-pos I have:
{

“battery”: 100,*
“last_seen”: “2025-02-16T21:14:03.781Z”,*
“linkquality”: 255,*
“voltage”: 3000*
}

and when I press a button, the status also appears:

zigbee2mqtt/Switch-4-pos/action
1_single

but why doesn’t HA show it?

[koying (Chris B)]

Assuming you upgraded your Z2M to 2.*:

Zigbee2MQTT 2.0.0 breaking changes · Koenkk/zigbee2mqtt · Discussion #24198

Specifically:

All action sensors are now disabled by default (sensor.*_action entities). It’s recommended to use the MQTT device trigger instead.

[belamy (Ralph)]

My Zigbee2MQTT version is 2.1.1-1 and I understand issue about actions but shouldn’t it show device state and entities Switch-4-pos?
{

“battery”: 100,*
“last_seen”: “2025-02-16T21:14:03.781Z”,*
“linkquality”: 255,*
“voltage”: 3000*
}

[ShadowFist]

@belamy

I removed the switch from zigbee2mqtt, paired it again.

When you did that, did you also update the name and make sure to select “Update Home Assistant entities” (or something similar).

If you didn’t, HA is still referring to the switch by the default random bunch of numbers.

[Cyberbeni (Benedek Kozma)]

You want to turn on “Home Assistant legacy action sensors” inside Zigbee2MQTT, the new events are really bad, one of the admins even opened a WTF thread about them.

[maxym]

Cyberbeni,
would you like to point us to this issue?
While new triggers work ok to me, I’m curious what might be the cons of this approach.

[Cyberbeni (Benedek Kozma)]

WTH are event entities not triggered a second time when using the attribute `event_type` in a state trigger?

The new event entities are meant to replace old school event triggers (and Z2M sensor’s). The problem is, the features are not 1 to 1. Old school events will always trigger when an event occurs, same with the legacy event sensors in z2m. The new event entities do not support this functionality though. If the same event comes through a second time, the event is essentially ignored because the event_type attribute does not change. It’s also not clear to users how to get around this issue. Yo…

There is also a possibility for people to set it up in a way that triggers it after a HA restart.

[belamy (Ralph)]

That was a problem. I had disabled “legacy” and “experimental” options at Zigbee2MQTT->Settinges->Home Assistant Integrations

Thanks

[belamy (Ralph)]

Yes, I always remember to have “Update Home Assistant entities” enabled when rename devices.
It was different problem caused by new method of maintaining buttons event at new version od Zigbee2MQTT (since 2.0).
Cyberbeni and my replies resolve this problem.

[maxym]

Thank you.
It seems I don’t experience those issues because I solely use the NodeRed for automations.