Hi all, this has been working for about 4 years but after I reset a password in SunnyBoy, it no longer connects.
I can confirm that I have the right password by logging in manually to SunnyBoy using User/pw.
I am running /usr/local/bin/sbfspot.3/SBFspot -finq -v5 -d to check my configuration, and it outputs CRITICAL : Logon failed. Check ‘USER’ Password.
Fully patched Raspberry, and latest SBFSpot deploy
Any help appreciated
Thanks
Ivan
Hi,
Just a shot in the dark, but is it possible that the ‘reset’ password is using a reserved character. I have been caught out before by including a reserved / special character in a password.
Grannos.
Thanks Granno - I’m thinking thats not the problem because I can successfully log in to SunnyBoy with the User account, and manually type in the password - when I put this same password in the SBFSpot config, it fails - password is only in one spot right?
How do you login? Sunnyexplorer or webinterface?
When using SE it should work with SBFspot too.
AFAIK webinterface uses different password.
Hmmm, sounds promising - I’m using the web interface direct to the IP of the inverter - page name is Sunny Boy. It has the option of logging in as Installer or User - its the User password that I’m usin in Spot
What is the URL for SE?
Ok, downloaded and installed (speedwire, no encryption) - same User password being used in SBFSpot also works here 
OK, changed User password in Sunny Explorer
Set same password in SBFSpot config file (/home/pi/sunnyportal-py-master/sunnyportal.config)
Ran /usr/local/bin/sbfspot.3/SBFspot -finq -v5 -d
Result "CRITICAL: Logon failed. Check ‘USER’ Password
Just confirming that is the right place to be setting the password?
No, default config file is SBFspot.cfg in the application folder. If you want a different config, use the -cfg:full_path_to_config argument on the SBFspot command line
Hi there - no, not looking for a different config - thought that was the default. Which is the application folder please?
Thought I’d run the installer again - I get:
pi@raspberrypi:~/sunnyportal-py-master $ PYTHONPATH=. ./bin/sunnyportal2pvoutput --dry-run sunnyportal.config
2024-04-24 21:49:31,663 DEBUG: GET /services/authentication/100/45delprat%Loading...
Traceback (most recent call last):
File “./bin/sunnyportal2pvoutput”, line 284, in
main()
File “./bin/sunnyportal2pvoutput”, line 228, in main
plants = client.get_plants()
File “/home/pi/sunnyportal-py-master/sunnyportal/client.py”, line 62, in get_plants
req = requests.PlantListRequest(self.get_token())
File “/home/pi/sunnyportal-py-master/sunnyportal/client.py”, line 51, in get_token
self.token = self.do_request(req)
File “/home/pi/sunnyportal-py-master/sunnyportal/client.py”, line 46, in do_request
return request.perform(conn)
File “/home/pi/sunnyportal-py-master/sunnyportal/requests.py”, line 79, in perform
self.service, response.status, response.reason
RuntimeError: HTTP error performing authentication request: 410 Gone
I’m afraid you’re mixing two systems… the python script (installer) is not part of SBFspot.
The SBFspot default config file is /usr/local/bin/sbfspot.3/SBFspot.cfg
right!! So I’ve read a couple of posts - as a result have changed the user password to be the same as the installer password. Then run the command at bottom to change the password, which appears successful. Same issue though when I run the earlier command:
Ran /usr/local/bin/sbfspot.3/SBFspot -finq -v5 -d
Result "CRITICAL: Logon failed. Check ‘USER’ Password
/usr/local/bin/sbfspot.3/SBFspot -v -finq -nocsv -installer -password:xxxxxxxx
SBFspot V3.5.2
Yet another tool to read power production of SMA solar inverters
© 2012-2018, SBF (GitHub - SBFspot/SBFspot: Yet another tool to read power production of SMA® solar/battery inverters)
Compiled for Linux (LE) 32 bit with SQLite support
Commandline Args: -v -finq -nocsv -installer -password:?4con6EBTdhq
Reading config ‘/usr/local/bin/sbfspot.3/SBFspot.cfg’
Thu Apr 25 04:36:30 2024: INFO: Starting…
sunrise: 06:58
sunset : 17:38
Connecting to Local Network…
Initializing…
SUSyID: 125 - SessionID: 832552281 (0x319FBD59)
Inverter IP address: 192.168.1.114 found via broadcastidentification
Logon OK
SUSyID: 409 - SN: 3006906963
Device Name: SB5.0-1AV-41 963
Device Class: Solar Inverters
Device Type: Sunny Boy 5.0 AV-41
Software Version: 04.00.75.R
Serial number: 3006906963
SUSyID: 409 - SN: 3006906963
Device Status: Ok
SUSyID: 409 - SN: 3006906963
Device Temperature: 0.0°C
SUSyID: 409 - SN: 3006906963
GridRelay Status: Information not available
SUSyID: 409 - SN: 3006906963
Pac max phase 1: 5000W
Pac max phase 2: 0W
Pac max phase 3: 0W
SUSyID: 409 - SN: 3006906963
Energy Production:
EToday: 0.000kWh
ETotal: 27034.827kWh
Operation Time: 17948.92h
Feed-In Time : 17284.60h
SUSyID: 409 - SN: 3006906963
DC Spot Data:
String 1 Pdc: 0.000kW - Udc: 0.00V - Idc: 0.000A
String 2 Pdc: 0.000kW - Udc: 0.00V - Idc: 0.000A
SUSyID: 409 - SN: 3006906963
AC Spot Data:
Phase 1 Pac : 0.000kW - Uac: 0.00V - 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: 409 - SN: 3006906963
Grid Freq. : 0.00Hz
SUSyID: 409 - SN: 3006906963
Current Inverter Time: 25/04/2024 04:36:29
Inverter Wake-Up Time: 24/04/2024 06:34:56
Inverter Sleep Time : 25/04/2024 04:35:30
startTime = 66291060 → 25/04/2024 00:00:00
startTime = 660A1520 → 01/04/2024 13:00:00
Reading events: 2024-Apr-01
Thu Apr 25 04:36:31 2024: INFO: Done.
OK, getting there - thanks for your help!
I have now successfully uploaded todays data to PVOutput, but there is a 13 day gap in data.
I have run /usr/local/bin/sbfspot.3/SBFspot -v -finq -nocsv -startdate:20240412 - results below - but it doesn’t pick up the missing days - any thoughts please
/usr/local/bin/sbfspot.3/SBFspot -v -finq -nocsv -startdate:20240412
SBFspot V3.5.2
Yet another tool to read power production of SMA solar inverters
© 2012-2018, SBF (GitHub - SBFspot/SBFspot: Yet another tool to read power production of SMA® solar/battery inverters)
Compiled for Linux (LE) 32 bit with SQLite support
Commandline Args: -v -finq -nocsv -startdate:20240412
Reading config ‘/usr/local/bin/sbfspot.3/SBFspot.cfg’
Thu Apr 25 15:51:33 2024: INFO: Starting…
sunrise: 06:58
sunset : 17:38
Connecting to Local Network…
Initializing…
SUSyID: 125 - SessionID: 939566226 (0x3800A492)
Inverter IP address: 192.168.1.114 from SBFspot.cfg
Logon OK
SUSyID: 409 - SN: 3006906963
Device Name: SB5.0-1AV-41 963
Device Class: Solar Inverters
Device Type: Sunny Boy 5.0 AV-41
Software Version: 04.00.75.R
Serial number: 3006906963
SUSyID: 409 - SN: 3006906963
Device Status: Ok
SUSyID: 409 - SN: 3006906963
Device Temperature: 0.0°C
SUSyID: 409 - SN: 3006906963
GridRelay Status: Closed
SUSyID: 409 - SN: 3006906963
Pac max phase 1: 5000W
Pac max phase 2: 0W
Pac max phase 3: 0W
SUSyID: 409 - SN: 3006906963
Energy Production:
EToday: 19.216kWh
ETotal: 27054.044kWh
Operation Time: 17958.09h
Feed-In Time : 17293.63h
SUSyID: 409 - SN: 3006906963
DC Spot Data:
String 1 Pdc: 0.493kW - Udc: 237.16V - Idc: 2.083A
String 2 Pdc: 0.227kW - Udc: 319.56V - Idc: 0.711A
SUSyID: 409 - SN: 3006906963
AC Spot Data:
Phase 1 Pac : 0.629kW - Uac: 245.78V - Iac: 2.696A
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.629kW
SUSyID: 409 - SN: 3006906963
Grid Freq. : 50.02Hz
SUSyID: 409 - SN: 3006906963
Current Inverter Time: 25/04/2024 15:51:32
Inverter Wake-Up Time: 25/04/2024 06:29:54
Inverter Sleep Time : 25/04/2024 15:51:32
startTime = 6617ECE0 → 12/04/2024 00:00:00
startTime = 660A1520 → 01/04/2024 13:00:00
Reading events: 2024-Apr-01
Thu Apr 25 15:51:34 2024: INFO: Done.
Use -ad60 to get all data for the missing days.
In your first post you said “latest SBFspot deploy” but actually you´re running a 5YO version 3.5.2 
Lol, that’s all tied up with my dual install of SBFSpot and also sunnyportal-py…
I ran the update with -ad60 and I could see much more data scroll on the screen so that was good - hasn’t yet updated the missing days on PVOutput (45delprat 6.600kW). Figured that might be a scheduled task on their end so we’ll see…
I ran the update per GitHub, and still ran into the USER password being wrong (see below) - interesting, because I now am seeing updates in PVOutput (for 25 and 26 Apr…)
Output of both the -ad60 command, and also the version update below:
pi@raspberrypi:~ $ /usr/local/bin/sbfspot.3/SBFspot -v -finq -nocsv -startdate:20240412 -ad60
SBFspot V3.5.2
Yet another tool to read power production of SMA solar inverters
© 2012-2018, SBF (GitHub - SBFspot/SBFspot: Yet another tool to read power production of SMA® solar/battery inverters)
Compiled for Linux (LE) 32 bit with SQLite support
Commandline Args: -v -finq -nocsv -startdate:20240412 -ad60
Reading config ‘/usr/local/bin/sbfspot.3/SBFspot.cfg’
Fri Apr 26 07:55:17 2024: INFO: Starting…
sunrise: 06:58
sunset : 17:36
Connecting to Local Network…
Initializing…
SUSyID: 125 - SessionID: 851127955 (0x32BB2E93)
Inverter IP address: 192.168.1.114 from SBFspot.cfg
Logon OK
SUSyID: 409 - SN: 3006906963
Device Name: SB5.0-1AV-41 963
Device Class: Solar Inverters
Device Type: Sunny Boy 5.0 AV-41
Software Version: 04.00.75.R
Serial number: 3006906963
SUSyID: 409 - SN: 3006906963
Device Status: Ok
SUSyID: 409 - SN: 3006906963
Device Temperature: 0.0°C
SUSyID: 409 - SN: 3006906963
GridRelay Status: Closed
SUSyID: 409 - SN: 3006906963
Pac max phase 1: 5000W
Pac max phase 2: 0W
Pac max phase 3: 0W
SUSyID: 409 - SN: 3006906963
Energy Production:
EToday: 0.083kWh
ETotal: 27054.397kWh
Operation Time: 17960.91h
Feed-In Time : 17296.08h
SUSyID: 409 - SN: 3006906963
DC Spot Data:
String 1 Pdc: 0.085kW - Udc: 277.57V - Idc: 0.308A
String 2 Pdc: 0.118kW - Udc: 292.70V - Idc: 0.404A
SUSyID: 409 - SN: 3006906963
AC Spot Data:
Phase 1 Pac : 0.128kW - Uac: 239.13V - Iac: 0.876A
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.128kW
SUSyID: 409 - SN: 3006906963
Grid Freq. : 49.97Hz
SUSyID: 409 - SN: 3006906963
Current Inverter Time: 26/04/2024 07:55:16
Inverter Wake-Up Time: 26/04/2024 06:31:08
Inverter Sleep Time : 26/04/2024 07:55:15
startTime = 6617ECE0 → 12/04/2024 00:00:00
startTime = 66169B60 → 11/04/2024 00:00:00
startTime = 661549E0 → 10/04/2024 00:00:00
startTime = 6613F860 → 09/04/2024 00:00:00
startTime = 6612A6E0 → 08/04/2024 00:00:00
startTime = 66114750 → 07/04/2024 00:00:00
startTime = 660FF5D0 → 06/04/2024 00:00:00
startTime = 660EA450 → 05/04/2024 00:00:00
startTime = 660D52D0 → 04/04/2024 00:00:00
startTime = 660C0150 → 03/04/2024 00:00:00
startTime = 660AAFD0 → 02/04/2024 00:00:00
startTime = 66095E50 → 01/04/2024 00:00:00
startTime = 66080CD0 → 31/03/2024 00:00:00
startTime = 6606BB50 → 30/03/2024 00:00:00
startTime = 660569D0 → 29/03/2024 00:00:00
startTime = 66041850 → 28/03/2024 00:00:00
startTime = 6602C6D0 → 27/03/2024 00:00:00
startTime = 66017550 → 26/03/2024 00:00:00
startTime = 660023D0 → 25/03/2024 00:00:00
startTime = 65FED250 → 24/03/2024 00:00:00
startTime = 65FD80D0 → 23/03/2024 00:00:00
startTime = 65FC2F50 → 22/03/2024 00:00:00
startTime = 65FADDD0 → 21/03/2024 00:00:00
startTime = 65F98C50 → 20/03/2024 00:00:00
startTime = 65F83AD0 → 19/03/2024 00:00:00
startTime = 65F6E950 → 18/03/2024 00:00:00
startTime = 65F597D0 → 17/03/2024 00:00:00
startTime = 65F44650 → 16/03/2024 00:00:00
startTime = 65F2F4D0 → 15/03/2024 00:00:00
startTime = 65F1A350 → 14/03/2024 00:00:00
startTime = 65F051D0 → 13/03/2024 00:00:00
startTime = 65EF0050 → 12/03/2024 00:00:00
startTime = 65EDAED0 → 11/03/2024 00:00:00
startTime = 65EC5D50 → 10/03/2024 00:00:00
startTime = 65EB0BD0 → 09/03/2024 00:00:00
startTime = 65E9BA50 → 08/03/2024 00:00:00
startTime = 65E868D0 → 07/03/2024 00:00:00
startTime = 65E71750 → 06/03/2024 00:00:00
startTime = 65E5C5D0 → 05/03/2024 00:00:00
startTime = 65E47450 → 04/03/2024 00:00:00
startTime = 65E322D0 → 03/03/2024 00:00:00
startTime = 65E1D150 → 02/03/2024 00:00:00
startTime = 65E07FD0 → 01/03/2024 00:00:00
startTime = 65DF2E50 → 29/02/2024 00:00:00
startTime = 65DDDCD0 → 28/02/2024 00:00:00
startTime = 65DC8B50 → 27/02/2024 00:00:00
startTime = 65DB39D0 → 26/02/2024 00:00:00
startTime = 65D9E850 → 25/02/2024 00:00:00
startTime = 65D896D0 → 24/02/2024 00:00:00
startTime = 65D74550 → 23/02/2024 00:00:00
startTime = 65D5F3D0 → 22/02/2024 00:00:00
startTime = 65D4A250 → 21/02/2024 00:00:00
startTime = 65D350D0 → 20/02/2024 00:00:00
startTime = 65D1FF50 → 19/02/2024 00:00:00
startTime = 65D0ADD0 → 18/02/2024 00:00:00
startTime = 65CF5C50 → 17/02/2024 00:00:00
startTime = 65CE0AD0 → 16/02/2024 00:00:00
startTime = 65CCB950 → 15/02/2024 00:00:00
ArchiveDayData returned an error: -1
startTime = 65CB67D0 → 14/02/2024 00:00:00
startTime = 65CA1650 → 13/02/2024 00:00:00
startTime = 660A1520 → 01/04/2024 13:00:00
Reading events: 2024-Apr-01
Fri Apr 26 07:55:28 2024: INFO: Done.
pi@raspberrypi:~ $ cd /tmp
pi@raspberrypi:/tmp $ sudo bash -c “$(curl -s https://raw.githubusercontent.com/sbfspot/sbfspot-config/master/sbfspot-config)”
SBFspot Configuration Tool V1.3.5
Running on Raspberry Pi 4 Model B Rev 1.1
Checking whiptail… Installed.
architecture=armhf
Raspbian GNU/Linux 10 (buster)
username=pi
userhome=/home/pi
Minimum SBFspot version supported by this tool is 3.5.0
Request to install latest version (3.9.8)
Searching for existing configuration(s)…
Reading defaults from /var/tmp/sbfspot.3/sbfspot.defaults… Done
Saving defaults to /var/tmp/sbfspot.3/sbfspot.defaults… Done
Performing some checks before installation… Done
Downloading sbfspot-sqlite-arm-linux-buster.tar.gz
Copying files…
SBFspot.db exists
Checking database…
Schema Version=1
Saving existing SBFspot.cfg… Done
Configuring SBFspot… Done
Running SBFspot…
SBFspot V3.9.8
Yet another tool to read power production of SMA solar inverters
© 2012-2023, SBF (GitHub - SBFspot/SBFspot: Yet another tool to read power production of SMA® solar/battery inverters)
Compiled for Linux (LE) 32 bit with SQLite support
Commandline Args: -v -ad0 -am0 -ae0 -sp0 -nocsv -nosql -finq -cfg/usr/local/bin/sbfspot.3/SBFspot.cfg
Reading config ‘/usr/local/bin/sbfspot.3/SBFspot.cfg’
Fri Apr 26 08:01:55 2024: INFO: Starting…
sunrise: 06:58
sunset : 17:36
Connecting to Local Network…
Initialising…
SUSyID: 125 - SessionID: 964633696
Device IP address: 192.168.1.114 from config
Inverter replied: 192.168.1.114 → 409:3006906963
Fri Apr 26 08:01:55 2024: CRITICAL: Logon failed. Check ‘USER’ Password
Fri Apr 26 08:01:55 2024: INFO: Done.
Installation aborted
pi@raspberrypi:/tmp $
No, it should start almost immediately.
Just remove the -startdate:20240412 from the command line like this:
/usr/local/bin/sbfspot.3/SBFspot -v -finq -nocsv -ad60
Still not happy with the password
pi@raspberrypi:/usr/local/bin/sbfspot.3 $ /usr/local/bin/sbfspot.3/SBFspot -v -finq -nocsv -ad60
SBFspot V3.9.8
Yet another tool to read power production of SMA solar inverters
© 2012-2023, SBF (GitHub - SBFspot/SBFspot: Yet another tool to read power production of SMA® solar/battery inverters)
Compiled for Linux (LE) 32 bit with SQLite support
Commandline Args: -v -finq -nocsv -ad60
Reading config ‘/usr/local/bin/sbfspot.3/SBFspot.cfg’
Fri Apr 26 17:03:15 2024: INFO: Starting…
sunrise: 06:58
sunset : 17:36
Connecting to Local Network…
Initialising…
SUSyID: 125 - SessionID: 904615930
Device IP address: 192.168.1.114 from config
Inverter replied: 192.168.1.114 → 409:3006906963
Fri Apr 26 17:03:15 2024: CRITICAL: Logon failed. Check ‘USER’ Password
Fri Apr 26 17:03:15 2024: INFO: Done.
That will not change unless you have the correct user pw…
But with -installer -password:**** it works, no?
I’ve synchronised both user and installer to the same one, and 100% confident SBFspot is using that too (set and reset multiple times cos I can’t get rid of the error - connecting with that pw with Sunny Explorer too
Last option I have is to check if there aren´t any spaces before or after the PW in SBFspot.cfg