I am confused with kWh value in HA...

[Jaxel]

I just connected my GEM to Home Assistant... But I'm confused about the values showing up in HA.

So far I've only connected one CT. You can see the values in the image above...

However, in HA, it shows the following:

Why is energy usage negative? Watts and Amps are accurate, but kWh are completely wrong.

[jkeljo]

GEM channels can measure energy going in both directions. The GEM UI only shows one of those directions, but the HA integration sees both and computes the difference. It is possible that setting the net metering flag for that channel would make the GEM UI do the same calculation, I'm not sure. However, since it's a new setup I'd recommend just clearing the totals in the GEM so it can start from zero.

[bourba85]

I am having a similar issue, but after several months of use of two GEM monitors and this integration in HA. Specifically, I had energy sensors that worked just fine until a couple weeks ago, when the GEM stopped sending packets to HA (due to a network issue). I was traveling and could not fix this until yesterday. Now, while my Watt-seconds readings on the GEM WebGUI read correct, the values on the corresponding energy sensors in HA are all large negative numbers. I tried to look into the Python files but could not figure out where/how the conversion from the native GEM Watt-seconds counters to the kWh HA sensors is performed (if at all).
Thanks in advance!

[yeti08]

I get big negative kwh spikes when the GEM is disconnected from HA for a period of time (network down). Around the time the network goes down, there is the big negative spike. When the network is reconnected, HA appears to catch up and log the increase in kwh over the period of time the network was down, but the latest kwh values are all still hugely negative (hundreds of megawatts). This has happened to me each time my network was down for a period of hours. The kwh values reported on the GEM itself are positive and reasonable if I log in to the web portal. I browsed the code but didn't see anything obvious

[BenK22]

If you have a V2 GEM (blue board) the GEM uses a super capacitor to keep values stored in memory persistent (including the wattseconds counters). If the GEM loses power for a long amount of time or if the hardware setting is configured incorrectly (this will cause excessive drain on the cap) this will cause the wattseconds counters to go to random values due to memory corruption.

The super capacitor should last at least 2-3 days unless the hardware option is set incorrectly.

The header above the onboard Ethernet jack also needs to be in place. That header keeps the super capacitor in-line with the circuit.

[yeti08]

If you have a V2 GEM (blue board) the GEM uses a super capacitor to keep values stored in memory persistent (including the wattseconds counters). If the GEM loses power for a long amount of time or if the hardware setting is configured incorrectly (this will cause excessive drain on the cap) this will cause the wattseconds counters to go to random values due to memory corruption.

The super capacitor should last at least 2-3 days unless the hardware option is set incorrectly.

The header above the onboard Ethernet jack also needs to be in place. That header keeps the super capacitor in-line with the circuit.

The GEM itself continues to record accurate values. If I log into its interface, its total kWh values are what they should be over the time range of the negative energy spikes. So, it seems something in the homeassistant integration isn't working properly since the GEM tracks along accurately, but homeassistant ends up with big negative spikes for my GEM sensors.

[BenK22]

If you have a V2 GEM (blue board) the GEM uses a super capacitor to keep values stored in memory persistent (including the wattseconds counters). If the GEM loses power for a long amount of time or if the hardware setting is configured incorrectly (this will cause excessive drain on the cap) this will cause the wattseconds counters to go to random values due to memory corruption.
The super capacitor should last at least 2-3 days unless the hardware option is set incorrectly.
The header above the onboard Ethernet jack also needs to be in place. That header keeps the super capacitor in-line with the circuit.

The GEM itself continues to record accurate values. If I log into its interface, its total kWh values are what they should be over the time range of the negative energy spikes. So, it seems something in the homeassistant integration isn't working properly since the GEM tracks along accurately, but homeassistant ends up with big negative spikes for my GEM sensors.

I think this may be happening due to residual data in the polarized wattseconds counters. Let me talk to Paul about creating a COM F/W with a command that will zero all polarized counters.

[BenK22]

Posted COM 5.48 in our software section which adds the command ^^^SYSRSTB. This will reset only the polarized counters.

One note, the ESP-WiFi module can only load COM F/W in Access Point mode currently (it's also very slow). Looking into a fix for that.