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

Default Unit of None Incompatible #153

Open
WendelFelius opened this issue Oct 4, 2024 · 3 comments
Open

Default Unit of None Incompatible #153

WendelFelius opened this issue Oct 4, 2024 · 3 comments
Labels
bug Something isn't working

Comments

@WendelFelius
Copy link

After installing Home Assistant Core 2024.10 it offered some repairs for Baby Buddy entities. This is the one for the lastfeeding-sensor:

The unit of 'xxx last feeding' (sensor.xxx_last_feeding) changed to '' which can't be converted to the previously stored unit, 'mL'. If the historic statistic values have a wrong unit, you can update the units of the old values. The values will not be updated. Otherwise you can choose to delete all historic statistic values, and start over.

How do you want to fix this issue?
[X] Update the unit of the historic statistic values from 'mL' to '', without converting.
[O] Delete all old statistic data for this entity

Also getting them for last temperature (°C) and last weight (kg).

Should I choose a fix myself (if so, which?) or wait for an update of the baby buddy integration?

@jcgoette
Copy link
Owner

jcgoette commented Oct 5, 2024

I don't think this has anything to do with the integration per se. I personally had it come up with an unrelated sensor also.

@jcgoette jcgoette added the invalid This doesn't seem right label Oct 5, 2024
@jcgoette jcgoette closed this as completed Oct 5, 2024
@WendelFelius
Copy link
Author

Logger: homeassistant.components.sensor
Source: components/sensor/__init__.py:731
integration: Sensor (documentation, issues)
First occurred: 12:05:14 (1 occurrences)
Last logged: 12:05:14

Entity sensor.babyname_last_temperature (<class 'custom_components.babybuddy.sensor.BabyBuddyChildDataSensor'>) is using native unit of measurement 'None' which is not a valid unit for the device class ('temperature') it is using; expected one of ['°F', 'K', '°C']; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/jcgoette/baby_buddy_homeassistant/issues

@jcgoette jcgoette reopened this Oct 29, 2024
@jcgoette jcgoette added enhancement New feature or request and removed invalid This doesn't seem right labels Oct 29, 2024
@jcgoette jcgoette changed the title Repairs: "The unit of ... has changed" Default Unit of None Incompatible Oct 29, 2024
@jcgoette jcgoette added bug Something isn't working and removed enhancement New feature or request labels Nov 13, 2024
@jcgoette
Copy link
Owner

Probably handle this by adding OptionsFlow into the initial ConfigFlow.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants