well what do you know.
Had another issue with the !secret for the dark sky sensors, also newly added to secrets file. Rendered the same issue while all other (older ones) where loading fine.
Gave it a hard refresh/cache clear in the browser (not the three dots top left refresh) et voila, the Darksky sensor is live and the 3 windy iframes I had configured.
Don’t really understand that because the secrets have nothing to do with page refreshing do they? all backend in this case I would have thought.
so, more than 1 way to use the longer lines in secrets.
1 thing to take into account with these urls is the & sign should not end the line, but start a new line. Otherwise the url is broken, no matter the multiline notation or quotes
In my case I am using “window.location.hostname” to resolve host from the client browser in order to have it working with internal and external HA url. The only thing is, I do not know how to use secret in my case.
Here is my code but it is not working, it is complaining about Unexpected token ‘!’.
Workaround is to use config-template-card and “states[‘input_select.password’].state” but I would like to use secret everywhere if possible.