E1524/E1810 Tradfri remotes no longer work in 2.0

[arjenanker]

What happened?

After installing the 2.0 update, all my remotes no longer worked in Home Assistant. Looking at the Z2M logs, nothing happens when I push a button on a remote. Nothing in the logs whatsoever.

Trying to re-pair a remote ends up in the remote not being able to finish the interview with "Error: Interview failed because we can not get active endpoints".

I had to downgrade back to my backup of 1.42.0-2. Remotes worked again, pairing the remote that couldn't complete the interview worked straight away too.

What did you expect to happen?

I expect my remotes to work like they worked in the previous version.

How to reproduce it (minimal and precise)

Update to 2.0 and try to use a E1524 remote or try and pair a E1524 remote.

Zigbee2MQTT version

2.0

Adapter firmware version

20201026

Adapter

Texas Instruments LAUNCHXL-CC26X2R1

Setup

Addon on HA OS VM on Proxmox

Debug log

No response

[m0wlheld]

Could be related to breaking changes #24198

[arjenanker]

Well, all those remotes use *_action triggers. However, the z2m logs showed absolutely nothing when I pushed buttons on those remotes, which seems odd to me. Shouldn't the logs at least say something was triggered?

And, I still can't pair them in 2.0, which seems a separate issue.

Unfortunately, I can't test any of this since I downgraded since the Z2M addon was removed so I can't update again until that is resolved.

[Jopy2104]

Having the exact same problem. Can no longer remotely control anything anymore, becasue the _action triggers are all gone from Home Assistant. I can see the actions in Zigbee2MQTT.

#24198 gives a solution to this problem, which I will try.

