PVOutput getstatus.jsp regularly shows NaN for Voltage but intraday.jsp not

Problems Fixed
#1

I see regularly get NaN returned for Voltage using for example:
curl.exe -H “X-Pvoutput-Apikey: myapikey” -H “X-Pvoutput-SystemId: 11351” “pvoutput/r2/getstatus.jsp?d=20220825&h=1&limit=288”

Example part of the result, splitted at ;

20220825,16:45,16241,3.314,3336,3336,0.681,NaN,NaN,35.6,239.3;
20220825,16:40,15963,3.258,3336,3336,0.681,NaN,NaN,35.6,239.7;
20220825,16:35,15685,3.201,3324,3324,0.678,NaN,NaN,35.0,NaN;
20220825,16:30,15408,3.144,3324,3324,0.678,NaN,NaN,35.0,239.6;

But if I look at the web interface for my sid=11351 at 25/08/22

25/08/22 16:35 15.685kWh 3.201kWh/kW 3,324W 3,324W 0.678kW/kW 35.0C 239.6V

How is it possible the web interface shows a plausible Voltage number, but getstatus returns NaN for Voltage?

#2

I think the root cause is SBFSpot, which sometimes sends data of my SMA inverter to PVOutput with the Voltage not filled in. Today 20220826 I saw this already a few times in the SBFSpot logging.

[09:42:34.874] INFO: Uploading datapoint: 20220826,09:40,44749664,384,36.8,234.38 => OK (200)
[09:48:34.782] INFO: Uploading datapoint: 20220826,09:45,44749699,420 => OK (200)
[09:53:34.893] INFO: Uploading datapoint: 20220826,09:50,44749739,480,36.9,234.06 => OK (200)
[09:58:34.783] INFO: Uploading datapoint: 20220826,09:55,44749776,444,37,234.3 => OK (200)
[10:04:38.194] INFO: Uploading datapoint: 20220826,10:00,44749798,264,37.1,233.43 => OK (200)
[10:09:35.199] INFO: Uploading datapoint: 20220826,10:05,44749814,192,37.2,231.35 => OK (200)
[10:15:37.990] INFO: Uploading 2 datapoints, starting with 20220826,10:10,44749827,156,37.3,232.01 => OK (200)
[10:20:34.257] INFO: Uploading datapoint: 20220826,10:20,44749858,204,37.4,232.18 => OK (200)
[10:26:38.386] INFO: Uploading datapoint: 20220826,10:25,44749881,276,37.4,232.5 => OK (200)
[10:31:34.213] INFO: Uploading datapoint: 20220826,10:30,44749907,312,37.4,232 => OK (200)
[10:37:38.767] INFO: Uploading datapoint: 20220826,10:35,44749942,420,37.5,232.37 => OK (200)
[10:42:34.662] INFO: Uploading datapoint: 20220826,10:40,44749985,516,37.6,232.4 => OK (200)
[10:48:37.983] INFO: Uploading datapoint: 20220826,10:45,44750030,540 => OK (200)
[10:53:34.174] INFO: Uploading datapoint: 20220826,10:50,44750071,492,37.7,232.45 => OK (200)
[10:59:33.795] INFO: Uploading datapoint: 20220826,10:55,44750107,432,37.8,231.92 => OK (200)
[11:04:35.974] INFO: Uploading datapoint: 20220826,11:00,44750141,408,37.9,231.49 => OK (200)

If I look at pvoutput intraday.jsp sid=11351 for 2020826 it does show the Voltage at 09:45 and 10:45.

If I get the data for 20220826 with the getstatus.jsp command with my API key and X-Pvoutput-SystemId: 11351

I get the NaN for the specified times:

20220826,09:45,525,420,-1,-1,20.6,NaN
20220826,10:45,856,540,-1,-1,20.6,NaN

Looks like the web interface shows the voltage of the entry before and the getstatus.jsp command gives back the NaN. Why is there a difference? Should getstatus.jsp behave the same as what is shown on the web interface?

#3

Continued here

#4

The web interface fills in the data gaps for voltage and temperature, the API sends back the raw data.

#5

Thanks, that explains it. I solved it at the root cause, sending the data with SBFSpot.