Ok got it now. I don’t use GUI to edit those automation. In fact, just checked, because it is a separate file (not stored in automations.yaml) I can’t edit it at all in GUI. Maybe that’s the problem, maybe GUI doesn’t handle variables properly as it is design for quite simple automations and that’s why it keeps known properties at the top and moves unknown (from the GUI automation template perspective) at the bottom, not sure tbh.
Looking at the automations.yaml I am guessing that the only properties GUI can handle are id, alias, description, trigger, condition, action, mode (also use_blueprint) in this exact order so when the GUI is parsing your automation to save it in the automations.yaml file it reorder your properties to this exact order and leaves everything else at the bottom.
In theory you could add additional if before warning.link to check if warnign is null then do nothing, and if not, then use warning.link. Potential problem you may get is that the warning will never be set at the moment the action is running so you will never get this link working.
It looks like Somerset isn’t included in the current warning for the SW region, and you are filtering on Somerset for your card by the looks of it? I’m in Devon, and the warning is showing up correctly for me
Yeah it’s odd though. I check the forecast for Street, in Somerset & the wind goes over 40mph. A yellow warning is triggered by winds over 40mph. but maybe it has to last more than 2-3hours?
Anyone know why the sensor would show that I have 3 alerts for my area but only 2 are showing in the attributes? Is it because the event start time has already passed?