Announcement

**Kamikaze** · December 13, 2006, 07:18 PM

Welp, didn't make it but a couple of hours this time. As you can see in the included log, it was working fine, and then it stopped. My phone was still on and in the same general area within the house. My wife's phone is sitting in the kitchen, almost directly over the BT dongle, about 8' below.

Brian

12/13/2006 6:26:40 PM BT Debug Polling Lindas Phone (Method=DiscoverService) on Network0 returned signal strength=0
12/13/2006 6:27:11 PM BT Debug Polling Brians Phone (Method=DiscoverService) on Network0 returned signal strength=-13
12/13/2006 6:27:14 PM BT Debug Polling Lindas Phone (Method=DiscoverService) on Network0 returned signal strength=0
12/13/2006 6:27:48 PM BT Debug Polling Brians Phone (Method=DiscoverService) on Network0 returned signal strength=-13
12/13/2006 6:27:50 PM BT Debug Polling Lindas Phone (Method=DiscoverService) on Network0 returned signal strength=0
12/13/2006 6:28:21 PM BT Debug Polling Brians Phone (Method=DiscoverService) on Network0 returned signal strength=-13
12/13/2006 6:28:23 PM BT Debug Polling Lindas Phone (Method=DiscoverService) on Network0 returned signal strength=0
12/13/2006 6:28:55 PM BT Debug Polling Brians Phone (Method=DiscoverService) on Network0 returned signal strength=-13
12/13/2006 6:28:57 PM BT Debug Polling Lindas Phone (Method=DiscoverService) on Network0 returned signal strength=0
12/13/2006 6:29:31 PM BT Debug Polling Brians Phone (Method=DiscoverService) on Network0 returned signal strength=-13
12/13/2006 6:29:32 PM BT Debug Polling Lindas Phone (Method=DiscoverService) on Network0 returned signal strength=0
12/13/2006 6:30:04 PM BT Debug Polling Brians Phone (Method=DiscoverService) on Network0 returned signal strength=-13
12/13/2006 6:30:24 PM BT Debug Error while polling Lindas Phone: Service lookup timed out
12/13/2006 6:30:24 PM BT Debug Polling Lindas Phone (Method=DiscoverService) on Network0 returned signal strength=-2147483648
12/13/2006 6:30:24 PM BT Debug Device Lindas Phone lost. LostCount=1 LostConfirm=2
12/13/2006 6:30:54 PM BT Debug Error while polling Brians Phone: Service lookup timed out
12/13/2006 6:30:54 PM BT Debug Polling Brians Phone (Method=DiscoverService) on Network0 returned signal strength=-2147483648
12/13/2006 6:30:54 PM BT Debug Device Brians Phone lost. LostCount=1 LostConfirm=2
12/13/2006 6:30:55 PM BT Debug Error while polling Lindas Phone: A service discovery is already pending
12/13/2006 6:30:55 PM BT Debug Polling Lindas Phone (Method=DiscoverService) on Network0 returned signal strength=-2147483648
12/13/2006 6:30:55 PM BT Debug Bluetooth Device Lindas Phone value changed to 0
12/13/2006 6:31:24 PM BT Debug Error while polling Brians Phone: A service discovery is already pending
12/13/2006 6:31:24 PM BT Debug Polling Brians Phone (Method=DiscoverService) on Network0 returned signal strength=-2147483648
12/13/2006 6:31:24 PM BT Debug Bluetooth Device Brians Phone value changed to 0
12/13/2006 6:31:25 PM BT Debug Error while polling Lindas Phone: A service discovery is already pending
12/13/2006 6:31:25 PM BT Debug Polling Lindas Phone (Method=DiscoverService) on Network0 returned signal strength=-2147483648
12/13/2006 6:31:54 PM BT Debug Error while polling Brians Phone: A service discovery is already pending
12/13/2006 6:31:54 PM BT Debug Polling Brians Phone (Method=DiscoverService) on Network0 returned signal strength=-2147483648
12/13/2006 6:32:15 PM BT Debug Error while polling Lindas Phone: Service lookup timed out
12/13/2006 6:32:15 PM BT Debug Polling Lindas Phone (Method=DiscoverService) on Network0 returned signal strength=-2147483648
12/13/2006 6:32:24 PM BT Debug Error while polling Brians Phone: A service discovery is already pending
12/13/2006 6:32:24 PM BT Debug Polling Brians Phone (Method=DiscoverService) on Network0 returned signal strength=-2147483648
12/13/2006 6:32:45 PM BT Debug Error while polling Lindas Phone: A service discovery is already pending
12/13/2006 6:32:45 PM BT Debug Polling Lindas Phone (Method=DiscoverService) on Network0 returned signal strength=-2147483648
12/13/2006 6:33:14 PM BT Debug Error while polling Brians Phone: Service lookup timed out

