GivEnergy/GivTCP integration giving weird results

[jaunty dock]

I'm trying to get the default Energy dashboard setup to track my energy usage, generation, and battery information. Problem is, the values don't seem do add up, nor do what I'd expect.

For instance the "Net consumed from grid" section suggests my grid draw today totals to 5.2kWh, when in reality it's 35.9kWh. It also seems to think that my solar is generating 3.9kWh (it's nearly 6pm, and pitch black outside).

I assume I'm missing something around what values I'm supposed to be using for each property. Does anyone with experience of HA and GivTCP have any advice?

The library I'm using is this one: https://github.com/GivEnergy/giv_tcp

I guess if people don't know the GivTCP stuff, the next question becomes does anyone know whether the Grid Consumption, Return to grid, Solar Production, and Battery Systems fields should be looking at? A live feed of the "current" values? A total value for the day so far?

Note that I have just updated the Grid consumption field specifically to "Day Energy kWh", and the value on the needle did not change. This is what makes me thinks it wants "live" data, because I kinda get the feeling that it's expecting live data to build a database over the course of the day or something.

[blazing cargo]

That 3.9 kWh is what it generated today. 'net' consumption is just total grid consumption - total grid export

[jaunty dock]

It's also not, sorry, I should've provided more of this information upfront

I've a feeling I just didn't understand the assignment when I set the dashboard up

[blazing cargo]

can you share a screenshot of your energy dashboard?

[blazing cargo]

also keep in mind that kWh = energy, kW = power. When you see kWh it's almost always a total of that day, month, week etc

[jaunty dock]

Yeah I know, it's just oddly not very specific in the dashboard setup

this is the config i've got atm, i've recently changed the grid consumption field

[blazing cargo]

that spike to -12 kWh at the start of the day is causing the problem. Not sure why that happened

do you have more days of data?

[jaunty dock]

Yeah, that same dip is there every day from what I can tell

It varies each day though

So like 21st January it was about 2.9, 22nd 5.8, 23rd 2.6

I'm guessing this is related to my usage of the "day" values

I've given it data about the energy consumption for the day

So on 23rd where I'm dropping 2.6kWh at midnight, on 22nd I probably generated roughly that amount

That would sort of add up... On 22nd I drop 5.8kWh, and I generated about 1kW for 5 hours and then a couple of hours a bit below, so that checks out

[blazing cargo]

that's an issue with that integration you're using. I doubt they will fix it though, hasn't been updated in over 2 years

you can wrap your solar kWh sensor in a utility meter helper, and then add that one to the dashboard. It will fix the reset issue

[jaunty dock]

I maintain it's a config issue tbh, the API also hasn't changed in decades (the manufacturer is extremely slow and incompetent)

[blazing cargo]

I dont think so

if you have a lifetime total kWh sensor for your solar that could also help

instead of the daily one

[jaunty dock]

I do have lifetime, I think that's actually it

That's a lot closer to what I'd expect to see

Generation 15.5kWh, import 36.98kWh, export 6.2kWh... this all adds up

[blazing cargo]

normally that shouldnt matter if the resets are properly implemented in the integration

[jaunty dock]

In case anyone finds themselves searching and stumbling upon this thread with the exact same question:

• Grid Consumption should be set to <your integration name> Import Energy Total kWh
• Return to grid should be set to <your integration name> Export Energy Total kWh
• Solar production should be set to <your integration name> PV Energy Total kWh
• Battery storage should be set to the <your integration name> Battery Charge/Discharge Total kWh

[blazing cargo]

just a few notes. These names are not identical across different integrations, and you can change them yourself, so in general this will not work

also if the integration has kWh sensor reset properly implemented daily totals will also work just fine

lifetime totals do tend to be more stable, so if you have those use them