core: ZHA - newly added Tradfri Shortcut Buttons not getting zha_events
The problem
I’m not sure exactly when this started happening, but have tried to add 3 different TRADFRI Shortcut buttons with fresh batteries via ZHA and they are not binding events. Have gone through numerous startups and tried removing devices and re-adding them but they do not work. Existing TRADFRI Shortcut buttons all seem to be working (there are about 6 existing), and are on the same firmware as the non-functioning newly added buttons.
The only zha_events that show in the logs are device_offline after I quickly press the reset button on them 4 times. Not seeing any other zha_events fired for them (like a button press)
Pressing Identify in the device does not illuminate the light on the button.
Battery data is coming through, but not sure how up to date it is.
Using HUSBZB-1.
What version of Home Assistant Core has the issue?
2022.12.7
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
Zigbee Home Automation
Link to integration documentation on our website
https://www.home-assistant.io/integrations/zha/
Diagnostics information
Signature:
{
"node_descriptor": "NodeDescriptor(logical_type=<LogicalType.EndDevice: 2>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress: 128>, manufacturer_code=4476, maximum_buffer_size=82, maximum_incoming_transfer_size=82, server_mask=11264, maximum_outgoing_transfer_size=82, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=True, *is_full_function_device=False, *is_mains_powered=False, *is_receiver_on_when_idle=False, *is_router=False, *is_security_capable=False)",
"endpoints": {
"1": {
"profile_id": 260,
"device_type": "0x0820",
"in_clusters": [
"0x0000",
"0x0001",
"0x0003",
"0x0009",
"0x0020",
"0x1000"
],
"out_clusters": [
"0x0003",
"0x0004",
"0x0006",
"0x0008",
"0x0019",
"0x0102",
"0x1000"
]
}
},
"manufacturer": "IKEA of Sweden",
"model": "TRADFRI SHORTCUT Button",
"class": "zhaquirks.ikea.shortcutbtn.IkeaTradfriShortcutBtn"
}
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 50 (18 by maintainers)
After 3 frustrating hours, and probably a few minutes before I had had enough of ZHA & wanted to use Z2M, I got this to work.
And the damn thing works.
After hours trying and nothing working, I did something similar but in step 3 instead holding the button I kept pressing non-stop until an event was triggered. When I finally succeeded, I tried the same with a second button I bought. I didn’t even had to remove and pair again, just paired once, reset and then kept pressing the button like crazy. So, my solution is:
One of the old bugs is that battery is running out and the device is corrupting the NVM the that is holding the network key and counters for it and is trying writing the couters and is corrupting it and if its happening you must resenting the device and paring it agen and it shall being fixed in the lasted updates (i think it was in the late EZSP 6.8 or later).
We have not fixing the batter reading from most 24.5 firmware that is being reported as Zigbee standard (was not before) but the rest looks working OK,
@fdesoye You only need marking
QueryJitterand move theQuery_Jitterslider from zero and execute the command and have waking the device up so its not sleeping. The rest options is not needed and can making problems if not getting it right 😃)Struggled with the same issue. Just follow the steps (but first follow the steps to enable IKEA OTA updates for ZHA here: https://community.home-assistant.io/t/zha-ota-firmware-update-upgrade/488960).
I basically followed step 1 and 2. Then I added the device again via ZHA. Then I went on and started the manual update via the instructions on the page I just provided. I was able to see the status logs for the update come in in the Core logs (Settings=>System=>Logs=> load all logs). After that (well over 4 hours, maybe don’t set the data package sizes too low next time…) I simply removed the device again, restarted HA, added the device again and poof, I was able to see the zha_event coming through.
Best of luck!
You sir, you made my day. Have been struggling with this issue (not a HA/Zigbee pro but not a noob either) and you way was the way for me. Thank you so much for sharing! FYI: Googled the bit on how to activate OTA updates for IKEA devices for ZHA, wenty through a couple of steps and then simply followed your steps. All done, happy days!
Hmm. Have you tried clicking a button on the device once a second or so to keep it awake, and then click the “Reconfigure” button on the device page (while still clicking buttons to keep it awake)? IKEA devices seem to go to sleep quite quickly after joining and ZHA sometimes doesn’t have time to configure reporting.