3 inverters. Only 2 showing on Pvoutput

Topics: 5. Support
Dec 2, 2016 at 8:49 PM
Edited Dec 4, 2016 at 12:54 PM
I have 3 sma 2500hf inverters. All in netID 2. So mis =1

At first I had inverter 1 in upload configuration (with its BT addres) . Till I noticed I had to provide all 3 SN with each a Pvoutput id, taking into account the aggregation (so I made 1 full and 3 children)

Then I made those 3 children who all have the full plant as parent.

In Pv output I only the output of the original inverter is missing

I decommissioned 1 of those 3 because it was not uploading, thought I'd put that outpunt on main, and simply add the other 2 along with it, but no luck

Any advice?

spfspot config: BT address of #1 (which i'm missing out on)

config:
################################################################################
#  SBFspotUpload.cfg - Configuration file for SBFspotUploadService/Daemon
#  (c)2012-2014, SBF (https://sbfspot.codeplex.com)
#
#  DISCLAIMER:
#  A user of SBFspotUploadService/Daemon software acknowledges that he or she is
#  receiving this software on an "as is" basis and the user is not relying on
#  the accuracy or functionality of the software for any purpose. The user
#  further acknowledges that any use of this software will be at his own risk
#  and the copyright owner accepts no responsibility whatsoever arising from
#  the use or application of the software.
#
################################################################################


################################
### Log Settings             ###
################################
# Windows: C:\Users\Public\SMAdata\Logs
# Linux  : /home/pi/smadata/logs
#LogDir=C:\Users\Public\SMAdata\Logs
LogDir=/home/pi/smadata/logs

################################
### PVoutput Upload Settings ###
################################
#PVoutput_SID
#Map inverters to PVoutput System ID's
#PVoutput_SID=SerialNmbrInverter_1:SID_1,SerialNmbrInverter_2:SID_2
#e.g. PVoutput_SID=200212345:4321
PVoutput_SID=2120102129:49259,2120093240:49274,2120102179:49275

#PVoutput_Key
#Sets PVoutput API Key
PVoutput_Key=

################################
### SQL DB Settings          ###
################################
# SQL_Database (Fullpath to SQLite DB)
# Windows: C:\Users\Public\SMAdata\SBFspot.db
# Linux  : /home/pi/smadata/SBFspot.db
#SQL_Database=C:\Users\Public\SMAdata\SBFspot.db
SQL_Database=/home/pi/smadata/SBFspot.db

# Reserved for MySQL
#SQL_Database=SBFspot
#SQL_Hostname=<Network Name> or <IP-address>
#SQL_Username=SBFspotUser
#SQL_Password=SBFspotPassword
PVoutput itsself:

Parent #0 -- 49259 -- Active (32x240=7680) => 2120102129 (BT adress I connect to= missing)
Child #1 -- 49275 -- Active (12x240=2880) 2120102179
Child #2 -- 49274 --    Active (10x240=2400) 2120093240
Child #3 --49273 -- Decommissioned (10x240=2400) (this data is missing, but I thought this one is being sent to #0 ???)
Coordinator
Dec 4, 2016 at 10:31 AM
You should upload the data of the 3 inverters to the child systems (not to the parent)
Is the data of the missing one in the db? You should check this first.

Btw, NEVER show your personal API key - better change it on PVOutput now
Dec 4, 2016 at 12:56 PM
Weird I did that at first without results of the 1st.

How do I check that on db then? I'll try to find out.

Key changed already thx
Dec 4, 2016 at 2:20 PM
Edited Dec 4, 2016 at 3:33 PM
I reverted back as you suggested, 3x the childsystems, but still I don't see it on pvoutput ...

It does show in DB though, but obviously not on pvoutput

