From: Marc M. <ma...@me...> - 2009-02-27 05:44:20
|
So I know the device is listen only unless you put it in pairing mode (not unlike a remotlinc). But I was hoping to setup my pairings from motion sensor to switches in insteon.mht and just sync them to it instead of doing the manual linking (especially after an earlier run of delete orphan links deleted my pairing between them, when my config was not complete yet). However, the pull down menu in the web interface is definitely lacking the sync links feature. Is that intentional? Could it not be added and work liek a remotelinc sync? Thanks, Marc -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ |
From: Gregg L. <gr...@li...> - 2009-02-27 11:40:47
|
Marc MERLIN wrote: > So I know the device is listen only unless you put it in pairing mode > (not unlike a remotlinc). > > But I was hoping to setup my pairings from motion sensor to switches in > insteon.mht and just sync them to it instead of doing the manual linking > (especially after an earlier run of delete orphan links deleted my pairing > between them, when my config was not complete yet). > > However, the pull down menu in the web interface is definitely lacking the > sync links feature. Is that intentional? IPLD (vice IPLL) are not linkable. I've not tested attempting to manage links w/ the motion sensor via mh. If my memory is correct, it is an i2 device. I suppose you could try setting it to IPLL and see whether you turn it to a brick. > Could it not be added and work liek > a remotelinc sync? See above. If it doesn't work (or you're reluctant to see if you can make it no longer function), then it will likely be a while until I get to it since doing so will depend on some long procrastinated refactoring. Gregg |
From: Marc M. <ma...@me...> - 2009-02-27 15:37:55
|
On Fri, Feb 27, 2009 at 06:40:42AM -0500, Gregg Liming wrote: > Marc MERLIN wrote: > > So I know the device is listen only unless you put it in pairing mode > > (not unlike a remotlinc). > > > > But I was hoping to setup my pairings from motion sensor to switches in > > insteon.mht and just sync them to it instead of doing the manual linking > > (especially after an earlier run of delete orphan links deleted my pairing > > between them, when my config was not complete yet). > > > > However, the pull down menu in the web interface is definitely lacking the > > sync links feature. Is that intentional? > > IPLD (vice IPLL) are not linkable. I've not tested attempting to manage Oh, right. > links w/ the motion sensor via mh. If my memory is correct, it is an i2 > device. I suppose you could try setting it to IPLL and see whether you > turn it to a brick. Sure, what the hell? :) Good news is that it didn't catch fire, but that didn't work either: I couldn't sync links (got no error though), and my two existing manual links to switchlinc relays did not show up. Oh well, it was worth a shot :) For now, defining the link in insteon.mht should be enough so that remove orphan links doesn't wipe the record on the receiving switchlincs If you were curious: 27/02/2009 07:33:20 Running: gar mos1 log links 27/02/2009 07:33:20 [Insteon_Device] link table for $gar_mos1 (devcat: 1001): 27/02/2009 07:33:20 [Insteon_Device] aldb 0ed9ee011 [0x0FF8] contlr(01) record to $PLM(01), (d1:fe, d2:00, d3:00) 27/02/2009 07:33:20 [Insteon_Device] adlb [0x0FF0] is empty 27/02/2009 07:33:52 Running: gar mos1 scan link table 27/02/2009 07:33:52 [Insteon_Device] $gar_mos1 accessing memory at location: 0x0FF8 27/02/2009 07:33:52 [Insteon_PLM] Parsing serial data: 0262118e1c0f280f06 27/02/2009 07:33:52 [Insteon_PLM] Parsing serial data: 0250118e1c0ed9ee23280f 27/02/2009 07:33:52 [Insteon_PLM] Processing message for $gar_mos1 27/02/2009 07:33:52 [Insteon_Device] $gar_mos1 command queued but not yet sent; awaiting ack from prior command 27/02/2009 07:33:52 [Insteon_PLM] Parsing serial data: 0262118e1c0f2bf806 27/02/2009 07:33:53 [Insteon_PLM] Parsing serial data: 0250118e1c0ed9ee272bf8 27/02/2009 07:33:53 [Insteon_PLM] Processing message for $gar_mos1 27/02/2009 07:33:53 [Insteon_Device] $gar_mos1 completed link memory scan 27/02/2009 07:33:53 [Insteon_Device] link table for $gar_mos1 (devcat: 1001): 27/02/2009 07:33:53 [Insteon_Device] adlb [0x0FF8] is empty Cheers, Marc -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ |
From: Gregg L. <gr...@li...> - 2009-02-27 15:54:56
|
Marc MERLIN wrote: >> links w/ the motion sensor via mh. If my memory is correct, it is an i2 >> device. I suppose you could try setting it to IPLL and see whether you >> turn it to a brick. > > Sure, what the hell? :) > > Good news is that it didn't catch fire, but that didn't work either: > I couldn't sync links (got no error though), and my two existing manual links > to switchlinc relays did not show up. > Oh well, it was worth a shot :) > > For now, defining the link in insteon.mht should be enough so that remove > orphan links doesn't wipe the record on the receiving switchlincs Yes, good point. So, this is reminding me once again that I really need to work hard on the refactoring as that is preventing proper i2 support as well as lots of other proper things. Likely, this will mean little bug support and/or minor enhancements until all that is sorted out. Gregg |