Jump to content

Failure during Device Restore

justin.cool

Recommended Posts

justin.cool Member

justin.cool

Posted
Posted

Failure performing a Device Restore         

 

Configuration  Dec 2014

 

ISY-994i IR/PRO, running 4.0.5 and UI 4.0.11

PLM:  2412S  (Have 2413S, but not yet installed)

Approximately 120 Insteon devices:

  • Mainly Switchlincs, Lamplincs, Outletlincs, On/Off Adapters, etc etc
    10 KPL’s – about 15% are dual band units
    Triggerlincs (2)
    RemoteLincs (3)
    RemoteLinc2 (4)
    Controllincs (2)
    Access Points (4) – 2 on each phase from each subpanel
    Dualband LampLinc dimmers (4)
    Dual Band 240V load controller (2) (Normal Open, dual band)
    Signal Linc (2)
    Venstar Thermostats (3) with V2 RF interface
    EZRain/EZFlora Irrigation Controller v.92
     

House is about 4000 sq feet, two floors, but spread out.

  • Two primary subpanels, one secondary.  Secondary is dedicated to dryer, pool filter and water feature, and some outdoor outlets on the patio. 
  • Both primary panels each have a signal linc installed in the panels. 
  • Both primary panels have Leviton 51110-1 120/240 120/240 Volt Single-Phase Panel surge protectors. 
  • All power strips in use in the house are either filtered via X-10 Pro 20 A in line or 15A plug in filters, or do NOT have any surge suppression or noise filtering.
  • No UPS in the system.
  • Numerous other devices are filtered via one of the above or a simple X-10 5A plug in filter or a Leviton in line 5A filter.
  • All thermostat dongles (T1, T2 and T3) are Rev 2.2R

 

Issue

A 2486DWH8 KPL started acting flakey in that some of programmed buttons did not control their assigned scene, either ON or OFF or DIM. 

 

I performed the usual things:

  • Pull out the tab to create an air gap, wait 10 seconds, push back in (without performing a factory reset).  No change. 
  • Attempted to run a Restore Device, generated an error, “cannot communicate with the device”, about 5 minutes into it.
  • Performed a factory reset. 
  • Tried to Restore Device again, same results. 
  • This time I had the Event Viewer going, see below, for the last 20 seconds of the 8 minute attempt to restore the device. 
  • Question #1:  Do I need to try something else, or can you deduce that this KPL has kicked the bucket? 
  • Note 1:  There are 91 records in the PLM device links table for this device.   A device links table compare after the last failure showed that only the first 7 matched, then about 3 were a Record Mismatch, then the rest were  Missing This Record. 
  • From my novice viewpoint, it seems that 8 minutes is a bit long for Device Restore to run and only write the first 10 or so records??? 
  • Question #2:  Could this indicate a new, killer noise source, or a signal sucker?  I did do a lot of "slaying" of those kinds of problems back in 2008 and 2009 when I installed my first 40 or so devices, and have been a bit careful of what and where I plug in new things. 
  • Note 2:  I have attached the full event viewer file.  ISY-Events-Log.v4.2.66__Wed 2014.12.03 11.15.35 PM.txt

 

Wed 12/03/2014 11:14:09 PM : [std-Direct Ack] 10.03.DB-->ISY/PLM Group=0, Max Hops=3, Hops Left=0

Wed 12/03/2014 11:14:09 PM : [iNST-TX-I1  ] 02 62 10 03 DB 0F 29 A0

Wed 12/03/2014 11:14:09 PM : [iNST-ACK    ] 02 62 10.03.DB 0F 29 A0 06          POKE   (A0)

Wed 12/03/2014 11:14:10 PM : [iNST-ERX    ] 02 51 10 03 DB 0F D5 9D 54 D6 5E D5 D6 DF 3D BF DB 03 8F 00 19 16 DE 41 BF

Wed 12/03/2014 11:14:10 PM : [std-Cleanup ] 10.03.DB-->ISY/PLM Group=94, Max Hops=0, Hops Left=1

Wed 12/03/2014 11:14:19 PM : [iNST-TX-I1  ] 02 62 10 03 DB 0F 28 0E

Wed 12/03/2014 11:14:19 PM : [iNST-ACK    ] 02 62 10.03.DB 0F 28 0E 06          SET-MSB(0E)

Wed 12/03/2014 11:14:28 PM : [iNST-TX-I1  ] 02 62 10 03 DB 0F 28 0E

Wed 12/03/2014 11:14:28 PM : [iNST-ACK    ] 02 62 10.03.DB 0F 28 0E 06          SET-MSB(0E)

Wed 12/03/2014 11:14:28 PM : [iNST-SRX    ] 02 50 10.03.DB 0F.D5.9D 23 28 0E    SET-MSB(0E)

Wed 12/03/2014 11:14:28 PM : [std-Direct Ack] 10.03.DB-->ISY/PLM Group=0, Max Hops=3, Hops Left=0

Wed 12/03/2014 11:14:28 PM : [iNST-TX-I1  ] 02 62 10 03 DB 0F 2B F3

Wed 12/03/2014 11:14:28 PM : [iNST-ACK    ] 02 62 10.03.DB 0F 2B F3 06          PEEK   (F3)

Wed 12/03/2014 11:14:32 PM : [10 3 DB 1   ] Link   33 : 0EF0 [A20116A02BFF1F07] *Failed Writing [A20116A02BFF1F07]

Wed 12/03/2014 11:14:32 PM : [D2D EVENT   ] Event [10 3 DB 1] [ERR] [1] uom=0 prec=-1

Wed 12/03/2014 11:14:32 PM : [   10 3 DB 1]      ERR   1

 

 

Link to comment
Share on other sites
stusviews Advanced

stusviews

Posted
Posted

Before doing anything else, ensure that the firmware and the Administrative Console are the same version. Yours aren't. (It may not have anything to do with your difficulty, but troubleshooting requires it.)

 

BTW, the latest official release is 4.2.18

Link to comment
Share on other sites
justin.cool Member

justin.cool

Posted
  • Author
Posted

Stusviews,

 

Thanks for the prompt response. 

 

I am aware that my Admin and ISY firmware are different.  Further, if I remember correctly, I was specifically provided this admin version, by the UD staff.  Driven by a power failure that my ISY did not recover from (hung state of some sort) and somehow related to the fact that I have DirecTV and Sonos on my network.  Possibly too much traffic from these two???  Don't remember exactly.  In any case, my entire system has been working well since the firmware upgrade in July 2014. 

 

While I cannot rule out this mismatch somehow causing the problem, I am reluctant to start changing firmware that appeared to be working fine well before any problems with this KPL.  In addition, this KPL is one of the first I installed back in 2008, and that makes it relatively OLD. 

 

Is there anything definitive that can be drawn from this error? 

Link to comment
Share on other sites
LeeG Advanced

LeeG

Posted
Posted

Communication was okay going into writing link record 33.  At that point either the KeypadLinc began to fail or something on the powerline turned On and destroyed comm capability.   Up to that point Hops Left=2 was normal, but starting with link record 33 Hops Left=0 was the normal response.  Soon after comm failed completely.  I would move the KPL to the PLM location with a patch cord and see if comms fail well into the restore.   

 

Wed 12/03/2014 11:13:43 PM : [iNST-TX-I1  ] 02 62 10 03 DB 0F 29 02
 
Wed 12/03/2014 11:13:43 PM : [iNST-ACK    ] 02 62 10.03.DB 0F 29 02 06          POKE   (02)
 
Wed 12/03/2014 11:13:44 PM : [iNST-SRX    ] 02 50 10.03.DB 0F.D5.9D 2B 29 02    POKE   (02)
 
Wed 12/03/2014 11:13:44 PM : [std-Direct Ack] 10.03.DB-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
 
 
Communication was good to this point.   It appears that something turned On at this point (or KPL failed) as all comm past this point is bad and soon failed completely. 
 
 
Wed 12/03/2014 11:13:44 PM : [10 3 DB 1   ] Link   33 : 0EF0 [A20116A02BFF1F07] Writing [A20116A02BFF1F07]
 
Wed 12/03/2014 11:13:44 PM : [iNST-TX-I1  ] 02 62 10 03 DB 0F 28 0E
 