select * from vwspotdata;
2/12/2016 13:50 2/12/2016 13:50         2120102179  200 0   0.0 0.0 0.0 0.0 0   0   0   0.0 0.0 0.0 0.0 0.0 0.0 200 0   0.0 949 12190962    50.01   20913.4 19622.3 0.0 OK  Closed  26.9
2/12/2016 13:50 2/12/2016 13:50 SN: 2120102129  SB 2500HF-30    2120102129  152 0   0.362   0.0 422.78  0.0 146 0   0   0.629   0.0 0.0 233.42  0.0 0.0 152 146 96.1    792 8741309 50.01   20603.1 19172.7 71.4    OK  Closed  26.8
2/12/2016 13:50 2/12/2016 13:50         2120093240  167 0   0.0 0.0 0.0 0.0 0   0   0   0.0 0.0 0.0 0.0 0.0 0.0 167 0   0.0 824 9673480 50.01   20755.0 19393.1 0.0 OK  Closed  25.4
select * from inverters;
2120102129|SN: 2120102129|SB 2500HF-30|02.54.11.R|1480860905|0|0|0|20618.4|19186.5|OK|Closed|27.72
0||||1480835810|0|0|0|0.0|0.0|?|?|0.0
2120102179|||02.54.11.R|1480860905|0|0|0|20929.6|19637.0|OK|Closed|26.9
2120093240|||02.54.11.R|1480860905|0|0|0|20770.7|19407.2|OK|Closed|26.36
pi@raspberrypi:~ $ /usr/local/bin/sbfspot.3/SBFspot -v -finq -nocsv
SBFspot V3.3.1
Yet another tool to read power production of SMA solar inverters
(c) 2012-2016, SBF (https://sbfspot.codeplex.com)
Compiled for Linux (LE) 32 bit

Commandline Args: -v -finq -nocsv
Reading config '/usr/local/bin/sbfspot.3/SBFspot.cfg'
Sun Dec  4 16:31:46 2016: INFO: Starting...
sunrise: 08:27
sunset : 16:36
Connecting to 00:80:25:1D:5B:96 (1/10)
Initializing...
SUSyID: 125 - SessionID: 809566776 (0x30410238)
SMA netID=02
SUSyID: 131 - SN: 2120102179
SUSyID: 131 - SN: 2120102129
SUSyID: 131 - SN: 2120093240
BT Signal=0.0%
Logon OK
Local Host Time: 04/12/2016 16:31:49
Plant Time     : 04/12/2016 16:31:49 (0 sec)
TZ offset      : 0 sec - DST: Off
Last Time Set  : 04/12/2016 08:35:06
SUSyID: 131 - SN: 2120102129
Device Name:      SN: 2120102129
Device Class:     Solar Inverters
Device Type:      SB 2500HF-30
Software Version: 02.54.11.R
Serial number:    2120102129
SUSyID: 131 - SN: 2120102179
Device Name:      12 ACHTER SN: 2120102179
Device Class:     Solar Inverters
Device Type:      SB 2500HF-30
Software Version: 02.54.11.R
Serial number:    2120102179
SUSyID: 131 - SN: 2120093240
Device Name:      SN: 2120093240
Device Class:     Solar Inverters
Device Type:      SB 2500HF-30
Software Version: 02.54.11.R
Serial number:    2120093240
SUSyID: 131 - SN: 2120102129
Device Status:      Ok
SUSyID: 131 - SN: 2120102179
Device Status:      Ok
SUSyID: 131 - SN: 2120093240
Device Status:      Ok
SUSyID: 131 - SN: 2120102129
Device Temperature: 25.1°C
SUSyID: 131 - SN: 2120102179
Device Temperature: 25.2°C
SUSyID: 131 - SN: 2120093240
Device Temperature: 22.7°C
SUSyID: 131 - SN: 2120102129
GridRelay Status:      Open
SUSyID: 131 - SN: 2120102179
GridRelay Status:      Open
SUSyID: 131 - SN: 2120093240
GridRelay Status:      Open
SUSyID: 131 - SN: 2120102129
Pac max phase 1: 2500W
Pac max phase 2: 2500W
Pac max phase 3: 2500W
SUSyID: 131 - SN: 2120102179
Pac max phase 1: 2500W
Pac max phase 2: 2500W
Pac max phase 3: 2500W
SUSyID: 131 - SN: 2120093240
Pac max phase 1: 2500W
Pac max phase 2: 2500W
Pac max phase 3: 2500W
SUSyID: 131 - SN: 2120102129
Energy Production:
        EToday: 2.507kWh
        ETotal: 8746.316kWh
        Operation Time: 20619.70h
        Feed-In Time  : 19186.85h
SUSyID: 131 - SN: 2120102179
Energy Production:
        EToday: 1.573kWh
        ETotal: 12194.286kWh
        Operation Time: 20930.88h
        Feed-In Time  : 19637.94h
SUSyID: 131 - SN: 2120093240
Energy Production:
        EToday: 1.706kWh
        ETotal: 9677.030kWh
        Operation Time: 20771.98h
        Feed-In Time  : 19407.94h
SUSyID: 131 - SN: 2120102129
DC Spot Data:
        String 1 Pdc:   0.000kW - Udc: 354.41V - Idc:  0.000A
        String 2 Pdc:   0.000kW - Udc:   0.00V - Idc:  0.000A
SUSyID: 131 - SN: 2120102179
DC Spot Data:
        String 1 Pdc:   0.000kW - Udc: 486.85V - Idc:  0.000A
        String 2 Pdc:   0.000kW - Udc:   0.00V - Idc:  0.000A
SUSyID: 131 - SN: 2120093240
DC Spot Data:
        String 1 Pdc:   0.000kW - Udc: 405.30V - Idc:  0.000A
        String 2 Pdc:   0.000kW - Udc:   0.00V - Idc:  0.000A
SUSyID: 131 - SN: 2120102129
AC Spot Data:
        Phase 1 Pac :   0.000kW - Uac: 231.58V - Iac:  0.000A
        Phase 2 Pac :   0.000kW - Uac:   0.00V - Iac:  0.000A
        Phase 3 Pac :   0.000kW - Uac:   0.00V - Iac:  0.000A
        Total Pac   :   0.000kW
SUSyID: 131 - SN: 2120102179
AC Spot Data:
        Phase 1 Pac :   0.000kW - Uac: 233.76V - Iac:  0.000A
        Phase 2 Pac :   0.000kW - Uac:   0.00V - Iac:  0.000A
        Phase 3 Pac :   0.000kW - Uac:   0.00V - Iac:  0.000A
        Total Pac   :   0.000kW
SUSyID: 131 - SN: 2120093240
AC Spot Data:
        Phase 1 Pac :   0.000kW - Uac: 233.90V - Iac:  0.000A
        Phase 2 Pac :   0.000kW - Uac:   0.00V - Iac:  0.000A
        Phase 3 Pac :   0.000kW - Uac:   0.00V - Iac:  0.000A
        Total Pac   :   0.000kW
SUSyID: 131 - SN: 2120102129
Grid Freq. : 50.01Hz
SUSyID: 131 - SN: 2120102179
Grid Freq. : 50.00Hz
SUSyID: 131 - SN: 2120093240
Grid Freq. : 50.01Hz
SUSyID: 131 - SN: 2120102129
Current Inverter Time: 04/12/2016 16:31:51
Inverter Wake-Up Time: 04/12/2016 08:32:39
Inverter Sleep Time  : 04/12/2016 16:31:52
SUSyID: 131 - SN: 2120102179
Current Inverter Time: 04/12/2016 16:31:47
Inverter Wake-Up Time: 04/12/2016 08:30:56
Inverter Sleep Time  : 04/12/2016 16:31:52
SUSyID: 131 - SN: 2120093240
Current Inverter Time: 04/12/2016 16:31:51
Inverter Wake-Up Time: 04/12/2016 08:31:41
Inverter Sleep Time  : 04/12/2016 16:31:53
********************
* ArchiveDayData() *
********************
startTime = 58434E70 -> 04/12/2016 00:00:00
**********************
* ArchiveMonthData() *
**********************
startTime = 584002B0 -> 01/12/2016 12:00:00
Reading events: 2016-Dec-01
Sun Dec  4 16:31:57 2016: INFO: Done.
can't figure out what's wrong here, it connects to all 3 of them, no ? did just change config of sbfspot (took another BT address now ...)
Coordinator
Dec 5, 2016 at 8:20 AM
What's in vwDayData? This one is important too...
And the output of vwPVOdata?
Dec 5, 2016 at 3:09 PM
Edited Dec 5, 2016 at 4:21 PM
vwDayData
2016-12-05 15:10:00|12 ACHTER SN: 2120102179|SB 2500HF-30|2120102179|12195872|72|
2016-12-05 15:10:00|||2120102129|8748647|36|
2016-12-05 15:10:00|||2120093240|9678701|60|
2016-12-05 15:05:00|12 ACHTER SN: 2120102179|SB 2500HF-30|2120102179|12195866|84|
2016-12-05 15:05:00|||2120102129|8748644|48|
2016-12-05 15:05:00|||2120093240|9678696|48|
2016-12-05 15:00:00|12 ACHTER SN: 2120102179|SB 2500HF-30|2120102179|12195859|72|
2016-12-05 15:00:00|||2120102129|8748640|36|
2016-12-05 15:00:00|||2120093240|9678692|48|
and counting ... 
this does seem fine, no ?

vwPVOdata
2016-12-05 15:55:00|12 ACHTER SN: 2120102179|SB 2500HF-30|2120102179|12195922|48|||26.1|0.0|||||||
2016-12-05 15:55:00|SN: 2120102129|SB 2500HF-30|2120102129|8748669|24|||26.7|0.0|||||||
2016-12-05 15:55:00|SN: 2120093240|SB 2500HF-30|2120093240|9678733|24|||25.1|0.0|||||||
2016-12-05 15:50:00|12 ACHTER SN: 2120102179|SB 2500HF-30|2120102179|12195918|60|||26.2|231.58|||||||
2016-12-05 15:50:00|SN: 2120102129|SB 2500HF-30|2120102129|8748667|12|||26.8|0.0|||||||
2016-12-05 15:50:00|SN: 2120093240|SB 2500HF-30|2120093240|9678731|36|||25.1|0.0|||||||
and counting as well ...
weird, all seems to be there though

for easy purpouse I have downloaded the entire content of my pi :)
Dec 5, 2016 at 7:30 PM
Hmm. Somehow my uploaddaemon got stuck yesterday after changing api key. Though I rebooted (or so I thought)

Now after rebooting (again?) everything got uploaded all at once? (where I had data starting 2/12, and now I got all data till 2 months back)

Do u need to update api after every change? Can't figure out what else could have caused this (adding other inverters after creating api)
Coordinator
Dec 5, 2016 at 8:19 PM
No need to change API key. So everything is working now?
Dec 6, 2016 at 5:57 AM
It appears that way yeah...

Gonna keep an eye on it today and hopefully all is fine now
Dec 6, 2016 at 3:19 PM
Yep, all seems to be working perfectly now!

thx for the nice tool SBF!