maybe we will also get the state:attribute directly involved? instead of 53,51… and 7,27… ${states['sensor.tankerkoenig_shop_chill_diesel'].attributes.latitude} ${states['sensor.tankerkoenig_shop_chill_diesel'].attributes.longitude}
@DavidFW1960 I know I can download it manually, but it is a hassle for anyone that wants to try my dashboard.
I tried to fork the repo, but when adding my repo in HACS it will always say Repository structure for master is not compliant. I have tried releasing different versions and even tried using the current stable version but for some reason whatever I do it will keep throwing this error. (I have had more success with other stale repositories that I just forked, fixed and added as a custom repo).
Would you maybe have an idea? (or anyone else ofc)
I didn’t change anything, I just want to be able to get the ‘beta’ release in HACS
Edit: I removed the releases, since they didn’t do much good anyways, it always throws the same error. Even if I release some version (just by releasing it through the already existing tags), but instead of master it will show that version number instead.
Jerome took it on pretty quickly… He is pretty busy with Apex Charts and is a very active dev but it has concerned me in the past that his very high level of responsiveness to every request etc will just burn him out… and I use so much of his stuff it’s a worry.
Yeah he did and made it much better too. He’s a great person imho. His cards are the best around, but indeed as you say I hope he doesnt get burnt out by it.
Its for that reason I tried to fork it and just release the latest beta (people could then add it as a custom repository) which would be enough currently. But my knowledge of HACS is well, mediocre at best.
Ah, sorry. I’ve overseen something. You mixing up different languages.
{{ … }}is jinja which doesn’t work in a button card.
I don’t know if there is an expression similar to distance available there.
My recommendation: Create a template sensor and display this.
In configuration.yaml
Means that you want transport variables from a button_card_template into Browser_Mod. I assumed (wrong) that you were using a custom:button-card. Since I don’t use browser_mod, I can’t say whether the fields are templatable.
You can try it with
entities: |
[[[
var items = ['- ' + variables.name + '_state', '- ' + variables.name + '_cpu', '- ' + variables.name + '_percent', '- ' + variables.name + '_uptime'];
var list = items.join('<br/>')
return list
]]]
which computes
entity_id_state
entity_id_cpu
entity_id_percent
entity_id_uptime
But as said, I don’t know if this works for browser_mod.