From: Alan W. <arw...@wo...> - 2002-09-29 14:11:03
|
As a newbie I was NEVER able to get that piece of code to work.. I left it = enabled for months with my BX24-AHT and never once saw the print_log message. I think there is a piece of code elsewhere it relies on, but it baffled me. = Perhaps the key is the tie_event needs to be tied to something else? Because, = I could never find a device being set that was tied to. >> $Remote =3D new X10_MR26; >> $Remote -> tie_event('print_log "MR26 key: $state"'); >> # Enable this code if you want the MA26 to relay >> # incoming RF X10 data to the power line. >> # You may want to limit this to not relay busy motion detectors >> $Transmitter =3D new X10_Item; >> if ($state =3D state_now $Remote and $state =3D~ /^XP2/) { >> print_log "Relaying X10 data from the MR26: $state"; >> set $Transmitter $state; >> } |
From: Alan W. <arw...@wo...> - 2002-09-29 21:16:04
|
I had a MR26, I moved to the BX24-AHT. It handles the RF for me so I didn't = need to code every single item in mh to respond that I had on the RF system. I = had a really long period that I didn't grasp mh doesn't relay received RF to = the powerline automatically. At the time I grasped that, the MR26 code was = pointed out. I could just never get it to work at all. Alan >> So you have a MR26 you have never got to work with mh, or just that >> tie_event code never worked? The above 2 lines should be all it takes, >> along with these 2 mh.ini parms: >> MR26_module =3D X10_MR26 >> MR26_port =3D COM9 >> Bruce |
From: Jack I. <em...@re...> - 2002-09-29 22:43:58
|
Could you provide a detailed account of your BX24-AHT implementation for the rest of us. I know I would greatly appreciate it. Thanks Jack -----Original Message----- From: mis...@li... [mailto:mis...@li...]On Behalf Of Alan Womack Sent: Sunday, September 29, 2002 4:16 PM To: Majordomo leben.com Subject: re: [misterhouse-users] Difficulty with relaying commands I had a MR26, I moved to the BX24-AHT. It handles the RF for me so I didn't need to code every single item in mh to respond that I had on the RF system. I had a really long period that I didn't grasp mh doesn't relay received RF to the powerline automatically. At the time I grasped that, the MR26 code was pointed out. I could just never get it to work at all. Alan >> So you have a MR26 you have never got to work with mh, or just that >> tie_event code never worked? The above 2 lines should be all it takes, >> along with these 2 mh.ini parms: >> MR26_module = X10_MR26 >> MR26_port = COM9 >> Bruce ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ________________________________________________________ To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id65 |
From: Bruce W. <br...@mi...> - 2002-09-29 16:40:24
|
> As a newbie I was NEVER able to get that piece of code to work.. > I left it enabled for months with my BX24-AHT and never once saw > the print_log message. > > I think there is a piece of code elsewhere it relies on, but it > baffled me. Perhaps the key is the tie_event needs to be tied to > something else? Because, I could never find a device being set > that was tied to. > >> $Remote = new X10_MR26; >> $Remote -> tie_event('print_log "MR26 key: $state"'); So you have a MR26 you have never got to work with mh, or just that tie_event code never worked? The above 2 lines should be all it takes, along with these 2 mh.ini parms: MR26_module = X10_MR26 MR26_port = COM9 Bruce |