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
Hey there @MisterCommand, mind taking a look at this issue as it has been labeled with an integration (hko) you are listed as a code owner for? Thanks!
Code owner commands
Code owners of hko 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 hko 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.
The problem
Wrong state of weather of HKO Integration
the result value on home assistant is hail while the website of HKO is cloudy
i cant find the root cause but
ATTR_CONDITION_RAINY was written in ATTR_CONDITION_HAIL in https://github.com/home-assistant/core/blob/dev/homeassistant/components/hko/coordinator.py
which might be the root cause of the problem
What version of Home Assistant Core has the issue?
core-2024.12.5
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant Container
Integration causing the issue
Hong Kong Observatory
Link to integration documentation on our website
https://www.home-assistant.io/integrations/hko#weather-platform
Diagnostics information
in https://github.com/home-assistant/core/blob/dev/homeassistant/components/hko/coordinator.py
it is
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: