You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.name_account_balance (<class 'custom_components.chargepoint.sensor.ChargePointSensorEntity'>) is using state class 'measurement' which is impossible considering device class ('monetary') it is using; expected None or one of 'total'; Please update your configuration if your entity is manually configured, otherwise report it to the custom integration author.
WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.cph50_charge_cost (<class 'custom_components.chargepoint.sensor.ChargePointChargerSensorEntity'>) is using state class 'total_increasing' which is impossible considering device class ('monetary') it is using; expected None or one of 'total'; Please update your configuration if your entity is manually configured, otherwise report it to the custom integration author.
The text was updated successfully, but these errors were encountered:
WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.name_account_balance (<class 'custom_components.chargepoint.sensor.ChargePointSensorEntity'>) is using state class 'measurement' which is impossible considering device class ('monetary') it is using; expected None or one of 'total'; Please update your configuration if your entity is manually configured, otherwise report it to the custom integration author.
WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.cph50_charge_cost (<class 'custom_components.chargepoint.sensor.ChargePointChargerSensorEntity'>) is using state class 'total_increasing' which is impossible considering device class ('monetary') it is using; expected None or one of 'total'; Please update your configuration if your entity is manually configured, otherwise report it to the custom integration author.
The text was updated successfully, but these errors were encountered: