-
Notifications
You must be signed in to change notification settings - Fork 24
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
numereic / non-numeric type errors in latest home assistant beta #25
Comments
I’m seeing similar entries in the release version (HA 2023.2] e.g. Logger: homeassistant.components.sensor Sensor sensor.smart_meter_ihd_software_version has device class None, state class measurement and unit None thus indicating it has a numeric value; however, it has the non-numeric value: v1.8.13 (<class 'str'>); Please update your configuration if your entity is manually configured, otherwise report it to the custom integration author. and Logger: homeassistant.components.sensor Entity sensor.smart_meter_electricity_import_standing_charge (<class 'custom_components.hildebrand_glow_ihd.sensor.HildebrandGlowMqttSensor'>) is using state class 'measurement' which is impossible considering device class ('monetary') it is using; Please update your configuration if your entity is manually configured, otherwise report it to the custom integration author. |
I can confirm having just installed this integration tonight that I am also getting the same errors. I'm running on: Home Assistant 2023.2.2 |
Looking at this, it would appear this is due to the "v" in the version number that's picked up. if the "v" can be stripped from the front of the text then that would fix this issue I think. I'm not sure how to do that, but I'm sure someone cleverer than me can do it!! So when the data gets pulled through, the values are coming in like this:
Then from line 40 in sensor.py, the following section creates the sensor:
On the last line, is there anything that can be done at this point to drop the first letter of the "software" value?? |
@Clam58 I've seen this too and found the following from a spot of Googling..... I tried replacing the value Also found that someone has mentioned a similar problem on the DCC version of this repo: I've also found a couple of my own template sensors with this issue too. |
errors in log: Home Assistant 2023.2.0b4
The text was updated successfully, but these errors were encountered: