[AHP ADD-ON] BlueWatch (Control via BlueTooth or WIFI Detection)

[Tuicemen]

IT WORKS

Well, I was not about to give up on this.  I did some searching on the net for my Rocketfish bluetooth adapter and found this http://www.serialio.com/support/LaserChamp/3rdPartyRemove.php. This article shows how to use any bluetooth adapter with the windows stacks.  I felt that my frustrations with this were things that others may encounter, so I felt this to be a MUST POST.  Click on the link above and scroll down to the section "How To Hack Windows Bluetooth to support any Bluetooth adapter!".  Follow the instructions listed as a guide for your version of bluetooth adapter.  This article has you modify the "bth.inf" file.  I ALWAYS recommend that if you are changing a windows file of any kind that you make a backup of the original file before making any changes..

Glad to here you found a way!
There usually is away to do something if one is persistant enough!  
Thanks for sharing your findings I'm sure it will benefit someone.
I'll also add the link you supplied to the BlueWatch web site!

[yancy]

I also had a non-Windows bluetooth driver installed.  Used dbemowsk's tip and got bluewatch to see my BB.  I'm running the Trial Version just to see if this is going to work for my needs.  After discovering and adding my BB to the watched list, I set 2 different x10 commands to execute, when when found and one when lost.  When found it fires the correct command, however when lost it does nothing.
Is this a limitation in the trial version?

Also, it only fires the found command once.  I'm assuming that is by design to keep from running the same command over and over.  I'm also assuming, (since the lost function doesn't appear to work), that if it sees a lost signal it resets so the next found does fire the command.

Also, just checked log, and it doesn't appear like it is logging every single scan.  I'm missing many entries that I would expect to see.

Help.

[Tuicemen]

I couldn't remember what all I had changed in the trial version 

After discovering and adding my BB to the watched list, I set 2 different x10 commands to execute, when when found and one when lost.  When found it fires the correct command, however when lost it does nothing.
Is this a limitation in the trial version?

If BlueWatch is seeing a disconnect it should fire the configured X10 command, this wasn't disabled in the trial.

Also, it only fires the found command once.  I'm assuming that is by design to keep from running the same command over and over.  I'm also assuming, (since the lost function doesn't appear to work), that if it sees a lost signal it resets so the next found does fire the command.

That's correct
The info screen will show if a device has been detected as lost, as well you should get a pop-up screen for that device when it is detected as lost.

Also, just checked log, and it doesn't appear like it is logging every single scan.  I'm missing many entries that I would expect to see.

Help.

The log file will only display devices not in the watched device list and logging has to be enabled.
Log file is limited only to Size in the trial.
In order for the lost detect function to work properly you can not have the watched device setup in the Windows Bluetooth devices.

[HA Dave]

I just ordered me a couple extra USB BlueTooth dongles (thinking an antenna mod may be in my future). I am not sure everyone knows where to find these cheap easy to use devices... (or even what they look like).
http://www.geeks.com/details.asp?invtid=ES-388&cpc=SCH

[yancy]

I couldn't remember what all I had changed in the trial version 

After discovering and adding my BB to the watched list, I set 2 different x10 commands to execute, when when found and one when lost.  When found it fires the correct command, however when lost it does nothing.
Is this a limitation in the trial version?

If BlueWatch is seeing a disconnect it should fire the configured X10 command, this wasn't disabled in the trial.
you can not have the watched device setup in the Windows Bluetooth devices.

I've double checked my settings as well as the Windows Bluetooth setup and there is no other device capturing my BB.  Since a lost signal is never being recognized, BW won't change it's status so the "Found" device triggers the command again.  If I close BW and restart, it will find and trigger the found command again.  Lost never gets triggered.

[Tuicemen]

yancy

If I close BW and restart, it will find and trigger the found command again.  Lost never gets triggered.

This is typical if you have your Bt Device setup in windows.

Go to Control Panel\Bluetooth Devices
Under Devices select device you wish  BlueWatch to monitor click remove.
Dave_x10_L   I have acouple of the mini ones coming

[yancy]

yancy

If I close BW and restart, it will find and trigger the found command again.  Lost never gets triggered.

This is typical if you have your Bt Device setup in windows.

Go to Control Panel\Bluetooth Devices
Under Devices select device you wish  BlueWatch to monitor click remove.
Dave_x10_L   I have acouple of the mini ones coming

I don't have any BT devices listed in Bluetooth Devices under control panel.  The list is empty.

[Tuicemen]

yancy Clear the devices from BlueWatch watched list
Turn off your Bluetooth Device
Restart BlueWatch
Press the Discovery button
Is BlueWatch still seeing your device? 

[yancy]

yancy Clear the devices from BlueWatch watched list
Turn off your Bluetooth Device
Restart BlueWatch
Press the Discovery button
Is BlueWatch still seeing your device? 

Bluewatch does not see the device after I do the above.

[Tuicemen]

Ok good sign!
Turn on your device, press discover then add to the watched list.
Don't worry about adding any info in the device configuration just press save.
Press the info button Brings up the "Watched Bluetooth..." screen
After a few seconds you should see a pop up with the device name
Your device should switch from disconnected to connected
Now turn off you Bluetooth device
After a bout 10-15 seconds (double that if you have dual disconnect checked in the settings)the device should switch to disconnected and you should get another pop up.
Are you seeing a disconnect & or the pop ups? 

[yancy]

Interesting result:

Rediscovered, which worked fine.

Opened Watched BlueTooth Device Status window.  BB shows in Disconnected then goes to connected.  I get the default voice message saying I'm using the Trial Version of Bluewatch and the popup screen showing my device name.

I turn discovery off on the BB and after several seconds my BB entry goes to the Disconnected window.  However, I don't get a voice message or the popup window.  (These latter 2 never occured.)

I turn my discovery on again, but the status never returns to connected.

It appears that the disconnect process within BlueWatch may not be completing 100%, and that's why the disconnect message never runs and a reconnect never occurs.

The cycle can be repeated just by shutting down BlueWatch and restarting it.

I've also tried with other BT devices I have and get the same result.

[Tuicemen]

Man I hate Vista
Sure would be easier if I had a tesPC with it on!
Well at least I know where to start looking!
thanks yancy
Voice message(nag) only happens once per session.(didn't want to go over board)

[dbemowsk]

A suggestion for the BlueWatch software.  IF POSSIBLE, give the user the option to not have the little popup window show when a device is discovered or lost.

Dan B.

[HA Dave]

I see the latest version of BlueWatch is 4.7. I am currently using 4.2. How do I get the latest greatest?

[Tuicemen]

The original link sent to you will work for the latest release Dave.
If you've lost the link, let me know and I'll email you a new link.