ZHA ikea tradfri button up/down buttons service calls are not recognized anymore #69375
Comments
|
Hey there @dmulcahey, @Adminiuga, mind taking a look at this issue as it has been labeled with an integration ( zha documentation |
|
This seems to be maybe related: |
It's not. Enable debug logging and post debug log of incoming events. |
|
I'm not sure what exactly belongs to the events, but here is the zigbee log: Log |
|
You can filter by # Battery voltage report
2022-04-06 12:11:35 DEBUG (MainThread) [zigpy.zcl] [0x777B:1:0x0001] Decoded ZCL frame: PowerConfiguration1CRCluster:Report_Attributes(attribute_reports=[Attribute(attrid=0x0020, value=TypeValue(type=uint8_t, value=30))])
2022-04-06 12:11:35 DEBUG (MainThread) [zigpy.zcl] [0x777B:1:0x0005] Decoded ZCL frame: ScenesCluster:press(param1=257, param2=13, param3=0)
2022-04-06 12:11:38 DEBUG (MainThread) [zigpy.zcl] [0x777B:1:0x0005] Decoded ZCL frame: ScenesCluster:press(param1=256, param2=13, param3=0)
2022-04-06 12:11:38 DEBUG (MainThread) [zigpy.zcl] [0x777B:1:0x0008] Decoded ZCL frame: LevelControl:step_with_on_off(step_mode=<StepMode.Up: 0>, step_size=43, transition_time=5)
2022-04-06 12:11:39 DEBUG (MainThread) [zigpy.zcl] [0x777B:1:0x0008] Decoded ZCL frame: LevelControl:step(step_mode=<StepMode.Down: 1>, step_size=43, transition_time=5, options_mask=<bitmap8.0: 0>, options_override=<bitmap8.0: 0>)I can't really tell what button was being pressed here so if you can |
|
Hmm the ssh terminal does not seem to know the Is there any alternative for that? |
|
Feel free to omit that flag. |
|
Here is the filterd log: Button order: left, up, right, down And here the full log: Log022-04-06 19:18:55 DEBUG (MainThread) [zigpy_deconz.api] Device state changed response: [<DeviceState.128|APSDE_DATA_REQUEST_SLOTS_AVAILABLE|APSDE_DATA_INDICATION|2: 170>, 0] |
|
So each button press results in a message received by the coordinator? That looks fine to me. Can you post the Zigbee device signature? |
|
Device signature: I can also see the event in the HA dev page, but the service call does not work. When I track for events in the automation it works (see initial post description) |
|
@MattWestb you're totally right, the new, optional @dmulcahey Any ideas for how we can preserve the existing behavior but not rely on the exact values of those fields? Is it possible to do "prefix" matching with the |
|
Sorry Puddly i was posing in the wrong closed issue :-(( |
|
I think other no IKEA remotes can having the same problem like HUE dimmer switch(es) and the tuya TS004F dimmer switch and knob that is using the dame Zigbee commands in DA. But i have not time updating all my 5 (Z)HA systems for testing and adding the HUE dimmer that is in the black Zigbee box for bad devices but i doing tomorrow. |
|
So what's the word? I reverted the newest ha update after this broke |
|
I have a lot of automations based on various zigbee wall switches all of which now don't work. Possibly related is this error in the automation trace: The automation has a template that contains this: I read about trigger variables being introduced in 2022.4 so I'm wondering if that is clearing A sample captured event doesn't seem to have any additional args that would cause it not to match by the looks of it: This is my trigger YAML: It doesn't fire/match now unless I remove the |
|
I have this same issue with a ts004f switch that is sending 'step' messages on two of the buttons which now don't trigger automations the other two buttons work, this broke after the 2022.4 update. Any suggestions on how to resolve this would be appreciated! Thanks, |
|
@hastime I have the 5 button ikea tradfi remote as well as the single button one. On the single button one I noticed the command have changed to one of On the 5 button remote it can see the brightness up/down buttons command has changed to It looks like |
|
|
|
Hmm, or maybe not. The ZCL R8 spec ambiguously lists two
But the lighting spec matches what is now in the new version of zigpy:
So it looks like the IKEA devices were indeed sending a |
|
I use this blueprint "EPMatt/ikea_e1524_e1810" I have updated my blueprints to reflect the following commands My wild guess is that the "_bitmap8.0_bitmap8.0" is an error |
|
I can confirm the fault in handling "args" in the zha trigger. In case you use args for a specific indentifaction the event will never fire since the update 2022.04. In my case it is a sunricher zigbee remote control ZG2868A.
The result of
with this changed behaviour the args can't be used in the event trigger. The same strange issue appears in reading args. The result of
The result of
|
ugh... I think it is time to change how these work. I am not sure about your question off the top of my head. I need to reacquaint myself w/ the code to see what can be done. |
|
I had a similar issue with an IKEA STYRBAR. |
|
Can confirm I’m having the same issue with my Tradfri 5-button remote. Also with my Ikea Symfonisk rotary remotes too; click to play/pause works, but rotation triggers actions such as |
|
@hastime with this update you is also having "scene" / events mode of your TS004F and you is getting 12 "scenes" you can using for automatons. More info in the PR zigpy/zha-device-handlers#1437. The problem i Dimmer mode we must waiting and see what the devs is desiding how to fixing it perhaps we must redoing many quirks for getting it working. |
|
I have 2 remotes. Both behave the same. |
|
0x61d3 is an osram plug that is not plugged in. |
|
Attach the device diagnostic data for both please. You can get this from the device page in HA |
|
You remote is one with old firmware The errors you was getting is that your OSRAM plug is not responding on the command sent to it. |
|
In fact one is IkeaTradfriRemote1 and the other IkeaTradfriRemote |
|
@dmulcahey thanks for hint !!! Shall we changing from ARGS to PARMS in all light controller or updating the ARGS that is "new" (i have all IKEA made local and have testing the current firmware ones) ? |
|
Robert your error is coming not from the remotes its coming from the 0x61d3 is an osram plug that your automation is trying sending on and off commands to. |
|
Here's the diagnostic for one of those |
Params should be used from now on |
|
Then i getting the Do you have one 5 button for testing with older firmware ? |
|
Anything more I can help with? |
|
Rober can you posting one log then doing one long pressing of the toggle button ? Is you automatons working OK or is it some that is not working ? |
|
The up/down buttons are not working. The other buttons work. |
|
Toggle is the on/off button. |
|
|
BTW I'm using this blueprint to control the remote: |
|
Your remote is sending commands OK but its having one not so common firmware that is using different parameters for long press (have only seen one very old issue with that). @dmulcahey is one very unusual firmware version and one PR is not merged for it (shall not being instead updating the device firmware) zigpy/zha-device-handlers#318. |
|
I don't have a Ikea Gateway so I cannot update.
Sorry, but where can I change this? |
|
You is running ZHA so you can only configuring IKEA OTA and its shall working https://github.com/zigpy/zigpy/wiki/OTA-Device-Firmware-Updates |
|
This doesn't seem to work. When I try using the manual update service I'm getting errors. How do I use the other option changing blur print? |
|
Ops i have not testing HA 2033.4.X but i think its one braking thing implanted zigpy/zigpy#961 that shall being fixed but i think its not getting the the last HA 2022.4.4. |
|
After some further testing I figured out that the ZHA events are actually coming through, also for up and down buttons. I created an automation that successfully acts on the event. The issue must be in the blueprint then. |
|
@EPMatt Are you looking at updating your Awesome HA Blueprints for IKEA Controllers to be compatible with new ZHA events? https://github.com/EPMatt/awesome-ha-blueprints/tree/main/blueprints/controllers https://epmatt.github.io/awesome-ha-blueprints/docs/blueprints/controllers/ |
|
Hi @Hedda, thank you so much for reaching out here. Sure! I can see a fix was proposed for this issue on this PR on the Awesome HA Blueprints repo. I'll take some time to review it later today. Thank you for your patience! |
and others
The problem
The up and down button services are not recognized on the ikea tradfri button with ZHA anymore:
When I track the zha_event I see that there are events received when I press the button.
But when I use the up or down service in an automation, it is not triggered.
Here you can see two triggers for the same device, on is using the service description and one is using the event trigger.
Only the event trigger is "triggered" while the other is not.
This worked until the recent beta, so I assume something related to those services changed here.
What is interesting here is, that the main button in the middle works without any issue, but the left/right arrow buttons don't work as well.
What version of Home Assistant Core has the issue?
core-2022.4.0b0
What was the last working version of Home Assistant Core?
core-2022.3.8
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
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: