Jump to content

How to restore a ISY994 IR Pro?


RichTJ99

Recommended Posts

Hi,

 

I have had some major problems with my system.  I had to do a factory reset of my ISY & the PLM.  I have several backups & they are all able to be imported into the ISY.  

 

I have two ISY 994 IR Pros (ISY1, ISY2).  I only use one, the second one is from the upgrade program as a spare - not in use.  I also have two PLMs (PLM1 active, PLM2 a spare).

 

At this point, I am using my oringal items - ISY1 & PLM1.  I restore my most recent backup & I get every device coming back with a communication error.  If I am in the ISY admin platform, I am able to turn certain lights on & off primarily with the fast on / fast off commands.

 

I am able to browse on my cell phone to the web interface & control devices from there as well.  

 

In my home, i notice serious lag on the physical buttons for devices in a scene.  Also the lights on the switches themselves seem to pulsate a bit (some of them).  

 

So, I have tried many many factory resets of both ISY1 & PLM1 & loads of combonations of restore devices or restore PLM.  Every one seems to result in all communication failures.

 

However as I said above, if I log into the ISY I am able to get some lights on & off, so it is confusing to me.

 

 

If i do the PLM links table I get one link & I should have about 600+.

 

What is the best way to proceed?  Do I use ISY2 & PLM2 & start over from scratch?  I have about 100+ devices, loads of programs, and I am not anxious to do that as it will take a few days.  

 

Is there an way to figure out what is going wrong?

 

Thanks,

Rich

 

Link to comment

When I try a PLM restore on PLM2, all I get is error after error (communication).  Nothing gets restored.

 

Now when I goto the PLM -show links it shows nothing at all, not a single link.

 

Hello Rich,

 

To be clear you're not swapping between the two PLM's as you go along are you? If you're you can't do that and must focus with just one and either do a restore PLM.

Link to comment

If switching to PLM2 it means the "PLM is being replaced".  All the devices will still have PLM1 address in all the links back to the ISY PLM.

 

The Wiki section 6.1 has the procedure for "replacing" a PLM (moving from PLM1 to PLM2).  The steps in the Wiki must be followed, particularly the power off steps.    

 

http://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:File_Menu#Replace_Modem_.28PLM.29

Link to comment

Hi,

 

I spoke with Steve in support for a while, I am on hour 16 of the PLM restore, it keeps moving, so its doing something.  I do have a ton of links so I am expecting it to take a while.  I am just patiently waiting.

 

The main difference this time after following hte wiki, was I disabled all the battery devices.

 

Thanks,

Rich

Link to comment

Hi,

 

It is still going.  Nothing changed at all in the electrical.  Just one night last week, the isy seemed slow.  I logged in, rebooted it and it never came up again.  

 

I think its the old PLM.  I can try ISY 2 with PLM2 & start again.

 

How long should it take?  It is still going.

 

Thanks,

Rich

Link to comment

Hi,

 

I have given up.  I rebooted the ISY1 with PLM2, and it would not come back up.  At that point, I loaded ISY2, restored a backup onto it, did a hard reset on the ISY2, PLM2, and am in the middle of a restore PLM.  

 

How many hours should a restore take?

 

I did order another PLM from smarthome but I dont have it yet.

 

Thanks,

Rich

Link to comment

Hi Rich,

 

I really do not think the issue is the PLM or ISY. Do you get any communication errors?

 

Restoring PLM only should not take more than 10-15 minutes (the restore only changes PLM records in devices and nothing else). Restoring Devices may take hours depending on the number of devices you have and whether or not you have turned off the battery operated button. Again, the main question is whether or not you get any comm errors.

 

With kind regards,

Michel

Link to comment

Sooo, in the end, a new PLM fixed everything.  All my scenes are working - even better than before.  I would get a bunch of 'missed' offs on the larger scenes (pressing the off button multiple times, etc).  Now they are working great.

 

The only issue I have is a few devices are getting communication errors when writing.

 

If I press on or off physically, the ISY sees the change, if i press on or off in the ISY admin platform, the devices register the commands.

 

If i do a query on the system, everything responds, but a few devices are always waiting to do a write & then time out with communication errors.

 

Yet all devices work properly.  I dont get it. 

 

Any suggestions would be great.  These communication error devices work great, just the ISY says they are a problem (but there not).

 

Thanks,
Rich

 

Link to comment

Run the event viewer at level 3 then select write updates to device on one of the problem devices.  Post the event trace.

 

-Xathros

Link to comment

here it goes:  Whole thing is attached.  

 

This device does work just fine when I am physically touching it  or when the ISY 'talks' to it.

Wed 09/03/2014 09:58:33 PM : [INST-ACK    ] 02 62 19.3B.FC 0F 2B 90 06          PEEK   (90)

Wed 09/03/2014 09:58:33 PM : [INST-SRX    ] 02 50 19.3B.FC 2A.A1.A4 23 2B E2    PEEK   (E2)

Wed 09/03/2014 09:58:33 PM : [Std-Direct Ack] 19.3B.FC-->ISY/PLM Group=0, Max Hops=3, Hops Left=0

Wed 09/03/2014 09:58:33 PM : [INST-TX-I1  ] 02 62 19 3B FC 0F 28 0C

Wed 09/03/2014 09:58:34 PM : [INST-ACK    ] 02 62 19.3B.FC 0F 28 0C 06          SET-MSB(0C)

Wed 09/03/2014 09:58:36 PM : [INST-SRX    ] 02 50 19.3B.FC 2A.A1.A4 23 28 0C    SET-MSB(0C)

Wed 09/03/2014 09:58:36 PM : [Std-Direct Ack] 19.3B.FC-->ISY/PLM Group=0, Max Hops=3, Hops Left=0

Wed 09/03/2014 09:58:36 PM : [INST-TX-I1  ] 02 62 19 3B FC 0F 2B 91

Wed 09/03/2014 09:58:36 PM : [INST-ACK    ] 02 62 19.3B.FC 0F 2B 91 06          PEEK   (91)

Wed 09/03/2014 09:58:37 PM : [INST-SRX    ] 02 50 19.3B.FC 2A.A1.A4 23 2B 06    PEEK   (06)

Wed 09/03/2014 09:58:37 PM : [Std-Direct Ack] 19.3B.FC-->ISY/PLM Group=0, Max Hops=3, Hops Left=0

Wed 09/03/2014 09:58:37 PM : [INST-TX-I1  ] 02 62 19 3B FC 0F 28 0C

Wed 09/03/2014 09:58:37 PM : [INST-ACK    ] 02 62 19.3B.FC 0F 28 0C 06          SET-MSB(0C)

Wed 09/03/2014 09:58:37 PM : [INST-SRX    ] 02 50 19.3B.FC 2A.A1.A4 23 2B 06    PEEK   (06)

Wed 09/03/2014 09:58:37 PM : [Std-Direct Ack] 19.3B.FC-->ISY/PLM Group=0, Max Hops=3, Hops Left=0

Wed 09/03/2014 09:58:38 PM : [INST-SRX    ] 02 50 19.3B.FC 2A.A1.A4 23 28 0C    SET-MSB(0C)

Wed 09/03/2014 09:58:38 PM : [Std-Direct Ack] 19.3B.FC-->ISY/PLM Group=0, Max Hops=3, Hops Left=0

Wed 09/03/2014 09:58:38 PM : [INST-TX-I1  ] 02 62 19 3B FC 0F 2B 92

Wed 09/03/2014 09:58:38 PM : [INST-ACK    ] 02 62 19.3B.FC 0F 2B 92 06          PEEK   (92)

Wed 09/03/2014 09:58:39 PM : [INST-SRX    ] 02 50 19.3B.FC 2A.A1.A4 23 2B 1C    PEEK   (1C)

Wed 09/03/2014 09:58:39 PM : [Std-Direct Ack] 19.3B.FC-->ISY/PLM Group=0, Max Hops=3, Hops Left=0

Wed 09/03/2014 09:58:39 PM : [INST-TX-I1  ] 02 62 19 3B FC 0F 28 0C

Wed 09/03/2014 09:58:39 PM : [INST-ACK    ] 02 62 19.3B.FC 0F 28 0C 06          SET-MSB(0C)

Wed 09/03/2014 09:58:40 PM : [INST-SRX    ] 02 50 19.3B.DC 2A.A1.A4 23 28 0C    SET-MSB(0C)

Wed 09/03/2014 09:58:40 PM : [Std-Direct Ack] 19.3B.DC-->ISY/PLM Group=0, Max Hops=3, Hops Left=0

Wed 09/03/2014 09:58:40 PM : [INST-DUP    ] Previous message ignored.

Wed 09/03/2014 09:58:49 PM : [INST-TX-I1  ] 02 62 19 3B FC 0F 28 0C

Wed 09/03/2014 09:58:49 PM : [INST-ACK    ] 02 62 19.3B.FC 0F 28 0C 06          SET-MSB(0C)

Wed 09/03/2014 09:58:50 PM : [INST-SRX    ] 02 50 19.3B.FC 2A.A1.A4 23 28 0C    SET-MSB(0C)

