-
Notifications
You must be signed in to change notification settings - Fork 42
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
[Bug]: sensor: state_class_removed for all humidity sensors #306
Comments
@coreGreenberet is it a normal sensor or a custom sensor. |
It's the normal touch tree |
Now there is more info in the "repair" part of HA:
looks like it is missing |
@coreGreenberet humidity sensors does not get a state class by default. You have to set it if you want to use the statistics. It is not a bug. I have at the moment no possibility to set the state class correctly for humidity sensors. |
I can confirm this behavior for: |
Of course this would fix the problem. Why is it not so easy to automatically assign all the needed parameters: When a sensor is created I need the information what sensor type it is. For example a Temperature So I do not really see a perfect way to solve this problem for all users. The only way to solve it at the moment is |
can you try the version from the 306-bug-sensor-state_class_removed-for-all-humidity-sensors I tried to set at least the state_class to measurement for both types of sensors. |
Warnings in HA are gone and so far everything is working =) thanks |
I can also confirm: warnings are gone - thanks! |
I integrate it in the next release. Thanks for your help. |
Describe the bug
After upgrading to HomeAssistant 2024.10.0 I'm receiving this warning for all humidity sensors:
sensor.luftfeuchte Verfügt nicht mehr über eine Zustandsklasse
sensor: state_class_removed
Firmware of your Miniserver
15.1.8.20
HomeAssistant install method
HASSIO
Version of HomeAssistant
2024.10.0
Version of Pyloxone
0.6.15
Update pyloxone
is already latest
Log
Settings for the log can be found on the main page under the section Log Configuration
The text was updated successfully, but these errors were encountered: