Incorrect energy calculation when power provided in separate upload

Problems
#1

Hi,

Searched forums but didn’t see anything similar – might be useful for someone…

For the Add Status service, just worked out that if you provide energy and power figures in separate uploads then the last upload completely overwrites the previous.

I had wrongly assumed that if I, for instance, upload energy figures and then shortly thereafter upload power figures for a single timeslot – that PVOutput would then sensibly consolidate the two. Instead, it appears that PVOutout just overwrites with the last output.

Fair enough, just a trap for the unwary…

#2

so does PVOutput create its own energy figure if you only upload a power figure?

#3

Yes it does - which is, of course, highly inaccurate (and deceptive if you don’t look closely & realise that’s what’s going on).

#4

It does combine the separate uploads with the same timestamp. Please provide samples of both requests.

#5

Hi,

If you have a look at today’s stats for system ID: 61602 you’ll see the in the morning (say, 10 o’clock) that it’s very different (fractional energy numbers) from the afternoon (say, 4 pm) where energy is in multiples of 0.100 kWh.

The only thing that changed is that in the morning I was uploading energy and power with different requests (though same timestamp), whilst in the afternoon I consolidated those into a single request (exactly the same data source for both versions – just used two requests in one version, and one request in the other).

[EDIT – found the log in an old scrollback buffer! :stuck_out_tongue:]

So… before (bad):

Tue Oct 09 2018 14:20:00 GMT+1100 (AEDT) Sending [{"d":"20181009","t":"14:20","v1":489800,"v3":149900,"c1":1}] for House to pvoutput.org
Tue Oct 09 2018 14:20:00 GMT+1100 (AEDT) Sending [{"d":"20181009","t":"14:20","v2":6723,"v4":1266,"v5":22.5,"v6":242.65,"v7":54.4,"v8":315.7}] for House to pvoutput
Tue Oct 09 2018 14:25:00 GMT+1100 (AEDT) Sending [{"d":"20181009","t":"14:25","v1":490500,"v3":150000,"c1":1}] for House to pvoutput.org
Tue Oct 09 2018 14:25:00 GMT+1100 (AEDT) Sending [{"d":"20181009","t":"14:25","v2":8868,"v4":1296,"v5":23.062,"v6":244.25,"v7":53.7,"v8":314}] for House to pvoutput
Tue Oct 09 2018 14:30:00 GMT+1100 (AEDT) Sending [{"d":"20181009","t":"14:30","v1":491200,"v3":150100,"c1":1}] for House to pvoutput.org
Tue Oct 09 2018 14:30:00 GMT+1100 (AEDT) Sending [{"d":"20181009","t":"14:30","v2":8501,"v4":1423,"v5":22.937,"v6":244.22,"v7":52.9,"v8":312.3}] for House to pvoutput
Tue Oct 09 2018 14:35:00 GMT+1100 (AEDT) Sending [{"d":"20181009","t":"14:35","v1":491700,"v3":150200,"c1":1}] for House to pvoutput.org
Tue Oct 09 2018 14:35:00 GMT+1100 (AEDT) Sending [{"d":"20181009","t":"14:35","v2":5408,"v4":1402,"v5":22.687,"v6":243.09,"v7":52.1,"v8":310.7}] for House to pvoutput
Tue Oct 09 2018 14:40:00 GMT+1100 (AEDT) Sending [{"d":"20181009","t":"14:40","v1":491900,"v3":150300,"c1":1}] for House to pvoutput.org
Tue Oct 09 2018 14:40:00 GMT+1100 (AEDT) Sending [{"d":"20181009","t":"14:40","v2":3296,"v4":1381,"v5":22.687,"v6":239.86,"v7":51.3,"v8":309.2}] for House to pvoutput
Tue Oct 09 2018 14:45:00 GMT+1100 (AEDT) Sending [{"d":"20181009","t":"14:45","v1":492200,"v3":150400,"c1":1}] for House to pvoutput.org
Tue Oct 09 2018 14:45:00 GMT+1100 (AEDT) Sending [{"d":"20181009","t":"14:45","v2":3503,"v4":1388,"v5":22.687,"v6":239.67,"v7":50.5,"v8":307.7}] for House to pvoutput
Tue Oct 09 2018 14:50:00 GMT+1100 (AEDT) Sending [{"d":"20181009","t":"14:50","v1":492500,"v3":150500,"c1":1}] for House to pvoutput.org
Tue Oct 09 2018 14:50:00 GMT+1100 (AEDT) Sending [{"d":"20181009","t":"14:50","v2":3333,"v4":1370,"v5":22.562,"v6":240.03,"v7":49.7,"v8":306.2}] for House to pvoutput