**stipus** · December 13, 2006, 08:15 PM

Someone reported the same problem a month ago, and he was using a non supported Widcomm stack (too old). Which BT stack, and what version of the stack are you using ?

I also had this problem with an old phone, and in fact it was the phone BT stack going wild. It doesn't seem to be your case, because both phones are suddenly lost at the same time. Can you confirm it works again if you don't touch the phones and just restart HomeSeer.

Which version of the plugin are you using ? Latest is V0.42.2.2 available from the updater.

You can also try the following:

- Increase the poll delay. From the log, it seems your BT stack/dongle didn't finish the previous service discovery, when the plugin asks the stack for the next round of discovery.

- If it doesn't work, can you try with other polling methods such as autodiscovery or ConnectService ?

**Kamikaze** · December 14, 2006, 02:28 PM

Originally posted by stipus

Someone reported the same problem a month ago, and he was using a non supported Widcomm stack (too old). Which BT stack, and what version of the stack are you using ?

WIDCOMM 2.0.0.0

Originally posted by stipus

I also had this problem with an old phone, and in fact it was the phone BT stack going wild. It doesn't seem to be your case, because both phones are suddenly lost at the same time. Can you confirm it works again if you don't touch the phones and just restart HomeSeer.

See the log below. The phone was on the counter, but HS showed it "away". I didn't touch the phone, just restarted HS.
Also, for the record, my wife's phone is only 1 week old.... ;-D

Originally posted by stipus

Which version of the plugin are you using ? Latest is V0.42.2.2 available from the updater.

40.2.2, latest as of a week or so ago... I'll check the updater.

Originally posted by stipus

- Increase the poll delay. From the log, it seems your BT stack/dongle didn't finish the previous service discovery, when the plugin asks the stack for the next round of discovery.

I thought that, but I went from the "default" of 10secs to 30 secs.... how long would you suggest??

Originally posted by stipus

- If it doesn't work, can you try with other polling methods such as autodiscovery or ConnectService ?

I'll try the new version first, and see how that goes. I can try uping the poll time some more, but don't really want that to be the final solution (don't really need it if it takes minutes to know if my phone is within range or not). Thanks for the reply....

Brian

12/14/2006 2:17:12 PM ~ ~BT Debug~ ~Error while polling Lindas Phone: A service discovery is already pending
12/14/2006 2:17:12 PM ~ ~BT Debug~ ~Polling Lindas Phone (Method=DiscoverService) on Network0 returned signal strength=-2147483648
12/14/2006 2:17:12 PM ~ ~BT Debug~ ~Error while polling Brians Phone: A service discovery is already pending
12/14/2006 2:17:12 PM ~ ~BT Debug~ ~Polling Brians Phone (Method=DiscoverService) on Network0 returned signal strength=-2147483648
12/14/2006 2:17:37 PM ~ ~BT Debug~ ~ShutdownIO() called
12/14/2006 2:18:48 PM ~ ~BT Connector~ ~BT Connector V0.40.2.2 Copyright 2006 stipus at stipus dot com
12/14/2006 2:18:48 PM ~ ~BT Debug~ ~BT Connector : Debug Mode activated. Waiting 10 secs...
12/14/2006 2:18:59 PM ~ ~BT Debug~ ~BT Connector : Network0: WidComm Bluetooth Stack 2.0.0.0 Enabled= True AutoDiscovery=False AutoDiscoveryInterval=0
12/14/2006 2:18:59 PM ~ ~BT Debug~ ~BT Connector : 2 Bluetooth device(s) configured
12/14/2006 2:19:42 PM ~ ~BT Debug~ ~Error while polling Lindas Phone: Failed to find services on the device due to a connection error
12/14/2006 2:19:42 PM ~ ~BT Debug~ ~Polling Lindas Phone (Method=DiscoverService) on Network0 returned signal strength=-2147483648
12/14/2006 2:19:42 PM ~ ~BT Debug~ ~Device Lindas Phone lost. LostCount=1 LostConfirm=2
12/14/2006 2:19:44 PM ~ ~BT Debug~ ~Polling Brians Phone (Method=DiscoverService) on Network0 returned signal strength=-7
12/14/2006 2:19:44 PM ~ ~BT Debug~ ~Bluetooth Device Brians Phone value changed to 1
12/14/2006 2:20:24 PM ~ ~BT Debug~ ~Error while polling Lindas Phone: Failed to find services on the device due to a connection error
12/14/2006 2:20:24 PM ~ ~BT Debug~ ~Polling Lindas Phone (Method=DiscoverService) on Network0 returned signal strength=-2147483648
12/14/2006 2:20:24 PM ~ ~BT Debug~ ~Bluetooth Device Lindas Phone value changed to 0
12/14/2006 2:20:28 PM ~ ~BT Debug~ ~Polling Brians Phone (Method=DiscoverService) on Network0 returned signal strength=-13
12/14/2006 2:21:07 PM ~ ~BT Debug~ ~Error while polling Lindas Phone: Failed to find services on the device due to a connection error
12/14/2006 2:21:07 PM ~ ~BT Debug~ ~Polling Lindas Phone (Method=DiscoverService) on Network0 returned signal strength=-2147483648
12/14/2006 2:21:08 PM ~ ~BT Debug~ ~Polling Brians Phone (Method=DiscoverService) on Network0 returned signal strength=-8
12/14/2006 2:21:49 PM ~ ~BT Debug~ ~Error while polling Lindas Phone: Failed to find services on the device due to a connection error
12/14/2006 2:21:49 PM ~ ~BT Debug~ ~Polling Lindas Phone (Method=DiscoverService) on Network0 returned signal strength=-2147483648
12/14/2006 2:21:57 PM ~ ~BT Debug~ ~Polling Brians Phone (Method=DiscoverService) on Network0 returned signal strength=-5
12/14/2006 2:22:31 PM ~ ~BT Debug~ ~Error while polling Lindas Phone: Failed to find services on the device due to a connection error
12/14/2006 2:22:31 PM ~ ~BT Debug~ ~Polling Lindas Phone (Method=DiscoverService) on Network0 returned signal strength=-2147483648
12/14/2006 2:22:33 PM ~ ~BT Debug~ ~Polling Brians Phone (Method=DiscoverService) on Network0 returned signal strength=-5

**stipus** · December 14, 2006, 03:16 PM

I thought that, but I went from the "default" of 10secs to 30 secs.... how long would you suggest??

30 seconds should be OK.

You should try an other polling method... it seems Widcomm 2.0.0.0 has problem when too many service discoveries are sent.

If you still have problem with the other polling methods, I'll send you another set of Bluetooth Support dlls for you to try.

**Kamikaze** · December 14, 2006, 03:58 PM

Originally posted by stipus

30 seconds should be OK.

You should try an other polling method... it seems Widcomm 2.0.0.0 has problem when too many service discoveries are sent.

Okay, just switched it to AUTODISCOVERY. We'll see what happens.

If you still have problem with the other polling methods, I'll send you another set of Bluetooth Support dlls for you to try.

Thanks. Hopefully, this is all I need. BTW, when I upgraded to 42.2.2, the first time HS started, it did not see the phone! I restarted a second time, and it picked it up, but that's the first time that's happened.

Thanks again for the quick responses. I'll post again when I now more.

Brian

**Kamikaze** · December 15, 2006, 06:52 PM

Well, unfortunately, all the above steps did nothing. Things ran for less than 24 hours, and I've "lost" my phones again. I'm running v42.2.2, Widcomm 2.0.0.0, Autodiscovery, and a 30 sec poll. Still get the same "A service discovery is already pending " error. Guess I'll try the 3rd method....

Brian

**stipus** · December 15, 2006, 08:21 PM

I don't understand how you can get this error if you are running in auto-discovery mode. In this mode no service discovery is launched by the plugin.

Are you sure you changed the poll method to autodiscovery for each device ?

Both steps below must be done:

1) In the Bluetooth Networks configuration tab, autodiscovery must be enabled (checked), and autodiscovery interval set to 30 seconds.

