I would just like to concur that this blueprint is broken on 2022.4.0 and 2022.4.1 on my system. I reverted to 2022.3.8, and everything is working againāIāll hang here until I can find a solution as I rely on this blueprint in my system.
Unfortunately, I donāt have the know-how for how to trace and debug the problem.
Edit to add, Iām using this for media control, play/pause on click do in fact work, it is the volume up/down that no longer works.
Broken for me too on 2022.4.1. I was hoping it wasnāt just me.
The push button still works, the rotary control does not.
Have you checked so that itās not ZHA that is ābrokenā?
Open developer tools => events and listen for zha_events.
Broken for me too on 2022.4.0 and 4.1. ZHA seems not to be broken, as in developer tools I receive events for CW and CCW rotation movement, but only push button (on/off) still works.
@epmatt It seems as there is definitely a group of us that have had this blueprint break in 2022.4.x. Is it still working for you? Is there something we can do to help track down the issue?
Hi all,
Iād first like to thank you for reaching out here. Iām sorry for the huge delay in answering, but Iām currently very busy and Iām unable to follow all the support requests Iām receiving both here and on GitHub.
Could you please try to update Home Assistant to 2022.4.2 and check if the issue persists? I read a similar issue on ControllerX was solved by the HA Core version released today.
Thank you so much for your patience, looking forward to hearing your feedback! 
Thanks for taking the time to look at this. Iām away from home for a few days, but Iāll try the latest as soon as I return.
Fwiw, been using HA for over 2 years now and this is my first breaking change. I guess Iāve been lucky & I guess I should start heeding others warnings about not updating until the .1 or .2 release is available.
PS, thanks for this blueprint! It makes for a great & unique control option in HA.
Hi,
first I must thank you for your AWESOME blueprints
Unfortunately issue persist also in 2022.4.2.
It seems to me the issue raised since zha_events in 2022.4.0 - 2022.4.2 have changed;
Here you can see new zha_event format for right rotation:
Event 138 fired 23:03:
{
"event_type": "zha_event",
"data": {
"device_ieee": "ec:1b:bd:ff:fe:39:63:da",
"unique_id": "ec:1b:bd:ff:fe:39:63:da:1:0x0008",
"device_id": "a6e2928ee51d31c25e7afa6d1f55dbc9",
"endpoint_id": 1,
"cluster_id": 8,
"command": "move",
"args": [
0,
195,
0,
0
],
"params": {
"move_mode": 0,
"rate": 195,
"options_mask": 0,
"options_override": 0
}
},
"origin": "LOCAL",
"time_fired": "2022-04-12T21:03:00.224206+00:00",
"context": {
"id": "ad76032c18e711ee9757881b8ad66973",
"parent_id": null,
"user_id": null
}
}
I tried to do some debugging but I donāt have enough knowledge to do it. 
I checked automation traces and I found one strange thing - trigger_action has strange value 
I would expect something like move_0_195_0_0 I donāt understand why&where from this value move_MoveMode.Up_195_bitmap8.0_bitmap8.0 comes.
Executed: April 12, 2022, 23:03:00
Result:
params:
domain: input_text
service: set_value
service_data:
entity_id: input_text.text_symfonisk1
value:
trigger_action: move_MoveMode.Up_195_bitmap8.0_bitmap8.0
last_triggered: '2022-04-12 23:03:00.351792+02:00'
target: {}
running_script: false
limit: 10
This is also the case for āleft rotationā and ārotation stopā
Executed: April 12, 2022, 23:17:59
Result:
params:
domain: input_text
service: set_value
service_data:
entity_id: input_text.text_symfonisk1
value:
trigger_action: move_MoveMode.Down_195_bitmap8.0_bitmap8.0
last_triggered: '2022-04-12 23:17:59.891456+02:00'
target: {}
running_script: false
limit: 10
service_data:
entity_id: input_text.text_symfonisk1
value:
trigger_action: stop_bitmap8.0_bitmap8.0
last_triggered: '2022-04-12 23:03:02.071231+02:00'
target: {}
Because these trigger_actions are different as expected the blueprint conditions are not met.
I hope this info will help you do some more debugging.
If the structure of the message has been changed then I canāt understand why this is not part of the breaking changes in the release
I just want to mention that this is still broken as of 2022.4.5
Edit to ask:
Does anyone know if this is an unreported breaking change in zha, or if itās a bug? Should we report it as a bug on GitHub?
Itās a bug it seems.
You can fix it yourself as I understand it by listening for the events and change the blueprint accordingly.
I have not updated yet so I donāt know what the new message looks like for sure
Hi @epmatt ,
Although it was reported in HA, it seems that they did not revert they changes, so the new args are still added. They do not seem to be willing to revert this change.
You can find the ControllerX PR with the events that I had to change. Unfortunately, I was not able to try it out, but I got these event changes from the issues reported (#455 and #457).
Hope this helps.
Regards,
Xavi M.
Iām trying to edit the blueprint to make this work again, but Iām stumped. Iāve changed the following in the zha section of ikea_e1744.yaml:
From:
rotate_left:
- move_1_195
rotate_right:
- move_0_195
To:
rotate_left:
- move_1_195_0_0
rotate_right:
- move_0_195_0_0
but it doesnāt seem to do anything. Iāve also tried to add 1 zero instead of two, but also no help. Iāve tried to use āTrace Timelineā in automations debug & i do see a difference when there are two zeroāsā¦ the bitmap8.0 thing referenced aboveā¦ but Iām not a programmer and I donāt really understand what Iām changing, or what Iām seeing in the debug. I couldnāt find reference to zha anywhere else in the blueprint, but maybe Iām missing something? Iām kind of bummed this isnāt working anymore. Has anyone been able to fix this?
If you listen for ZHA events in developer tools.
What kind of message do you get when you rotate the device?
Event 1: Rotate Right
Event 2: Stop
Event 1 fired 7:21 AM:
{
"event_type": "zha_event",
"data": {
"device_ieee": "ec:1b:bd:ff:fe:aa:4e:f4",
"unique_id": "ec:1b:bd:ff:fe:aa:4e:f4:1:0x0008",
"device_id": "4c23eae6d2f6d1695a4fb198fe3488ce",
"endpoint_id": 1,
"cluster_id": 8,
"command": "move",
"args": [
0,
195,
0,
0
],
"params": {
"move_mode": 0,
"rate": 195,
"options_mask": 0,
"options_override": 0
}
},
"origin": "LOCAL",
"time_fired": "2022-05-05T11:21:35.554390+00:00",
"context": {
"id": "018093f4304225abfa31a10a8730845d",
"parent_id": null,
"user_id": null
}
}
Event 2 fired 7:21 AM:
{
"event_type": "zha_event",
"data": {
"device_ieee": "ec:1b:bd:ff:fe:aa:4e:f4",
"unique_id": "ec:1b:bd:ff:fe:aa:4e:f4:1:0x0008",
"device_id": "4c23eae6d2f6d1695a4fb198fe3488ce",
"endpoint_id": 1,
"cluster_id": 8,
"command": "stop",
"args": [
0,
0
],
"params": {
"options_mask": 0,
"options_override": 0
}
},
"origin": "LOCAL",
"time_fired": "2022-05-05T11:21:35.954266+00:00",
"context": {
"id": "018093f431d265ffc9b1ef480456d1bd",
"parent_id": null,
"user_id": null
}
}
Reading this part of the blueprint:
{%- elif integration_id == "zha" -%}
{{ trigger.event.data.command }}{{"_" if trigger.event.data.args|length > 0}}{{ trigger.event.data.args|join("_") }}
{%- endif -%}
It seems like you are correct.
I will have a look at my events when I get home, Iām still on the old version without this issue.
This is what my event is for rotate right:
{
"event_type": "zha_event",
"data": {
"device_ieee": "5c:02:72:ff:fe:40:af:22",
"unique_id": "5c:02:72:ff:fe:40:af:22:1:0x0008",
"device_id": "f594d0a16628c130b023f476a35c0091",
"endpoint_id": 1,
"cluster_id": 8,
"command": "move",
"args": [
0,
195
]
},
"origin": "LOCAL",
"time_fired": "2022-05-05T16:13:33.456555+00:00",
"context": {
"id": "f4228152f94306ea830cb2b37a3ccb85",
"parent_id": null,
"user_id": null
}
}
And if the command used to be move_0_195, then I would say move_0_195_0_0 should be correct.
Hello,
i am a bit stupid how to disable the legacy function of the SYMFONISK. I dont have a devices.yaml and tried to add the required lines into the configuration.yaml but it does not work. The configuration validation fails.
'0xabc457fffe679xyz':
friendly_name: my_remote
legacy: false
In addition i am struggling a bit what is the correct address from the device? I used the IEEE address from z2m. Is that correct?
But how to add the code in configuration.yaml properly?
Been thru this myself, the confusion is because itās a different configuration.yaml being discussed in the Z2M documentation that the configuration.yaml in home assistant your familiar with. The one you need to edit is the configuration file for Z2M, should be located here on your SDcard \hassio\share\zigbee2mqtt