Open sarahmva opened 1 year ago
So it looks like the instantaneous power is showing up correctly, but the aggregate energy is half what you expect? That's surprising, because the way this stuff works is the GEM sends the energy total in every packet and the integration computes power from the difference in energy between consecutive packets.
I played around with turning on 240V mode on one of my GEM channels, and verified that the power number showing up in HA doubled.
How did you create those "Monthly" and "Last Session" entities? That's not something this integration does on its own.
For completeness, what are your GEM firmware versions?
Thanks for checking. COM firmware ver: 5.39 ENG firmware ver: 1.49
I did some more testing yesterday and restarted everything (HA, GEM). Once I had done this, it seemed to be more accurate. I wonder if the issue was that I had not restarted things after making the changes in GEM.
I will have to monitor again next time I charge the car. I also need to replace the CT, it seems to pick up some phantom power.
Regarding the Monthly and Last Session: Those are Utility Monitor Helpers. I reset the "Last Session" anytime power consumption on that channel goes above 100W.
I primarily use the instantaneous power to control charge current so I can keep the overall house consumption under control.
The latest version of this integration (2023.9.03) supports downloading diagnostic information and debug logs, which I hope will help me diagnose this issue more quickly. To use it, do the following:
Thanks!
Home Assistant version: 2023.7.3
HACS version: 1.32.1
hacs-greeneye-monitor
version: 2023.5.30Configuration
Describe the bug
I have one channel monitoring a symetric 240V load (Car Charger). GEM Is configured accordingly:
The Car Charger is pulling 20 Amps, about 4,700 Watts.
After 1:15 minutes, the energy measured is half of what I expected:
I compared with the app for the charger which says 5.6 kwh.
Not sure if this is a GEM issue or a issue of the monitor component.
home-assistant_greeneye_monitor_2023-08-03T04-10-53.129Z.log