Service call requested response data but did not match any entities about core HOT 7 CLOSED

Hey there @MatthewFlamm, @kamiyo, mind taking a look at this issue as it has been labeled with an integration (nws) you are listed as a code owner for? Thanks!

_{^{(message by CodeOwnersMention)}}

nws documentation
nws source
_{^{(message by IssueLinks)}}

from core.

This error Failed to call service weather.get_forecasts. Service call requested response data but did not match any entities is because the entity is unavailable due to some combination of NWS API weather outage or caching issue and stale data of the observation station you are using. When an entity is unavailable, the weather.get_forecasts service returns this error.

It is an unfortunate design that the unavailability of the observation data prevents you from retrieving the forecast data, even if that data is valid.

from core.

#119114 has a discussion of the no data/stale data problem for NWS.

from core.

I just curl'd the API real quick for one of the stations not working in HA and the data looks good and current, here's just the timestamps but the forecast also looks good and matches their own UI.

 "forecastGenerator": "HourlyForecastGenerator",
 "generatedAt": "2024-06-25T21:01:21+00:00",
 "updateTime": "2024-06-25T20:11:55+00:00",
 "validTimes": "2024-06-25T14:00:00+00:00/P8DT2H",

Like I said in #119114 I had never seen this behavior since recently upgrading my HA core which was quite a bit behind. I'm not sure if there were other changes in regards to how you handle this caching/validation that weren't there previously? A bit confused since the data looks good when I skip over the integration.

from core.

I just curl'd the API real quick for one of the stations not working in HA and the data looks good and current, here's just the timestamps but the forecast also looks good and matches their own UI.

This looks like the forecast endpoint, the observation end point is separate and causes most, but not all, problems.

The recent changes were maybe a bit too aggressive on pruning out stale data. And just because you curl once and get valid data does not mean that your HA user agent isn't being served stale data.

These are my guesses to what is going on.

from core.

Thanks, that explains it. I just looked at their example docs real quick, but using the observations/latest route I see:

"timestamp": "2024-06-24T21:13:00+00:00"

With my 2 hour timeout for valid data that lines up perfectly. So just issues on their side. I'll chalk it up to their recent changes and maybe some deployment issues as I've never seen such a gap. Thanks for helping me confirm.

I'm going to do a REST sensor for the forecast endpoint temporarily as that data looks good.

from core.

Now you have me thinking that it might be better with the current state of HA to have separate entities for observations and forecasts, but this is going around the weather entity model. So probably not a good long term solution.

from core.