Re: [mh] syncing a manually defined scene to remotelinc

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 454-5900

On Thu, Feb 26, 2009 at 07:50:42AM -0500, Gregg Liming wrote:
> >I'd love to fix it myself, but I never got an reply to my account/edit
> >access request to the page owners.
> 
> I fixed it.  Matt holds the keys; shout louder.

I'll ask again. Also, I will need someone to review my notes and
documentation for accuracy since I kept track of hopefully everything a
beginner might stumble on (which will hopefully save you the trouble of
answering the same questions later :) )

> >The other garbage data is still there. Wasn't sync links supposed to 
> >delete local pairings
> >and remove them with the ones mh has?
> 
> No.  Delete orphan links does that.  Also, sync all attempts to the 
> extent that it can; but is not as complete as delete orphan links.

Gotcha. The other thing that got me a few times is that for a remotelinc
scan all links on button1 does everything, whereas I kept doing sync links
on button1, forgetting that I needed to sync links on each button one per
one.
Would you consider a 'sync all links' in the button1 dropdown for symetry?

> >sync links only added one good pairing (button 6), it didn't remove my bad 
> >parings on button 2 & 5.
> >
> >Hell, I even tried remove orphan links on the plm, and I still have:
> >>02/25/2009 23:58:45  [Insteon_Device] aldb 077e87061 [0x0FE8] contlr(06) 
> >>record to 077e87(01), (d1:06, d2:00, d3:00)
> >>02/25/2009 23:58:45  [Insteon_Device] aldb 0f72ec021 [0x0FE0] contlr(02) 
> >>record to 0f72ec(01), (d1:02, d2:00, d3:00)
> 
> It should have.  I can't explain what you are seeing.

One of the two disappeared eventually, the other one only went away when
I did a full reset of the remote. After syncing my config to all buttons
(forgot to sync 6 times and to wait between each button for things to not
step on one another), it worked eventually.

On Thu, Feb 26, 2009 at 08:12:34AM -0500, Gregg Liming wrote:
> >>Hell, I even tried remove orphan links on the plm, and I still have:
> >>>02/25/2009 23:58:45  [Insteon_Device] aldb 077e87061 [0x0FE8] contlr(06) 
> >>>record to 077e87(01), (d1:06, d2:00, d3:00)
> >>>02/25/2009 23:58:45  [Insteon_Device] aldb 0f72ec021 [0x0FE0] contlr(02) 
> >>>record to 0f72ec(01), (d1:02, d2:00, d3:00)
> >
> >It should have.  I can't explain what you are seeing.
> 
> You might try running it again.  If you see any other attempts to delete 
> records, then perhaps something kept it from completing.  From looking 
> at your mht entries, the remotelinc items are defined last; so, orphan 
> processing will be done on all prior items first.  It should continue, 
> but guaranteeing continuity with async processing is difficult and prone 
> to stopping on any error.  If this is the case, then having your full 
> log would have been nice (not to the list as that would not be nice to 
> everyone else) so as to attempt to determine possible cause of stopping.

I couldn't see anything stopping that processing, but I'll admit now that it
was late, and after hours of working on it, I can't truely guarantee
anything anymore :-/
Anyway, a reset took care of it.

On Thu, Feb 26, 2009 at 10:44:57AM -0500, Gregg Liming wrote:
> One last thing... "scan all ..." and "sync all ..." deliberately 
> excludes the RemoteLinc and MotionSensor since their default operation 
> is to be deaf.  Therefore, to ensure accurate memory scan, you must use 
> the device-specific "scan link" function.  I'll add those comments to 
> the wiki later on.  So, any syncing or scanning must be done specific to 
> the device (which is not similarly constrained).  There is no constraint 
> applied to "remove orphans".

Thanks makes sense, thanks for spelling that out.
One possible suggestion for scan all/sync all is to do a quick check on the
remotelincs to see if they happen to be in listening mode, and include them
if they are (although, they seem not to stay in listening mode not long
enough sometimes, so maybe it won't work :-/)

Thanks for you help, I think I'm back in business now, and while it was
work, things are *much* nicer now that they are controlled by mh and pushed
from there.

The only gotcha for me was that I first synced dimmer settings with a ramp
rate of 0.1s as in the example, and when I went to switch to 2s, I was able
to sync to my 2 way switches, but not to my remotelinc:
26/02/2009 11:39:13  [Sync all links] Now syncing links: $rlink_blk1_5 (16 of 17)
26/02/2009 11:39:13  [Insteon_Device] WARN: attempt to add link to $rlink_blk1_1 that already exists! object=$PLM, group=05, is_contr
oller=1
26/02/2009 11:39:13  [Sync all links] Now syncing links: $rlink_blk1_2 (17 of 17)
26/02/2009 11:39:13  [Insteon_Device] WARN: attempt to add link to $rlink_blk1_1 that already exists! object=$PLM, group=02, is_contr
oller=1
26/02/2009 11:39:29  Running: rlink blk1 1 sync links
26/02/2009 11:39:40  Running: rlink blk1 3 sync links
26/02/2009 11:39:40  [Insteon_Device] WARN: attempt to add link to $rlink_blk1_1 that already exists! object=$PLM, group=03, is_contr
oller=1
26/02/2009 11:39:47  Running: rlink blk1 5 sync links
26/02/2009 11:39:47  [Insteon_Device] WARN: attempt to add link to $rlink_blk1_1 that already exists! object=$PLM, group=05, is_contr
oller=1
26/02/2009 11:39:50  Running: rlink blk1 2 sync links
26/02/2009 11:39:50  [Insteon_Device] WARN: attempt to add link to $rlink_blk1_1 that already exists! object=$PLM, group=02, is_contr
oller=1
26/02/2009 11:39:54  Running: rlink blk1 4 sync links
26/02/2009 11:39:54  [Insteon_Device] WARN: attempt to add link to $rlink_blk1_1 that already exists! object=$PLM, group=04, is_contr
oller=1
26/02/2009 11:39:56  Running: rlink blk1 6 sync links
26/02/2009 11:39:56  [Insteon_Device] WARN: attempt to add link to $rlink_blk1_1 that already exists! object=$PLM, group=06, is_contr
oller=1

so right now pushing the buttons on my remotelinc sends a 0.1s ramp rate
and my update in insteon.mht isn't being pushed.
Do I need to reset my remotelinc again and re-push all 6 buttons one per one
with the new ramp rate?

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/  