-
-
Notifications
You must be signed in to change notification settings - Fork 39
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
HA warning: Entity is using state class 'total_increasing' which is impossible considering device class ('monetary') it is using #304
Comments
i would like to mention that i got a similar issue Logger: homeassistant.components.sensor Entity sensor.dcc_sourced_smart_electricity_meter_cost_today (<class 'custom_components.hildebrandglow_dcc.sensor.Cost'>) is using state class 'total_increasing' 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. |
Yes also seeing this as soon as I updated to Home Assistant 2023.2: Entity sensor.electric_cost_today (<class 'custom_components.hildebrandglow_dcc.sensor.Cost'>) is using state class 'total_increasing' which is impossible considering device class ('monetary') it is using |
I'm looking into this - for the moment it should be safe to just ignore this |
I manage to fix the warning my changing
to
Code where I changed it
|
I just installed today and am getting the same error, Has the above PR been merged? |
@HandyHat Hi, is there any progress with this PR being merged? |
Describe the bug
Since upgrading Home Assistant to 2023.2, it now logs this warning about both "cost today" sensors
To Reproduce
Steps to reproduce the behaviour:
Expected behaviour
No warning from Home Assistant when using this integration
Screenshots
Version
Hildebrand Glow (DCC) Integration v1.0.3
Home Assistant 2023.2.0
Supervisor 2023.01.1
Operating System 9.5
Frontend 20230201.0 - latest
Debug log
Does not seem relevant here
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: