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

Wrong pressure units for weather cards for Dark Sky and OpenWeatherMap when using US #16818

Closed
duckpuppy opened this issue Sep 24, 2018 · 4 comments

Comments

@duckpuppy
Copy link

Home Assistant release with the issue:

0.78.3

Last working Home Assistant release (if known):
N/A

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

Docker

Component/platform:

https://www.home-assistant.io/components/weather.darksky/
https://www.home-assistant.io/components/weather.openweathermap/

Description of problem:
Dark Sky and OpenWeatherMap return pressure in mbar and hPa respectively, but the HA cards in the UI label those as inHg. Either the labeling should be corrected, or each weather component should make sure to convert from the returned value to the expected standard unit for the currently set unit configuration.

Both DarkSky and OpenWeatherMap return pressure in those units regardless of the unit settings of their respective APIs. Dark Sky does say the SI unit used for pressure is hPa, but there's a 1:1 relationship between mbar and hPa.

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

 weather:
   - platform: darksky
     api_key: !secret darksky_api_key
   - platform: openweathermap
     api_key: !secret owm_api_key

Additional information:
OpenWeatherMap API Data: https://openweathermap.org/weather-data
Dark Sky API Data: https://darksky.net/dev/docs

@timothybrown
Copy link

Just wanted to confirm I see the same behavior.
13bae2d7-ba05-4e67-905e-7bca728774b0

@balloobbot
Copy link

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 👍

@balloobbot
Copy link

This issue will be auto-closed because there hasn't been any activity for a few months. Feel free to open a new one if you still experience this problem 👍

@MatthewFlamm
Copy link
Contributor

@duckpuppy are you able to reopen this?

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

No branches or pull requests

5 participants