Energy Dashboard - How can I get the spikes out

[sender]

Many hits on the forum about spikes in the energy dashboard. There must be an option to troubleshoot the data sources used in the energy dashboard and to get these spike out

[sender]

tom_i, thanks for replying

[makai]

I think that you can remove them by editing the statistics data of the entity. Go to Developer tools > Statistics and click on the “Ajust Sum” button on the right

Then you can remove spikes

[sender]

Thanks, thats for removing them retrospectively. I would like them to not come in every day…

[petro]

Fix your sensor… They only come every day if your sensor is outputting invalid data when it shouldn’t.

[tom_l]

Yep. We’ve been over this. The integration or inverter firmware needs fixing.

Energy dashboard not populating

This is not normal behaviour for an inverter. The integration needs to be fixed or the inverter settings need to be changed. e.g. SMA inverter: [Untitled]

[sender]

I have been over this with the esphome boys… nothing to fix anymore overthere.

Many people have this issue (not with my intergration/sensor from esphome but others).

[sender]

Tom, I really could use some help with this one. O every topic I respond to this I am sent away (by you) that something must be wrong or needs to be fixed.

But I really don’t know what could be wrong or can be fixed. From my perspective everything is set ok.

Can you help me out please?

This is a spikey topic:

Energy Integration Spike

I just set up the new Energy Dashboard using IotAWatt an the Integration sensor. I noticed a huge spike yesterday that appears false, so I’m trying to figure out what caused and how to prevent. Energy Dashboard showing 40.38kwh usage at 7am (from sensor.import_wh_calculated) [energy-usage] When I look at the history for sensor.import_wh_calculated around the same time, I see a 3kwh drop, then it flatlines (which is expected when solar production kicks in) [image] Where does this usage spi…

[Mattie (Mattias)]

Has ANYONE actually countered this problem in a swift manner? I’m also having this issue with a range of different components, It can be shelly, zwave or modbus. Its not the component thats faulty, its how they send data to hassio or something else, mabye how its stored in the db…

I could also promote my old thread about letting hassio know when a value is out of the ordinary here: Severity attribute for entities

something needs to change, many of us need to fix the statistics for many sensors every month, and if we dont the energy stats page wont be worth much.

as it is now mabye a bad work around could be to create bandpassfilters for these sensors instead… but I then loose my history due to the new entity and it wouldnt be a good enough fix anyway.