2) In the Bluetooth Devices configuration tab, the Poll Method column must be set to AutoDiscovery for all devices.

From what you wrote, I think you forgot one of the 2 steps.

**darren-mc** · December 16, 2006, 04:57 AM

Stipus,

With the new version when any of my remote clients are started on the first scan they always fail to find the devices...this is happening on both my WidComm and MS stacks. After the first scan I have no issues with the WidComm stacks.

However, my MS device is no longer correctly performing the device translation..

Code:

10:04:12 AutoDiscovery found device (00:00:3A:69:86:90)
10:04:48 AutoDiscovery lost device (00:60:57:DA:B3:3F)

Any ideas?

Cheers,

Darren

**stipus** · December 16, 2006, 05:20 AM

That's weird because there has been no change at all in the Bluetooth client. It has just been recompiled with a new version number.

However, my MS device is no longer correctly performing the device translation

Autodiscovery mode cannot perform any device translation, as it just gets the device address. The plugin needs to actualy connect to the device to get its name.

However, I can remember I changed the default device polling method from DiscoverService to AutoDiscovery. I'm not sure, but this might explain why you saw these changes ?

**darren-mc** · December 16, 2006, 02:02 PM

On the MS stack if you perform a scan then the system will correctly report the devices and the exisiting presence in the config file....it the goes on to not report the devices. (WidComm are OK).

I changed the config of the MS network (just to check communication) and the client correctly picked up the config changes.

**Kamikaze** · December 16, 2006, 04:12 PM

Originally posted by stipus

I don't understand how you can get this error if you are running in auto-discovery mode. In this mode no service discovery is launched by the plugin.

Are you sure you changed the poll method to autodiscovery for each device ?

Both steps below must be done:

1) In the Bluetooth Networks configuration tab, autodiscovery must be enabled (checked), and autodiscovery interval set to 30 seconds.

2) In the Bluetooth Devices configuration tab, the Poll Method column must be set to AutoDiscovery for all devices.

From what you wrote, I think you forgot one of the 2 steps.

You were correct. I forgot to reenable it in the networks tab. I did that, but I ended up having to reboot to get it to find my phone, regardless of what the method was or how many times I restarted HS. It's currently set to AUTO, with a rate of 10 secs under network, and 30 secs. under each device. Guess we'll see how long this lasts....

B

**Kamikaze** · December 16, 2006, 04:39 PM

Well, switching to AutoDiscovery didn't work. It seemed to find the phone when it HS first came up, then dropped like a rock.

