Re: [mh] Dual band PLM death after 5 years

On Tue, Jun 04, 2019 at 05:46:36PM -0400, Carl McGrath wrote:
>    It has been a while since I had to do this, but here are my "notes to
>    self" on how to remotely link
>    I2CS Insteon devices.
> 
>                Running MH 3.1, no longer         
>    Jun 6, 2016 necessary to manually link I2CS   
>                units via push button, do via web 
>                interface (ia7)                   
>                                                  Step 1 - Put PLM into     
>                                                  initiate Linking as       
>                                                  Controller mode           
>                                                  Step 2 - Send link to     
>                                                  interface command to      
>                                                  remote I2CS unit          
>                                                  be sure to select action, 

Actually I found out that it's now a lot easier than it used to be.

1) go to insteon list, select device, and 'link to interface'
2) there is no step 2

This puts the remote I2 device into linking mode, links to it, and then
even syncs all the links it's missing (more than once if it's a KPL).

I thought the security restriction forced you to physically start
linking on the device, but it seems that you don't need to do so.

And sure enough, some devices forced me to go push the button to link,
while some others did not.
08/06/2019 17:57:12  Running: garage2 neon kpl link to interface
08/06/2019 17:57:12  [Insteon_PLM] DEBUG2: Sending obj=$garage2_neon_kpl; command=get_engine_version incurred delay of 0.00 seconds; starting hop-count: 0
Sending  PLM raw data: 026228a418000d00
Received PLM raw data: 026228a418000d0006
Processing PLM raw data: 026228a418000d0006
Received PLM acknowledge: obj=$garage2_neon_kpl; command=get_engine_version
Received PLM raw data: 025028a4184c14aea50d02
Processing PLM raw data: 025028a4184c14aea50d02
Message received with 1 hops left, delaying next transmit by 150 milliseconds to avoid collisions.
PLM command:insteon_received; Device command:get_engine_version; type:direct; group: 
DEBUG3: Adding hop count of 0 to hop_array of $garage2_neon_kpl
WARN!! encountered a nack message () for $garage2_neon_kpl.  It may be unplugged, have a burned out bulb, or this may be a new I2CS type device that must first be manually linked to the PLM using the set button.
WARN: Now calling message failure callback: $garage2_neon_kpl->_get_engine_version_failure();$garage2_neon_kpl->link_to_interface_i2cs("01","01")

Now I'm dealing with never ending scan all changed link tables and sync
all links, but it doesn't converge easily. I get a lot of these:
 [Scan all link tables] WARN, unable to  complete a scan of the following devices: $lvr_kpl, $kitchen_kpl, $garage2_neon_kpl, $corridor_mbr, $corridor_kpl,
and then sync all links won't work because it tells me the aldb for many
devices is out of date, even if I say force sync all links.

I also tried to find a DB I could just wipe with all mh insteon saved
data, but I'm not sure if I found the right one.

Still going at it, a few hours in...

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 ....
                                      .... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/                       | PGP 7F55D5F27AAF9D08


________________________________________________________
To unsubscribe from this list, go to: https://lists.sourceforge.net/lists/listinfo/misterhouse-users