Skip to content
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

Spikes in total energy consumption #440

Open
erikfluff opened this issue Jul 15, 2024 · 1 comment
Open

Spikes in total energy consumption #440

erikfluff opened this issue Jul 15, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@erikfluff
Copy link

erikfluff commented Jul 15, 2024

The problem

I have an equalizer connected to an Aidon meter. Almost every month i get one or two crazy spikes in my total consumption sensor, it seems like it moves the decimal one step for one or two hours, and then move back, so the total consumtion is 35 548,8 kwh at one hour, and then 355 549,2 kwh the next hour, and then back to 35 550,3 kwh, making the energy dashboard crazy. I don't know if it is my aidon meter or the equalizer that is acting up. Maybe its possible to create a filter for theese kinds of events?

spik1
spik2

Version of Easee integration having the issue?

0.9.59

Version of Home Assistant Core having the issue?

2024.6.3

Anything in the logs that might be useful for us?

No response

Additional information

No response

@erikfluff erikfluff added the bug Something isn't working label Jul 15, 2024
@olalid
Copy link
Collaborator

olalid commented Jul 15, 2024

If you turn on logging (see readme) and look for the keyword state_cumulativeActivePowerImport you can see the value that Easee reports back to the integrateion. This value is always in kWh.
If you can see the incorrect values to match what you see in HA UI then the problem really lies on Easee or meter side and I suggest you also report it to Easee if so.

I can see how it is annoying but I am kind of reluctant to make workarounds for issues that are in fact caused by bugs in other systems. Maybe you can use an outlier filter to fix this for your specific case?
https://www.home-assistant.io/integrations/filter/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants