Energy Dashboard Electricity Out of Sync

I’ve had this problem for several months and finally got round to trying to resolve it again yesterday.

My electricity costs shown in the energy dashboard do not align with my cad meter costs. The meter costs can be seen in ha and they are correct, see attached image showing electricity cost today is £0.99 but ha energy day is saying £-3.46. It’s like it hasn’t reset. Compare it to the gas costs that are correctly synced. The import consumption and price values are all correct too which makes it more confusing.

I don’t mind wiping all the data if needed to reset it all but I’m not sure how to do that.

This is running the very latest HA versions on a “ha yellow” device.

Does anyone have an idea what’s going on?



Please share picture of your energy dashboard settings for these entity. Are you using a cost sensor from your device, or are you using a fixed cost?

The values all come from the integration. You can see the integration details and raw values and also the energy configuration in the following screen shots.



emphasised text

Thank you, and please also share the entity attributes of those cost entities (from developer-tools/states). I suspect they are not handling reset correctly.

Here you go and now I’m thinking is it because of the _2 suffix?


The _2 is ok. What I’m seeing is entities with a total state class that don’t have a last_reset attribute. So every day when those values go to 0, that will be treated as a negative cost. That is incorrect.

Those cost entities should either have been class total_increasing, or they should be total but have a last_reset attribute. The former is preferred.

You can report this as a bug to the author of the integration you are using.

I’ll log it as a bug on that integration.

Is there anyway to correct it myself? At least temporarily?

Many thanks for your help

Maybe with customize: Home Assistant Core Integration - Home Assistant

Suggest try overriding the state_class to total_increasing for these cost entities.

1 Like

This appears to have now been fixed with the latest release