12/16/2006 4:21:36 PM BT Debug Polling Brians Phone (Method=DiscoverService) on Network0 returned signal strength=0
12/16/2006 4:21:38 PM Database Item Saving Device Brian's Phone
12/16/2006 4:21:48 PM BT Debug AutoDiscovery found 1 device(s)
12/16/2006 4:22:10 PM BT Debug AutoDiscovery found 0 device(s)
12/16/2006 4:22:10 PM BT Debug Polling Lindas Phone (Method=AutoDiscovery) on Network0 returned signal strength=-2147483648
12/16/2006 4:22:10 PM BT Debug Device Lindas Phone lost. LostCount=1 LostConfirm=2
12/16/2006 4:22:10 PM BT Debug Polling Brians Phone (Method=AutoDiscovery) on Network0 returned signal strength=-2147483648
12/16/2006 4:22:10 PM BT Debug Device Brians Phone lost. LostCount=1 LostConfirm=2
12/16/2006 4:22:31 PM BT Debug AutoDiscovery found 0 device(s)
12/16/2006 4:22:40 PM BT Debug Polling Lindas Phone (Method=AutoDiscovery) on Network0 returned signal strength=-2147483648
12/16/2006 4:22:40 PM BT Debug Bluetooth Device Lindas Phone value changed to 0
12/16/2006 4:22:40 PM BT Debug Polling Brians Phone (Method=AutoDiscovery) on Network0 returned signal strength=-2147483648
12/16/2006 4:22:40 PM BT Debug Bluetooth Device Brians Phone value changed to 0
12/16/2006 4:22:53 PM BT Debug AutoDiscovery found 0 device(s)
12/16/2006 4:23:15 PM BT Debug AutoDiscovery found 0 device(s)

I even rebooted again, and that didn't help. I switched back to DiscoverService, and it picked it right up.

<TABLE cellSpacing=2 cellPadding=0 width="100%" border=0><TBODY><TR><TD class=LOGDateTime0 noWrap align=left>12/16/2006 4:43:29 PM </TD><TD class=LOGType0 align=left colSpan=3>BT Debug </TD><TD class=LOGEntry0 align=left colSpan=8>Polling Lindas Phone (Method=AutoDiscovery) on Network0 returned signal strength=-2147483648</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>12/16/2006 4:43:29 PM </TD><TD class=LOGType1 align=left colSpan=3>BT Debug </TD><TD class=LOGEntry1 align=left colSpan=8>Polling Brians Phone (Method=AutoDiscovery) on Network0 returned signal strength=-2147483648</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>12/16/2006 4:43:39 PM </TD><TD class=LOGType0 align=left colSpan=3>BT Debug </TD><TD class=LOGEntry0 align=left colSpan=8>BT Connector : Network0: WidComm Bluetooth Stack 2.0.0.0 Enabled= True AutoDiscovery=False AutoDiscoveryInterval=10</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>12/16/2006 4:43:42 PM </TD><TD class=LOGType1 align=left colSpan=3>BT Debug </TD><TD class=LOGEntry1 align=left colSpan=8>AutoDiscovery found 0 device(s)</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>12/16/2006 4:43:53 PM </TD><TD class=LOGType0 align=left colSpan=3>Database Item </TD><TD class=LOGEntry0 align=left colSpan=8>Saving Device Linda's Phone</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>12/16/2006 4:44:01 PM </TD><TD class=LOGType1 align=left colSpan=3>Database Item </TD><TD class=LOGEntry1 align=left colSpan=8>Saving Device Brian's Phone</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>12/16/2006 4:44:07 PM </TD><TD class=LOGType0 align=left colSpan=3>BT Debug </TD><TD class=LOGEntry0 align=left colSpan=8>Polling Brians Phone (Method=DiscoverService) on Network0 returned signal strength=0</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>12/16/2006 4:44:07 PM </TD><TD class=LOGType1 align=left colSpan=3>BT Debug </TD><TD class=LOGEntry1 align=left colSpan=8>Bluetooth Device Brians Phone value changed to 1</TD></TR></TBODY></TABLE>

I'm not sure what's going on anymore....

B

**Kamikaze** · December 18, 2006, 04:38 AM

Stipus,

Well, I resorted to upping the polling interval to 60 secs and had an interesting occurrence last night. It actually dropped the phones because of the discovery in process, and then it cleared itself. That's a first in all this....

You mentioned sending me another set of "bluetooth support dlls" for me to try. At this point, that's my last hope to get this to work....

Brian

