Button-card manual refresh | Home Assistant | Page 1

supple ocean Sep 16, 2025, 12:05 PM

#

Is it possible to manually refresh the content of a single button-card, without having to refresh the entire browser window?

Background: I have a variable that contains randomly generated text. I want to trigger an update of this card by help of the tap_action to display different random text.

I am currently using the following code to refresh the entire browser:

tap_action:
  action: fire-dom-event
  browser_mod:
    service: browser_mod.refresh

Thanks!

#

Button_card manual refresh

#

Button-card manual refresh

torn garnet Sep 16, 2025, 2:19 PM

#

triggers_update might be of some help

#

type: custom:button-card
name: |
  {{ var.randomtext }}
tap_action:
  action: call-service
  service: script.generatenewrandomtext
triggers_update:
  - var.randomtext

... or something like that

supple ocean Sep 16, 2025, 3:37 PM

#

torn garnet ``` type: custom:button-card name: | {{ var.randomtext }} tap_action: action...

Thanks, yes, I was thinking along the same lines, i.e., calling up a script. However, I really do not know how a script can change / update a variable that is defined in my setup as follows:

  variables:
    my_variable: |
      [[[
        const number = Math.floor(Math.random() * 14) + 1; 
        const dailySpecial = {
          '1': {
            recipe: "Some text for case 1", 
            subline: "(Some subline for case 1)"
          },
...
          '14': {
            recipe: "Some text for case 14", 
            subline: "(Some subline for case 14)"
          }
        };
        var recipe = dailySpecial[number].recipe;
        var subline = dailySpecial[number].subline;
        if (number in dailySpecial) 
          return `<div>${recipe}</div><p> ${subline} </p>`;
        else 
          return "";
      ]]]

torn garnet Sep 16, 2025, 3:38 PM

#

the tiggers_update should fire if the variable changes

#

oh. wait I see what you mean

supple ocean Sep 16, 2025, 3:47 PM

#

torn garnet oh. wait I see what you mean

Yes, in principle, I just need to somehow force the “triggers_update” service manually. ... but that's obviously not possible. :/

torn garnet Sep 16, 2025, 3:50 PM

#

might be worth looking at how you are defining my_variable? maybe the random integration?

#

using random with a template seems like it could work

supple ocean Sep 16, 2025, 3:58 PM

#

torn garnet might be worth looking at how you are defining my_variable? maybe the random i...

hmm... So, instead of defining all the text in one variable, I have to do it in a template and pick one of them randomly out of the template. This can then be triggered with a service call?

torn garnet Sep 16, 2025, 4:05 PM

#

maybe? hang on I'm throwing together something for you, hopefully

torn garnet Sep 16, 2025, 4:33 PM

#

ok. I think I have something here

torn garnet Sep 16, 2025, 4:57 PM

#

I just had it working for a second and it dumped. hang on there

supple ocean Sep 16, 2025, 4:58 PM

#

torn garnet ok. I think I have something here

This would be really great. In the meantime, I'm trying to trigger a card update with a dummy entity...

supple ocean Sep 16, 2025, 5:20 PM

#

torn garnet I just had it working for a second and it dumped. hang on there

lol

torn garnet Sep 16, 2025, 5:29 PM

#

ok pretty sure I got it here. gonna alter some things for readability and paste in a sec

torn garnet Sep 16, 2025, 5:56 PM

#

template:
  - trigger:
      - trigger: event
        event_type: randomize_dailyspecial
    sensor:
      - name: "Random Special"
        state: >
          {% set attrs = this.attributes %}
          {% set keys = attrs.keys() | select("match", "^option") | list %}
          {% set choice = keys | random %}
          {{ attrs[choice] }}
        attributes:
          option1: "<div>Recipe1</div><p> Subline1 </p>"
          ...
          option[n]: "<div>Recipe[n]</div><p> Subline[n] </p>"

script:
  random_daily_special:
    alias: Randomize the Daily Special
    sequence:
      - event: randomize_dailyspecial

#

sorry took so long; tryingto "work", eat, this, and people keep calling me on the phone lol

#

then, for your custom button

#

just call the script

#

looks like youre doing a random dinner or item for dinner thing.

#

you can tap_action -> call the script

#

then triggers_update: sensor.random_daily_special

supple ocean Sep 16, 2025, 6:06 PM

#

Thanks for your kind help. Will try your code asap. This is a fun card, showing the daily special from the Bobs Burgers series 😉

supple ocean Sep 17, 2025, 6:54 AM

#

torn garnet looks like youre doing a random dinner or item for dinner thing.

I tried your code but somehow it does not work for me. This is what I have in my package:

template:
  - trigger:
      - trigger: event
        event_type: randomize_dailyspecial
    sensor:
      - name: "Random Daily Special"
        unique_id: random_daily_special
        state: >
          {% set attrs = this.attributes %}
          {% set keys = attrs.keys() | select("match", "^option") | list %}
          {% set choice = keys | random %}
          {{ attrs[choice] }}
        attributes:
          option1: "<div>Totally Radish Burger</div><p>(Comes with Radish)</p>"
          option2: "<div>Last of the Mo-Jicama</div><p>(Comes with Jicama)</p>"
          option3: "<div>THE CHILD MOLESTER</div><p>(Comes with Candy)</p>"
script:
  random_daily_special:
    alias: Randomize the Daily Special
    sequence:
      - event: randomize_dailyspecial

After a fresh restart of HA, the template sensor "sensor.random_daily_special" is present with a state "unknown". After I manually trigger the script, the sensor becomes unavailable. What am I missing here? Any idea?

torn garnet Sep 17, 2025, 2:04 PM

#

Hmm ... I feel like I ran into that somewhere else, hangon

torn garnet Sep 17, 2025, 2:47 PM

#

found it.

        state: >
          {% set attrs = this.attributes %}
          {% set keys = attrs.keys() | select("match", "^option") | list %}
          {% if keys | length > 0 %}
            {% set choice = keys | random %}
            {{ attrs[choice] }}
          {% else %}
            "None"
          {% endif %}

#

on first reset, you'll need to hit the script one time to get it from 'unknown' to 'None', then subsequent presses will randomize

#

you can also change it up so that you don't get the same option on script run:

        state: >
          {% set attrs = this.attributes %}
          {% set keys = attrs.keys() | select("match", "^option") | list %}
          {% set current = this.state %}

          {% if keys | length > 0 %}
            {# Build candidate list excluding current state #}
            {% set candidates = keys | reject('equalto', current) | list %}
            
            {% if candidates | length > 0 %}
              {% set choice = candidates | random %}
            {% else %}
              {% set choice = keys | random %}
            {% endif %}
            
            {{ attrs[choice] }}
          {% else %}
            "None"
          {% endif %}

#

though it doesnt always seem to work, I've only tested it with like 4 options

#

might work better with more'

supple ocean Sep 17, 2025, 4:48 PM

#

torn garnet found it. ``` state: > {% set attrs = this.attributes %} ...

Thank you very much! It's working now. I still need to tweak the HTML syntax a little, but the framework is ready. 🙂

torn garnet Sep 17, 2025, 4:50 PM

#

👍

supple ocean Sep 18, 2025, 2:47 PM