RalfJL / S10history

Read historical data from a S10/E3DC solar power station
6 stars 2 forks source link

S10history

This program reads historical data from a S10 solar power station manufactured by E3DC and prints it to standard output.

Reports include:

Features

Prerequisites

Usage

To use the S10history script you should first store the passwords in environment variables:
export PW="your login password"
export AES="AES secret shared with S10"
user="mys10username"
ip="IP addr of S10"

Reading one paticular day (2017-02-17):
S10history -u $user -P PW -A AES -i $ip -y 2017 -m 2 -d 17

Read only the sum of that day:
S10history -u $user -P PW -A AES -i $ip -y 2017 -m 2 -d 17 -b

Read the sum of yesterday:
S10history -u $user -P PW -A AES -i $ip -d -1 -b

Read the Month and all days of that month:
S10history -u $user -P PW -A AES -i $ip -y 2017 -m 2

Read the sum of one year:
S10history -u $user -P PW -A AES -i $ip -y 2016

Put all days of one year into a Mysql database (please fill the scripts with your values):
examples/getYearperDay.sh 2016 > Year2016perDay.txt # reads all days to file
./S10toMysql.pl -dbname=myDBName -user=mySQLUser -password=PWofSQLuser Year2016perDay.txt
use the file to fill the database

Issues

A lot of values, reported by the S10 solar power station are off by some percent. If you find a flaw in my calculations please report. I am more than happy to correct that.

Contributing

  1. Fork it!
  2. Create your feature branch: git checkout -b my-new-feature
  3. Commit your changes: git commit -am 'Add some feature'
  4. Push to the branch: git push origin my-new-feature
  5. Submit a pull request :D

History

07.2017 added switch so that UTC can be used instead of local TZ S10 uses UTC only for time; did not really help with accuracy 02.2017 Initial version

Credits

All credits go to E3DC for providing the RSCP protocol and demo that this program is based on