how to template the confirmation text relative to the performed action on the button

[Mariusthvdb]

using a series of config templates the scenario is like this:
holding a button unlocks the lock, and next should just respond the next action, hold or tap.

the pop up confirmation should ideally reflect the action applied. I am not sure if that can be done, and if yes, how

This is the configuration I used:

      - type: custom:button-card
        template:
          - button_switch_lock
          - var_icon
        entity: switch.freezer_bijkeuken
        triggers_update: sensor.freezer_bijkeuken_actueel
        name: Vriezer Bijk.
        variables:
          on_icon: mdi:fridge
          off_icon: mdi:fridge-off

and templates:

button_switch_lock:
  template:
    - button_switch
    - lock

button_switch:
  variables:
    id: >
      [[[ return entity.entity_id.split('.')[1]; ]]]
  template:
    - etc
  tap_action:
    action: toggle
    haptic: light

  hold_action:
    action: perform-action
    perform_action: zwave_js.refresh_value
    target:
      entity_id: >
        [[[ return 'sensor.' + variables.id + '_actueel'; ]]]

lock:
  tap_action:
    action: more-info
    haptic: light
  lock:
    enabled: true
    unlock: hold
    exemptions:
      - username: etc
  confirmation:
    text: >
      [[[ return `Wil je ${entity.attributes.friendly_name} schakelen?`; ]]]

As the current confirmation is now on either action, this is rather confusing for the user, always seeing the 'do you want to toggle' ;-)

so should be in pseudo-code:

 confirmation:
    text: >
      [[[ 
          return action = tap ? `Wil je ${entity.attributes.friendly_name} schakelen?`: 
                                              `Wil je fresh the value of ${entity.attributes.friendly_name}?`; ]]]

maybe even only confirmation on tap, hold/refresh would be ok always...

btw, I now realize the tap_action on the lock: template is futile, it never shows more-info I think

it isnt, it executes on the open lock after all. factually overriding the tap_action on the main button

[RomRider]

confirmation can be set as an sub-option for any action. It doesn't need to be in the main configuration part.

[Mariusthvdb]

Feature request coming up: triggers_update.entity_id

as you can see, I template the entity to use in the perform-action, based on the entity_id string.
In the end, I finish with the same entity as set in the triggers_update.

how simple would it be if we could do

  hold_action:
    action: perform-action
    perform_action: zwave_js.refresh_value
    target:
      entity_id: >
        [[[ return triggers_update.entity_id; ]]]

would that be something you'd be willing to consider. I use this in many buttons, it would make life a lot simpler without having to extract those object_ids (which in this case they are)

[RomRider]

triggers_update is going to be deprecated in the next release. There's no need for it anymore.
You can use variables for what you want to achieve.

[Mariusthvdb]

I don't think !secret is supported in any front-end yaml. It's only backend. This has nothing to do with button-card.

you got to be kidding, so this has never worked?? aaarghh

  - type: custom:button-card
    <<: &users
      visibility:
        - condition: user
          users:
            - !secret user_m
            - !secret user_l
            - !secret user_h
            - !secret user_f

this works though
and this

      - type: custom:hui-element
        card_type: iframe
        aspect_ratio: 100%
        url: !secret blitz

even stock frontend

  - type: button
    icon: cli:network-map
    name: Z-Wave Visualization
    action_name: Ga
    tap_action:
      action: navigate
      navigation_path: !secret zwave_visualization

or

title: Notificatie
path: notificatie
visible: !secret admin_m

[RomRider]

Alright, my bad, I thought it was limited to backend.

But exemptions should work, so there's something else going on with your configuration.

[Mariusthvdb]

hmm, seems !secrets works alright on the button config I gave. However, somehow the exemption on the confirmation shows for the users listed in that exemption list, and not as described in the docs: does Not show for them.

If I change my name to a lower typed, I can unlock the lock by hold, but then can not click or hold to perform any action...

using below config now for the lock object

lock:
  tap_action:
    action: toggle
    haptic: light
    confirmation:
      text: >
        [[[ return `Wil je ${entity.attributes.friendly_name} schakelen?`; ]]]
  lock:
    enabled: true
    unlock: hold
    exemptions:
      - username: !secret button_unlock_name_1
      - username: !secret button_unlock_name_2
      - username: !secret button_unlock_name_3
      - username: !secret button_unlock_name_4

#   confirmation:
#     text: >
#       [[[ return `Wil je ${entity.attributes.friendly_name} schakelen?`; ]]]