Trigger solution is doubtful, because I am using IKEA tradfri remotes in the "Awesome HA Blueprints" (https://epmatt.github.io/awesome-ha-blueprints). And they only allow to enter an action sensor as controller entity.

Setting the "legacy_action_sensor: true" in configuration.yaml as mentioned in #24198 is my workaround until the blueprint accepts triggers.

For the moment, my problem is solved.

[eastvan]

Well, all those remotes use *_action triggers. However, the z2m logs showed absolutely nothing when I pushed buttons on those remotes, which seems odd to me. Shouldn't the logs at least say something was triggered?

And, I still can't pair them in 2.0, which seems a separate issue.

Unfortunately, I can't test any of this since I downgraded since the Z2M addon was removed so I can't update again until that is resolved.

I can confirm I have the same issue after updating Z2M to 2.0.0-2.
I am aware of the breaking changes described in #24198, and I was able to modify the existing automations after upgrading to 2.0.0-1 and the remote was working correctly for a day until I moved to 2.0.0 - 2.
As you correctly noted, there are no events in the logs when I press the buttons. The battery is 100%, tried to reset the device a few times without any luck.

[Koenkk]

@eastvan you should see events in the debug log when pressing the buttons, do you get any?

See this on how to enable debug logging.

[eastvan]

No events whatsoever. I enabled "permit join" and try to reset the remote. The log entries related to that

[2025-01-06 13:16:35] debug: 	zh:controller: Device '0x588e81fffeb4e59b' joined
[2025-01-06 13:16:35] debug: 	zh:zstack:unpi:parser: --- parseNext []
[2025-01-06 13:16:35] debug: 	zh:controller: Device '0x588e81fffeb4e59b' accepted by handler
[2025-01-06 13:16:35] debug: 	zh:controller: Device '0x588e81fffeb4e59b' is already in database with different network address, updating network address
[2025-01-06 13:16:35] debug: 	zh:controller:database: Writing database to '/config/zigbee2mqtt/database.db'
[2025-01-06 13:16:35] info: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Remote Control', payload '{"battery":90,"identify":null,"last_seen":"2025-01-06T13:16:35-08:00","linkquality":10,"update":{"installed_version":604241925,"latest_version":604241925,"state":"idle"},"update_available":false}'
[2025-01-06 13:16:35] debug: 	zh:controller: Not interviewing '0x588e81fffeb4e59b', completed 'true', in progress 'false'

No events when I press any buttons after that
I removed the device completely from Z2M and try to join it. I can no longer join the remote as per below

2025-01-06 13:23:31z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/response/permit_join', payload '{"data":{"time":254},"status":"ok","transaction":"hcvl1-4"}'
info 2025-01-06 13:23:52z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/0x588e81fffeb4e59b', payload '{"last_seen":"2025-01-06T13:23:52-08:00","linkquality":112,"update":{"installed_version":-1,"latest_version":-1}}'
info 2025-01-06 13:23:52zh:controller: Interview for '0x588e81fffeb4e59b' started
info 2025-01-06 13:23:52z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/0x588e81fffeb4e59b', payload '{"last_seen":"2025-01-06T13:23:52-08:00","linkquality":112,"update":{"installed_version":-1,"latest_version":-1}}'
info 2025-01-06 13:23:52z2m: Device '0x588e81fffeb4e59b' joined
info 2025-01-06 13:23:52z2m: Starting interview of '0x588e81fffeb4e59b'
info 2025-01-06 13:23:53z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x588e81fffeb4e59b","ieee_address":"0x588e81fffeb4e59b"},"type":"device_joined"}'
info 2025-01-06 13:23:53z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x588e81fffeb4e59b","ieee_address":"0x588e81fffeb4e59b","status":"started"},"type":"device_interview"}'
info 2025-01-06 13:23:55z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/0xa4c138b4b3838a19', payload '{"battery":88,"humidity":43.75,"last_seen":"2025-01-06T13:23:55-08:00","linkquality":109,"temperature":22.37,"voltage":2900}'
info 2025-01-06 13:24:12z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/0x588e81fffeb4e59b', payload '{"last_seen":"2025-01-06T13:24:12-08:00","linkquality":112,"update":{"installed_version":-1,"latest_version":-1}}'
info 2025-01-06 13:24:12z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x588e81fffeb4e59b","ieee_address":"0x588e81fffeb4e59b"},"type":"device_announce"}'
error 2025-01-06 13:24:12zh:controller: Interview failed for '0x588e81fffeb4e59b with error 'Error: Interview failed because can not get active endpoints ('0x588e81fffeb4e59b')'
error 2025-01-06 13:24:12z2m: Failed to interview '0x588e81fffeb4e59b', device has not successfully been paired

[soostdijck]

Same issue here, when I look in z2m itself, under the "state" tab for the device I do see it registering presses. (Make sure you press different buttons, because the same button keeps sending the same things, which hides the change).
The info doesn't seem to make it into HASS though.

The logs in the z2m plugin inside HASS shows these logs:

[2025-01-06 22:53:43] info: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/ikea puck woonkamer', payload '{"action":"toggle","battery":90,"identify":null,"linkquality":43,"update":{"installed_version":604241925,"latest_version":604241925,"state":"idle"}}'
[2025-01-06 22:53:43] info: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/ikea puck woonkamer/action', payload 'toggle'
[2025-01-06 22:53:43] info: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/ikea puck woonkamer', payload '{"action":"toggle","battery":90,"identify":null,"linkquality":43,"update":{"installed_version":604241925,"latest_version":604241925,"state":"idle"}}'
[2025-01-06 22:53:43] info: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/ikea puck woonkamer/action', payload 'toggle'

The "logbook" inside HASS shows nothing.

[lensherm]

With the 1810 TRADFRI remote I can get it to work like so:

For a list of all available payloads, see here:
https://www.zigbee2mqtt.io/devices/E1524_E1810.html

I used the MQTT Explorer app to see the topic and payloads
https://mqtt-explorer.com/

[Fo3niks]

@soostdijck have you activated the legacy triggers option?

See: #25631 (comment)

[arjenanker]

No events whatsoever. I enabled "permit join" and try to reset the remote. The log entries related to that

[2025-01-06 13:16:35] debug: 	zh:controller: Device '0x588e81fffeb4e59b' joined
[2025-01-06 13:16:35] debug: 	zh:zstack:unpi:parser: --- parseNext []
[2025-01-06 13:16:35] debug: 	zh:controller: Device '0x588e81fffeb4e59b' accepted by handler
[2025-01-06 13:16:35] debug: 	zh:controller: Device '0x588e81fffeb4e59b' is already in database with different network address, updating network address
[2025-01-06 13:16:35] debug: 	zh:controller:database: Writing database to '/config/zigbee2mqtt/database.db'
[2025-01-06 13:16:35] info: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Remote Control', payload '{"battery":90,"identify":null,"last_seen":"2025-01-06T13:16:35-08:00","linkquality":10,"update":{"installed_version":604241925,"latest_version":604241925,"state":"idle"},"update_available":false}'
[2025-01-06 13:16:35] debug: 	zh:controller: Not interviewing '0x588e81fffeb4e59b', completed 'true', in progress 'false'

No events when I press any buttons after that I removed the device completely from Z2M and try to join it. I can no longer join the remote as per below

2025-01-06 13:23:31z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/response/permit_join', payload '{"data":{"time":254},"status":"ok","transaction":"hcvl1-4"}'
info 2025-01-06 13:23:52z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/0x588e81fffeb4e59b', payload '{"last_seen":"2025-01-06T13:23:52-08:00","linkquality":112,"update":{"installed_version":-1,"latest_version":-1}}'
info 2025-01-06 13:23:52zh:controller: Interview for '0x588e81fffeb4e59b' started
info 2025-01-06 13:23:52z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/0x588e81fffeb4e59b', payload '{"last_seen":"2025-01-06T13:23:52-08:00","linkquality":112,"update":{"installed_version":-1,"latest_version":-1}}'
info 2025-01-06 13:23:52z2m: Device '0x588e81fffeb4e59b' joined
info 2025-01-06 13:23:52z2m: Starting interview of '0x588e81fffeb4e59b'
info 2025-01-06 13:23:53z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x588e81fffeb4e59b","ieee_address":"0x588e81fffeb4e59b"},"type":"device_joined"}'
info 2025-01-06 13:23:53z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x588e81fffeb4e59b","ieee_address":"0x588e81fffeb4e59b","status":"started"},"type":"device_interview"}'
info 2025-01-06 13:23:55z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/0xa4c138b4b3838a19', payload '{"battery":88,"humidity":43.75,"last_seen":"2025-01-06T13:23:55-08:00","linkquality":109,"temperature":22.37,"voltage":2900}'
info 2025-01-06 13:24:12z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/0x588e81fffeb4e59b', payload '{"last_seen":"2025-01-06T13:24:12-08:00","linkquality":112,"update":{"installed_version":-1,"latest_version":-1}}'
info 2025-01-06 13:24:12z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x588e81fffeb4e59b","ieee_address":"0x588e81fffeb4e59b"},"type":"device_announce"}'
error 2025-01-06 13:24:12zh:controller: Interview failed for '0x588e81fffeb4e59b with error 'Error: Interview failed because can not get active endpoints ('0x588e81fffeb4e59b')'
error 2025-01-06 13:24:12z2m: Failed to interview '0x588e81fffeb4e59b', device has not successfully been paired

Had this exact thing. The remote can't be paired again, had to restore my backup of 1.42 to get my remote to pair again.

[sevorl]

same probleme here.
the sensor.*_action entity is no longer exposed to HA.
Had to downgrade to 1.42

[rwjack]

To confirm, by adding:

homeassistant:
  legacy_action_sensor: true

to the Z2M config, as per: #24198

and restarting Z2M, the remotes started working again.

I suppose the awesome blueprints would need to be reworked in order to be functional with Z2M > 2.0.0

[Fo3niks]

I suppose the awesome blueprints would need to be reworked in order to be functional with Z2M > 2.0.0

There's a fork that is already working on it. Now that the original creator EPMatt is back there are apparently efforts underway to merge those fixes back into the main repository.

EPMatt/awesome-ha-blueprints#622 (comment)

[Hessenpower01]

Same here, Remote no longer working under 2.0.0.2, unable to re pair. Downgraded to 1.42 and now working again.

[eastvan]

Downgrade to 1.42 resolved the issue with my remote as well. I noticed people having pairing issues with some other devices with the same error message.

Error: Interview failed because can not get active endpoints

Hopefully will be addressed soon