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.