Missing device triggers after firmware update

[magnushacker]

The problem

After upgrading firmware on IKEA Rodret dimmer remotes to version 1.0.57, they no longer expose device triggers for button press events (e.g on/off events). Only these triggers are available:

For remotes using older firmware (1.0.47), all triggers are exposed:

There is no difference in the raw zha_event though:

Not working (FW version 1.0.57):

event_type: zha_event
data:
  device_ieee: 5c:c7:c1:ff:fe:3f:9e:e3
  unique_id: 5c:c7:c1:ff:fe:3f:9e:e3:1:0x0006
  device_id: d290afdbc3e9cf748d51fb96db09b17e
  endpoint_id: 1
  cluster_id: 6
  command: "on"
  args: []
  params: {}
origin: LOCAL
time_fired: "2024-10-04T07:27:14.370196+00:00"
context:
  id: 01J9B6SXE2W1CM75DPYJNJ046B
  parent_id: null
  user_id: null

Working (FW version 1.0.47):

event_type: zha_event
data:
  device_ieee: 5c:c7:c1:ff:fe:83:de:8c
  unique_id: 5c:c7:c1:ff:fe:83:de:8c:1:0x0006
  device_id: 501d0c1184bc29275a0abe7bf2c396b0
  endpoint_id: 1
  cluster_id: 6
  command: "on"
  args: []
  params: {}
origin: LOCAL
time_fired: "2024-10-04T07:27:58.384239+00:00"
context:
  id: 01J9B6V8DGDKE85A0FGSMCK7HW
  parent_id: null
  user_id: null

What version of Home Assistant Core has the issue?

core-2024.10.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

ZHA

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]]

Hey there @dmulcahey, @adminiuga, @puddly, @thejulianjes, mind taking a look at this issue as it has been labeled with an integration (zha) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of zha 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 zha 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)}}

---

zha documentation zha source _{^{(message by IssueLinks)}}

[puddly]

Please upload diagnostics JSON for your device.

[magnushacker]

Just noticed that one of my remotes that did get the firmware upgrade still works fine. So perhaps it's not related to FW but to hardware revision? In any case, here are diagnostics for both working and not working remotes, both are on FW 1.0.57.

zha-not-working.json zha-working.json

[GTB3NW]

Same issue, latest firmware. In addition it forgets the firmware version, I get a logbook entry <device> Firmware became unknown after about a minute of the device being online

[magnushacker]

Let me know if any other info is required.

I noticed that for the non-working remote, no quirk is applied:

    "quirk_applied": false,
    "quirk_class": "zigpy.device.Device",
    "quirk_id": null,

For the working remote, it looks like this:

    "quirk_applied": true,
    "quirk_class": "zhaquirks.ikea.twobtnremote.IkeaRodretRemote2Btn",
    "quirk_id": null,

I don't know enough about ZHA/zigpy in order to figure out why this is happening though.

[Stortag]

Same issue, rodret button running version 1.0.57 diagnostics.json

The only available trigger is battery change

[menacedk]

one more the the same problem

[magnushacker]

Let me know if any other info is required.

I noticed that for the non-working remote, no quirk is applied:

    "quirk_applied": false,

    "quirk_class": "zigpy.device.Device",

    "quirk_id": null,

For the working remote, it looks like this:

    "quirk_applied": true,

    "quirk_class": "zhaquirks.ikea.twobtnremote.IkeaRodretRemote2Btn",

    "quirk_id": null,

I don't know enough about ZHA/zigpy in order to figure out why this is happening though.

Is it possible to force a quirk to be applied to a certain device?

[menacedk]

Please upload diagnostics JSON for your device.

do you still need json diagnostics on non-working devices??

[sejnub]

Same problem here. My device worked fine for monts until it didn't.
The action entity does not exist anymore.

But the following automation works:

alias: dummy
description: ""
triggers:
  - domain: mqtt
    device_id: 387b4df09b86031c4b8b535404452837
    type: action
    subtype: "on"
    trigger: device
  - domain: mqtt
    device_id: 387b4df09b86031c4b8b535404452837
    type: action
    subtype: "off"
    trigger: device
conditions: []
actions:
  - action: script.log
    metadata: {}
    data:
      description: descriiption-not-set
      message: rodret was pressed
      severity: info
      file: "{{this.entity_id}}"
mode: single

[magnushacker]

Same problem here. My device worked fine for monts until it didn't.

The action entity does not exist anymore.

But the following automation works:

Looks like you are using zigbee2mqtt? My problem is with ZHA.

Currently I have several Rodret that work fine in ZHA, only a couple of them are causing problems. I believe the issue is that for some reason the appropriate quirk is not applied, but I don't know how to force a quirk for a particular device id.

Also noticed that this device is sometimes difficult to pair correctly in ZHA, I have to retry it a few times before it works.

[sejnub]

Yes, Zigbee2MQTT.

[gnif]

I have a device that has failed exactly the same way. I am running HA beta and it is showing the quirk has been applied. I have several other switches that have also been updated to the same firmware that work fine, just one single device has failed.

~~This indicates a firmware upgrade failure, is there a way to force an update again even though it's already updated?~~

Edit: I got it working by reconfiguring the device multiple times while pressing the buttons multiple times to keep it awake. Removing and re-adding the device did not resolve the issue, it required multiple reconfigurations while the device was already paired.

[Stortag]

Edit: I got it working by reconfiguring the device multiple times while pressing the buttons multiple times to keep it awake. Removing and re-adding the device did not resolve the issue, it required multiple reconfigurations while the device was already paired.

Could you be more specific. Does it now show the missing triggers in the GUI for editing automations or are you using it some other way? When you say reconfigure do you mean through the ikea app or ikea integration or are you using some kind of usb zigbee stick directly?

[gnif]

Literally the "RECONFIGURE" option on the device in Home Assistant:

And yes, all the triggers are again available.

I am not using the ikea hub or integration, I am using a SLZB-06M over wired ethernet with ZHA, not MQTT

[Stortag]

I am not using the ikea hub or integration, I am using a SLZB-06M over wired ethernet with ZHA, not MQTT

Ah I see. I'm using the first gen ikea gateway with the ikea trådfri integration, so for me there is no reconfigure option. I tried removing it and re adding it in the app while spamming the buttons without any success.

So far the issue seems to appear when pairing/configuring the device with all methods. ZHA, Zigbee2MQTT and IKEA TRÅDFRI

[Stortag]

Ah I see. I'm using the first gen ikea gateway with the ikea trådfri integration, so for me there is no reconfigure option. I tried removing it and re adding it in the app while spamming the buttons without any success.

I ditched the ikea gateway and bought a Sonoff zigbee 3.0 usb dongle. So now I'm using the ZHA integration and it worked on the first try.

[GTB3NW]

I just had an update to my ZigBee dongle firmware which looks like it should address this

[magnushacker]

Which Zigbee dongle are you using?

On Sun, 6 Apr 2025 at 22:42, Ben @.***> wrote:

I just had an update to my ZigBee dongle firmware which looks like it should address this

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/127528#issuecomment-2781648701, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA73OUWPIHOEB2OSYFLS4YD2YGGUTAVCNFSM6AAAAABPLJUE3OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOBRGY2DQNZQGE . You are receiving this because you authored the thread.Message ID: @.***> [image: GTB3NW]GTB3NW left a comment (home-assistant/core#127528) https://github.com/home-assistant/core/issues/127528#issuecomment-2781648701

I just had an update to my ZigBee dongle firmware which looks like it should address this

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/127528#issuecomment-2781648701, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA73OUWPIHOEB2OSYFLS4YD2YGGUTAVCNFSM6AAAAABPLJUE3OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOBRGY2DQNZQGE . You are receiving this because you authored the thread.Message ID: @.***>

[GTB3NW]

Which Zigbee dongle are you using? …

Home Assistant Connect ZBT-1

I thought it had solved problems with IKEA firmware being unknown as well but it didn't.

I've still not had chance to test. But thought it was worth sharing in case others hadn't seen the firmware update

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.