now since the virtual buttons are select object nothing works #49
Unanswered
commentsonly
asked this question in
Q&A
Replies: 2 comments 1 reply
-
Hi @commentsonly, Try: tap_action:
action: call-service
service: select.select_option
service_data:
option: AO
entity_id: select.e2m_virt_ar_esszimmer_action |
Beta Was this translation helpful? Give feedback.
1 reply
-
Hi Marc .... done. 😄 (no more mqtt buttons no templates and such like. I really love the addon in the new form. I saved me next to 80% of my previously required lines of YAML code to get the same thing done. a unified script which I pass 3 informations from within the service_data section.
no more code fiddling with the script, only 3 lines to change within the tap action. script looks like this:
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm a bit stuck with some automations due to the change from buttons to selects.
In the past I used the buttons to being the trigger.
This worked in automations, scripts aswell as if being within a tap_action of buttoncards.
Now with the selects instead of buttons it remains to work in automations being an action but it fails if being used as a tap_action in buttoncards. Don't ask me where I'm wrong with my config.
this works in an automation:
and this fails in a custom:button-card
depending upon using data or service_data it throws differnt errors.
a missing entity_id, device_id if using
service_data
or with
key not provided @data['option']
Any example on how the new implementation should be used so it not only look cleaned from the number of entites span by the addon but also does work?
Beta Was this translation helpful? Give feedback.
All reactions