IKEA E1524/E1810 not working since Z2M 2.0.0 #25613

nicolinuxfr · 2025-01-06T12:37:53Z

nicolinuxfr
Jan 6, 2025

I'm using an old IKEA E1524 remote that worked great for years. Since 2.0.0, the device has no action entity, so every automations are broken.

Following the instructions on it's page, I tried to reconfigure but got this error every time and with no delay :

zigbee2mqtt  | [2025-01-06 09:42:33] error: 	z2m: Failed to configure 'Salon - télécommande', attempt 9 (TypeError: Cannot read properties of undefined (reading 'split')
zigbee2mqtt  |     at configure (/app/node_modules/.pnpm/zigbee-herdsman-converters@21.12.0/node_modules/src/lib/ikea.ts:205:52)
zigbee2mqtt  |     at Object.configure (/app/node_modules/.pnpm/zigbee-herdsman-converters@21.12.0/node_modules/src/index.ts:257:27)
zigbee2mqtt  |     at processTicksAndRejections (node:internal/process/task_queues:105:5)
zigbee2mqtt  |     at Configure.configure (/app/lib/extension/configure.ts:124:13)
zigbee2mqtt  |     at Configure.onMQTTMessage (/app/lib/extension/configure.ts:49:25)
zigbee2mqtt  |     at EventEmitter.wrappedCallback (/app/lib/eventBus.ts:204:17))

I tried to force remove the device and re-adding it, but I got this error during the interview process :

zigbee2mqtt  | [2025-01-06 13:31:45] error: 	zh:controller: Interview failed for '0x000b57fffe9ffb97 with error 'Error: Interview failed because can not get active endpoints ('0x000b57fffe9ffb97')'
zigbee2mqtt  | [2025-01-06 13:31:45] error: 	z2m: Failed to interview '0x000b57fffe9ffb97', device has not successfully been paired

I'm guessing this is a bug in 2.0.0 ? It's the only device that stopped working for me, after editing some configurations for others following the breaking changes notice.

jschonenberg · 2025-01-06T16:54:01Z

jschonenberg
Jan 6, 2025

FYI: I have (had?) the same issue, and noticed this comment in another issue: #22651 (comment)

This procedure (removing the battery, and reinserting it) allowed the interview to complete for me.

1 reply

nicolinuxfr Jan 6, 2025
Author

I saw the procedure and tried it, but it made no difference. What surprised me is the lack of delay, I don’t think the bug is that Z2M can’t reach the device, I think it’s lower in the stack and maybe a bug in Z2M itself. Since there was a breaking change related to actions, it made sense to me it was an update bug…

But do you have updated to Z2M 2.0.0 ? If so, is the remote working as usual ?

Koenkk · 2025-01-06T21:05:48Z

Koenkk
Jan 6, 2025
Maintainer

Pushed a fix for the failing configure!

Changes will be available in the dev branch in a few hours from now.

4 replies

sumasage Jan 7, 2025

Is the fix going to give the action entity back? I have a few Ikea buttons that stopped working. They paired fine but not action entity show up in HA. Just want to ask before i open a bug report. Thanks.

Pushed a fix for the failing configure!

Changes will be available in the dev branch in a few hours from now.

Chartreusito Jan 7, 2025
Sponsor

Is the fix going to give the action entity back? I have a few Ikea buttons that stopped working. They paired fine but not action entity show up in HA. Just want to ask before i open a bug report. Thanks.

Pushed a fix for the failing configure!
Changes will be available in the dev branch in a few hours from now.

All action sensors are now disabled by default, please read the changelog
You should use the MQTT device trigger instead.

nicolinuxfr Jan 7, 2025
Author

It's off-topic I guess, but what's weird is most of my devices (for instance all Aqara switches) still respond to actions. This IKEA remote is the only one that broke with the update for me.

sumasage Jan 8, 2025

Is the fix going to give the action entity back? I have a few Ikea buttons that stopped working. They paired fine but not action entity show up in HA. Just want to ask before i open a bug report. Thanks.

Pushed a fix for the failing configure!
Changes will be available in the dev branch in a few hours from now.

All action sensors are now disabled by default, please read the changelog You should use the MQTT device trigger instead.

I've read the documentation about MQTT Device Trigger. I dont understand much of is as i have limited coding background. It seem like instead of having the action now i have to code the action and automation. Not sure how this would translate over to NodeRed as that is where i have all my automations.

Koenkk · 2025-01-07T19:20:14Z

Koenkk
Jan 7, 2025
Maintainer

@nicolinuxfr could you try re-pairing the device and see if the device sends the actions after that? If not could you provide the debug log when pressing the buttons

See this on how to enable debug logging.

1 reply

nicolinuxfr Jan 8, 2025
Author

I tried, but I still get an error during the interview process, same as before :

zigbee2mqtt  |     at Object.start (/app/node_modules/.pnpm/zigbee-herdsman@3.2.1/node_modules/zigbee-herdsman/src/utils/waitress.ts:59:23)
zigbee2mqtt  |     at func (/app/node_modules/.pnpm/zigbee-herdsman@3.2.1/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:423:47)
zigbee2mqtt  |     at processTicksAndRejections (node:internal/process/task_queues:105:5)
zigbee2mqtt  |     at Queue.execute (/app/node_modules/.pnpm/zigbee-herdsman@3.2.1/node_modules/zigbee-herdsman/src/utils/queue.ts:36:20)
zigbee2mqtt  |     at ZStackAdapter.sendZdoInternal (/app/node_modules/.pnpm/zigbee-herdsman@3.2.1/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:428:43)
zigbee2mqtt  |     at ZStackAdapter.sendZdo (/app/node_modules/.pnpm/zigbee-herdsman@3.2.1/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:305:16)
zigbee2mqtt  |     at Endpoint.bind (/app/node_modules/.pnpm/zigbee-herdsman@3.2.1/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:562:30)
zigbee2mqtt  |     at configure (/app/node_modules/.pnpm/zigbee-herdsman-converters@21.14.0/node_modules/src/lib/modernExtend.ts:228:17)
zigbee2mqtt  |     at Object.configure (/app/node_modules/.pnpm/zigbee-herdsman-converters@21.14.0/node_modules/src/index.ts:257:21)
zigbee2mqtt  |     at Configure.configure (/app/lib/extension/configure.ts:124:13))
zigbee2mqtt  | [2025-01-08 08:20:40] error: 	zh:controller: Interview failed for '0x000b57fffe9ffb97 with error 'Error: Interview failed because can not get active endpoints ('0x000b57fffe9ffb97')'
zigbee2mqtt  | [2025-01-08 08:20:40] error: 	z2m: Failed to interview '0x000b57fffe9ffb97', device has not successfully been paired

I'm using the dev branch : 2.0.0-dev commit: 6f3524b251ed8218ffed132df262eb0850687e61

I tried to force remove it and start over, but it does not seem to make a difference.

nmaggioni · 2025-01-08T14:09:39Z

nmaggioni
Jan 8, 2025

@nicolinuxfr As coincidental as it sounds, after upgrading to Z2M 2.0.0 I was having the same problems with my E1524 (no activity in the bound lights group, failures to poll and reconfigure) and replacing the battery in the remote seems to have solved them. Interviewing completes correctly, but I have not tried a reconfiguration yet. FW version is 24.4.5.

The last time I used the remote was barely a few hours before the upgrade, and it reported 20% battery capacity. In my experience it should last down to <10% or so, and indeed it was not flashing its low battery LED. Going back to the old cell (~2.7V) brings back the loss of connectivity and absence of pairing indications, so I wonder if the upgrade somehow caused a temporary higher/spurious radio traffic that drained the cell? But I find that very unlikely, mine is probably just an unfortunate coincidence.

2 replies

nicolinuxfr Jan 8, 2025
Author

@nmaggioni I tried to change the battery, just to be safe, but it changed nothing and mine was replaced rather recently, like 2 or 3 months ago. The LED is correctly flashing, it seems to me it's a software bug, but it's surprising you could go through the interview process and not me…

nmaggioni Jan 8, 2025

I had little hope but it was worth a try :)

@Koenkk Let me know if you need me to collect some data, I'm on the stable channel (060ae99).

jorismocka · 2025-01-12T16:37:32Z

jorismocka
Jan 12, 2025

Having the same problem with Zigbee2MQTT 2.0.0-2 after updating from 1.42.0-2 - no activity or action entity for these adapters

IKEA TRADFRI remote control (E1524/E1810)
IKEA TRADFRI on/off switch (E1743)
Tuya Zigbee 4 button remote - 12 scene (TS0044_1)
IKEA STYRBAR remote control (E2001/E2002)

Not 100% sure but I think the same with Hue dimmer switch (324131092621) (324131092621) by Philips.

After stepping back by backup to 1.42.0-2 - activity or action entity where back again and everything worked like a charme again.

2 replies

Chartreusito Jan 12, 2025
Sponsor

Having the same problem with Zigbee2MQTT 2.0.0-2 after updating from 1.42.0-2 - no activity or action entity for these adapters

IKEA TRADFRI remote control (E1524/E1810) IKEA TRADFRI on/off switch (E1743) Tuya Zigbee 4 button remote - 12 scene (TS0044_1) IKEA STYRBAR remote control (E2001/E2002)

Not 100% sure but I think the same with Hue dimmer switch (324131092621) (324131092621) by Philips.

After stepping back by backup to 1.42.0-2 - activity or action entity where back again and everything worked like a charme again.

Please read Breaking changes about 2.0.0 version : #24198 (comment)

Only breaking when legacy is enabled:

All click sensors have been removed (homeassistant.legacy_triggers setting). This means all sensor.*_click entities are removed. Use the [MQTT device trigger](https://www.zigbee2mqtt.io/guide/usage/integrations/home_assistant.html#via-mqtt-device-trigger-recommended) instead.
All action sensors are now disabled by default (sensor.*_action entities). It's recommended to use the [MQTT device trigger](https://www.zigbee2mqtt.io/guide/usage/integrations/home_assistant.html#via-mqtt-device-trigger-recommended) instead. In case you really need the action sensors, add the following to your configuration.yaml.

homeassistant:
  legacy_action_sensor: true

jorismocka Jan 12, 2025

Yes, worked! Thanks a lot and sorry for not RTFM ;-)
But if legacy_action_sensor is deprecated the blue prints are all not working. Hope they will add MQTT device trigger...

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

IKEA E1524/E1810 not working since Z2M 2.0.0 #25613

{{title}}

Replies: 5 comments 10 replies

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

IKEA E1524/E1810 not working since Z2M 2.0.0 #25613

Replies: 5 comments · 10 replies

nicolinuxfr Jan 6, 2025 Author

Koenkk Jan 6, 2025 Maintainer

Chartreusito Jan 7, 2025 Sponsor

nicolinuxfr Jan 7, 2025 Author

Koenkk Jan 7, 2025 Maintainer

nicolinuxfr Jan 8, 2025 Author

nicolinuxfr Jan 8, 2025 Author

Chartreusito Jan 12, 2025 Sponsor

Replies: 5 comments 10 replies

nicolinuxfr Jan 6, 2025
Author

Koenkk
Jan 6, 2025
Maintainer

Chartreusito Jan 7, 2025
Sponsor

nicolinuxfr Jan 7, 2025
Author

Koenkk
Jan 7, 2025
Maintainer

nicolinuxfr Jan 8, 2025
Author

nicolinuxfr Jan 8, 2025
Author

Chartreusito Jan 12, 2025
Sponsor