I have the Belkin F8T012 working ok with the Bluetooth Connector, except for an eventual issue I believe is related to the RSSI vaules and an arithmetic operation going bad.
HomeSeer 2.3.0.0 on WinXPpro SP3 and quite stable
BTConnector hspi_bt.dll 2.48.2.2 registered Using 'Discover Service' for up to 4 devices
Belkin F8T012 dongle
Widcomm BT stack 4.0.1.2401 <- From Device Manager
BT Connector - Network0: WidComm Bluetooth Stack 4.0.1.2401 Enabled= True AutoDiscovery=False AutoDiscoveryInterval=123
The Belkin is working pretty well with poll times around 120 sec. Range is limited by the connected bt device, not the Belkin F8T012, at about 20ft indoors thru multiple floors & walls. Right at 30ft for line of sight thru windows onto the deck. Also of influenece is a 2.4gHz cordless phone system within 6ft (I will replace this with a DECT6 system as soon as I can wean the wife off of her favorite phone).
I disabled any of the services offered by the bt stack/dongle down to just a few, but left the PAN network on and ocassionally connected to a 5th bt device which does not leave the area and is not polled or setup for use with the BT Connector. The Belkin dongle is on one of the legacy 12mbs usb ports and is the only device on that root hub.
I tweaked the boolean as follows (minor) based on signal strengths:
3 Strong Device Signal @(Network0)>0
2 Device Signal OK @(Network0)>-10
1 Device Signal Low @(Network0)>-25
One can watch the device values move between states by moving the devices around the house.
I have the 'report lost' values set at 5, which is about 10-12 minutes to determine the 'away' state. I use a premisis alarm system ARM/DISARM STAY/AWAY outputs to distinguish the primary HOME AWAY state. I use the BT Connector to distinguish *who* is home. So the 10-12 minutes is an acceptable time for me.
It helps tremendously if, once you are done configuring the bt parameters on the configuration page, to exit gacefully out, close HomeSeer and restart it and then leave all the bluetooth things alone. Do not even check status on the bt devices until several poll cycles have elapsed. If you can reboot after you exit out of HomeSeer and let the usb interface reset, so much the better I have found.
Here is the problem: If a device 'leaves' or is on the fringe, about 75% of the time (but not always), the BTConnector & dongle combination reports a VERY LARGE but negative signal level. The second device that enters the 'away' state *and* results in the same VERY LARGE but negative signal level, then something goes awry and the plugin dongle combination goes south. Many times the main HS log will report 'BT dongle not found' .
So far, if the bt devices remain in range, there are no issues. Something related to that VERY LARGE but negative signal level (derived from an RSSI from the stack?) reminds me of a "Divide By Zero" issue. Something arithmetic is going wrong somewhere in the handling of the signal level numbers. I am not a programmer type, so I can't tell for sure, but that would be my guess. If we can figure this out and correct, I think we would have a nice improvement to the BT Connector.
Any ideas anyone?
HomeSeer 2.3.0.0 on WinXPpro SP3 and quite stable
BTConnector hspi_bt.dll 2.48.2.2 registered Using 'Discover Service' for up to 4 devices
Belkin F8T012 dongle
Widcomm BT stack 4.0.1.2401 <- From Device Manager
BT Connector - Network0: WidComm Bluetooth Stack 4.0.1.2401 Enabled= True AutoDiscovery=False AutoDiscoveryInterval=123
The Belkin is working pretty well with poll times around 120 sec. Range is limited by the connected bt device, not the Belkin F8T012, at about 20ft indoors thru multiple floors & walls. Right at 30ft for line of sight thru windows onto the deck. Also of influenece is a 2.4gHz cordless phone system within 6ft (I will replace this with a DECT6 system as soon as I can wean the wife off of her favorite phone).
I disabled any of the services offered by the bt stack/dongle down to just a few, but left the PAN network on and ocassionally connected to a 5th bt device which does not leave the area and is not polled or setup for use with the BT Connector. The Belkin dongle is on one of the legacy 12mbs usb ports and is the only device on that root hub.
I tweaked the boolean as follows (minor) based on signal strengths:
3 Strong Device Signal @(Network0)>0
2 Device Signal OK @(Network0)>-10
1 Device Signal Low @(Network0)>-25
One can watch the device values move between states by moving the devices around the house.
I have the 'report lost' values set at 5, which is about 10-12 minutes to determine the 'away' state. I use a premisis alarm system ARM/DISARM STAY/AWAY outputs to distinguish the primary HOME AWAY state. I use the BT Connector to distinguish *who* is home. So the 10-12 minutes is an acceptable time for me.
It helps tremendously if, once you are done configuring the bt parameters on the configuration page, to exit gacefully out, close HomeSeer and restart it and then leave all the bluetooth things alone. Do not even check status on the bt devices until several poll cycles have elapsed. If you can reboot after you exit out of HomeSeer and let the usb interface reset, so much the better I have found.
Here is the problem: If a device 'leaves' or is on the fringe, about 75% of the time (but not always), the BTConnector & dongle combination reports a VERY LARGE but negative signal level. The second device that enters the 'away' state *and* results in the same VERY LARGE but negative signal level, then something goes awry and the plugin dongle combination goes south. Many times the main HS log will report 'BT dongle not found' .
So far, if the bt devices remain in range, there are no issues. Something related to that VERY LARGE but negative signal level (derived from an RSSI from the stack?) reminds me of a "Divide By Zero" issue. Something arithmetic is going wrong somewhere in the handling of the signal level numbers. I am not a programmer type, so I can't tell for sure, but that would be my guess. If we can figure this out and correct, I think we would have a nice improvement to the BT Connector.
Any ideas anyone?
Comment