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

Not valid unit for device class distance #812

Closed
jwillemsen opened this issue Feb 1, 2024 · 8 comments
Closed

Not valid unit for device class distance #812

jwillemsen opened this issue Feb 1, 2024 · 8 comments

Comments

@jwillemsen
Copy link
Contributor

Region and Brand of car

EU, Hyundai Kona 2024 (scc2 supported)

Version of the integration

master using hyundai_kia_connect_api==3.14.1

Describe the bug

I found the following errors in my HA log after upgrading to master so that I cloud test hyundai_kia_connect_api==3.14.1

Debug logs if an error occurred

Logger: homeassistant.components.sensor
Source: components/sensor/__init__.py:719
Integration: Sensor (documentation, issues)
First occurred: 1:38:12 PM (3 occurrences)
Last logged: 1:38:12 PM

Entity sensor.kona_total_driving_range (<class 'custom_components.kia_uvo.sensor.HyundaiKiaConnectSensor'>) is using native unit of measurement 'None' which is not a valid unit for the device class ('distance') it is using; expected one of ['km', 'cm', 'ft', 'mi', 'yd', 'm', 'mm', 'in']; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/fuatakgun/kia_uvo/issues
Entity sensor.kona_target_range_of_charge_ac (<class 'custom_components.kia_uvo.sensor.HyundaiKiaConnectSensor'>) is using native unit of measurement 'None' which is not a valid unit for the device class ('distance') it is using; expected one of ['km', 'cm', 'ft', 'mi', 'yd', 'm', 'mm', 'in']; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/fuatakgun/kia_uvo/issues
Entity sensor.kona_target_range_of_charge_dc (<class 'custom_components.kia_uvo.sensor.HyundaiKiaConnectSensor'>) is using native unit of measurement 'None' which is not a valid unit for the device class ('distance') it is using; expected one of ['km', 'cm', 'ft', 'mi', 'yd', 'm', 'mm', 'in']; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/fuatakgun/kia_uvo/issues
@Bubo08
Copy link
Collaborator

Bubo08 commented Feb 1, 2024

I see the same. Not sure were it is comming from. The hard coded odometer (km) is working.

@Bubo08
Copy link
Collaborator

Bubo08 commented Feb 1, 2024

I think I found the problem. It should be fixed now.
Hyundai-Kia-Connect/hyundai_kia_connect_api#491

Bad pull request. I will check it in tomorrow again.

@Bubo08
Copy link
Collaborator

Bubo08 commented Feb 2, 2024

Pull request created: Hyundai-Kia-Connect/hyundai_kia_connect_api#492
You may test it.

@Bubo08
Copy link
Collaborator

Bubo08 commented Feb 4, 2024

A new version 2.20 is out which has fixed this bug. You might control and close this bug.

@jwillemsen
Copy link
Contributor Author

The changes where merged after 2.20, so we need a new 2.21 for this

@Bubo08
Copy link
Collaborator

Bubo08 commented Feb 5, 2024

It was included in v3.14.2 and that is included in the manifest. I also checked my log and I did not see the error messages anymore. So It looks good :-)

@cdnninja
Copy link
Collaborator

cdnninja commented Feb 5, 2024

You can try it out by using HACS and using redownload and select master version. Releases of Ki_uvo auto release Sundays and Wednesday. Or if we force it.

@jwillemsen
Copy link
Contributor Author

Fixed, warnings gone

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

No branches or pull requests

3 participants