Yes, you can certainly include this in the official solget release.
I made some more enhancements (e.g. the temperature part, handling of multiple
serial devices (as I had more than 1 Soladin) etc. Will see if I can separate
them and post here as well
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I also build (based on your code) a small utility to post the daily totals to
pvoutput by querying the historic data instead of the current data. i found
that usefull esp when sometimes my wl500g dies and I miss out a few
measurements..
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
historical data is left out the code with a reason. I had several issues where
the internal register did not store the correct values. If the soladin is
shutdown for a period of time, it's expecting that a new day is started.
(Happens during maintenance, snow or very bad weather, etc) There's no way to
correct errors like that. I experimented with the historical info, I had it
working, but encountered the same problems as before. Main reason: Soladin
lacks a internal clock.
Concluding: Only use the historical values in the soladin as a backup
facility, not as your main source for measurements.
Using pvoutput.org to feed zonnestroomopbrengst is indeed possible but not the
best solution. Better is to feed it directly. It's not very difficult to do
that I think.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi
For whoever is liking this...
I used the solget to load data to pvoutput.org.
This is the code I added to make it possible
add to the program below lines
USE_PVOUTPUT=1
PVOUTPUT_APIKEY="get the API key from the site and put it here"
SYSTEM_ID="and here goes your systemID"
CURL_OPT=$WORKDIR/CURL_EX
PVOUTPUT
pvoutput(){
if ; then
echo "Empty ... skipping update"
else
echo "-d \"d=
date +"%Y%m%d"\"" > $CURL_OPTecho "-d \"t=
date +"%H:%M"\"" >> $CURL_OPTecho "-d \"v1=$\"" >> $CURL_OPT
echo "-d \"v2=$Wsol\"" >> $CURL_OPT
echo "-d \"c1=1\"" >> $CURL_OPT
echo "-d \"v5=$Tsol\"" >> $CURL_OPT
echo "-d \"v6=
print_float 1 $ | sed 's/\,/./'\"" >> $CURL_OPTecho "--header \"X-Pvoutput-Apikey: $PVOUTPUT_APIKEY\" " >> $CURL_OPT
echo "--header \"X-Pvoutput-SystemId: $SYSTEM_ID\" " >> $CURL_OPT
echo "--url http://pvoutput.org/service/r2/addstatus.jsp" >> $CURL_OPT
curl -q -K $CURL_OPT
if ; then
succes loading
else
you can submit this one once more at later time
cp $CURL_OPT $CURL_OPT-
date +"%Y-%m-%d-%H%M%S"fi
fi
}
in the part of the code where is say #Run all routines in correct order
add after the "format_page" line the following
if (( USE_PVOUTPUT )); then
pvoutput
fi
Hi Erik,
Thanks for sharing!
I can include your piece of code to the official SolGet release if you like?
I looks great, it can be great replacement for the hard-to-understand RRDtool.
I will definitely try your solution. I heard about pvoutput earlier, but never
looked at it.
Yes, you can certainly include this in the official solget release.
I made some more enhancements (e.g. the temperature part, handling of multiple
serial devices (as I had more than 1 Soladin) etc. Will see if I can separate
them and post here as well
The nice thing is that pvoutput.org can also be used to fill the other 'big'
monitoring site
http://www.zonnestroomopbrengst.eu
I also build (based on your code) a small utility to post the daily totals to
pvoutput by querying the historic data instead of the current data. i found
that usefull esp when sometimes my wl500g dies and I miss out a few
measurements..
historical data is left out the code with a reason. I had several issues where
the internal register did not store the correct values. If the soladin is
shutdown for a period of time, it's expecting that a new day is started.
(Happens during maintenance, snow or very bad weather, etc) There's no way to
correct errors like that. I experimented with the historical info, I had it
working, but encountered the same problems as before. Main reason: Soladin
lacks a internal clock.
Concluding: Only use the historical values in the soladin as a backup
facility, not as your main source for measurements.
Using pvoutput.org to feed zonnestroomopbrengst is indeed possible but not the
best solution. Better is to feed it directly. It's not very difficult to do
that I think.
Hi Erik, can you contact me by using the contact form: http://www.solget.nl/contact.htm