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
73.81k stars 30.9k forks source link

Open Meteo (open_meteo) integration date parsing issue. #87899

Closed formatBCE closed 1 year ago

formatBCE commented 1 year ago

The problem

Open Meteo integration reports incorrect day name in forecast. First of all, I checked server and client device time zone setting and it's correct, as well as Home zone coordinates. Time zome I live in is PST (America/Vancouver). On screenshot, there's time card with correct time/date and day name, and Open Meteo forecast information. Check the first day - it's showing day back from now, but temp/weather info for today. Screenshot_20230211_112350_Home Assistant

On second screenshot you may see forecast info at the same moment. Screenshot_20230211_112427_Home Assistant

Most probably, the problem is in parsing date string from datetime field (for other integrations it seems to be timestamp, but here it's string representation). I tried to use template to parse this date to day, and it works correctly.

There was another issue open for this topic, but closed as stale. Please check this out https://github.com/home-assistant/core/issues/79064.

What version of Home Assistant Core has the issue?

2023.2.3

What was the last working version of Home Assistant Core?

Unknown

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

No response

home-assistant[bot] commented 1 year ago

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` Change the title of 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.

(message by CodeOwnersMention)


open_meteo documentation open_meteo source (message by IssueLinks)

gambalaya commented 1 year ago

I have the same display issue as @formatBCE . I am in time_zone America/Denver and on container version 2023.2.4, no errors in the logs. Appending T00:00:00 to the forecast datetime element using dev tools to manually override the value results in the day of week showing correctly, so it seems the date string by itself without time is indeed the problem:

open_meteo

StevenDTX commented 1 year ago

I seem to be having the same issue. However, I am not using open_mateo. I have my own weather station that feeds to Weather Underground. I get a weather entity from that.

This morning, it switched to Sunny at 4AM, and then at 3PM, it switched to Clear-Night.

weather card

issue-triage-workflows[bot] commented 1 year 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.

formatBCE commented 1 year ago

It's not stale, and still reproducible. I moved to different integration.

issue-triage-workflows[bot] commented 1 year 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.