Unauthorized 401: Invalid System ID by using cURL on Synology or .PHP script

Problems
#1

Before today i could send data to PvOut by using cURL from my Synology with this script

curl -d “d=20230725” -d “t=21:15” -d “v1=65190” -d “v2=0” -d “v3=124” -d “v4=505” -d “v5=16.2” -d “v6=236” -d “v7=30.194” -d “v8=8.782” -d “c1=1” -H “X-Pvoutput-Apikey: MyApiKey” -H “X-Pvoutput-SystemId: MySystemId” https://pvoutput.org/service/r2/addstatus.jsp

No i’ll get always a ‘Invalid SystemId’, while nothing changed…

I’m trying to get it running by using this script within .PHP

<?php $url = "https://pvoutput.org/service/r2/addstatus.jsp"; $curl = curl_init(); curl_setopt($curl, CURLOPT_URL, $url); curl_setopt($curl, CURLOPT_POST, true); curl_setopt($curl, CURLOPT_RETURNTRANSFER, true); $headers = array( "Accept: application/json", "Content-Type: application/json", ); curl_setopt($curl, CURLOPT_HTTPHEADER, $headers); $data = '-d "d=20230726" -d "t=23:10" -d "v1=36459322" -d "v2=0" -d "v3=140" -d "v4=770" -d "v5=14.9" -d "v6=236.3" -d "c1=1" -H "X-Pvoutput-Apikey: MyApiKey" -H "X-Pvoutput-SystemId: MySystemId"'; curl_setopt($curl, CURLOPT_POSTFIELDS, $data); $resp = curl_exec($curl); curl_close($curl); echo $resp; ?>

Response is also
Unauthorized 401: Invalid System ID

Do have anyone a suggestion ?

Thanks a lot
Rob

#2

Hi @TeamKleijn, I may be barking up the wrong tree but your ‘curl’ string includes the terms v7 and v8 which are Extended Data terms. The Extended Data terms are only available to Donors.

Did you recently modify your ‘curl’ string to push v7 and v8 or is it possible that your Donor status recently expired?

https://www.pvoutput.org/help/extended_data.html

Grannos.

#3

Hello @grannos, I think my donor status is expired. I’ve changed my software, i only send live time counters for Generation and Production, at the moment the Both Power variable’s i don’t send.
To day i’ve seen a nice working log for my system.

So it worked, i’m wondering my solution has nothing with ‘Invalid Key’ so if you’re right my Donorship is expired, and it might be not allowed to send V7 and V8, then i suggest another errormessage

The API call isn’t changed technical…

#4

The request will still accept the standard parameters v1-v6 and v7-v12 will be ignored.

The “Invalid API Key” error returns when the key is missing or empty.