Hii,
How do i get to Home assistant legacy entity attributes? The new layout is confusing me.
Also do you know how I can change the colours of the light bulbs with left and right buttons?
Thanks!
Hii,
How do i get to Home assistant legacy entity attributes? The new layout is confusing me.
Also do you know how I can change the colours of the light bulbs with left and right buttons?
Thanks!
Hello!
The option is found in:
Settings (top of the Z2M page in your Home Assistant) > Home Assistant integration > Home Assistant legacy entity attributes
For the colors, I’d you want the buttons to assign a specific color, like the right button always setting it to Red, then you just have the right button action in the automation you make with the blueprint be Call Service > Light: Turn On > (your color option) [depends on your needs and the types of color commands your bulb can accept. Color name or rgb color will probably work in most cases].
If you want the left or right buttons to cycle through colors, you’ll need to make a script that does that and then Call Service > Script: (your script) for the hold actions. That will have it cycle the colors as long as the button is held and stop when cycling when the button is released.
I know there are some other threads in this forum about cycling through colors and scripts to accomplish that.
I didn’t come across any colour changing posts. I’ll read it again.
Which is method is better, to adapt the blue print or to simply create a script?
Cheers!
A script would be better than editing the blueprint. That way you can edit it more easily in the future and use it with other automations in the future.
Here’s one of threads about a color cycling Script.
@Mari143, I think you can create a script to change the colors of the bulb and assign the left and right button actions in the blueprint to activate the script.
HIi
I’m struggling a little to create a script to change the light colours using the left and right buttons. I looked into the links above for creating a script and it doesnt work for me.
Can you please help in that? I want to change the colours of the grouped lights.
Thanks!
@starbuck93 I’m not being able to import this blueprint on HA 2022.6
It says “No valid blueprint found in the topic. Blueprint syntax blocks need to be marked as YAML or no syntax.”
I’ve tried to import frenck’s one without issues just to test if I was doing something wrong
Anyone having the same problem?
@calexandre I can also see the issue. Must be something wrong with the formatting of the blueprint yaml? I can take a look later today.
Thank you! Will wait for a fix
Same issue here - Home Assistant Core 2022.6.1
@calexandre @cgten Fixed! Turns out, the blueprint importer doesn’t like multiple “code” styled yaml blocks.
Thank you! its working perfectly.
@starbuck93 I’m very new to HA so could be being very stupid somewhere, but the hold up and down to change brightness isn’t working. Press to increase/decrease in increments works.
I’ve ticked the box for legacy attributes and tried importing from URL and the button.
Any help would be greatly appreciated!
Stand down! The hold to adjust brightness has started working. I haven’t done anything so not sure what it was, but I’ll take it!
Not sure if its me or what but new to HA and still learning.
Found that I was creating the actions in the blueprint, but sometimes it doesn’t work - I note that the automation has then been deleted and this in the log file.
Logger: homeassistant.components.automation
Source: components/automation/init.py:651
Integration: Automation (documentation, issues)
First occurred: 18:32:12 (16 occurrences)
Last logged: 18:58:32
Have I missed anything?
@digrem It looks like your automation for the short button press up “action_button_up_short” has an extra line in it that’s empty. Here’s the relevant parts of your error message:
(‘device_id’, ‘’), (‘domain’, ‘’), (‘entity_id’, ‘’)
...
Integration ‘’ not found.
It looks like it’s the last one?
Try to delete that from your automation and see if it works then.
I imported the blueprint, activated "Home Assistant legacy entity attributes” in zigbee2mqtt, and it works great - almost. Hold is not working.
When pressing and holding brightness up, I get two traces:
First trace:
When releasing brightness up, I get two more traces with no condition met (outermost right path).
Any hint?
Edit:
zigbee2mqtt uses these two topics
A) The “new way” how mqtt messages should be sent to HA
topic: zigbee2mqtt/TRADFRI remote control 1
payload: {“action”:“brightness_up_hold”,“battery”:74,“linkquality”:21,“update”:{“state”:“idle”},“update_available”:null}
B) Home Assistant legacy entity attributes
topic: zigbee2mqtt/TRADFRI remote control 1/action
payload: up_hold
When holding and releasing brightness up, the following is sent out via mqtt:
So the action is cleared immediately for topic A (the new way how mqtt messages should be send).
Only for Topic B the payload stays correctly at “up_hold”
So this blueprints obviously reacts to messages of kind A), where the action is immediatly cleared out.
Shouldn’t it use triggers of kind B)?
And if I have a look at the state, then this is confirmed:
So I thought this blueprint is using the “legacy entity attributes”, but it is not, right?
Because of the same reason, if e.g. for “Left button - short press” you define several actions, only the first action is executed.
I am using the Blueprint to activate scenes, which consist of 2 Zigbee lights and a Nanoleaf light. With the author’s version it only turned on the Nanoleaf light and one (!) Zigbee light.
After changing line 87 from
mode: restart
to
mode: single
it works.
I think the cause is, that the remote throws 2 actions when pressing an arrow: arrow_left_click and battery. Therefor the automation is interrupted in-between and executed another time if mode: restart is set.
The logged error would be
Stopped because of unknown reason “null”
I’m getting the error UndefinedError: 'dict object' has no attribute 'to_state'
when using this blueprint with the default IKEA E1524/E1810 5 button remote. Any help for that?