After (good):

Tue Oct 09 2018 16:15:00 GMT+1100 (AEDT) Sending [{"d":"20181009","t":"16:15","v1":498200,"v2":3657,"v3":150800,"v4":83,"v5":22.25,"v6":242.43,"v7":33.9,"v8":287.1,"c1":1}] for House to pvoutput.org
Tue Oct 09 2018 16:20:00 GMT+1100 (AEDT) Sending [{"d":"20181009","t":"16:20","v1":498500,"v2":3418,"v3":150900,"v4":120,"v5":22.375,"v6":241.86,"v7":32.9,"v8":286.2,"c1":1}] for House to pvoutput.org
Tue Oct 09 2018 16:25:00 GMT+1100 (AEDT) Sending [{"d":"20181009","t":"16:25","v1":498800,"v2":3220,"v3":150900,"v4":184,"v5":22.312,"v6":241.92,"v7":31.9,"v8":285.4,"c1":1}] for House to pvoutput.org
Tue Oct 09 2018 16:30:00 GMT+1100 (AEDT) Sending [{"d":"20181009","t":"16:30","v1":499000,"v2":3178,"v3":150900,"v4":182,"v5":22.25,"v6":241.78,"v7":30.9,"v8":284.5,"c1":1}] for House to pvoutput.org
Tue Oct 09 2018 16:35:00 GMT+1100 (AEDT) Sending [{"d":"20181009","t":"16:35","v1":499300,"v2":2735,"v3":150900,"v4":182,"v5":22.062,"v6":240.33,"v7":29.9,"v8":283.7,"c1":1}] for House to pvoutput.org
Tue Oct 09 2018 16:40:00 GMT+1100 (AEDT) Sending [{"d":"20181009","t":"16:40","v1":499500,"v2":2665,"v3":150900,"v4":121,"v5":21.812,"v6":240.05,"v7":28.9,"v8":282.8,"c1":1}] for House to pvoutput.org
Tue Oct 09 2018 16:45:00 GMT+1100 (AEDT) Sending [{"d":"20181009","t":"16:45","v1":499700,"v2":2767,"v3":150900,"v4":80,"v5":22.062,"v6":240.44,"v7":27.8,"v8":282,"c1":1}] for House to pvoutput.org
Tue Oct 09 2018 16:50:00 GMT+1100 (AEDT) Sending [{"d":"20181009","t":"16:50","v1":499900,"v2":2627,"v3":150900,"v4":78,"v5":21.937,"v6":240.21,"v7":26.8,"v8":281.2,"c1":1}] for House to pvoutput.org
Tue Oct 09 2018 16:55:01 GMT+1100 (AEDT) Sending [{"d":"20181009","t":"16:55","v1":500200,"v2":2744,"v3":151000,"v4":79,"v5":21.687,"v6":238.95,"v7":25.8,"v8":280.4,"c1":1}] for House to pvoutput.org

Hope that helps!!

#6

Thanks for the examples, v2/v4 and v1/v3 can be combined, but not v1/v2 and v3/v4 pairs.

There will need to be an enhancement to explicitly disable calculation, of power to energy and energy to power, if one is missing.

This would be done either by system setting or a new API parameter.