I figured that this subject had probably been previously discussed. The 0:00 push would need to be attributed to the previous day.
A remedy would be to make 00:00 that LAST value of a given date which would of course be very confusing. I also assume then that there aren’t too many PVO users living in very high latitudes… 24 hours of sunlight and low ambient temperatures for panel efficiency - at least for a few days / year.
In PVO (via Fronius push) and this php code the 0:00 interval is always null. That’s OK if it really is yesterday’s data, but why then is there no 24:00 interval?
Put another way, the Fronius push to PVO and in this php code only provide data for 287 intervals per day.
In Solarweb there are data for 288 intervals per day.
There are 288 x 5-min intervals per day.
Solarweb and PVO daily reports both show time intervals from ranging from 0:00 to 23:55 and NOT from 0:05 to 24:00 (or 0:00).
Hence why to me it seems the time stamps mark the start of the interval, not the end.
I don’t see why it would not make sense to consider them to mark the start of the interval. It’s just an arbitrary definition of what to name an interval.
Why is that confusing? “00:00” is simply equivalent to “24:00” of the previous day.
In June 2019 I compared my PVO graphs (created using my own pusher logic) to Solarweb and they were essentially exactly the same except Solarweb was setting the day’s total consumption energy to the 23:55 value, not the next 00:00 value. The last 5 mins of consumption energy was being “leaked away” which was the same flaw as PVOutput. I sent many emails to Fronius Australia and Austria and eventually performed demonstrations of how it was clearly wrong, e.g. I turned an 2400W electric heater on at 23:55 and off at 23:59 each day and showed them the bump in consumption was not seen on their graphs. They finally agreed with me and fixed their graphs to calculate this correctly in Nov 2019.
The Fronius push message sent with timestamp 00:00 contains the last day generation energy value for the entire day. (I.e. the final total, i.e. the maximum value). After the inverter sends that then it immediately resets it’s internal day accumulator.
BTW, this whole issue of dealing with day rollover is a bit of a pain and for generation energy and power it is essentially a moot point given there is no generation over midnight. However, it seems to me that Fronius realized this themselves when they added the smart meter (i.e. consumption monitoring) to the API because I note they did not even bother with a day consumption energy total, they only have a lifetime consumption total and software must derive day totals itself if a day count is wanted. This is how generation should have been done also. There is actually a lifetime counter for generation in the API but it is useless because it updates at a much slower rate than DAY_ENERGY so can not be used. Believe me, I have spent a lot of time on all these issues to get my generation and consumption energy and power graphs displayed perfectly on PVOutput.
Except that they occur on completely different days.
I do agree though that it is highly likely that it was never considered how / when to perform a final update for a given day since most systems wouldn’t be generating when the calendar advances from one day to another.
No, “time 00:00 @ date” is mathematically exactly equivalent to “time 24:00 @ (date - 1)”.
Some languages/library/standards even accept either form. E.g. see https://en.wikipedia.org/wiki/ISO_8601#Times.
How do you get correct consumption data into PVO?
I created a free proxy service on the web which you point your Fronius inverter to instead of directly to PVOuput. It calculates everything correctly from the inverter and meter push data and stores that to PVOutput, fixing all the issues I know of. There is no need for the logdata push so you can delete it. Message me if you want to use it. Apart from myself, a couple of other users have been using it for ages very happily.
Hey, would appreciate some help. I’m getting the following errors when running the script before it spits out power and energy, but consumption equals energy. XXXXX is my meters serial.
Warning: Undefined array key “meter:xxxxx” in C:\Users\Vesta\Downloads\PHP 803\GetFroniusData.php on line 41
Warning: Trying to access array offset on value of type null in C:\Users\Vesta\Downloads\PHP 803\GetFroniusData.php on line 41
Warning: Trying to access array offset on value of type null in C:\Users\Vesta\Downloads\PHP 803\GetFroniusData.php on line 41
Warning: Trying to access array offset on value of type null in C:\Users\Vesta\Downloads\PHP 803\GetFroniusData.php on line 41
Warning: Trying to access array offset on value of type null in C:\Users\Vesta\Downloads\PHP 803\GetFroniusData.php on line 41
Warning: Undefined array key “meter:XXXXX” in C:\Users\Vesta\Downloads\PHP 803\GetFroniusData.php on line 42
Warning: Trying to access array offset on value of type null in C:\Users\Vesta\Downloads\PHP 803\GetFroniusData.php on line 42
Warning: Trying to access array offset on value of type null in C:\Users\Vesta\Downloads\PHP 803\GetFroniusData.php on line 42
Warning: Trying to access array offset on value of type null in C:\Users\Vesta\Downloads\PHP 803\GetFroniusData.php on line 42
Warning: Trying to access array offset on value of type null in C:\Users\Vesta\Downloads\PHP 803\GetFroniusData.php on line 42
23:50,44431.735,0,44431.735
Lines 41 and 42 are
$EnergyReal_WAC_Minus_Absolute = $arr[Body][Data][meter: . $meterSerial][Data][EnergyReal_WAC_Minus_Absolute][Values][$x];|
$EnergyReal_WAC_Plus_Absolute = $arr[Body][Data][meter: . $meterSerial][Data][EnergyReal_WAC_Plus_Absolute][Values][$x];|
Cheers
Hi @max-nz,
A couple of things to check first.
(i) Do you access your inverter my hostname or IP address? Line 4 of the script needs to be able to resolve to the inverter.
$dataManagerIP = “fronius”;
If you can ‘ping’ ‘fronius’ from your computer all is well otherwise replace "fronius’ with the IP address. e.g.
$dataManagerIP = “192.168.1.55”;
The IP address MUST be in quotes. Don’t accidentally delete the trailing semicolon ‘;’ or you will be in a world of hurt.
(ii) Have you altered lines 5 & 6 to set a “valid” country and “location”? Take a look at PHP: List of Supported Timezones - Manual to make sure that you have used values that are valid for PHP. Make sure that you do not accidentally delete or insert extra inverted commas around the values or accidentally delete on the trailing semicolons.
(iii) If you want to extract data from an earlier DATE you must specify it at line 14.
$date = “YYYY-MM-DD”;
(iv) If you want to extract data for TODAY you should set a time that is not in the future otherwise ignore $time as the entire 24 period will be extracted.
Let me know how things go.
I’m facing the same issue as @max-nz above.
It seems to be loading the meter ID ok as I see a number listed (which I’ll blank out below with xxx)
Warning: Undefined array key “meter:xxxxxxxx” in E:\PHP\FroniusData.php on line 41
Warning: Trying to access array offset on value of type null in E:\PHP\FroniusData.php on line 41
Warning: Trying to access array offset on value of type null in E:\PHP\FroniusData.php on line 41
Warning: Trying to access array offset on value of type null in E:\PHP\FroniusData.php on line 41
Warning: Trying to access array offset on value of type null in E:\PHP\FroniusData.php on line 41
Warning: Undefined array key “meter:xxxxxxxx” in E:\PHP\FroniusData.php on line 42
Warning: Trying to access array offset on value of type null in E:\PHP\FroniusData.php on line 42
Warning: Trying to access array offset on value of type null in E:\PHP\FroniusData.php on line 42
Warning: Trying to access array offset on value of type null in E:\PHP\FroniusData.php on line 42
Warning: Trying to access array offset on value of type null in E:\PHP\FroniusData.php on line 42
23:55,42566.143611111,0,42566.143611111
Then repeats for the next 5min increment but reports the same errors above each time then ends with what looks like the time and usage details we are after on the last line above before it repeats again…
I’m running Windows 11 and downloaded PHP version 8.1.2 - VS16 x64 Non Thread Safe (2022-Jan-19 10:43:46), I also installed the mentioned Visual C++ Redistributable for Visual Studio 2015-2019 Pack that did not help.
Any idea what might cause the above? I have made the following changes to the PHP file:
$dataManagerIP = “192.168.1.200”;
$country = “Australia”;
$capitalCity =“Brisbane”;
$date = “2022-02-11”;
$time = “23:59”; (tried commenting this out as well)
P.S. I also tried to use the “VS16 x64 Non Thread Safe (2022-Jan-19 10:43:46)” Version of PHP as well as the 32bit “VS16 x86 Non Thread Safe (2022-Jan-19 10:44:10)” but got the same errors with the script on these builds of PHP as well.
P.S. I’ve also noticed the Energy Consumed does not seem to bright for our system that I’ll need to look into next (I had the same issue with the main PVOutput push script by needing to add a /n switch at the end of the export URL to export "net’ usage I believe…
Hi @jonnoc
What output do you get if you put the following into a browser? Depending on your local DNS you may need to use the Fronius’ IP rather than ‘fronius’.
http://fronius/solar_api/v1/GetMeterRealtimeData.cgi?Scope=System
It should return a ‘screenful’ of data.
Grannos
I’m not able to use ‘fronius’ as it does not seem to be registered on my router as such but if I enter the IP address in the URL link you requested I get the following output:
{
“Body” : {
“Data” : {
“0” : {
“Current_AC_Phase_1” : 4.1790000000000003,
“Current_AC_Sum” : 4.1790000000000003,
“Details” : {
“Manufacturer” : “Fronius”,
“Model” : “Smart Meter 63A-1”,
“Serial” : “2xxxxxxx”
},
“Enable” : 1,
“EnergyReactive_VArAC_Phase_1_Consumed” : 12216970,
“EnergyReactive_VArAC_Phase_1_Produced” : 47856630,
“EnergyReactive_VArAC_Sum_Consumed” : 12216970,
“EnergyReactive_VArAC_Sum_Produced” : 47856630,
“EnergyReal_WAC_Minus_Absolute” : 12911235,
“EnergyReal_WAC_Phase_1_Consumed” : 5069201,
“EnergyReal_WAC_Phase_1_Produced” : 12911235,
“EnergyReal_WAC_Plus_Absolute” : 5069201,
“EnergyReal_WAC_Sum_Consumed” : 5069201,
“EnergyReal_WAC_Sum_Produced” : 12911235,
“Frequency_Phase_Average” : 50,
“Meter_Location_Current” : 0,
“PowerApparent_S_Phase_1” : 988.33000000000004,
“PowerApparent_S_Sum” : 988.33000000000004,
“PowerFactor_Phase_1” : 0.78000000000000003,
“PowerFactor_Sum” : 0.78000000000000003,
“PowerReactive_Q_Phase_1” : -504.64999999999998,
“PowerReactive_Q_Sum” : -504.64999999999998,
“PowerReal_P_Phase_1” : 780.28999999999996,
“PowerReal_P_Sum” : 780.28999999999996,
“TimeStamp” : 1644925657,
“Visible” : 1,
“Voltage_AC_Phase_1” : 236.5
}
}
},
“Head” : {
“RequestArguments” : {
“DeviceClass” : “Meter”,
“Scope” : “System”
},
“Status” : {
“Code” : 0,
“Reason” : “”,
“UserMessage” : “”
},
“Timestamp” : “2022-02-15T21:47:38+10:00”
}
}
If I do a ping -a 192.168.1.200 via cmd on my system I don’t get a hostname back but I can ping the unit fine. If I do an nslookup on the same IP address I get the following back: *** UnKnown can’t find 192.168.1.200: Non-existent domain
I also checked my Asus router that gives out IP addresses and it lists the device as “u-blox AG” but that does not allow me to ping that name
If I login to my inverter directly and goto “System information”
I see the following details:
Inverter
No Device type PMC Serial number
1 Fronius Primo 8.2-1 31191001154400485|4,071,334|1.4D_I|RECERBO|R| 3xxxxxxx
Meter
No Device type Location of the meter Serial number
1 Smart Meter 63A-1 Feed-in point (Primary meter) 2xxxxxxx
Essentially the serial number listed in the PHP output file starts with a ‘2’ as does the API link you posted however I’ve noticed this is the serial number of the Smart Meter and not the inverter (is that correct or could that be the issue possibly?) I could possibly manually enter the serial number starting with ‘3’ being the inverters in the PHP file and try again ?
Well it took me a while to work out what’s going on… After doing some digging I’ve discovered that the API call to the Fronius inverter is returning the data in a slightly different format now. I have updated my
Fronius inverter’s firmware several times since I wrote the script and it has been quite some time since I used the script [ posted above ]. Clearly at some point Fronius have changed the formatting for whatever reason.
In the original version of the API call GetArchiveData.cgi the Data Meter’s serial number was returned as:
"meter: 17380***" :
but now it is returned as:
"meter:IME - Smart Meter 63A - 17380***"
The change in format caused the json_decode() function calls to fail.
To fix the script so that it works with the newer version of the Fronius inverter firmware two changes are required - see blow.
A problem that I foresee is that the change that I have made will work only if the installed meter is a ‘Smart Meter 63A’. The data that you posted above shows that you have a ‘Smart Meter 63A-1’.
I will modify my script ( & repost it to PVO ) so that it extracts the ‘Model’ from GetMeterRealtimeData.cgi and uses that value to generate the function call that parses the returned Archive Data. You will need to append ‘-1’ to the model number.
REPLACE
$EnergyReal_WAC_Minus_Absolute = $arr["Body"]["Data"]["meter:" . $meterSerial]["Data"]["EnergyReal_WAC_Minus_Absolute"]["Values"][$x];
WITH
$EnergyReal_WAC_Minus_Absolute = $arr["Body"]["Data"]["meter:IME - Smart Meter 63A - " . $meterSerial]["Data"]["EnergyReal_WAC_Minus_Absolute"]["Values"][$x];
REPLACE
$EnergyReal_WAC_Plus_Absolute = $arr["Body"]["Data"]["meter:" . $meterSerial]["Data"]["EnergyReal_WAC_Plus_Absolute"]["Values"][$x];
WITH
$EnergyReal_WAC_Plus_Absolute = $arr["Body"]["Data"]["meter:IME - Smart Meter 63A - " . $meterSerial]["Data"]["EnergyReal_WAC_Plus_Absolute"]["Values"][$x];
Grannos
All,
Fronius appear to have changed the format of the data returned by the API call GetArchiveData.cgi. I have downloaded the latest version of the API documentation from Fronius’ website to check. The API documentation does NOT appear to have been updated. I have emailed Fronius some questions relating to the change. Watch this space.
If I query http://fronius/solar_api/GetAPIVersion.cgi I see:
{
“APIVersion” : 1,
“BaseURL” : “/solar_api/v1/”,
“CompatibilityRange” : “1.8-1”
}
I have altered the script [ shown inline above ] to extract the Smart Meter’s model number and use it in the JSON parsing. In theory it should work correctly with different model meters. I cannot however test it against older versions of the Fronius in which case the older version of the PHP script should still work. I will post a copy of my updated script after some further testing.
I do not know which firmware update broke the script.
Grannos
Thanks very much for that with the changes mentioned it seems to be working now, eg, snips from morning, midday and evening 
| Time | Energy Generated | Power Generated | Energy Consumed |
|---|---|---|---|
| 2:00 | 0 | 0 | 891 |
| 2:05 | 0 | 0 | 914 |
| 2:10 | 0 | 0 | 939 |
| 2:15 | 0 | 0 | 977 |
| 2:20 | 0 | 0 | 1021 |
| 2:25 | 0 | 0 | 1064 |
| 2:30 | 0 | 0 | 1107 |
| 2:35 | 0 | 0 | 1150 |
| 2:40 | 0 | 0 | 1188 |
| 2:45 | 0 | 0 | 1220 |
| 2:50 | 0 | 0 | 1252 |
| 2:55 | 0 | 0 | 1277 |
| 3:00 | 0 | 0 | 1310 |
| 12:00 | 21427.55111 | 5404.016556 | 9468.551111 |
| 12:05 | 21946.20861 | 6286.757576 | 9570.208611 |
| 12:10 | 22423.79139 | 5693.039735 | 9681.791389 |
| 12:15 | 22948.13722 | 6355.707071 | 9791.137222 |
| 12:20 | 23486.02361 | 6411.890728 | 9919.023611 |
| 12:25 | 24021.57472 | 6491.52862 | 10041.57472 |
| 12:30 | 24569.65056 | 6533.354305 | 10173.65056 |
| 12:35 | 25107.46861 | 6519.006734 | 10295.46861 |
| 12:40 | 25633.77139 | 6358.020134 | 10426.77139 |
| 12:45 | 26079.42583 | 5294.90429 | 10552.42583 |
| 12:50 | 26355.09889 | 3341.491582 | 10661.09889 |
| 12:55 | 26878.86028 | 6243.513245 | 10774.86028 |
| 20:00 | 42566.14361 | 0 | 25697.14361 |
| 20:05 | 42566.14361 | 0 | 25848.14361 |
| 20:10 | 42566.14361 | 0 | 26152.14361 |
| 20:15 | 42566.14361 | 0 | 26484.14361 |
| 20:20 | 42566.14361 | 0 | 26695.14361 |
| 20:25 | 42566.14361 | 0 | 26845.14361 |
| 20:30 | 42566.14361 | 0 | 26999.14361 |
| 20:35 | 42566.14361 | 0 | 27151.14361 |
| 20:40 | 42566.14361 | 0 | 27301.14361 |
| 20:45 | 42566.14361 | 0 | 27437.14361 |
| 20:50 | 42566.14361 | 0 | 27563.14361 |
| 20:55 | 42566.14361 | 0 | 27651.14361 |
| 21:00 | 42566.14361 | 0 | 27724.14361 |
Sorry this might be a silly question but is it at all possible to also include in the data ‘exported’ and ‘consumption’ as it seems the current ‘energy consumed’ is a total of something? I might have a read through your script and try understand how it all works to get a better idea of what’s possible and how it matches up to the Fronius API…etc…
Appreciate all your work and help!
Cheers!
Hi @jonnoc.
The exported columns were chosen to be in the correct format for the PVO LIveLoader Bulk Loading — PVOutput documentation. Both Energy values are cumulative and PVO expects cumulative figures.
If you’d like to see the 5 minutely interval figures it would be a fairly straightforward exercise to subtract one 5 minutely figure from its successor.
The script achieves a similar thing by preserving the starting MIDNIGHT figure and subtracting it from each of the successive amounts. You could simply subtract adjacent cumulative figures.
The $EnergyReal_WAC_Minus_Absolute and $EnergyReal_WAC_Plus_Absolute values represent the energy flowing through the Smart Meter.
if ( $x == 0 )
{
$startMinus = $EnergyReal_WAC_Minus_Absolute;
$startPlus = $EnergyReal_WAC_Plus_Absolute;
}
The meter itself reports cumulative lifetime figures whereas the script is designed to generate daily cumulative figures. The script generated energy fields therefore start at 0Wh each day.
grannos
All worked great, thanks for all your help…
Now the next project trying to export all the daily data as far back as I can to add it to my profile as I already hit the 14-day limit but at least I have a little more history in the system now…
Thank you grannos much appreciated and saved yours of manual entry
Hi Grannos, just wanted to say thanks for your script, as I’ve used it to recover and upload a couple of days of missing data. Cheers, Tim