Weather units: climacell (1.3/4)#61472
Conversation
|
Hey there @raman325, mind taking a look at this pull request as it has been labeled with an integration ( |
|
Some attribute values in the tests have changed. Can you verify if the new value is correct? If they are, please update the tests, and thank you! EDIT: at second glance, some of these changes seem suspect. Look at wind speed as an example: that's a 3+ factor difference between numbers. That would not make sense for MPH -> KPH or MPH -> m/s. So something seems off but I haven't dug in enough to figure out why |
|
My bad! I'll update! It's KPH -> m/s (the default metric wind speed got changed to m/s since it seems that's what most of the world uses). However, the easy fix is to adjust the unit system to keep the units that were used before. |
320b527 to
f35e535
Compare
* climacell units * Fix climacell tests
Proposed change
Uses the new weather conversion in the weather entity ( #59533) to convert weather values to the configured units.
Type of change
Additional information
Checklist
black --fast homeassistant tests)If user exposed functionality or configuration variables are added/changed:
If the code communicates with devices, web services, or third-party tools:
Updated and included derived files by running:
python3 -m script.hassfest.requirements_all.txt.Updated by running
python3 -m script.gen_requirements_all..coveragerc.The integration reached or maintains the following Integration Quality Scale:
To help with the load of incoming pull requests: