Hi, do you use Zigbee2Mqtt also? I use ZHA and havenāt updated yet, I donāt update immediately anymore to avoid regressions on the first versions.
The same here. I use ZHA and had the same problem after the update yesterday. After importing the backup from the morning (i.e. rollback), it worked again. Now Iām waiting for feedback here before updating again.
What a pityā¦ This blueprint is really useful, itās a shame it keeps getting broken. What are the alternatives?
Hi guys.
I have since the update (2023.5.x) yesterday also problems with the Blueprint and the SYMFONISK sound controller (E1744).
I can no longer stop the volume control. Either the volume moves to 0% or to 100%.
1 Like
Update:
Unfortunately, I find it difficult to understand the script.
However, the helper sends a slightly different format since the update. Before the update there was always a space after the colon, after the update this has disappeared.
I have no idea if this affects the function, but thatās what I notice.
After update:
{"a":"brightness_stop","t":1683304412.369172
{"a":"brightness_move_down","t":1683304412.024501}
{"a":"brightness_stop","t":1683197195.208142
{"a":"brightness_move_down","t":1683197194.97702}
Bevore update:
{"a": "brightness_stop", "t": 1683004163.070071}
{"a": "brightness_move_up", "t": 1683004162.884988}
{"a": "brightness_stop", "t": 1683004163.070071
For ZHA the strings from the button presses that are expected with the working version are this:
button_left_long: hold_3329_0
button_left_release: release
button_right_short: press_256_13_0
button_right_long: hold_3328_0
button_right_release: release
button_up_short: 'on'
button_up_long: move_with_on_off_MoveMode.Up_83
button_up_release: stop_with_on_off
button_down_short: 'off'
button_down_long: move_MoveMode.Down_83_bitmap8.0_bitmap8.0
button_down_release: stop_with_on_off
Can someone with the current non working version share what is seen while pressing the buttons? Maybe we can fix the strings and get this working again.
Im nog using zha but z2m, but maybe if you explain a bit I can show the non working for z2m and when it all comes together we can solve it.
Btw, not working with 2023.5.2 either, as expected
Hi folks,
On Github, LordSushiPhoenix has already published a solution to the problem.
If you donāt want to wait until all controllers.yaml have been adapted, you can help yourself. All you have to do is to remove 3 spaces in two lines. See link.
https://github.com/EPMatt/awesome-ha-blueprints/pull/546/commits/3eb5bf49bc95f841b7911b2fb959344e17c0421a
After the change, automation must be restarted
1 Like
Cool, it seems a detail but spaces matters. Good catch, I would never found with limited knowledge about this programing language and debug capabilities. Once again the community comes to the rescue. 
I took a look at the code and although it fixes the problem with the latest HA version, it doesnāt include my previous fixes. Check my posts for more information about this.
I will have a look at the āspaceā changes and add them into the pull request. If everyone can test when Iāve done it that would be appreciated.
To make things easier for me and maybe others, I created a project fork to include my fixes and eventually others. You can check the fork here: GitHub - lsismeiro/awesome-ha-blueprints: A curated collection of automation blueprints for Home Assistant.
Update: Answering to myself and others, the LordSushiPhoenix fix prevents the blueprint from working because the space evaluation is needed in the pre 202305 Home Assistant versions. Since I didnāt install the 202305 HA version yet I donāt know if it works or not.
What is the best way to deal with the amount of forks for this controller?
I think there needs to be consolidation - I have one linked to the pull, you have one and theres another one that was created generically alongside other controllers.
Donāt get me wrong - I have no issue with your fork - Iām actually quite grateful for it.
What is the best course of action for my pull request? Either we can close it and create a new pull request using your fork, or is there a way to change the fork the pull request is based from?
Cheers
Blueprint schema - Home Assistant (home-assistant.io) Can you add a min_version to the blueprint? It will stop the blueprint from being imported/run on versions that are unsupported.
Like I said, the fork was for my own control. What is needed from my point of view is someone to step forward and that can maintain the code in a single repository. The original developer canāt spend the time now and we need someone to step in for him.
Since your pull request precedes my fork I think for the sake of simplicity and if you agree, you can update your pull request and keep things simpler. When someone steps in as a maintainer it will be easier to merge the changes.
I donāt have the means to test the change provided by LordSushiPhoenix with the latest HA release, I canāt take the risk of breaking my working environment now. If someone can test it, I can provide de controller file with my changes and LordSushiPhoenix changes.
Thatās fine, I can update my fork.
Is the current version on your fork with or without LordSushiPhoenixās space changes? I am running 2023.5.0 at the moment.
EDIT: Itās without. I will add the space changes and test.
1 Like
Hi @LewisSpring Iām not good at this developer stuff since Iām not one. Meanwhile, I created a branch on my fork that include LordSushiPhoenix space fix and added also the minimum version:
Great, thanks.
I did the same on my fork, but other than the description it is the same.
1 Like
Hi, did you had the opportunity to test? Thx.
Iāve only tested it briefly but it seems to be working quite well so far.
A lot more reliable than previously.
1 Like