Closed onelius closed 8 months ago
Since this is most likely a bug in the equalizer and not in the HA component (you probably see the same incorrect value in the easee app, right?) you should contact Easee about this.
Found it on the Easee app and that is right, it's the wrong value there too.
I have sent a bug report to Easee now.
Any update on this? My dad's meter seems to be very buggy and reporting all over the place...
Please report your problem to Easee, we are not able to do anything about this at our end.
Contact Easee support, they made a firmvare update for me and now everything works fine :)
I have a similar problem, decimal separator jump one step right or left from the correct position, giving a value 10 times too big or a 10th of the correct value.. In contact with Easee support they say everything looks fine at their side. And I have a hard time to believe that the integration to Easee should report a different value than the in the cloud registered. The problem is the same for both imported and exported energy exactly at the same reporting timestamps. Any thoughts?
Are you saying that is behaves randomly such that the decimal point moves back and forth? Does the Easee app show the same values as the HA integration?
The only conversion we do is to change between kWh and Wh depending on the settings you selected in the integration. A division or multiplication by 10 should not be possible.
If you enable debug logging, you can see what the values that are transferred from the easee cloud are. Add this to your configuration.yaml:
logger:
default: info
logs:
pyeasee: debug
custom_components.easee: debug
Then you should see the corresponding data in the log file by searching for lines that look like this:
Callback xxxxx 45 state_cumulativeActivePowerImport 73262.7265625
Callback xxxxx 46 state_cumulativeActivePowerExport 11993.2900390625
This is the raw data that is sent by the cloud. If it is wrong already here, there is not much we can do...
Thank you for the tip on how to debug log the integration!
As @onelius earlier wrote I could today caught Easee cloud having the same wrong decimal positions as I experience it in the integration. It was actually for all cumulative values and not only import and export as I first thought. Easee support claims that this can be caused by drop out of connection between the Equalizer and easee.cloud, but I have a hard time believing that a real time reading could move the value by 10 times up and down depending on a connection dropout. I have reported it again, awaiting response coming week.
Update: If some one else ends up here for help with the same issue. Easee support has finally recognized that there is a problem with the Equalizer integration to "Some Swedish Aidon meters". They wrote: "Some Swedish Aidon meters output the energy value at 10x of what they should. The Equalizer code has some compensation for it. But it appears to not be perfect. I have escalated the issue, and we will look into it." I am waiting for their correction.
Update: I have had a FW update from 117 to 119 on the Equalizer, but still two month later Easee hasn't been able to correct the erroneous meter reading by Easee Equalizer from Swedish Aidon meters.
@fondberg First: Is there a way to correct historic data for the integration and that way being able to look back on correct data? I have DB access and have been able to identified wrong stored reported data but it will not affect my energy-usage-graph. Is that stored in a different table?
Secondly, is it possible to change the code locally in my HA, to divide the measurement by 10 if the new reported value is greater that 10 times the previous reported value?
Sorry for very late reply, but you can use a template sensor to divide the value by 10 if you need to. Closing this now, since it is not a bug in this component.
The problem
The Easee equalizer import energy shows the value with decimal in the wrong place.
Example: shows 521961,0 kwh, but the correct value is 52196,1 kwh
Version of Easee integration having the issue?
v0.9.45
Version of Home Assistant Core having the issue?
2022.9.7
Anything in the logs that might be useful for us?
No response
Additional information
No response