macjeff Posted Saturday at 11:21 PM Posted Saturday at 11:21 PM Had a severe thunderstorm watch and warning. Neither showed up. watch is still in effect for 3 more hours. My zone is VAZ505 I tried a few others with active alerts and same issue. So most likely they changed their format again NOAA_5-3-2025_70932_PM.zip Quote
bpwwer Posted Sunday at 05:23 PM Posted Sunday at 05:23 PM From the log, it shows that the return response to the alert query is that no alerts are available. For a couple of the queries, it returned bad request, which implies that their servers are having issues because a few queries later it back to returning a valid response with no alerts. Doing additional manual queries, I can't find anything for VAZ505 (or any VAZ area). /alerts/active/count shows no active alerts for VAZ /alerts/active also shows no alerts for VAZ It doesn't appear that the query formats have changed. Quote
macjeff Posted Sunday at 06:33 PM Author Posted Sunday at 06:33 PM I will monitor. There are no warnings now but the next time there is I will check. One issue we have. VAZ506 is the county but since the western half of Loudoun county where I live is higher elevation they split it mainly for Winter. VA505 is Western Loudoun When I searched BOTH yesterday until 10pm last night there was a watch. I will email you when one is issued again if not working. thanks Quote
macjeff Posted 20 hours ago Author Posted 20 hours ago See screenshot showing VAZ506 (see url) Shows active watch and warning. See NOAA. NOTHING And logs attached but issue is they may be gone by the time you get this. But you can plug in and see if you do before midnight EDT. I did just restart 025-05-05 18:05:14.200 Thread-4 (start) udi_interface DEBUG noaa:query_alerts: Parse XML and set drivers 2025-05-05 18:05:14.200 Thread-4 (start) udi_interface DEBUG noaa:query_alerts: <?xml version="1.0" encoding="UTF-8"?> <feed xmlns="http://www.w3.org/2005/Atom" xmlns:cap="urn:oasis:names:tc:emergency:cap:1.2"> <id>https://api.weather.gov/alerts.atom?zone%5B0%5D=VAZ505&limit=500&active=1</id> <generator>NWS CAP Server</generator> <updated>2025-04-29T00:00:00+00:00</updated> <author> <name>w-nws.webmaster@noaa.gov</name> </author> <title>Current watches, warnings, and advisories for Western Loudoun (VAZ505) VA</title> <link rel="self" href="https://api.weather.gov/alerts.atom?zone%5B0%5D=VAZ505&limit=500&active=1"/> </feed> 2025-05-05 18:05:14.200 Thread-4 (start) udi_interface DEBUG noaa:query_alerts: Parse XML and set drivers 2025-05-05 18:05:14.201 Thread-4 (start) udi_interface DEBUG noaa:query_alerts: No alerts found. 2025-05-05 18:05:14.201 Thread-4 (start) udi_interface.node DEBUG node:setDriver: controller:NOAA Weather Reporting set GV21 to 0.0 to Polyglot 2025-05-05 18:05:14.201 Thread-4 (start) udi_interface DEBUG noaa:query_alerts: No alerts found. 2025-05-05 18:05:14.201 Thread-4 (start) udi_interface.node DEBUG node:setDriver: controller:NOAA Weather Reporting set GV21 to 0.0 to Polyglot 2025-05-05 18:05:14.201 Thread-4 (start) udi_interface.node DEBUG node:reportDriver: Updating value to 0.0 2025-05-05 18:05:14.201 Thread-4 (start) udi_interface DEBUG noaa:update_driver: setDriver (GV21, 0.000000) 2025-05-05 18:05:14.201 Thread-4 (start) udi_interface.node DEBUG node:reportDriver: Updating value to 0.0 2025-05-05 18:05:14.201 Thread-4 (start) udi_interface DEBUG noaa:update_driver: setDriver (GV21, 0.000000) 2025-05-05 18:05:14.201 Thread-4 (start) udi_interface.node DEBUG node:setDriver: controller:NOAA Weather Reporting set GV22 to 0.0 to Polyglot 2025-05-05 18:05:14.201 Thread-4 (start) udi_interface.node DEBUG node:setDriver: controller:NOAA Weather Reporting set GV22 to 0.0 to Polyglot 2025-05-05 18:05:14.201 Thread-4 (start) udi_interface.node DEBUG node:reportDriver: Updating value to 0.0 2025-05-05 18:05:14.201 Thread-4 (start) udi_interface DEBUG noaa:update_driver: setDriver (GV22, 0.000000) 2025-05-05 18:05:14.201 Thread-4 (start) udi_interface.node DEBUG node:setDriver: controller:NOAA Weather Reporting set GV23 to 0.0 to Polyglot 2025-05-05 18:05:14.201 Thread-4 (start) udi_interface.node DEBUG node:reportDriver: Updating value to 0.0 2025-05-05 18:05:14.201 Thread-4 (start) udi_interface DEBUG noaa:update_driver: setDriver (GV23, 0.000000) 2025-05-05 18:05:14.201 Thread-4 (start) udi_interface.node DEBUG node:setDriver: controller:NOAA Weather Reporting set GV24 to 0.0 to Polyglot 2025-05-05 18:05:14.201 Thread-4 (start) udi_interface.node DEBUG node:reportDriver: Updating value to 0.0 2025-05-05 18:05:14.202 Thread-4 (start) udi_interface DEBUG noaa:update_driver: setDriver (GV24, 0.000000) 2025-05-05 18:05:14.202 Thread-4 (start) udi_interface.node DEBUG node:setDriver: controller:NOAA Weather Reporting set GV25 to 0.0 to Polyglot 2025-05-05 18:05:14.202 Thread-4 (start) udi_interface.node DEBUG node:reportDriver: Updating value to 0.0 2025-05-05 18:05:14.202 Thread-4 (start) udi_interface DEBUG noaa:update_driver: setDriver (GV25, 0.000000) 2025-05-05 18:05:14.202 Thread-4 (start) udi_interface.node DEBUG node:setDriver: controller:NOAA Weather Reporting set GV26 to 0.0 to Polyglot 2025-05-05 18:05:14.201 Thread-4 (start) udi_interface.node DEBUG node:reportDriver: Updating value to 0.0 2025-05-05 18:05:14.201 Thread-4 (start) udi_interface DEBUG noaa:update_driver: setDriver (GV22, 0.000000) 2025-05-05 18:05:14.201 Thread-4 (start) udi_interface.node DEBUG node:setDriver: controller:NOAA Weather Reporting set GV23 to 0.0 to Polyglot 2025-05-05 18:05:14.201 Thread-4 (start) udi_interface.node DEBUG node:reportDriver: Updating value to 0.0 2025-05-05 18:05:14.201 Thread-4 (start) udi_interface DEBUG noaa:update_driver: setDriver (GV23, 0.000000) 2025-05-05 18:05:14.201 Thread-4 (start) udi_interface.node DEBUG node:setDriver: controller:NOAA Weather Reporting set GV24 to 0.0 to Polyglot 2025-05-05 18:05:14.201 Thread-4 (start) udi_interface.node DEBUG node:reportDriver: Updating value to 0.0 2025-05-05 18:05:14.202 Thread-4 (start) udi_interface DEBUG noaa:update_driver: setDriver (GV24, 0.000000) 2025-05-05 18:05:14.202 Thread-4 (start) udi_interface.node DEBUG node:setDriver: controller:NOAA Weather Reporting set GV25 to 0.0 to Polyglot 2025-05-05 18:05:14.202 Thread-4 (start) udi_interface.node DEBUG node:reportDriver: Updating value to 0.0 2025-05-05 18:05:14.202 Thread-4 (start) udi_interface DEBUG noaa:update_driver: setDriver (GV25, 0.000000) 2025-05-05 18:05:14.202 Thread-4 (start) udi_interface.node DEBUG node:setDriver: controller:NOAA Weather Reporting set GV26 to 0.0 to Polyglot 2025-05-05 18:05:14.202 Thread-4 (start) udi_interface.node DEBUG node:reportDriver: Updating value to 0.0 2025-05-05 18:05:14.202 Thread-4 (start) udi_interface DEBUG noaa:update_driver: setDriver (GV26, 0.000000) 2025-05-05 18:05:14.202 Thread-4 (start) udi_interface.node DEBUG node:setDriver: controller:NOAA Weather Reporting set GV27 to 0.0 to Polyglot 2025-05-05 18:05:14.202 Thread-4 (start) udi_interface.node DEBUG node:reportDriver: Updating value to 0.0 2025-05-05 18:05:14.202 Thread-4 (start) udi_interface DEBUG noaa:update_driver: setDriver (GV27, 0.000000) 2025-05-05 18:05:14.202 Thread-4 (start) udi_interface.node DEBUG node:reportDriver: Updating value to 0.0 2025-05-05 18:05:14.202 Thread-4 (start) udi_interface DEBUG noaa:update_driver: setDriver (GV26, 0.000000) 2025-05-05 18:05:14.202 Thread-4 (start) udi_interface.node DEBUG node:setDriver: controller:NOAA Weather Reporting set GV27 to 0.0 to Polyglot 2025-05-05 18:05:14.202 Thread-4 (start) udi_interface.node DEBUG node:reportDriver: Updating value to 0.0 2025-05-05 18:05:14.202 Thread-4 (start) udi_interface DEBUG noaa:update_driver: setDriver (GV27, 0.000000) Quote
macjeff Posted 20 hours ago Author Posted 20 hours ago see preious post but need to add this my zone is western Loudoun which is part of the PUBLIC ZONE list. There is also a county zone list. If you use that list its the entire county. We are in a LARGE county. If you use the entire county we could be under a winter storm warning with snow while the other half (Eastern Loudoun) is rain. Go here. Look in public zone and you will find eastern and western loudoun https://alerts.weather.gov/?reset=true Then on same page look in COUNTY zone and find LOUDOUN. Thats working. (VAC107) But I have had the VAZ505 in there since day 1 and always worked until now. So it is working for the COUNTY but not the PUBLIC zone that it used to. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.