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

[Tuicemen]

Dave_x10_L You don't need to do this being a beta tester!
The donation is fixed @ $15 US.

[HA Dave]

The donation is fixed @ $15 US.

I was thrilled to donate!!! I am hyped about this real advancement for X10 and Home Automation. Thank you for the software. AND thank-You for setting up the paypal to except U.S. Dollars. It really would be a pain to convert those Canadian liters to US Dollars when balancing a check book (he he).

[Alan V]

Okay Tuicemen, I'm hooked.  Happy to have just donated.

[Tuicemen]

Thanks Guys!!
Just install latest build with the installer. No issues so far!
I'll run it over night to give it a test run.
Baring any issues popping up,it looks like tomorrow morning will be official release!

[cantbreak80]

Well, my machinery is giving me fits...the xp is now only booting up to a blue screen and the vista machine is still not ready for prime time.
And, my iPhone doesn't play nice with either machine.  Oh, well...I don't know what I did to screw these things up and I'm sure I won't know
what I did when I fix them.

I look forward to solving all my equipment ills and getting that BlueWatch add on up and running.  I know it'll be KEWL!

For now, my garage door macros are going to have to continue serving as my occupancy sensor...as long as I don't get them out of sequence.
Since I live alone, that shouldn't be too hard...but I worry about my housesitter throwing a wrench through the radiator. 

[Alan V]

I just installed v0.0.3.8 and encountered some problems.  It seems that because Bluetooth pairing is not used, the phone has to be left in "discoverable" mode.  When the phone is in "discoverable" mode, BlueWatch alternately logs the 48-bit address and the model name of the phone.

But my phone will not remain in "discoverable" mode.  There is a 2 minute delay after which the mode is automatically turned off (most likely for security reasons). 

I think pairing would solve this issue, but that would of course involve more coding.

[Tuicemen]

There is a 2 minute delay after which the mode is automatically turned off (most likely for security reasons).

probably to save battery power too! 

I think pairing would solve this issue, but that would of course involve more coding.

Paring would involve more coding and require the program to ping your phone on a regular basis else it would never see you leave.
I'm not sure how Dave_x10_L has his setup but I know you can setup Paring in Windows, Control Panel\Bluetooth Devices.
Doing this may limit the program even more but is worth a try.
I initialy tried the pinging route but but Dave and I had no success with it!
I'll look more at the ping aspect of BlueTooth and possibly find a solution to add to future releases!
At least you can utilize the when seen triggers even if you have to turn the phone into discovery mode.

[HA Dave]

...I'm not sure how Dave_x10_L has his setup but I know you can setup Paring in Windows, Control Panel\Bluetooth Devices.

I just turned my BT services ON. You might try pairing it to a device... like a headset. Then the phone will look for that device whereever it is.

[Alan V]

I just turned my BT services ON. You might try pairing it to a device... like a headset. Then the phone will look for that device whereever it is.

I had already paired the phone with a headset.  I think the headset pings the phone when the headset is turned on (after the initial pairing) in order to establish a connection.

I think something similar needs to happen with BlueWatch.

Dave_x10_L, maybe your phone never leaves the "discoverable" mode.

[Alan V]

[snip]At least you can utilize the when seen triggers even if you have to turn the phone into discovery mode.

Not quite the "passive" solution I was looking for.

[Tuicemen]

Alan V Do you know what profiles your BT phone uses?
That may help me to find a solution!
The library I have for BT has 3 protocols I can try.
I can build a test program to see if we can ping your phone.
If we can get the test program to work I can write code into BlueWatch for pinging.
You'll need to pare to windows for this method to have a chance of working! 

[aussie mate]

Have just sent off my donation too.
I have been waiting for this software addition to simplify my set up.

I am looking forward to installing it down under in a hot sunny Sydney 

[Alan V]

Alan V Do you know what profiles your BT phone uses?
That may help me to find a solution!
The library I have for BT has 3 protocols I can try.
I can build a test program to see if we can ping your phone.
If we can get the test program to work I can write code into BlueWatch for pinging.
You'll need to pare to windows for this method to have a chance of working! 

I'm not sure how to find out, but I'll look into it.

Thanks for the support.

[Alan V]

Hi Tuicemen,

My phone has Bluetooth 2.1, but is backwards compatible with 1.2
Can you use SDP in your code to find out what profiles are available?  That however, may be a lot of extra work for you.  Otherwise, I'm almost sure that this version supports "Just works" SSP for pairing.

[Tuicemen]

Profiles available are: SerialPortProfile. OBEXFileTransfer and OBEXObjectPush
Most newer phones don't use the SerialPortProfile but I think windows can test this in ControlPanel\BlueToothDevices