The problem
I have couple Philips RWL022 buttons (to be precise this one: https://www.zigbee2mqtt.io/devices/929002398602.html). After .02 update something changed in ZHA, buttons which I added before this update works fine. Button who lost power (battery dies) and another brand new button added to ZHA send events (I checked this by subscribing in developer tools to "zha_event"), but automation engine doesn't get any trigger from device.
Example of full zha_event (button press) redistered by HA but doesn't passed to automation engine:
event_type: zha_event
data:
device_ieee: 00:17:88:01:0d:eb:cb:c8
device_id: 45505e7c35ff3c69e1d27ada88cd0e4d
unique_id: 00:17:88:01:0d:eb:cb:c8:1:0x0006
endpoint_id: 1
cluster_id: 6
command: "on"
args: []
params: {}
origin: LOCAL
time_fired: "2026-02-07T09:39:29.640845+00:00"
context:
id: 01KGVQGZQ87BVBY00NY7V9PSA4
parent_id: null
user_id: null
and this is same event form button (same brand/model/firmware) that works.
event_type: zha_event
data:
device_ieee: 00:17:88:01:0c:26:b2:44
device_id: 9616ebf9f84ef5b4b186450565f58dfa
unique_id: 00:17:88:01:0c:26:b2:44:1:0xfc00
endpoint_id: 1
cluster_id: 64512
command: on_short_release
args:
button: "on"
press_type: short_release
command_id: 0
duration: 1
args:
- 1
- 3145728
- 2
- 33
- 1
params: {}
origin: LOCAL
time_fired: "2026-02-07T09:37:46.098539+00:00"
context:
id: 01KGVQDTKJJM32MS9Z1H5JQQFH
parent_id: null
user_id: null
As You cleary see, something is changed on device setup. Old button has events called short_release, new one (and this one with new battery) has completly different set of events called "on", "off_with_effect" etc.
What version of Home Assistant Core has the issue?
core-2026.2.1
What was the last working version of Home Assistant Core?
core-2026.1.3
What type of installation are you running?
Home Assistant OS
Integration causing the issue
No response
Link to integration documentation on our website
No response
Diagnostics information
No response
Example YAML snippet
Anything in the logs that might be useful for us?
Additional information
No response
The problem
I have couple Philips RWL022 buttons (to be precise this one: https://www.zigbee2mqtt.io/devices/929002398602.html). After .02 update something changed in ZHA, buttons which I added before this update works fine. Button who lost power (battery dies) and another brand new button added to ZHA send events (I checked this by subscribing in developer tools to "zha_event"), but automation engine doesn't get any trigger from device.
Example of full zha_event (button press) redistered by HA but doesn't passed to automation engine:
event_type: zha_event
data:
device_ieee: 00:17:88:01:0d:eb:cb:c8
device_id: 45505e7c35ff3c69e1d27ada88cd0e4d
unique_id: 00:17:88:01:0d:eb:cb:c8:1:0x0006
endpoint_id: 1
cluster_id: 6
command: "on"
args: []
params: {}
origin: LOCAL
time_fired: "2026-02-07T09:39:29.640845+00:00"
context:
id: 01KGVQGZQ87BVBY00NY7V9PSA4
parent_id: null
user_id: null
and this is same event form button (same brand/model/firmware) that works.
event_type: zha_event
data:
device_ieee: 00:17:88:01:0c:26:b2:44
device_id: 9616ebf9f84ef5b4b186450565f58dfa
unique_id: 00:17:88:01:0c:26:b2:44:1:0xfc00
endpoint_id: 1
cluster_id: 64512
command: on_short_release
args:
button: "on"
press_type: short_release
command_id: 0
duration: 1
args:
- 1
- 3145728
- 2
- 33
- 1
params: {}
origin: LOCAL
time_fired: "2026-02-07T09:37:46.098539+00:00"
context:
id: 01KGVQDTKJJM32MS9Z1H5JQQFH
parent_id: null
user_id: null
As You cleary see, something is changed on device setup. Old button has events called short_release, new one (and this one with new battery) has completly different set of events called "on", "off_with_effect" etc.
What version of Home Assistant Core has the issue?
core-2026.2.1
What was the last working version of Home Assistant Core?
core-2026.1.3
What type of installation are you running?
Home Assistant OS
Integration causing the issue
No response
Link to integration documentation on our website
No response
Diagnostics information
No response
Example YAML snippet
Anything in the logs that might be useful for us?
Additional information
No response