Hello,
My inverter is a SMA SB 4000-TL20 (running since 2009 in Germany).
I am working with SBFspot 3.3.2.
Since a few month is discovered, I always get error when reading inverter data....
```
### End of Config ###
Mon Jun 5 12:50:01 2017: INFO: Starting...
sunrise: 05:18
sunset : 21:16
Connecting to 00:80:25:0A:1A:C5 (1/15)
Initializing...
SUSyID: 125 - SessionID: 866472527 (0x33A5524F)
SMA netID=01
Serial Nr: 7D2D036C (2100101996)
BT Signal=68.2%
Logon OK
Failed to get current plant time (0)
getInverterData(sbftest) returned an error: -1
getSoftwareVersion returned an error: -1
SUSyID: 78 - SN: 2100101996
Device Name: SN: 2100101996
Device Class: Solar Inverters
Device Type: SB 4000TL-20
Software Version:
Serial number: 2100101996
SUSyID: 78 - SN: 2100101996
Device Status: Ok
SUSyID: 78 - SN: 2100101996
Device Temperature: 36.9°C
SUSyID: 78 - SN: 2100101996
GridRelay Status: Closed
SUSyID: 78 - SN: 2100101996
```
Rest works.
Login in via SMA Sunny Explorer Windows-Software, Time can be read/changed... Software version is displayed..... ?1?
If this was always the case I can't say; I looked closer onto log-data when discvovering "123solar".
From old "SMASpot" I don't have any log-files remaining.
Any ideas?
Comments: Hello, Beside the BT trial I discovered another issue: I synchronizing RPi's clock with "ntpdate" every hour.... I thought... It was running only running in "pi" users crontab => no permission to change time. So RPi's time was far away from "real time". So solving the clock-synchronization problem I tried another BT-dongle (from "CSL")... First effect I saw: PVOuput live output now again schows AC-voltage and Temp. [PV-Snapshot](http://neumi.selfhost.bz/pv_neumi/snap20170615-135420.png) Next look into logfile ("-v5"): ``` Connecting to 00:80:25:0A:1A:C5 (1/15) Initializing... SUSyID: 125 - SessionID: 926812559 (0x373E098F) SMA netID=01 Serial Nr: 7D2D036C (2100101996) BT Signal=69.8% Logon OK Failed to get current plant time (0) getInverterData(sbftest) returned an error: -1 getSoftwareVersion returned an error: -1 SUSyID: 78 - SN: 2100101996 Device Name: SN: 2100101996 Device Class: Solar Inverters Device Type: SB 4000TL-20 Software Version: Serial number: 2100101996 ``` So not a real improvement... BTW. what means "-1" or "(0)" ? Logfile ("-v5 -d5"): [sbflog-20170615-1412.txt](http://neumi.selfhost.bz/pv_neumi/sbflog-20170615-1412.txt) ``` PacketLength=84 <<<====== Content of pcktBuf =======>>> --------: 00 01 02 03 04 05 06 07 08 09 00000000: 7E FF 03 60 65 0E 50 7D 00 8F 00000010: 23 EB 32 00 01 4E 00 6C 03 2D 00000020: 7D 00 01 00 00 00 00 04 80 0D 00000030: 04 FD FF 07 00 00 00 84 03 00 00000040: 00 1B 79 42 59 00 00 00 00 B8 00000050: B8 B8 B8 88 88 88 88 88 88 88 00000060: 88 AD E7 7E <<<=================================>>> Failed to get current plant time (0) getInverterData(-2147483648) --------: 00 01 02 03 04 05 06 07 08 09 00000000: 7E 3F 00 41 0D 71 DA 7D 1A 00 00000010: FF FF FF FF FF FF 01 00 7E FF 00000020: 03 60 65 09 A0 FF FF FF FF FF 00000030: FF 00 00 7D 5D 00 8F 23 EB 32 00000040: 00 00 00 00 00 00 06 80 00 02 00000050: 02 64 00 8C 61 00 FF 8F 61 00 00000060: 32 DE 7E 63 Bytes sent getPacket(1) Received 18 bytes ``` Packet ID mismatch... ? ``` PacketLength=84 <<<====== Content of pcktBuf =======>>> --------: 00 01 02 03 04 05 06 07 08 09 00000000: 7E FF 03 60 65 0E 50 7D 00 8F 00000010: 23 EB 32 00 01 4E 00 6C 03 2D 00000020: 7D 00 01 00 00 00 00 04 80 0D 00000030: 04 FD FF 07 00 00 00 84 03 00 00000040: 00 1B 79 42 59 00 00 00 00 B8 00000050: B8 B8 B8 88 88 88 88 88 88 88 00000060: 88 AD E7 7E <<<=================================>>> Packet ID mismatch. Expected 6, received 4 getPacket(1) Received 18 bytes Received 77 bytes ``` Time-out... ? ``` PacketLength=95 <<<====== Content of pcktBuf =======>>> --------: 00 01 02 03 04 05 06 07 08 09 00000000: 7E FF 03 60 65 10 50 7D 00 8F 00000010: 23 EB 32 00 A0 4E 00 6C 03 2D 00000020: 7D 00 00 00 00 00 00 92 BC 0A 00000030: 02 00 F0 00 00 00 00 00 00 00 00000040: 00 00 6D 23 00 13 79 42 59 46 00000050: 42 35 59 13 79 42 59 11 0E 00 00000060: 00 54 0F 59 58 01 00 00 00 9C 00000070: B2 7E <<<=================================>>> Packet ID mismatch. Expected 6, received 15506 getPacket(1) Timeout reading socket No data! getInverterData(sbftest) returned an error: -1 getInverterData(2048) ``` Log ("-v5 -d5") and another BT-Dongle ("LogiLink").... [sbflog-20170615-1420.txt](http://neumi.selfhost.bz/pv_neumi/sbflog-20170615-1420.txt) I don't know what goes wrong.... seems not be a BT-dongle issue.... I got the impression, some packet length is regonized/interpreted wrong and therefore the rest is no more in line.....
My inverter is a SMA SB 4000-TL20 (running since 2009 in Germany).
I am working with SBFspot 3.3.2.
Since a few month is discovered, I always get error when reading inverter data....
```
### End of Config ###
Mon Jun 5 12:50:01 2017: INFO: Starting...
sunrise: 05:18
sunset : 21:16
Connecting to 00:80:25:0A:1A:C5 (1/15)
Initializing...
SUSyID: 125 - SessionID: 866472527 (0x33A5524F)
SMA netID=01
Serial Nr: 7D2D036C (2100101996)
BT Signal=68.2%
Logon OK
Failed to get current plant time (0)
getInverterData(sbftest) returned an error: -1
getSoftwareVersion returned an error: -1
SUSyID: 78 - SN: 2100101996
Device Name: SN: 2100101996
Device Class: Solar Inverters
Device Type: SB 4000TL-20
Software Version:
Serial number: 2100101996
SUSyID: 78 - SN: 2100101996
Device Status: Ok
SUSyID: 78 - SN: 2100101996
Device Temperature: 36.9°C
SUSyID: 78 - SN: 2100101996
GridRelay Status: Closed
SUSyID: 78 - SN: 2100101996
```
Rest works.
Login in via SMA Sunny Explorer Windows-Software, Time can be read/changed... Software version is displayed..... ?1?
If this was always the case I can't say; I looked closer onto log-data when discvovering "123solar".
From old "SMASpot" I don't have any log-files remaining.
Any ideas?
Comments: Hello, Beside the BT trial I discovered another issue: I synchronizing RPi's clock with "ntpdate" every hour.... I thought... It was running only running in "pi" users crontab => no permission to change time. So RPi's time was far away from "real time". So solving the clock-synchronization problem I tried another BT-dongle (from "CSL")... First effect I saw: PVOuput live output now again schows AC-voltage and Temp. [PV-Snapshot](http://neumi.selfhost.bz/pv_neumi/snap20170615-135420.png) Next look into logfile ("-v5"): ``` Connecting to 00:80:25:0A:1A:C5 (1/15) Initializing... SUSyID: 125 - SessionID: 926812559 (0x373E098F) SMA netID=01 Serial Nr: 7D2D036C (2100101996) BT Signal=69.8% Logon OK Failed to get current plant time (0) getInverterData(sbftest) returned an error: -1 getSoftwareVersion returned an error: -1 SUSyID: 78 - SN: 2100101996 Device Name: SN: 2100101996 Device Class: Solar Inverters Device Type: SB 4000TL-20 Software Version: Serial number: 2100101996 ``` So not a real improvement... BTW. what means "-1" or "(0)" ? Logfile ("-v5 -d5"): [sbflog-20170615-1412.txt](http://neumi.selfhost.bz/pv_neumi/sbflog-20170615-1412.txt) ``` PacketLength=84 <<<====== Content of pcktBuf =======>>> --------: 00 01 02 03 04 05 06 07 08 09 00000000: 7E FF 03 60 65 0E 50 7D 00 8F 00000010: 23 EB 32 00 01 4E 00 6C 03 2D 00000020: 7D 00 01 00 00 00 00 04 80 0D 00000030: 04 FD FF 07 00 00 00 84 03 00 00000040: 00 1B 79 42 59 00 00 00 00 B8 00000050: B8 B8 B8 88 88 88 88 88 88 88 00000060: 88 AD E7 7E <<<=================================>>> Failed to get current plant time (0) getInverterData(-2147483648) --------: 00 01 02 03 04 05 06 07 08 09 00000000: 7E 3F 00 41 0D 71 DA 7D 1A 00 00000010: FF FF FF FF FF FF 01 00 7E FF 00000020: 03 60 65 09 A0 FF FF FF FF FF 00000030: FF 00 00 7D 5D 00 8F 23 EB 32 00000040: 00 00 00 00 00 00 06 80 00 02 00000050: 02 64 00 8C 61 00 FF 8F 61 00 00000060: 32 DE 7E 63 Bytes sent getPacket(1) Received 18 bytes ``` Packet ID mismatch... ? ``` PacketLength=84 <<<====== Content of pcktBuf =======>>> --------: 00 01 02 03 04 05 06 07 08 09 00000000: 7E FF 03 60 65 0E 50 7D 00 8F 00000010: 23 EB 32 00 01 4E 00 6C 03 2D 00000020: 7D 00 01 00 00 00 00 04 80 0D 00000030: 04 FD FF 07 00 00 00 84 03 00 00000040: 00 1B 79 42 59 00 00 00 00 B8 00000050: B8 B8 B8 88 88 88 88 88 88 88 00000060: 88 AD E7 7E <<<=================================>>> Packet ID mismatch. Expected 6, received 4 getPacket(1) Received 18 bytes Received 77 bytes ``` Time-out... ? ``` PacketLength=95 <<<====== Content of pcktBuf =======>>> --------: 00 01 02 03 04 05 06 07 08 09 00000000: 7E FF 03 60 65 10 50 7D 00 8F 00000010: 23 EB 32 00 A0 4E 00 6C 03 2D 00000020: 7D 00 00 00 00 00 00 92 BC 0A 00000030: 02 00 F0 00 00 00 00 00 00 00 00000040: 00 00 6D 23 00 13 79 42 59 46 00000050: 42 35 59 13 79 42 59 11 0E 00 00000060: 00 54 0F 59 58 01 00 00 00 9C 00000070: B2 7E <<<=================================>>> Packet ID mismatch. Expected 6, received 15506 getPacket(1) Timeout reading socket No data! getInverterData(sbftest) returned an error: -1 getInverterData(2048) ``` Log ("-v5 -d5") and another BT-Dongle ("LogiLink").... [sbflog-20170615-1420.txt](http://neumi.selfhost.bz/pv_neumi/sbflog-20170615-1420.txt) I don't know what goes wrong.... seems not be a BT-dongle issue.... I got the impression, some packet length is regonized/interpreted wrong and therefore the rest is no more in line.....