home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
72.71k stars 30.45k forks source link

Hourly weather forecasts no longer work after updating to Home Assistant 2023.8 #97787

Closed jaydeethree closed 2 months ago

jaydeethree commented 1 year ago

The problem

I have tested this with both custom components and core integrations, and it looks like Home Assistant 2023.8 broke hourly weather forecasts. Here's an example using the built-in National Weather Service integration - this is the entity that's created:

Screenshot 2023-08-04 094055

This entity contains a forecast for each hour. However Home Assistant is no longer able to display the hour for each forecast, it only displays the day:

Screenshot 2023-08-04 094300

And this is how it looks using the built-in weather card - again, hours are missing and only the day is displayed:

Screenshot 2023-08-04 094442

My best guess is that some part of this commit is the root cause, as it seems like that made significant changes to weather forecasting.

What version of Home Assistant Core has the issue?

core-2023.8.0

What was the last working version of Home Assistant Core?

core-2023.7.3

What type of installation are you running?

Home Assistant OS

Integration causing the issue

weather

Link to integration documentation on our website

https://www.home-assistant.io/integrations/weather

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

home-assistant[bot] commented 1 year ago

Hey there @home-assistant/core, mind taking a look at this issue as it has been labeled with an integration (weather) you are listed as a code owner for? Thanks!

Code owner commands Code owners of `weather` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign weather` Removes the current integration label and assignees on the issue, add the integration domain after the command.

(message by CodeOwnersMention)


weather documentation weather source (message by IssueLinks)

home-assistant[bot] commented 1 year ago

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!

Code owner commands Code owners of `nws` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign nws` Removes the current integration label and assignees on the issue, add the integration domain after the command.

(message by CodeOwnersMention)


nws documentation nws source (message by IssueLinks)

luxuwin commented 1 year ago

same issue here

iMiMx commented 1 year ago

Yep - tested with Pirate Weather and OpenWeatherMap, also multiple display cards, same on all.

Colorado4Wheeler commented 1 year ago

I see this on all hourly weather forecasts, including OpenWeatherMap, National Weather Service and Weatherflow.

katiuskt commented 1 year ago

Confirmed it also happens with AEMET integration (https://www.home-assistant.io/integrations/aemet/)

SentiHassio1979 commented 1 year ago

Too maybe point in the right direction (or totally not) :) if I go into developer tools for the openweather entity and change the value of the first datetime entry to tomorrow (or somewhere in future it might) all values show up with a time again. so seems that after the update HA does not like it that the first found value is historical and forecasting??? No expert

image image

andy1717 commented 1 year ago

Too maybe point in the right direction (or totally not) :) if I go into developer tools for the openweather entity and change the value of the first datetime entry to tomorrow (or somewhere in future it might) all values show up with a time again. so seems that after the update HA does not like it that the first found value is historical and forecasting??? No expert

image image

Didn't make any difference for me. I found the first value was already at a future time, changed it anyway but still showing (Day) on the forecast card.

katiuskt commented 1 year ago

I think this issue is related with these: https://github.com/bremor/bureau_of_meteorology/issues/181 https://github.com/home-assistant/frontend/issues/17472

And, apparently they should be fixed with https://github.com/home-assistant/frontend/pull/17486 It will be included in frontend version 20230802.1 (https://github.com/home-assistant/frontend/releases/tag/20230802.1) expected to be included into 2023.8.3 (https://github.com/home-assistant/core/pull/98623) 🤞🤞

SentiHassio1979 commented 1 year ago

I think this issue is related with these:

https://github.com/bremor/bureau_of_meteorology/issues/181

https://github.com/home-assistant/frontend/issues/17472

And, apparently they should be fixed with https://github.com/home-assistant/frontend/pull/17486

It will be included in frontend version 20230802.1 (https://github.com/home-assistant/frontend/releases/tag/20230802.1) expected to be included into 2023.8.3 (https://github.com/home-assistant/core/pull/98623) 🤞🤞

Confirmed, for me the update has resolved this issue and it displays hours again. Thanks!

issue-triage-workflows[bot] commented 9 months ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

jlrosssc commented 6 months ago

It looks like the same issue, or a similar one has arisen after the update to 2024.4.0. When I check the service Weather: get.forecasts it shows today plus 5 days future forecast but when I run Get States for it, I only get today's forecast. Also, previous templates referencing forecast do not work.

Noltari commented 6 months ago

It looks like the same issue, or a similar one has arisen after the update to 2024.4.0. When I check the service Weather: get.forecasts it shows today plus 5 days future forecast but when I run Get States for it, I only get today's forecast. Also, previous templates referencing forecast do not work.

@jlrosssc this was intentional: https://github.com/home-assistant/core/pull/110764 https://github.com/home-assistant/architecture/discussions/781

jlrosssc commented 6 months ago

I'm not clear how to now create this combined forecast showing hourly and daily. If I create Weather: Get forecasts service, and select daily or hourly, I get a daily or hourly forecast shown but neither shows when I select them in the States or reference in a card.

hettinger77 commented 5 months ago

The 'Example template sensor that contains the hourly forecast' doesn't work for me using met.no. Forecasts were working and then broke recently. :-/

MatthewFlamm commented 5 months ago

I'm removing the nws label from this as multiple people have chimed in with other integrations and forecasts were changed in the built-in weather model.

MatthewFlamm commented 5 months ago

@home-assistant unassign nws

issue-triage-workflows[bot] commented 2 months ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.