-
-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rewrite ActionPanel to use Home Assistant default panel #1076
base: main
Are you sure you want to change the base?
Rewrite ActionPanel to use Home Assistant default panel #1076
Conversation
…ith function. - Remove of how action panels where made. - Reuse home-assistant default action panel instead. - Rewrite how changed-actions are saved.
Thank you so much! This was probably the worst part of the editor 😅 I can't wait to try this! 🎉 |
I just tried it and this is almost perfect! There is just a use case that you removed, there was a new toggle for using the default entity instead of adding the same entity multiple times in the config, in YAML it was just "entity" instead of the entity id. It's still working but without any toggle or instructions about that it's hard to guess. Can you add the toggle back, or do you have a better suggestion? Edit: In YAML it looks like this: tap_action:
action: call-service
service: vacuum.start
target:
entity_id: entity |
Ah... Yes I remember you adding that switch. When I edit the yaml and try this. It does not work.
When I change it to "call service" and "service" it does work. |
Indeed I probably not covered this case, I always use call-service followed by service, I was not aware that it was a possibility. |
I will try if I find something that works, this evening. |
Thanks a lot! |
Breaking change
Proposed change
Type of change
Example configuration
Everything was made in with the new action panels
Example printscreens/gif
Additional information
Additional documentation needed.
Checklist
If user exposed functionality or configuration variables are added/changed: