nws_alerts icon indicating copy to clipboard operation
nws_alerts copied to clipboard

Please consider adding 'onset' as an attribute

Open kidhasmoxy opened this issue 1 year ago • 1 comments

The integration is fantastic and I'm using it for automations, but I've noticed that we'll often times have an alert long before the event in question. This is especially common for "watch" alerts.

I use this integration to trigger charging up my batteries to full and also certain other safety related items. Sometimes the onset is set as 24-36 hours after the alert starts, even when the alert is marked as severe. With the onset, I could decide when to start filling the batteries and also trigger certain automations for closer to the event vs the 1-2 days before where it's still sunny.

kidhasmoxy avatar Jul 08 '23 21:07 kidhasmoxy

I was about to suggest the same and then came across this. +1 for the suggestion, please. I would also like to suggest adding "ends" as I am seeing examples where the "ends" value and what is currently provided as "event expires" do not match. Thank you!

jhemak avatar Mar 31 '24 22:03 jhemak

I'll get this added soon. Sorry it's taken so long to implement.

finity69x2 avatar Jul 14 '24 10:07 finity69x2

Done

finity69x2 avatar Jul 15 '24 03:07 finity69x2

Are you open to also adding "ends" as suggested above? I have added it to mine manually but have to re-do the change every time you release an update to the integration.

jhemak avatar Jul 15 '24 22:07 jhemak