IKEA TRÅDFRI 5-button Zigbee remotes missing event triggers (latest v24.4.5 firmware + Yellow SilLabs coordinator + ZHA)

[FloatingBoater]

The problem

The recent (2023-02) automatic firmware update to v24.4.5 appears to have resulted on some preconfigured 5-button remotes from loosing 10x button Zigbee events (5x button on + 5x button off).

All but 3x event triggers missing

• 4x IKEA TRÅDFRI 5-button remotes automagically updated to 0x24040005

• One remote works fine, and shows the expected 13x event triggers. e.g. Device → Automations (+) → Do something when… → Show 13 more…

• Several other remotes show 3x triggers e.g. Device → Automations (+) → Do something when… → Show 3 more…

  So that’s 10x triggers missing (looks like 5x button On + 5x button Off)

All of the expected triggers caused by button presses (scene changes?) are missing. Pressing a remote button does fire something, but I can’t see a way of using the event:

Note the difference in event naming between devices:

• GOOD Bedroom 4 IKEA Remote Remote Button Short Press - Turn On event was fired Triggers an automation as expected

• BAD Study IKEA remote Toggle event was fired Doesn’t trigger a pre-existing automation, and none can be created

N.B. Noticed the working device lists Quirk: zhaquirks.ikea.fivebtnremotezha.IkeaTradfriRemote1, but the non-working devices don't mention quirks.

Has some post-firmware update re-configuration failed, missing out the quirks? Is there a way to re-scan quirks? (device factory reset + add doesn't work)

What version of Home Assistant Core has the issue?

2023.2.2

What was the last working version of Home Assistant Core?

2023.2.2

What type of installation are you running?

Home Assistant OS

Integration causing the issue

ZHA

Link to integration documentation on our website

https://www.home-assistant.io/integrations/zha/

Diagnostics information

Workarounds tried

• Bench power supply connected to the remote to prove voltae - 3V3 gives 130%! issue 86880
• Factory reset / + Add Device - see below
• RECONFIGURE scans fail every time, even removing attributes available after the original inclusion - see below

Historic Issues

IKEA TRÅDFRI 5-button remotes seem to work badly with ZHA even with the 'quirks' file automatically applied.

Recent issues include:

1. The well documented short battery life, ranging from:

   • 2x months (next to the coordinator) to
   • 2x days (next to two mains IKEA Zigbee switches acting as Zigbee routers)

2. Battery dies, replacement CR2032 doesn't bring it on-line. Workaround: press reset 4x times quickly for a factory reset, LED flashes 4x times, fiddle with the buttons and reset until the red LED 'pulses' and after several tries (+) Add Device works BUT only next to the coordinator which means it ignores local routers, runs the battery down quickly leading to... Workaround: Pair a device next to the coordinator, then turn HASS off completely for 60 minutes. My understanding is this forces the restarted coordinator to recalculate the Zigbee mesh so remotes use nearby routers, which may workaround the pairing and bad battery drain issue.

3. Devices also seem to work, then refuse to connect, with others failing a RECONFIGURE scan failing 100% of the time. The only fix I can see is a factory reset and 2.

4. Battery level very erratic (looks like a known issue). IKEA only seems to report 100% / 66% / 33% / dead, although applying 3.3V from a bench power supply as a test reported 130%!

N.B. Noticed the working device lists Quirk: zhaquirks.ikea.fivebtnremotezha.IkeaTradfriRemote1, but the non-working devices don't mention quirks. Has some post-firmware update re-configuration failed, missing out the quirks?

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Greybeard *nix sysadmin with too many years of complex diagnostic experience - very willing to capture specific scenario log data to assist. 
Didn't include any at this stage as unsure what level of logging would assist (e.g. database event rows, ZHA debug logs, etc).

Additional information

Also detailed in a community post

[home-assistant[bot]]

Hey there @dmulcahey, @adminiuga, @puddly, 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` Change the title of 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.

_{^{(message by CodeOwnersMention)}}

---

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

[TheJulianJES]

Should be fixed by https://github.com/zigpy/zha-device-handlers/pull/2156 Will be fully fixed once a new zha-quirks/zha-device-handlers version is released and upgraded to in HA Core. So this issue should be resolved with 2022.3.0 (or maybe even earlier).

For now, you could add the fivebtnremote.py file as a custom quirk. Basic tutorial: https://github.com/zigpy/zha-device-handlers/discussions/693#discussioncomment-857274 (So just add the two lines in your configuration.yaml and download the updated fivebtnremote.py file from GitHub and put it in that folder, then restart HA. If you do this, make sure to remove the custom quirk with 2023.3.0 though)

[MattWestb]

The 24.4.5 is having different cluster setting the system is using the old one then its saved in the device database. Remove the device from ZHA and wait one minute and paring it new fast pressing the paring button 4 times). Then its in do one reconfigure from the device card and waking it up then sending commands to it. If l is going well you is getting all events working and the DA for it and its doing checkins every 55 minutes. With the new quirk version loaded the battery % shall being fixed. The right quirk class is Quirk: fivebtnremotezha.IkeaTradfriRemote4.

[FloatingBoater]

Hi, First, I'd like to thank Julian, Matt, and your fellow developers for both ZHA, and responding so quickly to my issue report - THANKS!

Second - I can confirm FIXED via the custom quirks install your links pointed to. For others, here's a summary:

cd /root/config
mkdir custom_zha_quirks
cd /root/config/custom_zha_quirks
wget https://raw.githubusercontent.com/stickpin/zha-device-handlers/fbc724d8ac96471210efa8bfc2431b5f029f9094/zhaquirks/ikea/fivebtnremote.py
# add:
# zha:  
#   custom_quirks_path: /config/custom_zha_quirks/
vim configuration.yaml

For me, no repairing was needed, just a HASS restart. The device properties confirm the short path to a local quirks file (i.e. Quirk: fivebtnremote.IkeaTradfriRemote5).

My expectation is the root cause of all this is IKEA's desire to add 'value add' to their devices with direct pairing - we're all just patching around designs that don't meet our use case (something I've been doing since X10...).

[MattWestb]

Great now your quirk class is version 5 = the new for the firmware. Do you also getting the device checking in every 50 min ? = yes all is very OK.

Direct paring is the device working in one other mode and is using different code libs but many things is is the same as normal mode that Dirigera is using.

For my is the biggest problem that all IKEA controllers is light controllers and user is like using them as somthing else like having quad clicks with 5 time rotating from one dimer remote.

I think we is getting most out from our IKEA devices in one good way and they is pritty easy working with then they is good Zigbee complaint and only have some extras (compared with Xiaomi and tuya).

[FloatingBoater]

Yes - here's some real data: Check 1	Check 2	Interval
15:34:06	16:29:29	55.38
15:03:59	15:58:32	54.55

On a previous firmware version, I couldn't get the 5-button remote to pair with ZHA, but it kept pairing directly with a nearby Lidl stupid bulb! After factory resetting the bulb and remote, I tried again... :-)

IKEA stuff is cheap, well made, widely available - thankfully their CR2032 are also very cheap so the previous firmware battery life issues at least didn't cost much to fix.

My hope is firmware 0x24040005 (and ZHA updated quirks) helps.

Thanks again!

[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.