Hello,
I recently started using SBFspot, version 3.1.1 on raspberry pi.
I tried to get all archived data from the SMA inverter,
and then upload it to pvoutput.org.
I used the -ad and -ae flags too fetch the archived data
(I used -ad300 and -am300, which are larger than the
'live' data that is present in the inverter -- it gave me
'live' data for a few months;
it gave me per-day totals for all months since the inverter was activated.
Somehow, the very first datapoint for the very first day of the archived data
has an 'interesting' power/energy (V2) value:
I assume it is the amount of energy generated from the moment the SMA inverter was enabled upto that moment in time.
In my case, this is a large number: 110925396
In the csv file it looks as follows:
```
12/07/2015 04:25:00;9243,782;110925,396
12/07/2015 04:30:00;9243,782;0,000
```
When uploading the archived data to pvoutput.org
SBFspot tries to upload this huge value as a value for V2.
Pvoutput.org refuses the upload, because the value is higher than the system size:
```
Bad request 400: Power value [110925396] too high for system size [3825]
```
The following patch kind-of fixes this:
when obtaining the archived data using batch_get_archdaydata we take
the system size into account: the system size is passed as additional
parameter in the call to batch_get_archdaydata.
When it encounters a V2 value that is higher than system size,
it will use 0 instead; when that happens, a LOG line is printed.
This works for me; I only tested this with mysqlite.
Note: I slightly edited the attached diff to remove irrelevant changes;
because of this, line numbers in the patch may be slightly off.
Axel.
PS thanks for SBFspot, it does a nice job! :-)
Comments: submit to codeplex just failed, and I lost the long piece that I typed :-( I am confused by what you ask, because I would guess that ``` sbfspot -d5 -v5 ``` only gives info about fetching 'current' data from the convertor; maybe I misunderstood what you are asking for; I attach the stdout output anyway; the stderr output is empty. Sidenotes: 1) the sbfspot I used to obtain attached output differs from the one I used to obtain the archived data from the convertor: I compiled it with a newer version of bluez that I installed from source. Reason: initially I had installed bluez using apt-get; with that version, after a while (from 12 hours upto several days?) bluetooth connections were no longer working/possible. 2) my convertor clock is approx 6 minutes ahead of the (ntp-controlled, I think) computer clock. timeSync is enabled but does not seem to have any effect. Have you seen timeSync work? 3) voltage/temperature data appears only on pvoutput when i restart the raspi in the evening when bluetooth connection stopped working during the day. one day this gave me weird results: http://pvoutput.org/intraday.jsp?id=44413&sid=40547&dt=20150918&gs=0&m=0 regards, Axel.
I recently started using SBFspot, version 3.1.1 on raspberry pi.
I tried to get all archived data from the SMA inverter,
and then upload it to pvoutput.org.
I used the -ad and -ae flags too fetch the archived data
(I used -ad300 and -am300, which are larger than the
'live' data that is present in the inverter -- it gave me
'live' data for a few months;
it gave me per-day totals for all months since the inverter was activated.
Somehow, the very first datapoint for the very first day of the archived data
has an 'interesting' power/energy (V2) value:
I assume it is the amount of energy generated from the moment the SMA inverter was enabled upto that moment in time.
In my case, this is a large number: 110925396
In the csv file it looks as follows:
```
12/07/2015 04:25:00;9243,782;110925,396
12/07/2015 04:30:00;9243,782;0,000
```
When uploading the archived data to pvoutput.org
SBFspot tries to upload this huge value as a value for V2.
Pvoutput.org refuses the upload, because the value is higher than the system size:
```
Bad request 400: Power value [110925396] too high for system size [3825]
```
The following patch kind-of fixes this:
when obtaining the archived data using batch_get_archdaydata we take
the system size into account: the system size is passed as additional
parameter in the call to batch_get_archdaydata.
When it encounters a V2 value that is higher than system size,
it will use 0 instead; when that happens, a LOG line is printed.
This works for me; I only tested this with mysqlite.
Note: I slightly edited the attached diff to remove irrelevant changes;
because of this, line numbers in the patch may be slightly off.
Axel.
PS thanks for SBFspot, it does a nice job! :-)
Comments: submit to codeplex just failed, and I lost the long piece that I typed :-( I am confused by what you ask, because I would guess that ``` sbfspot -d5 -v5 ``` only gives info about fetching 'current' data from the convertor; maybe I misunderstood what you are asking for; I attach the stdout output anyway; the stderr output is empty. Sidenotes: 1) the sbfspot I used to obtain attached output differs from the one I used to obtain the archived data from the convertor: I compiled it with a newer version of bluez that I installed from source. Reason: initially I had installed bluez using apt-get; with that version, after a while (from 12 hours upto several days?) bluetooth connections were no longer working/possible. 2) my convertor clock is approx 6 minutes ahead of the (ntp-controlled, I think) computer clock. timeSync is enabled but does not seem to have any effect. Have you seen timeSync work? 3) voltage/temperature data appears only on pvoutput when i restart the raspi in the evening when bluetooth connection stopped working during the day. one day this gave me weird results: http://pvoutput.org/intraday.jsp?id=44413&sid=40547&dt=20150918&gs=0&m=0 regards, Axel.