You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I can tell if the root issue is Open-Meteo of the Weather forecast card by forecast (especial visible if you look at hourly forecast) and way off time wise.it appears that it’s using UTC and not the system or users time zone—in both cases mine is set to Pacific Time Zone/Los Angeles. I live in CA/USA and it’s very noticeable. It also seems to mess up the daily forecasts often showing the days prior for case in the list.
If I use the HACS plugin Pirate Weather then things look correct. I can’t tell if Pirate Weather is compensating of a bug in the Weather forecast card or if Open-Meteo is the source of the issue.
If have viewed a few of older bugs in your bug base that all were closed only because the bugs were stale with no fixes displayed.
What version of Home Assistant Core has the issue?
2024.6.4
What was the last working version of Home Assistant Core?
All the data shows fine. Showing a screen shot would not show much unless you knew the local weather. But I feel certain that my max temps are nit happening at 11pm but more like 2 or 3pm.
The text was updated successfully, but these errors were encountered:
Hey there @frenck, mind taking a look at this issue as it has been labeled with an integration (open_meteo) you are listed as a code owner for? Thanks!
Code owner commands
Code owners of open_meteo 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 open_meteo Removes the current integration label and assignees on the issue, add the integration domain after the command.
@home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
@home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.
This is the current data displayed and then directly used as is on the Weather forecast card without being offset to local time. As I said I can’t tell between the two where the bug is.
This is for comparison with Pirate Weather which shows this (both screen shots were within a few minutes of each other.) Pirate Weather matches my expectations and what I see on my iPhone as the hourly weather forecast from Apple’s weather app.
I also noticed that Pirate Weather is showing when the moon is out in the hourly forecast. I can’t they’ll if that’s a bug or not in Open-Meteo.
The problem
I can tell if the root issue is Open-Meteo of the Weather forecast card by forecast (especial visible if you look at hourly forecast) and way off time wise.it appears that it’s using UTC and not the system or users time zone—in both cases mine is set to Pacific Time Zone/Los Angeles. I live in CA/USA and it’s very noticeable. It also seems to mess up the daily forecasts often showing the days prior for case in the list.
If I use the HACS plugin Pirate Weather then things look correct. I can’t tell if Pirate Weather is compensating of a bug in the Weather forecast card or if Open-Meteo is the source of the issue.
If have viewed a few of older bugs in your bug base that all were closed only because the bugs were stale with no fixes displayed.
What version of Home Assistant Core has the issue?
2024.6.4
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Open-Meteo
Link to integration documentation on our website
https://www.home-assistant.io/integrations/open_meteo
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
All the data shows fine. Showing a screen shot would not show much unless you knew the local weather. But I feel certain that my max temps are nit happening at 11pm but more like 2 or 3pm.
The text was updated successfully, but these errors were encountered: