From: J W. <j...@wy...> - 2005-04-08 14:38:42
|
After accidentally stumbling across a piece of software yesterday (Google brought up a line of their open source code in response to a query), I am now actively pursuing something that I've thought made sense for quite some time: using my bluetooth phone as my "occupancy" trigger. The software (FMA: http://fma.sourceforge.net/index2.htm), is used to interface with bluetooth enabled phones, primarily the Sony Ericsson T610 and Z600. I'd like to start using my Z600 with MisterHouse. FMA basically monitors when the phone is within range and triggers a scriptable event for "Proximity = Near" and "Proximity = Away" when you leave the area. There are also events for disconnects where somehow the proximity didn't get triggered, etc. So, I really have 2 questions: 1. Are there any recommended class 1 bluetooth adapters that will adequately cover my house (split level 950 ft/2 foundation) and possibly (a definite stretch, I know), the rest of my 12,000 ft/2 lot. I"ve got several short range bluetooth adapters, but, at 30 feet in open air and less indoors, they're really only good for "J is in his office" type proximity rather than "J is home" and the former can easily be done already with a motion sensor. 2. The best way to hook up the FMA proximity event to trigger a MisterHouse event. While I'm sure I can hack something together, I'd rather see what the "best" way to do this might be. |
From: J K. <jk...@ne...> - 2005-04-08 18:08:43
|
> After accidentally stumbling across a piece of software yesterday > (Google brought up a line of their open source code in response to a > query), I am now actively pursuing something that I've thought made > sense for quite some time: using my bluetooth phone as my "occupancy" > trigger. > > The software (FMA: http://fma.sourceforge.net/index2.htm), is used to > interface with bluetooth enabled phones, primarily the Sony Ericsson > T610 and Z600. I'd like to start using my Z600 with MisterHouse. > > FMA basically monitors when the phone is within range and triggers a > scriptable event for "Proximity = Near" and "Proximity = Away" when you > leave the area. There are also events for disconnects where somehow the > proximity didn't get triggered, etc. I am planning to use l2ping (part of blues-utils) for the same task. > > So, I really have 2 questions: > > 1. Are there any recommended class 1 bluetooth adapters that will > adequately cover my house (split level 950 ft/2 foundation) and possibly > (a definite stretch, I know), the rest of my 12,000 ft/2 lot. I"ve got > several short range bluetooth adapters, but, at 30 feet in open air and > less indoors, they're really only good for "J is in his office" type > proximity rather than "J is home" and the former can easily be done > already with a motion sensor. I dont know, but in my local shop they have two different Belkin USB dongles. One is labeled 30 ft range, the other is labeled 300 ft range, so there are obviously some differences. > 2. The best way to hook up the FMA proximity event to trigger a > MisterHouse event. While I'm sure I can hack something together, I'd > rather see what the "best" way to do this might be. Good luck Joran Kvalvaag |
From: Robert R. <ro...@fr...> - 2005-04-08 20:58:16
|
Hi, sorry- will lead you maybe OffTopic, but: I'm currently working intensively with Pluto system - www.plutohome.com - (in one sentence: they are trying to bring all best open source apps (also MH) under 1 roof, with decent GUI possibilities) and guess what - bluetooth identification and tracking included - for now, they have working implementation for Symbian 60 phones. Their code is GPL in majority, so can take a peek. They also have nice feature (didn't tried it yet) "follow me", when music/video is moving with you and your phone across the house (they have media clients that do measure Bluetooth signal strentgth from your phone and can locate you this way)... If you ask me, maybe Pluto is pretty much close to what we described when we discussed MH beyond ver 3.... HTH, regards, Rob. ----- Original Message ----- From: "J Kvalvaag" <jk...@ne...> To: <mis...@li...> Sent: Friday, April 08, 2005 7:03 PM Subject: Re: [misterhouse-users] Bluetooth proximity >> After accidentally stumbling across a piece of software yesterday >> (Google brought up a line of their open source code in response to a >> query), I am now actively pursuing something that I've thought made >> sense for quite some time: using my bluetooth phone as my "occupancy" >> trigger. >> >> The software (FMA: http://fma.sourceforge.net/index2.htm), is used to >> interface with bluetooth enabled phones, primarily the Sony Ericsson >> T610 and Z600. I'd like to start using my Z600 with MisterHouse. >> >> FMA basically monitors when the phone is within range and triggers a >> scriptable event for "Proximity = Near" and "Proximity = Away" when you >> leave the area. There are also events for disconnects where somehow the >> proximity didn't get triggered, etc. > > I am planning to use l2ping (part of blues-utils) for the same task. > >> >> So, I really have 2 questions: >> >> 1. Are there any recommended class 1 bluetooth adapters that will >> adequately cover my house (split level 950 ft/2 foundation) and possibly >> (a definite stretch, I know), the rest of my 12,000 ft/2 lot. I"ve got >> several short range bluetooth adapters, but, at 30 feet in open air and >> less indoors, they're really only good for "J is in his office" type >> proximity rather than "J is home" and the former can easily be done >> already with a motion sensor. > > I dont know, but in my local shop they have two different Belkin USB > dongles. > One is labeled 30 ft range, the other is labeled 300 ft range, so there > are > obviously some differences. > >> 2. The best way to hook up the FMA proximity event to trigger a >> MisterHouse event. While I'm sure I can hack something together, I'd >> rather see what the "best" way to do this might be. > > Good luck > Joran Kvalvaag > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > ________________________________________________________ > To unsubscribe from this list, go to: > http://sourceforge.net/mail/?group_id=1365 > |
From: Robert R. <ro...@fr...> - 2005-04-08 21:00:03
|
----- Original Message ----- From: "J Kvalvaag" <jk...@ne...> To: <mis...@li...> Sent: Friday, April 08, 2005 7:03 PM Subject: Re: [misterhouse-users] Bluetooth proximity >> After accidentally stumbling across a piece of software yesterday >> (Google brought up a line of their open source code in response to a >> query), I am now actively pursuing something that I've thought made >> sense for quite some time: using my bluetooth phone as my "occupancy" >> trigger. >> >> The software (FMA: http://fma.sourceforge.net/index2.htm), is used to >> interface with bluetooth enabled phones, primarily the Sony Ericsson >> T610 and Z600. I'd like to start using my Z600 with MisterHouse. >> >> FMA basically monitors when the phone is within range and triggers a >> scriptable event for "Proximity = Near" and "Proximity = Away" when you >> leave the area. There are also events for disconnects where somehow the >> proximity didn't get triggered, etc. > > I am planning to use l2ping (part of blues-utils) for the same task. > >> >> So, I really have 2 questions: >> >> 1. Are there any recommended class 1 bluetooth adapters that will >> adequately cover my house (split level 950 ft/2 foundation) and possibly >> (a definite stretch, I know), the rest of my 12,000 ft/2 lot. I"ve got >> several short range bluetooth adapters, but, at 30 feet in open air and >> less indoors, they're really only good for "J is in his office" type >> proximity rather than "J is home" and the former can easily be done >> already with a motion sensor. > > I dont know, but in my local shop they have two different Belkin USB > dongles. > One is labeled 30 ft range, the other is labeled 300 ft range, so there > are > obviously some differences. > Well Bluetooth communication goes in two directions. So there is not much benefit from 300ft range of dongle if you phone bluetooth range is limited.. HTH, regards, Rob. |
From: J W. <jw...@pr...> - 2005-04-09 13:29:40
|
> Well Bluetooth communication goes in two directions. So there is not > much benefit from 300ft range of dongle if you phone bluetooth range > is limited.. True. However, with 2 parts that may vary, one costing $50 and the other $200 and you already need another one of the $50 end, I'd rather make sure that the adapter is, at the very least, not serving as a limiting factor. If the adapter covers the whole house, I'll know that I'm using the phone to its highest potential. |
From: J W. <j...@wy...> - 2005-04-11 14:04:49
|
J Wynia wrote: > >> Well Bluetooth communication goes in two directions. So there is not >> much benefit from 300ft range of dongle if you phone bluetooth range >> is limited.. > > > True. However, with 2 parts that may vary, one costing $50 and the > other $200 and you already need another one of the $50 end, I'd rather > make sure that the adapter is, at the very least, not serving as a > limiting factor. If the adapter covers the whole house, I'll know that > I'm using the phone to its highest potential. > Found this article over the weekend about boosting bluetooth to a *mile*. I don't want it to go that far, but an interesting story nonetheless. http://www.popsci.com/popsci/how2/article/0,20967,714017,00.html |
From: J W. <jw...@pr...> - 2005-04-08 19:33:44
|
J Kvalvaag wrote: >I am planning to use l2ping (part of blues-utils) for the same task. > > > >I dont know, but in my local shop they have two different Belkin USB dongles. >One is labeled 30 ft range, the other is labeled 300 ft range, so there are >obviously some differences > > Yeah. Those are the 2 classes: Class 1 is supposed to be 300 ft/100m and class 2 is supposed to be 30ft/10m. However, with all wireless technology, just because it is "rated" for 300 ft doesn't mean it actually will. Most of the online reviews of bluetooth adapters seem to focus on the fact it worked at all and don't make any reference to distance. I'd like to avoid having to walk away from my computer in all directions to see how far I can go, if there's one that people have found consistently of high quality. > > >>2. The best way to hook up the FMA proximity event to trigger a >>MisterHouse event. While I'm sure I can hack something together, I'd >>rather see what the "best" way to do this might be. >> >> > >Good luck >Joran Kvalvaag > > >------------------------------------------------------- >SF email is sponsored by - The IT Product Guide >Read honest & candid reviews on hundreds of IT Products from real users. >Discover which products truly live up to the hype. Start reading now. >http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >________________________________________________________ >To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365 > > |
From: Mike J. <mj...@sc...> - 2005-04-15 22:44:51
|
J Kvalvaag wrote: >>FMA basically monitors when the phone is within range and triggers a >>scriptable event for "Proximity = Near" and "Proximity = Away" when you >>leave the area. There are also events for disconnects where somehow the >>proximity didn't get triggered, etc. >> >> > >I am planning to use l2ping (part of blues-utils) for the same task. > > Hi, Sorry for joining this conversation late, but I just now had time. l2ping does not measure received signal strength (RSSI), so does not answer the question of proximity - it only answers the question of presence. It's the wrong tool for the job. I just found and tested this code, and it works perfectly: http://perl.jonallen.info/projects/bluetooth This script is set to trigger xscreensaver, but you can use it for anything. I had to turn down the $rssi_threshold to -2 in order to tune "near" proximity to be about 1 meter from my bluetooth hub. With -4, I was "near" even when I was 6 meters away from the BT hub! Tested with: ---------------------------------------------------------------------------------------------- OS: FC3 BT device: Logitech Bluetooth Hub (comes with the MX-900 mouse) Phone: Nokia Communicator 9500 BR, -- mike |
From: Bruce W. <wi...@ch...> - 2005-04-19 13:32:21
|
Mike Jackson wrote: > l2ping does not measure received signal strength (RSSI), so does not > answer the question of proximity - it only answers the question of > presence. It's the wrong tool for the job. > > I just found and tested this code, and it works perfectly: > > http://perl.jonallen.info/projects/bluetooth > > This script is set to trigger xscreensaver, but you can use it for > anything. I had to turn down the $rssi_threshold to -2 in order to tune > "near" proximity to be about 1 meter from my bluetooth hub. With -4, I > was "near" even when I was 6 meters away from the BT hub! > > Tested with: > ---------------------------------------------------------------------------------------------- > > OS: FC3 > BT device: Logitech Bluetooth Hub (comes with the MX-900 mouse) > Phone: Nokia Communicator 9500 That code looks like just the ticket! Except it didn't work here :( I installed bluez-libs-2.16.tar.gz and bluez-utils-2.16.tar.gz on my Linux RH8 box, then the perl Inline::C module (which also required I install ParseRecDescent). All those installs went ok. Plugging in Linksys USBBT100 Bluetooth USB interface, I see what look like good errata in the /var/log/messages file. But when I run the xscreensaver.pl program, it gives me the 'Device not available' messages. I also tried it on a friends Linux box with a more recent Linux kernel, along with another USB adapter (forgot to check which one it was), but I got the same fail there. I double checked the mac addresses on both adapters. Anyone else on Linux try this code? Mike, any other tricks you can remember that you used to get it to work? Maybe running one of the BlueZ utilities would help diagnose the problem? Bruce |
From: Mike J. <mj...@sc...> - 2005-04-19 14:27:55
Attachments:
bluetooth
|
Bruce Winter wrote: > That code looks like just the ticket! Except it didn't work here :( > > I installed bluez-libs-2.16.tar.gz and bluez-utils-2.16.tar.gz on my > Linux RH8 box, then the perl Inline::C module (which also required I > install ParseRecDescent). All those installs went ok. > > Plugging in Linksys USBBT100 Bluetooth USB interface, I see what look > like good errata in the /var/log/messages file. But when I run the > xscreensaver.pl program, it gives me the 'Device not available' > messages. You are missing the hci0 device... You can test it like this. Nothing will work before this is recognized. # hcitool dev Devices: hci0 00:07:61:0B:98:35 It might help for you to have a look at how recent redhats start up bluetooth. I've attached the /etc/init.d/bluetooth script. BTW, I am doing some bluetooth programming in C now, because of the existence of libbluetooth, but perl is my language of choice. I am thinking of implementing a perl interface to some of the functions... Of course, this isn't portable so it's probably not what you want in MH. Unfortunately, there are no pure-perl BT libs available. HTH, -- mike |
From: Bruce W. <wi...@ch...> - 2005-04-20 02:51:53
|
Mike Jackson wrote: > You are missing the hci0 device... You can test it like this. Nothing > will work before this is recognized. > > # hcitool dev > Devices: > hci0 00:07:61:0B:98:35 > > It might help for you to have a look at how recent redhats start up > bluetooth. I've attached the /etc/init.d/bluetooth script. Thanks for the info. hcitool lists no devices. Trying your startup script shows that the rfcomm fails with this msg: Can't open RFCOMM control socket: So my guess is that rfcomm needs to talk to a newer kernel than what I have on my old crusty RH8 box (2002, 2.14.18). I've have to dug up another box and try a newer Linux. First I should probably buy a cell phone! Somehow I managed to get my boys cell phones but not me. Probably get a Nokia (maybe the 7610) so I'd have the option of playing with the plutohome symbian application. > BTW, I am doing some bluetooth programming in C now, because of the > existence of libbluetooth, but perl is my language of choice. > I am thinking of implementing a perl interface to some of the > functions... Of course, this isn't portable so it's probably not what > you want in MH. > Unfortunately, there are no pure-perl BT libs available. It is hard to make hardware drivers like that portable. Would be most interested in whatever you came up with. Bruce |
From: Tom V. <tv...@gm...> - 2005-04-21 01:17:04
|
While Nokia bluetooth shopping, be wary of their 6230. Nice phone BUT the bluetooth is not all that it should be. I can't get it to properly interface with my Palm (Zire 72) to send sms or dial calls via bluetooth. After several rounds of finger pointing (Palm says Nokia problem, Nokia says Palm problem) finally found a 3rd party developer that contends that Palm's BT stack is not all it should be while Nokia strays from the BT standard a bit. I will say that I've been able to connect to a Plantronics BT headset and a Trendware BT adapter for the computer. What I've done so far with them has worked. Good Luck! > I've have to dug up another box and try a newer Linux. First I should > probably buy a cell phone! Somehow I managed to get my boys cell phones > but not me. Probably get a Nokia (maybe the 7610) so I'd have the > option of playing with the plutohome symbian application. |
From: Mike J. <mj...@sc...> - 2005-04-21 20:03:53
|
Tom Vanderpool wrote: >bluetooth. After several rounds of finger pointing (Palm says Nokia >problem, Nokia says Palm problem) finally found a 3rd party developer >that contends that Palm's BT stack is not all it should be while Nokia >strays from the BT standard a bit. > > While this was previously the case, it's not anymore. The current Nokia BT stacks in the new phones are perfectly standards compliant. I can not comment about Palm, because I don't own any Palm devices which have BT. A few years ago, I bought the first BT phone which Nokia produced, the 6310i (which I still have). The initial version(s) of the firmware on the phone wasn't interoperable with non-Nokia BT devices, but this was fixed in the newer versions of the firmware. I simply took my phone to a dealer, and was able to get a firmware upgrade for free since the phone was still under warranty. It works like a charm today, and I use it to provide GPRS over BT connection to my laptop, which has an SCM USB BT dongle attached. I just got a 9500 and the BT stack works just fine with all of my other devices, none of which are made by Nokia... I am so in awe of the features of the 9500. I highly recommend it, if it only fits in your budget. I guess the 6310i will be retired now, but I won't get rid of it! BR, -- mike |
From: Bruce W. <wi...@ch...> - 2005-04-23 02:30:02
|
Bruce Winter wrote: > Mike Jackson wrote: > Thanks for the info. hcitool lists no devices. Trying your startup > script shows that the rfcomm fails with this msg: > > Can't open RFCOMM control socket: > > So my guess is that rfcomm needs to talk to a newer kernel than what I > have on my old crusty RH8 box (2002, 2.14.18). I sneaked some time on a friends recently installed Linux. I found a bluetoothinit script, which ran ok, starting rfcomm and some other things. This time the hcitool to work! oscar@slimmy:/tmp/bbw$ hcitool dev Devices: hci0 00:0C:41:E2:32:8D Unfortunately, the perl code still didn't work: oscar@slimmy:/tmp/bbw$ perl b1.pl Device not available Monitoring RSSI for device 00:0C:41:E2:32:8D ()\nDevice not available Any other suggestions on how to debug? Bruce |
From: Mike J. <mj...@sc...> - 2005-04-23 19:51:21
|
Bruce Winter wrote: > Bruce Winter wrote: > >> Mike Jackson wrote: >> Thanks for the info. hcitool lists no devices. Trying your startup >> script shows that the rfcomm fails with this msg: >> >> Can't open RFCOMM control socket: >> >> So my guess is that rfcomm needs to talk to a newer kernel than what >> I have on my old crusty RH8 box (2002, 2.14.18). > > > I sneaked some time on a friends recently installed Linux. I found a > bluetoothinit script, which ran ok, starting rfcomm and some other > things. This time the hcitool to work! > > oscar@slimmy:/tmp/bbw$ hcitool dev > Devices: > hci0 00:0C:41:E2:32:8D > > Unfortunately, the perl code still didn't work: > > oscar@slimmy:/tmp/bbw$ perl b1.pl > Device not available > Monitoring RSSI for device 00:0C:41:E2:32:8D ()\nDevice not available Just do: chmod +x bl.pl ./bl.pl The script finds the device like this: $device = $ARGV[0] || "hci0"; I think it might have become confused with the above command. I don't know what it thought $ARGV[0] was in that case... -- mike |
From: Bruce W. <wi...@ch...> - 2005-04-24 20:45:08
|
Mike Jackson wrote: > Just do: > > chmod +x bl.pl > ./bl.pl > > > The script finds the device like this: > > $device = $ARGV[0] || "hci0"; > > I think it might have become confused with the above command. I don't > know what it thought $ARGV[0] was in that case... Hmmm, your script seems different than mine. The xscreensaver.pl script (both original and patched) that I got from here: http://perl.jonallen.info/projects/bluetooth Has this: my $mac = $ARGV[0] || '00:0A:D9:3F:84:E5'; I changed it to my mac address. I also tried "hci0", like your example, but that didn't work either. When I use my real mac address, as I think the code wants, it fails right away with the 'Device not available' message. If I use an arbitrary string, or hci0, then it seems to past that message, but fails later with the 'Could not find device' message. Could you post the errata you get when it works you? Anyone else give this code a try yet? Bruce |
From: Sean W. <li...@su...> - 2005-04-25 05:23:57
Attachments:
smime.p7s
|
> When I use my real mac address, as I think the code wants, it fails=20 > right away with the 'Device not available' message. If I use an=20 > arbitrary string, or hci0, then it seems to past that message, but=20 > fails later with the 'Could not find device' message. >=20 > Could you post the errata you get when it works you? >=20 > Anyone else give this code a try yet? >=20 > Bruce >=20 Just guessing here, but did you try running it as root? It could very well be a permissions thing. If you are trying it as root, did you try it as a normal user? Good luck. I'm really looking forward to getting some bluetooth stuff myself now. --Sean |
From: Gregg L. <gr...@li...> - 2005-04-26 23:36:40
|
Bruce Winter wrote: > Mike Jackson wrote: > >> Just do: >> >> chmod +x bl.pl >> ./bl.pl >> >> >> The script finds the device like this: >> >> $device = $ARGV[0] || "hci0"; >> >> I think it might have become confused with the above command. I don't >> know what it thought $ARGV[0] was in that case... > > > Hmmm, your script seems different than mine. The xscreensaver.pl > script (both original and patched) that I got from here: > > http://perl.jonallen.info/projects/bluetooth > > Has this: > > my $mac = $ARGV[0] || '00:0A:D9:3F:84:E5'; > > I changed it to my mac address. I also tried "hci0", like your > example, but that didn't work either. > > When I use my real mac address, as I think the code wants, it fails > right away with the 'Device not available' message. If I use an > arbitrary string, or hci0, then it seems to past that message, but > fails later with the 'Could not find device' message. > > Could you post the errata you get when it works you? > > Anyone else give this code a try yet? > Yes--it works for me. However, the mac address referenced above required the address of my phone--not the adapter (which I had originally thought from the discussions and assumed). I ended up trying a lot of different things--some of which may or may not have led to it eventually working (I'll post a follow-up once I get to what I think are the key steps). I do know that the first "hoop" was to rebuild my custom kernel.org kernel (2.6.6) because the stock defaults don't enable the bluetooth modules and I didn't think to enable them on the prior kernel build. Also, I'm virtually certain that I had to run "hciconfig hci0 up" to cause the adapter to be enabled (which makes sense if it follows the NIC analog). Once the adapter was "up", I used hcitool to get raw info, scan and create connections. I figured this needed to work reliably before I started playing w/ scripts that I didn't necessarily undertand. FWIW: I'm using the Belkin class 1 adapter. Gregg |
From: Gregg L. <gr...@li...> - 2005-04-26 23:53:37
|
Quoting Gregg Liming (4/26/05 7:34 PM): > Yes--it works for me. However, the mac address referenced above > required the address of my phone--not the adapter (which I had > originally thought from the discussions and assumed). I ended up trying > a lot of different things--some of which may or may not have led to it > eventually working (I'll post a follow-up once I get to what I think are > the key steps). I do know that the first "hoop" was to rebuild my > custom kernel.org kernel (2.6.6) because the stock defaults don't enable > the bluetooth modules and I didn't think to enable them on the prior > kernel build. Also, I'm virtually certain that I had to run "hciconfig > hci0 up" to cause the adapter to be enabled (which makes sense if it > follows the NIC analog). Once the adapter was "up", I used hcitool to > get raw info, scan and create connections. I figured this needed to > work reliably before I started playing w/ scripts that I didn't > necessarily undertand. FWIW: I'm using the Belkin class 1 adapter. Forgot to post the applicable part of my DMESG as requested: hub 2-0:1.0: USB hub found hub 2-0:1.0: 2 ports detected usb 2-2: new full speed USB device using address 2 Bluetooth: Core ver 2.4 NET: Registered protocol family 31 Bluetooth: HCI device and connection manager initialized Bluetooth: HCI socket layer initialized Bluetooth: HCI USB driver ver 2.5 Also, these show using lsmod: hci_usb 11008 2 bluetooth 40420 1 hci_usb And, an output showing the adapter status via hciconfig -a: [gliming@baltar gliming]$ hciconfig -a hci0: Type: USB BD Address: 00:0A:3A:56:C1:3A ACL MTU: 192:8 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN RX bytes:10147 acl:0 sco:0 events:964 errors:0 TX bytes:4790 acl:0 sco:0 commands:953 errors:0 Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: Link mode: SLAVE ACCEPT Name: 'WINDOWS-2000' Class: 0x000000 Service Classes: Unspecified Device Class: Miscellaneous, HCI Ver: 1.1 (0x1) HCI Rev: 0x33c LMP Ver: 1.1 (0x1) LMP Subver: 0x33c Manufacturer: Cambridge Silicon Radio (10) |
From: Bruce W. <wi...@ch...> - 2005-04-30 03:50:05
|
Gregg Liming wrote: >> Anyone else give this code a try yet? >> > Yes--it works for me. However, the mac address referenced above > required the address of my phone--not the adapter (which I had > originally thought from the discussions and assumed). Well silly me! Indeed, I was pointing to the adapter mac address. When I switched to the phone address (which I got from looking at it's properties when connected under a windows box), it works! Tried it on 2 different phones (Nokia 7610 and Motorola V551), and worked ok with separate instances running at the same time. Adapter was a Linksys USBBT100. So now I need to build myself a linux box with a newer kernel (I had been borrowing a box from a friend to test the above). I might give the plutohome install disk a spin. Bruce. |
From: Mike J. <mj...@sc...> - 2005-04-30 20:01:48
|
Bruce Winter wrote: > Gregg Liming wrote: > >>> Anyone else give this code a try yet? >>> >> Yes--it works for me. However, the mac address referenced above >> required the address of my phone--not the adapter (which I had >> originally thought from the discussions and assumed). > > > Well silly me! Indeed, I was pointing to the adapter mac address. > When I switched to the phone address (which I got from looking at it's > properties when connected under a windows box), it works! Tried it on > 2 different phones (Nokia 7610 and Motorola V551), and worked ok with > separate instances running at the same time. Adapter was a Linksys > USBBT100. Hi, Glad you figured it out. Sorry I didn't have time to help you. I have been working an enormous amount of overtime here lately :-( -- mike |
From: Robert R. <ro...@fr...> - 2005-05-03 13:22:03
|
----- Original Message ----- From: "Bruce Winter" <wi...@ch...> To: <mis...@li...> Sent: Saturday, April 30, 2005 5:49 AM Subject: Re: [mh] Re: [misterhouse-users] Bluetooth proximity > Gregg Liming wrote: > >>> Anyone else give this code a try yet? >>> >> Yes--it works for me. However, the mac address referenced above required >> the address of my phone--not the adapter (which I had originally thought >> from the discussions and assumed). > > Well silly me! Indeed, I was pointing to the adapter mac address. When I > switched to the phone address (which I got from looking at it's properties > when connected under a windows box), it works! Tried it on 2 different > phones (Nokia 7610 and Motorola V551), and worked ok with separate > instances running at the same time. Adapter was a Linksys USBBT100. > > So now I need to build myself a linux box with a newer kernel (I had been > borrowing a box from a friend to test the above). I might give the > plutohome install disk a spin. > Hi, glad to hear that... I'm also running Plutohome and I must say that I'm impressed - it's by far not complete system, but it gives great potentials... They're pretty opened and interested in connection with Misterhouse, although some better discussion is neede prior that, cause Pluto in some way mimic Misterhouse functionality... The big advantage is more beginners friendly installation.... I'll be happy to discuss and help with MH and plutohome .... Regards, Rob. |
From: Bruce W. <wi...@ch...> - 2005-05-07 17:43:36
|
Robert Rozman wrote: >> So now I need to build myself a linux box with a newer kernel (I had been >> borrowing a box from a friend to test the above). I might give the >> plutohome install disk a spin. >> > Hi, > > glad to hear that... I'm also running Plutohome and I must say that I'm > impressed - it's by far not complete system, but it gives great > potentials... They're pretty opened and interested in connection with > Misterhouse, although some better discussion is neede prior that, cause > Pluto in some way mimic Misterhouse functionality... The big advantage is > more beginners friendly installation.... > > I'll be happy to discuss and help with MH and plutohome .... I pulled the small solarpc.com EPIA ITX box I put in the car a few months back (ended up not using that too much ... the screen was not bright enough for daytime use and I found it was just too tempting to play with the touch screen while I was driving!) and brought it back in into the house for assimilation into the MisterHouse network ;) The Plutohome.com Linux boot from cd install was really slick and painless. I have not had much time to play with it, but I'll confess I'm not sure yet how to leverage it yet. I tried the Pluto Orbiter on an XP box, but it wouldn't connect. My WinCE box I think is too old to run their CE version of orbiter (pre CE.net). I'm not sure how to get the Symbian Orbiter installed on my nifty new bluetooth enabled Nokia 7610. Have you had any luck with Orbiter on any platform? Bruce |
From: Robert R. <ro...@fr...> - 2005-05-07 20:16:49
|
----- Original Message ----- From: "Bruce Winter" <wi...@ch...> To: <mis...@li...> Sent: Saturday, May 07, 2005 7:43 PM Subject: Re: [mh] Re: [misterhouse-users] Bluetooth proximity > Robert Rozman wrote: > >>> So now I need to build myself a linux box with a newer kernel (I had >>> been >>> borrowing a box from a friend to test the above). I might give the >>> plutohome install disk a spin. >>> >> Hi, >> >> glad to hear that... I'm also running Plutohome and I must say that I'm >> impressed - it's by far not complete system, but it gives great >> potentials... They're pretty opened and interested in connection with >> Misterhouse, although some better discussion is neede prior that, cause >> Pluto in some way mimic Misterhouse functionality... The big advantage is >> more beginners friendly installation.... >> >> I'll be happy to discuss and help with MH and plutohome .... > > I pulled the small solarpc.com EPIA ITX box I put in the car a few months > back (ended up not using that too much ... the screen was not bright > enough for daytime use and I found it was just too tempting to play with > the touch screen while I was driving!) and brought it back in into the > house for assimilation into the MisterHouse network ;) > > The Plutohome.com Linux boot from cd install was really slick and > painless. I have not had much time to play with it, but I'll confess I'm > not sure yet how to leverage it yet. I tried the Pluto Orbiter on an XP > box, but it wouldn't connect. My WinCE box I think is too old to run > their CE version of orbiter (pre CE.net). I'm not sure how to get the > Symbian Orbiter installed on my nifty new bluetooth enabled Nokia 7610. > Have you had any luck with Orbiter on any platform? > Hi, yes, I'm running Orbiter on WinXP and Nokia 3650. Mobile phone should be autodetected - if you add Mobile Orbiter device on your system... Sw installs as message attachement... On WinXP Orbiter you should change settings (right IP for Core and device ID for you winxp Orbiter - it's also added on Orbiter's wizard page). There is a strong development going on, so be sure to have latest version.... Also I defined my core as hybrid - that means that it also runs Orbiter - so you can see GUI on computer screen.... Let me know if I can help you further ... Regards, Rob. |
From: Bruce W. <wi...@ch...> - 2005-04-09 20:37:17
|
J Wynia wrote: > The software (FMA: http://fma.sourceforge.net/index2.htm), is used to > interface with bluetooth enabled phones, primarily the Sony Ericsson > T610 and Z600. I'd like to start using my Z600 with MisterHouse. > > FMA basically monitors when the phone is within range and triggers a > scriptable event for "Proximity = Near" and "Proximity = Away" when you > leave the area. There are also events for disconnects where somehow the > proximity didn't get triggered, etc. This would pretty slick! I don't have a bluetooth phone, but would switch to one if we could get this to work. > 2. The best way to hook up the FMA proximity event to trigger a > MisterHouse event. While I'm sure I can hack something together, I'd > rather see what the "best" way to do this might be. Probably a number of ways to do this. The simplest might be to have the fma code write out a status file, than have mh monitor it with something like this: $proximity_bruce_file = new File_Item 'path_to_file'; $proximity_bruce = new Generic_Item; set $proximity_bruce read_all $proximity_bruce_file if file_changed $proximity_bruce_file; Bruce |