Incorrect Tesla Charge Energy Added State Class
mstarks01 opened this issue · 4 comments
The problem
The sensor._name_.charge_energy_added entity has a state class: total_increasing attribute, but the sensor reading drops to zero between charges for my Tesla Model 3. A more appropriate state_class might be measurement.
What version of Home Assistant Core has the issue?
core-2024.10.2
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Tesla Fleet
Link to integration documentation on our website
https://www.home-assistant.io/integrations/tesla_fleet
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
Hey there @Bre77, mind taking a look at this issue as it has been labeled with an integration (tesla_fleet) you are listed as a code owner for? Thanks!
Code owner commands
Code owners of tesla_fleet can trigger bot actions by commenting:
@home-assistant closeCloses the issue.@home-assistant rename Awesome new titleRenames the issue.@home-assistant reopenReopen the issue.@home-assistant unassign tesla_fleetRemoves the current integration label and assignees on the issue, add the integration domain after the command.@home-assistant add-label needs-more-informationAdd a label (needs-more-information, problem in dependency, problem in custom component) to the issue.@home-assistant remove-label needs-more-informationRemove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.
(message by CodeOwnersMention)
tesla_fleet documentation
tesla_fleet source
(message by IssueLinks)
Dropping to zero resets a total_increasing allowing you to calculate how much power you have used in total across multiple sessions using statistics.
Unfortunately sometimes this sensor goes backwards when it shouldn't, did you get some sort of error?
The problem I have experienced is negative values in the energy dashboard under the individual devices section. I have worked around it by creating a utility meter from this entity, but thought a bug report was appropriate given the state class and behavior of the entity.