I get an "The API Weather.gov did not return a response." warning in logs since update. I assume something in the update has broken the app code. When I run the test alert and API response this is what I get:
"correlationId": "2797da60",
"title": "Unexpected Problem",
"type": "https://api.weather.gov/problems/UnexpectedProblem",
"status": 500,
"detail": "An unexpected problem has occurred.",
"instance": "https://api.weather.gov/requests/2797da60"
Anyone else having this issue?
This occurred occasionally prior to this release. I don’t think it’s related to the update. The betas didn’t seem to have a higher incidence for me.
I should point out that I’m not a coder, so I could be very wrong in my assumption. I’ve seen error 408, 500, 502, 503. I don’t have any idea what they mean.
The api.weather.gov has been a problem for some time now. A group of us have been working with the team and monitoring the server updates for several months. Read here for more information Weather.gov api github. It appears that most of us are now getting accurate data. Some are not. I get "500" errors often and have to resubmit.
500 is an internal server error at the web server.
This just got me looking and, yeah, ugh.
I'm seeing Dec 28, 2021 weather data returned by the call--but the browser gets current data.
I'm not seeing a way to "flush cache" or anything like that--seems something is getting old data.
From the browser, I get (the first bit):
In more viewable form:
@gopher.ny Any ideas about what might cause this?
The workaround mentioned in the thread referenced above does seem to work:
It seem wonky--but it also appears to force bypassing whatever cache is holding old data.
Haven't seen an httpGet call caching anything on its own before, but if you can create a standalone code sample that reproduces the issue, I'll take a look.
It sounds like others know to which app you’re referring. And if it’s an API problem the specific app may not matter that much.
But which community-developed app are you using? I’m not aware of a built-in app for NOAA alerts that queries the weather.gov API.
I use webcore. I have been pulling weather information from the api.weather.gov for months. I am using it on the pads around my house. Only recently have I been able to get data that is not days or weeks old.
Mine hasn't been working for months, even updated to the latest revision and I get this when I run the test option. It replies back with nothing can be found plus a url, the url is returns the following...
{
"correlationId": "53726559",
"parameterErrors": [
{
"parameter": "query.urgency[1]",
"message": "Does not have a value in the enumeration ["Immediate","Expected","Future","Past","Unknown"]"
},
{
"parameter": "query.urgency[2]",
"message": "Does not have a value in the enumeration ["Immediate","Expected","Future","Past","Unknown"]"
},
{
"parameter": "query.severity[1]",
"message": "Does not have a value in the enumeration ["Extreme","Severe","Moderate","Minor","Unknown"]"
},
{
"parameter": "query.severity[2]",
"message": "Does not have a value in the enumeration ["Extreme","Severe","Moderate","Minor","Unknown"]"
},
{
"parameter": "query.certainty[1]",
"message": "Does not have a value in the enumeration ["Observed","Likely","Possible","Unlikely","Unknown"]"
},
{
"parameter": "query.certainty[2]",
"message": "Does not have a value in the enumeration ["Observed","Likely","Possible","Unlikely","Unknown"]"
}
],
"title": "Bad Request",
"type": "https://api.weather.gov/problems/BadRequest",
"status": 400,
"detail": "Bad Request",
"instance": "https://api.weather.gov/requests/53726559"
Would really like get this workiing again, when it worked it worked really well.... Ideas?
Download the Hubitat app