Wed 09/03/2014 09:58:50 PM : [Std-Direct Ack] 19.3B.FC-->ISY/PLM Group=0, Max Hops=3, Hops Left=0

Wed 09/03/2014 09:58:50 PM : [INST-TX-I1  ] 02 62 19 3B FC 0F 2B 93

Wed 09/03/2014 09:58:50 PM : [INST-ACK    ] 02 62 19.3B.FC 0F 2B 93 06          PEEK   (93)

Wed 09/03/2014 09:58:59 PM : [INST-TX-I1  ] 02 62 19 3B FC 0F 28 0C

Wed 09/03/2014 09:58:59 PM : [INST-ACK    ] 02 62 19.3B.FC 0F 28 0C 06          SET-MSB(0C)

Wed 09/03/2014 09:58:59 PM : [INST-SRX    ] 02 50 19.3B.FC 2A.A1.A4 23 28 0C    SET-MSB(0C)

Wed 09/03/2014 09:58:59 PM : [Std-Direct Ack] 19.3B.FC-->ISY/PLM Group=0, Max Hops=3, Hops Left=0

Wed 09/03/2014 09:58:59 PM : [INST-TX-I1  ] 02 62 19 3B FC 0F 2B 93

Wed 09/03/2014 09:58:59 PM : [INST-ACK    ] 02 62 19.3B.FC 0F 2B 93 06          PEEK   (93)

Wed 09/03/2014 09:59:00 PM : [INST-SRX    ] 02 50 19.3B.FC 2A.A1.A4 23 2B AD    PEEK   (AD)

Wed 09/03/2014 09:59:00 PM : [Std-Direct Ack] 19.3B.FC-->ISY/PLM Group=0, Max Hops=3, Hops Left=0

Wed 09/03/2014 09:59:00 PM : [INST-TX-I1  ] 02 62 19 3B FC 0F 29 85

Wed 09/03/2014 09:59:00 PM : [INST-ACK    ] 02 62 19.3B.FC 0F 29 85 06          POKE   (85)

Wed 09/03/2014 09:59:04 PM : [19 3B FC 1  ] Link  109 : 0C90 [E2061C85F1FF1F06] *Failed Writing [E2061C85F1FF1F06]

Wed 09/03/2014 09:59:04 PM : [D2D EVENT   ] Event [19 3B FC 1] [ERR] [1] uom=0 prec=-1

Wed 09/03/2014 09:59:04 PM : [  19 3B FC 1]      ERR   1

Wed 09/03/2014 10:00:00 PM : [        Time] 22:00:00 1(0)

One more with the log file

Link to comment

It seems that the actual devices that are having problems are specifically keypad's - & only keypads.  I have a number of them that are having communication errors.  

 

Is there an easy way to "delete" and readd a keypad without my manually reprogramming the programs, and scenes (meaning the ISY could do it)?

 

Maybe I could swap another keypad in?

Link to comment

Deleting a device from the ISY affects related Scenes and Programs.   If you want, Factory Reset one of the KPLs.  Then do a Restore Device to have the ISY restore the device information.

 

Another approach is to "Replace xxxx With ....." using a different KPL.    Add the new KPL to the ISY using some dummy name.   This new KPL can physically replace the KPL being "Replace xxxx With .....".   Right click on original KPL Main A/ON button node and select "Replace oldKPLname With" function.  A popup will display listing the new KPLs that can "Replace" the old KPL.    Select the KPL with the dummy name.  The ISY will change all the references of the old KPL to the new KPL Insteon address.   When the Replace is done the Admin Console will terminate as the new KPL dummy name has been  removed from the list of devices.   

 

The old KPL Insteon address is not used during this process which is why the new KPL can physically replace the old KPL being replaced.   No changes to Scenes or Programs are needed because the old KPL node names  remain but with the new KPL Insteon address.

 

It is not likely that the old KPLs suddenly developed comm issues.   It is very possible the new KPLs will have the same comm issues which will have to be resolved. 

Link to comment

Look at the circuit(s) the KPLs are powered from.   Is the circuit(s) the same or near each other if multiple circuits.  With multiple KPLs it could be something on the same circuit such as a noisy CFL or some other device that is generating interference.  Since the KPL plugs in it can be moved to a different circuit to verify an issue with the circuit now being used.  

 

No harm is swapping ("Replace xxxx with") to a new KPL.   It is a simple sequence to implement.   However, since the KPL is easily moved to a different 120v circuit I would use that as a means of verifying the KPL. 

Link to comment

Archived

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


×
×
  • Create New...