Wed 12/03/2014 11:13:44 PM : [iNST-SRX    ] 02 50 10.03.DB 0F.D5.9D 23 29 02    POKE   (02)
 
Wed 12/03/2014 11:13:44 PM : [std-Direct Ack] 10.03.DB-->ISY/PLM Group=0, Max Hops=3, Hops Left=0
 
Wed 12/03/2014 11:13:44 PM : [iNST-ACK    ] 02 62 10.03.DB 0F 28 0E 06          SET-MSB(0E)
 
Wed 12/03/2014 11:13:44 PM : [iNST-SRX    ] 02 50 10.03.DB 0F.D5.9D 2B 28 0E    SET-MSB(0E)
 
Wed 12/03/2014 11:13:44 PM : [std-Direct Ack] 10.03.DB-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
 
Wed 12/03/2014 11:13:44 PM : [iNST-TX-I1  ] 02 62 10 03 DB 0F 2B F0
 
Wed 12/03/2014 11:13:44 PM : [iNST-ACK    ] 02 62 0F.2B.F0 00 00 00 06                 (00)
 
Wed 12/03/2014 11:13:53 PM : [iNST-TX-I1  ] 02 62 10 03 DB 0F 28 0E
 
Wed 12/03/2014 11:13:53 PM : [iNST-ACK    ] 02 62 10.03.DB 0F 28 0E 06          SET-MSB(0E)
 
Wed 12/03/2014 11:13:54 PM : [iNST-SRX    ] 02 50 10.03.DB 0F.D5.9D 23 28 0E    SET-MSB(0E)
 
Wed 12/03/2014 11:13:54 PM : [std-Direct Ack] 10.03.DB-->ISY/PLM Group=0, Max Hops=3, Hops Left=0
 
Wed 12/03/2014 11:13:54 PM : [iNST-TX-I1  ] 02 62 10 03 DB 0F 2B F0
 
Wed 12/03/2014 11:13:54 PM : [iNST-ACK    ] 02 62 10.03.DB 0F 2B F0 06          PEEK   (F0)
 
Wed 12/03/2014 11:13:54 PM : [iNST-SRX    ] 02 50 10.03.DB 0F.D5.9D 23 2B 00    PEEK   (00)
 
Wed 12/03/2014 11:13:54 PM : [std-Direct Ack] 10.03.DB-->ISY/PLM Group=0, Max Hops=3, Hops Left=0
 
Wed 12/03/2014 11:13:54 PM : [iNST-TX-I1  ] 02 62 10 03 DB 0F 29 A2
 
Wed 12/03/2014 11:13:54 PM : [iNST-ACK    ] 02 62 10.03.DB 0F 29 A2 06          POKE   (A2)
 
Wed 12/03/2014 11:13:55 PM : [iNST-SRX    ] 02 50 10.03.DB 0F.D5.9D 27 29 A2    POKE   (A2)
 
Wed 12/03/2014 11:13:55 PM : [std-Direct Ack] 10.03.DB-->ISY/PLM Group=0, Max Hops=3, Hops Left=1
 
Wed 12/03/2014 11:13:55 PM : [iNST-TX-I1  ] 02 62 10 03 DB 0F 2B F1
 
Wed 12/03/2014 11:13:56 PM : [iNST-ACK    ] 02 62 10.03.DB 0F 2B F1 06          PEEK   (F1)
 
Wed 12/03/2014 11:13:56 PM : [iNST-SRX    ] 02 50 10.03.DB 0F.D5.9D 23 29 A2    POKE   (A2)
 
Wed 12/03/2014 11:13:56 PM : [std-Direct Ack] 10.03.DB-->ISY/PLM Group=0, Max Hops=3, Hops Left=0
 
Wed 12/03/2014 11:13:56 PM : [iNST-SRX    ] 02 50 10.03.DB 0F.D5.9D 23 2B 00    PEEK   (00)
 
Wed 12/03/2014 11:13:56 PM : [std-Direct Ack] 10.03.DB-->ISY/PLM Group=0, Max Hops=3, Hops Left=0
 
Wed 12/03/2014 11:13:56 PM : [iNST-TX-I1  ] 02 62 10 03 DB 0F 29 01
 