12/17/2006 10:50:46 PM BT Debug Polling Brians Phone (Method=DiscoverService) on Network0 returned signal strength=-13
12/17/2006 10:50:48 PM BT Debug Polling Lindas Phone (Method=DiscoverService) on Network0 returned signal strength=-7
12/17/2006 10:51:51 PM BT Debug Polling Brians Phone (Method=DiscoverService) on Network0 returned signal strength=-13
12/17/2006 10:52:11 PM BT Debug Error while polling Lindas Phone: Service lookup timed out
12/17/2006 10:52:11 PM BT Debug Polling Lindas Phone (Method=DiscoverService) on Network0 returned signal strength=-2147483648
12/17/2006 10:52:11 PM BT Debug Device Lindas Phone lost. LostCount=1 LostConfirm=2
12/17/2006 10:53:11 PM BT Debug Error while polling Brians Phone: Service lookup timed out
12/17/2006 10:53:11 PM BT Debug Polling Brians Phone (Method=DiscoverService) on Network0 returned signal strength=-2147483648
12/17/2006 10:53:11 PM BT Debug Device Brians Phone lost. LostCount=1 LostConfirm=2
12/17/2006 10:53:11 PM BT Debug Error while polling Lindas Phone: A service discovery is already pending
12/17/2006 10:53:11 PM BT Debug Polling Lindas Phone (Method=DiscoverService) on Network0 returned signal strength=-2147483648
12/17/2006 10:54:11 PM BT Debug Error while polling Brians Phone: A service discovery is already pending
12/17/2006 10:54:11 PM BT Debug Polling Brians Phone (Method=DiscoverService) on Network0 returned signal strength=-2147483648
12/17/2006 10:54:32 PM BT Debug Error while polling Lindas Phone: Service lookup timed out
12/17/2006 10:54:32 PM BT Debug Polling Lindas Phone (Method=DiscoverService) on Network0 returned signal strength=-2147483648
12/17/2006 10:55:11 PM BT Debug Error while polling Brians Phone: A service discovery is already pending
12/17/2006 10:55:11 PM BT Debug Polling Brians Phone (Method=DiscoverService) on Network0 returned signal strength=-2147483648
12/17/2006 10:55:32 PM BT Debug Error while polling Lindas Phone: A service discovery is already pending
12/17/2006 10:55:32 PM BT Debug Polling Lindas Phone (Method=DiscoverService) on Network0 returned signal strength=-2147483648
12/17/2006 10:56:19 PM BT Debug Polling Brians Phone (Method=DiscoverService) on Network0 returned signal strength=-13
12/17/2006 10:56:19 PM BT Debug Bluetooth Device Brians Phone value changed to 1
12/17/2006 10:56:33 PM BT Debug Polling Lindas Phone (Method=DiscoverService) on Network0 returned signal strength=-11
12/17/2006 10:56:33 PM BT Debug Bluetooth Device Lindas Phone value changed to 1
12/17/2006 10:57:24 PM BT Debug Polling Brians Phone (Method=DiscoverService) on Network0 returned signal strength=-13
12/17/2006 10:57:35 PM BT Debug Polling Lindas Phone (Method=DiscoverService) on Network0 returned signal strength=-9
12/17/2006 10:58:35 PM BT Debug Polling Brians Phone (Method=DiscoverService) on Network0 returned signal strength=-13

**stipus** · December 18, 2006, 12:07 PM

Bluetooth support Dlls

Brian,

Here are 3 sets of Bluetooth support dlls:

Original set included with the plugin:
http://www.stipus.info/download/BT110.zip

New set of dll. I didn't include these with the plugin, because they were obviously incompatible with Darren-mc Bluetooth stack.
http://www.stipus.info/download/BT120.zip

Latest set of dll. I didn't include these with the plugin, because they are incompatible with my own Bluetooth stack...
http://www.stipus.info/download/BT120b.zip

I bought this Bluetools SDK, but unfortunately, I didn't get much support from the lib author to get a good working set of dlls that works in all cases... I know this is very difficult for him because most BT stacks are buggy...

I hope one of these dll sets will be compatible with your BT stack.

stipus

Announcement

Help!

Help!

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment