This project has moved and is read-only. For the latest updates, please go here.

Bluetooth connection issue

Topics: 1. General, 5. Support
Jan 29, 2016 at 9:00 PM
Edited Jan 29, 2016 at 10:59 PM
I can see the inverter when I do hcitool scan, but can't get it to connect.

Commandline Args: -cfg/usr/local/bin/sbfspot.3/SBFspot_1.cfg -v -finq -nocsv
Reading config '/usr/local/bin/sbfspot.3/SBFspot_1.cfg'
Fri Jan 29 20:54:32 2016: INFO: Starting...
sunrise: 14:48
sunset : 01:15
Connecting to 00:08:25:20:30:4D (1/10)
Initializing...
SUSyID: 125 - SessionID: 874685252 (0x3422A344)
recv() returned an error: 104
Fri Jan 29 20:55:04 2016: CRITICAL: Failed to initialize communication with inverter.
Jan 30, 2016 at 10:00 AM
Try another Bluetooth dongle for your RPi - This helps in most cases. More info here
This has no impact on your connection, but have a look at the timezone in the config file. Sunrise and sunset have weird values.
Jan 30, 2016 at 3:12 PM
What is strange is that it connected fine with this Bluetooth dongle using the last version, 301. Had a problem with the Pi and had to reinstall the operating software and the SBFspot.
Feb 2, 2016 at 10:51 PM
Edited Feb 2, 2016 at 10:53 PM
hej cabledave,

2questions:
-A- are your certain about the BT address for most SMA inverters it starts with "00:80:25:xx" and NOT "00:08:25:xx"
please control

-B- if there are further problems
-B.1- can you execute sbfspot including, in your command line, the debug options -d5 -v5
-B.2- redirect the output to file

command -cfg/usr/local/bin/sbfspot.3/SBFspot_1.cfg -d5 -v5 -finq -nocsv 1>>yourlog-ou.txt 2>>yourlog-er.txt

and send the files via private mail to me or sbf

kind regards wim
Marked as answer by SBF on 2/25/2016 at 12:23 PM
Feb 3, 2016 at 3:38 PM
Hi Willie,

Excellent catch! That was exactly what it was. Corrected the BT address and works perfectly. Thanks for your help. Very much appreciated.

Dave
Feb 3, 2016 at 5:03 PM
dear cabledav, the forum is used to assist in solving problems

for that reason,
  • can you do us the favour and execute SBFspot with the faulty condition == wrong destination addreess
    AND with the debug options that i did mention above
command -cfg/usr/local/bin/sbfspot.3/SBFspot_1.cfg -d5 -v5 -finq -nocsv 1>>yourlog-ou.txt 2>>yourlog-er.txt
and send the log files via private mail

Rational:
  • in your first information - one reads that sbfspot received a correct "connected" reply
  • followed by failing communications
  • your log files might help to identify the source of the "connected" status
thanks for your cooperation wim