@bpwwerCan Dense Fog Advisory alerts be added to your plug-in? We've had several in the last few days and they aren't being presented in the plug-in.

Thank you!

It's already there "Dense Fog Advisory".    If it's not working then possibly they've changed the wording so that the parsing is failing.  

With the log level at debug, what does the plug-in show when that alert comes in?

2 hours ago, bpwwer said:

It's already there "Dense Fog Advisory".    If it's not working then possibly they've changed the wording so that the parsing is failing.  

With the log level at debug, what does the plug-in show when that alert comes in?

The plugin shows nothing other than "None" in the admin console.  I will definitely look at the log next time.

Thank you!

Edited February 1, 20241 yr by dbuss

On 2/1/2024 at 12:14 PM, bpwwer said:

With the log level at debug, what does the plug-in show when that alert comes in?

@bpwwerHere's the debug log while we have a Dense Fog Advisory.

2024-02-04 06:03:18,153 Thread-4 udi_interface ERROR noaa:query_alerts: Weather alert update failure

2024-02-04 06:03:18,153 Thread-4 udi_interface ERROR noaa:query_alerts: not well-formed (invalid token): line 1, column 0

That doesn't look like debug information.   The errors indicate that whatever the plug-in got, it wasn't something it recognizes.   I'd need the see the data from the query which it should show if the log level is set to debug.

1 hour ago, bpwwer said:

That doesn't look like debug information.   The errors indicate that whatever the plug-in got, it wasn't something it recognizes.   I'd need the see the data from the query which it should show if the log level is set to debug.

We aren't under any weather alert at this time.

The first line below indicates an invalid zone. I have been using WIZ048/WIC139, and I have been getting other alerts just fine.

 

2024-02-04 12:43:48,700 Command udi_interface DEBUG noaa:query_alerts: ? invalid zone

2024-02-04 12:43:48,700 Command udi_interface DEBUG noaa:query_alerts: Parse XML and set drivers

2024-02-04 12:43:48,701 Command udi_interface ERROR noaa:query_alerts: Weather alert update failure

2024-02-04 12:43:48,701 Command udi_interface ERROR noaa:query_alerts: not well-formed (invalid token): line 1, column 0

There should be a debug message before the "? invalid zone" message that shows the actual query request that is being sent.

"? invalid zone" is what's is returned by the query which indicates that the zone is invalid.  WIZ048 is a valid zone and I don't get that error when I query for that zone (but currently, as you said, there are no alerts for that zone).

The query should look like:

https://alerts.weather.gov/cap/wwaatmget.php?x=WIZ048&y=1

 

7 minutes ago, bpwwer said:

There should be a debug message before the "? invalid zone" message that shows the actual query request that is being sent.

"? invalid zone" is what's is returned by the query which indicates that the zone is invalid.  WIZ048 is a valid zone and I don't get that error when I query for that zone (but currently, as you said, there are no alerts for that zone).

The query should look like:

https://alerts.weather.gov/cap/wwaatmget.php?x=WIZ048&y=1

 

2024-02-04 13:13:12,179 Thread-54 udi_interface DEBUG noaa:query_alerts: request = https://alerts.weather.gov/cap/wwaatmget.php?x=WIZ048/WIC139&y=1

2024-02-04 13:13:12,179 Thread-54 udi_interface DEBUG noaa:query_alerts: request = https://alerts.weather.gov/cap/wwaatmget.php?x=WIZ048/WIC139&y=1

WIZ048 is a valid zone code

WIC139 is a valid county code

WIZ048/WIC139 is not valid

16 minutes ago, bpwwer said:

WIZ048 is a valid zone code

WIC139 is a valid county code

WIZ048/WIC139 is not valid

I corrected it and will keep you posted.

Thank you!

On 2/4/2024 at 2:17 PM, bpwwer said:

WIZ048 is a valid zone code

WIC139 is a valid county code

WIZ048/WIC139 is not valid

Once I corrected the operator error, it worked perfectly. 

Thank you, @bpwwer!