I wrote a new DzVents based event so you do not need the extra Python script and (http)errors are handled better. The inverter needs current firmware version (>6.0?) so you can use the API to get JSON data directly. Just fill in the inverter IP and the device name. return { on = { timer = { 'every 5 ...

Deleting data point (shift left click) doesn't work in week graph, but it does work in month graph.
That way I was able to delete the initial value.
The second spike was my bad... LUA script hung up Domoticz around the time the daily total should be calculated.
Thanks for the help Gizmocuz!

Is it possible there is a bug in at MainWorker::decode_Energy (starting at line 8851 in mainworker.cpp)? I'm not very good at reading C++ code
The problem doesn't seem to exist with another virtual device (also solar inverter).

I am monitoring the total revenue of a Piko solar inverter. Type is virtual device Electric (Instant+Counter). Both counter are filled with correct values every 5 minutes. The data in the tables look correct. Two issues: 1. The initial value (here 6936 kWh) is always the initial counter of lifetime ...

If someone else want to read the Solivia Gateway counters of inverters you can use this. Edit: do not use os.exit() :? .. It kills Domoticz. Use return instead. Changed code below. -- Get Solivia inverter counters -- Change weburl and inverter device name return { on = { timer = { "every 5 minutes ...

I rewrote the script using the new dzVents format so you can change the interval (here it is 5 minutes). It does not use a temporary file anymore and the counters are fetched even if the number of digits change ...