Bluetooth connection not being cleared properly after sma-tool is run

[GoogleCodeExporter]

I have a Sunnybeam that communicates over Bluetooth with the inverter. If this 
is connected then I cannot run sma-tool repeatedly.
I can resolve the problem by either logging off the sunnybeam or by running 
sunny-explorer under windows. The inverter can hold 2 connections and will run 
sunnybeam and sunny-explorer together fine.
This seems to suggest that sma-tool is using 2 connections at the same time - 
perhaps until the later connection is successful?

What steps will reproduce the problem?
1. connect sunnybeam to inverter 
2. run sma-tool = successful
3. run sma-tool again = unsuccessful
Resolution -- either
4. Disconect sunnybeam 
5. run sma-tool multiple times = successful
OR
4. boot up hated windows XP machine (built for purpose)
5. run sunny-explorer and connect
6. disconnect sunny-explorer
7. run sma-tool once - successful
8. run sma-tool again - unsuccessful

What is the expected output? What do you see instead?
As the inverter allows 2 bluetooth conections conescutivly I should be able to 
have sunnybeam working and run sma-tool periodically

What version of the product are you using? On what operating system?
Inverter - SM3000-HF30
SMA-tool v0.12
Debian Linux on NSLU2

Please provide any additional information below.

myslug:/home/simon/sma-bluetooth-0.12# ./smatool -d    
variable=Inverter value=3000TLHF
variable=BTAddress value=00:80:25:18:56:8B
variable=BTTimeout value=
variable=Password value=0000
variable=Config value=
variable=File value=sma.in.new
variable=Latitude value=
variable=Longitude value=
variable=MySqlHost value=localhost
variable=MySqlDatabase value=smatool
variable=MySqlUser value=user
variable=MySqlPwd value=password
variable=PVOutputURL value=http://pvoutput.org/service/r1/addstatus.jsp
variable=PVOutputKey value=xxxxxxxxxxxxxxxxxxxxxxxxxx
variable=PVOutputSid value=xxxx
variable=PVOutputSid value=
utc=2011-05-18 22:40 local=2011-05-18 23:40 diff 1 hours
localOffset=1.000000
localOffset=1.000000 isdst=1
tzsecs=1 1
tzsecs=00 01
SELECT data FROM settings WHERE value='schema' 
SELECT DATE_FORMAT( DateTime, "%Y-%m-%d %H:%i:%S" ) FROM DayData ORDER BY 
DateTime DESC LIMIT 1
SELECT if(sunrise < NOW(),1,0) FROM Almanac WHERE date= DATE_FORMAT( NOW(), 
"%Y-%m-%d" ) 
SELECT if( dd.datetime > al.sunset,1,0) FROM DayData as dd left join Almanac as 
al on al.date=DATE(dd.datetime) and al.date=DATE(NOW()) WHERE 1 ORDER BY 
dd.datetime DESC LIMIT 1
datefrom=2011-05-18 23:30:00 dateto=2011-05-18 23:40:00
Error connecting to 00:80:25:18:56:8B
Error connecting to 00:80:25:18:56:8B
Error connecting to 00:80:25:18:56:8B
Error connecting to 00:80:25:18:56:8B

Original issue reported on code.google.com by simon.t....@googlemail.com on 18 May 2011 at 10:48

[GoogleCodeExporter]

this is always a range issue with the bt device for me....    make sure you are 
only a few feet away or possibly try a new (non cheap/Chinese) device.   Others 
have said that solves connection issues.

Original comment by mcknigh...@gmail.com on 27 Jun 2011 at 8:29

[GoogleCodeExporter]

this is fixed in 0.15

Original comment by stephenb...@gmail.com on 27 Nov 2011 at 4:16

• Changed state: Fixed