Wed 12/03/2014 11:13:56 PM : [iNST-ACK    ] 02 62 10.03.DB 0F 29 01 06          POKE   (01)
 
Wed 12/03/2014 11:13:57 PM : [iNST-SRX    ] 02 50 10.03.DB 0F.D5.9D 23 29 01    POKE   (01)
 
Wed 12/03/2014 11:13:57 PM : [std-Direct Ack] 10.03.DB-->ISY/PLM Group=0, Max Hops=3, Hops Left=0
 
Wed 12/03/2014 11:13:57 PM : [iNST-TX-I1  ] 02 62 10 03 DB 0F 2B F2
 
Wed 12/03/2014 11:13:57 PM : [iNST-ACK    ] 02 62 10.03.DB 0F 2B F2 06          PEEK   (F2)
 
Wed 12/03/2014 11:14:06 PM : [iNST-TX-I1  ] 02 62 10 03 DB 0F 28 0E
 
Wed 12/03/2014 11:14:06 PM : [iNST-ACK    ] 02 62 10.03.DB 0F 28 0E 06          SET-MSB(0E)
 
Wed 12/03/2014 11:14:07 PM : [iNST-SRX    ] 02 50 10.03.DB 0F.D5.9D 23 28 0E    SET-MSB(0E)
 
Wed 12/03/2014 11:14:07 PM : [std-Direct Ack] 10.03.DB-->ISY/PLM Group=0, Max Hops=3, Hops Left=0
 
Wed 12/03/2014 11:14:07 PM : [iNST-TX-I1  ] 02 62 10 03 DB 0F 2B F2
 
Wed 12/03/2014 11:14:07 PM : [iNST-ACK    ] 02 62 10.03.DB 0F 2B F2 06          PEEK   (F2)
 
Wed 12/03/2014 11:14:08 PM : [iNST-SRX    ] 02 50 10.03.DB 0F.D5.9D 26 2B 00    PEEK   (00)
 
Wed 12/03/2014 11:14:08 PM : [std-Direct Ack] 10.03.DB-->ISY/PLM Group=0, Max Hops=2, Hops Left=1
 
Wed 12/03/2014 11:14:08 PM : [iNST-TX-I1  ] 02 62 10 03 DB 0F 29 16
 
Wed 12/03/2014 11:14:08 PM : [iNST-ACK    ] 02 62 10.03.DB 0F 29 16 06          POKE   (16)
 
Wed 12/03/2014 11:14:08 PM : [iNST-SRX    ] 02 50 10.03.DB 0F.D5.9D 23 29 16    POKE   (16)
 
Wed 12/03/2014 11:14:08 PM : [std-Direct Ack] 10.03.DB-->ISY/PLM Group=0, Max Hops=3, Hops Left=0
 
Wed 12/03/2014 11:14:08 PM : [iNST-TX-I1  ] 02 62 10 03 DB 0F 2B F3
 
Wed 12/03/2014 11:14:08 PM : [iNST-ACK    ] 02 62 10.03.DB 0F 2B F3 06          PEEK   (F3)
 
Wed 12/03/2014 11:14:09 PM : [iNST-SRX    ] 02 50 10.03.DB 0F.D5.9D 23 2B 00    PEEK   (00)
 
Wed 12/03/2014 11:14:09 PM : [std-Direct Ack] 10.03.DB-->ISY/PLM Group=0, Max Hops=3, Hops Left=0
 
Wed 12/03/2014 11:14:09 PM : [iNST-TX-I1  ] 02 62 10 03 DB 0F 29 A0
 
Wed 12/03/2014 11:14:09 PM : [iNST-ACK    ] 02 62 10.03.DB 0F 29 A0 06          POKE   (A0)
 
Wed 12/03/2014 11:14:10 PM : [iNST-ERX    ] 02 51 10 03 DB 0F D5 9D 54 D6 5E D5 D6 DF 3D BF DB 03 8F 00 19 16 DE 41 BF 
 
Wed 12/03/2014 11:14:10 PM : [std-Cleanup ] 10.03.DB-->ISY/PLM Group=94, Max Hops=0, Hops Left=1
 
