We had a winter storm watch.  Worked perfectly and programs ran.  That changed to warning.  Also worked perfectly.

Warning has expired for about 10 hours now.  But its not clearing on my end.

So it looks like it cleared fine when a new warning replaced it but NOT when the alert went back to NONE

I ran the URL that I see in logs (logs attached) and I can see it seems to have issue.

I restarted the nodeserver and it worked fine and Alert changed to none but I cant do that after every alert.

Can you please take a look?  Logs were in ERROR but changed to dubug and did Query a few times.  Logs are before the restart.  I just did one AFTER restart and added after restart to name

https://api.weather.gov/alerts.atom?zone[0]=VAC107&limit=500&active=1

 

correlationId	"1953878"
parameterErrors
0
parameter	"query.amp;limit"
message	'Query parameter "amp;limit" is not recognized'
1
parameter	"query.amp;active"
message	'Query parameter "amp;active" is not recognized'
title	"Bad Request"
type	"https://api.weather.gov/problems/BadRequest"
status	400
detail	"Bad Request"
instance	"https://api.weather.gov/requests/1953878"

NOAA_1-7-2025_103852_AM.zip NOAA_1-7-2025_103856_AM.zip NOAA_1-7-2025_104445_AM AFTER RESTART.zip

As near as I can tell something changed in the response from NOAA.  The plug-in is looking for "There are no active watches, warnings or advisories"  but that doesn't seem to exist anymore.  Instead, the response is pretty much empty.  I'll need to re-work the plug-in to detect that the response is empty instead of looking for that string.

Just now, bpwwer said:

As near as I can tell something changed in the response from NOAA.  The plug-in is looking for "There are no active watches, warnings or advisories"  but that doesn't seem to exist anymore.  Instead, the response is pretty much empty.  I'll need to re-work the plug-in to detect that the response is empty instead of looking for that string.

sorry that I am the one who always finds the issues.  But having the alerts was really nice for the storm.

 

Jeff

I just publish version 2.0.11 which should clear the alerts once they are no longer active.