jparthum
(Jason Parthum)
July 19, 2020, 7:16pm
3
As a workaround you could try dynamic URLs. With this method your ‘Cast’ command would contain a static URL which would then be ‘resolved’ (redirected) to the input URL:
I wasn’t able to find any similar examples for such a useful tool so I’m posting in the hopes this will help others.
This is a simplified overview of a method for creating URLs that can be dynamically updated based on state changes. URLs created with template_sensors aren’t ‘live’ (clickable) in Lovelace and templates cannot be used directly in Lovelace Cards, but this gap can be bridged via APIs for ‘branded’ URL services. For this example I chose Rebrandly . The end result is a static URL t…