Wed 12/03/2014 11:14:19 PM : [iNST-TX-I1  ] 02 62 10 03 DB 0F 28 0E
 
Wed 12/03/2014 11:14:19 PM : [iNST-ACK    ] 02 62 10.03.DB 0F 28 0E 06          SET-MSB(0E)
 
Wed 12/03/2014 11:14:28 PM : [iNST-TX-I1  ] 02 62 10 03 DB 0F 28 0E
 
Wed 12/03/2014 11:14:28 PM : [iNST-ACK    ] 02 62 10.03.DB 0F 28 0E 06          SET-MSB(0E)
 
Wed 12/03/2014 11:14:28 PM : [iNST-SRX    ] 02 50 10.03.DB 0F.D5.9D 23 28 0E    SET-MSB(0E)
 
Wed 12/03/2014 11:14:28 PM : [std-Direct Ack] 10.03.DB-->ISY/PLM Group=0, Max Hops=3, Hops Left=0
 
Wed 12/03/2014 11:14:28 PM : [iNST-TX-I1  ] 02 62 10 03 DB 0F 2B F3
 
Wed 12/03/2014 11:14:28 PM : [iNST-ACK    ] 02 62 10.03.DB 0F 2B F3 06          PEEK   (F3)
 
Wed 12/03/2014 11:14:32 PM : [10 3 DB 1   ] Link   33 : 0EF0 [A20116A02BFF1F07] *Failed Writing [A20116A02BFF1F07]
 
Wed 12/03/2014 11:14:32 PM : [D2D EVENT   ] Event [10 3 DB 1] [ERR] [1] uom=0 prec=-1
 
Wed 12/03/2014 11:14:32 PM : [   10 3 DB 1]      ERR   1
Link to comment
Share on other sites
justin.cool Member

justin.cool

Posted
  • Author
Posted

I took your advice and replaced the PLM, but somewhere along the way things went South very quickly........

 

Replacing my PLM

 

Was 2412S

New unit:  2413S

 

  • Disabled all programs
  • Plugged in the new PLM, then powered up the ISY
  • Went to Admin Console and initiated Restore Modem
  • Left the room to let the restore take place
  • Returned some time later and found about 20 of the “Cannot communicate with……..” dialog boxes in the admin console.  (See Event Viewer for the PLM Restore).  Also, in the admin console each of the 20 devices had the little green “0110” icon indicating that updates were required. 
  • Went to all my RF devices and put them one at a time in Programming mode and initiated Updates for each.  That seemed to work OK.
  • I then went to each of the non-RF devices that had a “Cannot communicate…..” dialog box and initiated Update Device for each.  This seemed to complete successfully for the first 5 or 6 devices, then I got the “Cannot communicate” dialog box again for several devices. 
  • I ran Device Links Table / Compare on several of the problem devices and got some matches and some mismatches on all of those.  I attempted to do a Device Restore and got “Cannot communicate…..” dialog box again on several of them. 
  • I then attempted to do a Device Restore on a device that had NOT had any communication issues.  The restore device appears to complete in less than 1 second, and the event viewer only has two lines in it, then nothing, see below: (NOTE:  The event viewer was in level 3). 

Sun 12/07/2014 10:40:35 PM : [    A B7 7 1] Preparing Device 'Lvng Rm China Cab Li' for Restore

 

Sun 12/07/2014 10:40:35 PM : [    A B7 7 1] Device 'Lvng Rm China Cab Li' ready for Full Restore

 

 

At this point I can’t help but think that I have really got things hosed up, AND appear to have some serious communication issues. 

 

Your recommendations would be greatly appreciated…….

ISY-Events-Log.v4.2.66__Fri 2014.12.05 04.06.58 PM_New PLM.txt

Link to comment
Share on other sites
justin.cool Member

justin.cool

Posted
  • Author
Posted

Stusviews,

 

It seems I cut and pasted an OLD ISY config description when I first started this thread.  In particular, the firmware version I have been running for the last 5 months or so is:

 

Firmware 4.2.66

UI  4.2.5

 

and NOT

 

Firmware 4.0.5

UI  4.0.11

 

as I stated initially. 

 

I stand corrected.

 

Justin

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

Go to topic listing
×
×
  • Create New...