home-assistant[bot]
commented
4 weeks ago Hey there @frenck, mind taking a look at this issue as it has been labeled with an integration (season) you are listed as a code owner for? Thanks!
Code owner commands
Code owners of `season` 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 season` 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.(message by CodeOwnersMention)
season documentation season source (message by IssueLinks)
anthonykeane
The problem
The Season Integration shows as Autumn but at this time it has been winter for 7 hours in the AEST zone
What version of Home Assistant Core has the issue?
core-2024.5.4
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant Core
Integration causing the issue
season
Link to integration documentation on our website
https://www.home-assistant.io/integrations/season
Diagnostics information
None: as the integration is functioning well, no errors, it just shows the incorrect data in the state.
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
I suspect it is a time zone reference issue, ie the integration is using GMT to detect the season which would show the correct season if I was in that timezone, which I am not :) I am in AEST