Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OpenUV: null instead of unknown #30973

Closed
metbril opened this issue Jan 19, 2020 · 1 comment · Fixed by #31018
Closed

OpenUV: null instead of unknown #30973

metbril opened this issue Jan 19, 2020 · 1 comment · Fixed by #31018
Assignees

Comments

@metbril
Copy link

metbril commented Jan 19, 2020

Home Assistant release with the issue:
0.103.6

Last working Home Assistant release (if known):
n/a

Operating environment (Hass.io/Docker/Windows/etc.):
hassio

Integration:
https://www.home-assistant.io/integrations/openuv/

Description of problem:
When current UV index is 0 (zero), the sun exposure times are defined as null, which renders them as yellow rows in Lovelace. The sensor values should become 'unknown' instead, so the user at least sees a proper sensor in the UI.

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
n/a

Traceback (if applicable):
n/a

Additional information:
Schermafbeelding 2020-01-19 om 17 02 27

@probot-home-assistant
Copy link

Hey there @bachya, mind taking a look at this issue as its been labeled with a integration (openuv) you are listed as a codeowner for? Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants