Rough time replacing a modem

[arw01]

My caps replaced modem made it another 4 years, but a pair or all on events, one at 5:40 in the morning was the last straw.  Ordered a new modem on black friday pricing.  That took about a week to show up and I unplugged the old modem for the week.

 

This appears to have really caused me issues as the ISY apparently has a week or more of queries and program writes and non communications that it must work through before it will do a modem restore.  I've been coming along for days and causing it to try and restore one device.   Still waiting to get there.

 

Is there  a way to completely wipe out the que so I can do the modem restore actual writes to the devices?

[Michel Kohanim]

Hi @arw01,

What you need to do is to Restore Devices:

https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:File_Menu#Restore_Devices

With kind regards,
Michel

[arw01]

The steps for restore device have finished on the ISY, but I am still no closer.  I just factory reset a light switch that has a access point near it, the PLM within 10' and it just appears to completely not respond.  Not a single device seems to be restored.

 

Beginning to wonder if I got a defective modem from Smarthome.

 

Sat 12/15/2018 08:30:42 AM : [  16 F5 EF 1] Preparing Device 'Alan_Office' for Restore
Sat 12/15/2018 08:30:42 AM : [  16 F5 EF 1] Device 'Alan_Office' ready for Full Restore
Sat 12/15/2018 08:30:43 AM : [All         ] Writing 25 bytes to devices
Sat 12/15/2018 08:30:43 AM : [INST-TX-I1  ] 02 62 23 3C D4 0F 0D 00
Sat 12/15/2018 08:30:43 AM : [INST-ACK    ] 02 62 23.3C.D4 0F 0D 00 06                 (00)
Sat 12/15/2018 08:30:52 AM : [INST-TX-I1  ] 02 62 23 3C D4 0F 0D 00
Sat 12/15/2018 08:30:52 AM : [INST-ACK    ] 02 62 23.3C.D4 0F 0D 00 06                 (00)
Sat 12/15/2018 08:31:01 AM : [INST-TX-I1  ] 02 62 23 3C D4 0F 0D 00
Sat 12/15/2018 08:31:01 AM : [INST-ACK    ] 02 62 23.3C.D4 0F 0D 00 06                 (00)
 

[arw01]

an attempt to write updates to device:

 

Sat 12/15/2018 08:33:09 AM : [INST-TX-I1  ] 02 62 16 F5 EF 0F 0D 00
Sat 12/15/2018 08:33:09 AM : [INST-ACK    ] 02 62 16.F5.EF 0F 0D 00 06                 (00)
Sat 12/15/2018 08:33:18 AM : [INST-TX-I1  ] 02 62 16 F5 EF 0F 0D 00
Sat 12/15/2018 08:33:18 AM : [INST-ACK    ] 02 62 16.F5.EF 0F 0D 00 06                 (00)
Sat 12/15/2018 08:33:27 AM : [INST-TX-I1  ] 02 62 16 F5 EF 0F 0D 00
Sat 12/15/2018 08:33:27 AM : [INST-ACK    ] 02 62 16.F5.EF 0F 0D 00 06                 (00)
Sat 12/15/2018 08:33:31 AM : [16 F5 EF 1  ] Memory : Write dbAddr=0x0032 [FF] cmd1=0x2E cmd2=0x00
Sat 12/15/2018 08:33:31 AM : [INST-TX-I2  ] 02 62 16 F5 EF 1F 2E 00 01 06 FF 00 00 00 00 00 00 00 00 00 00 CC
Sat 12/15/2018 08:33:31 AM : [INST-ACK    ] 02 62 16.F5.EF 1F 2E 00 01 06 FF 00 00 00 00 00 00 00 00 00 00 CC 06        (00)
Sat 12/15/2018 08:33:40 AM : [INST-TX-I2  ] 02 62 16 F5 EF 1F 2E 00 01 06 FF 00 00 00 00 00 00 00 00 00 00 CC
Sat 12/15/2018 08:33:40 AM : [INST-ACK    ] 02 62 16.F5.EF 1F 2E 00 01 06 FF 00 00 00 00 00 00 00 00 00 00 CC 06        (00)
Sat 12/15/2018 08:33:49 AM : [INST-TX-I2  ] 02 62 16 F5 EF 1F 2E 00 01 06 FF 00 00 00 00 00 00 00 00 00 00 CC
Sat 12/15/2018 08:33:49 AM : [INST-ACK    ] 02 62 16.F5.EF 1F 2E 00 01 06 FF 00 00 00 00 00 00 00 00 00 00 CC 06        (00)
Sat 12/15/2018 08:33:49 AM : [INST-SRX    ] 02 50 16.F5.EF 4C.1C.0D 2B 2E 00           (00)
Sat 12/15/2018 08:33:49 AM : [Std-Direct Ack] 16.F5.EF-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Sat 12/15/2018 08:33:49 AM : [16 F5 EF 1  ] Memory : Write dbAddr=0x0021 [1C] cmd1=0x2E cmd2=0x00
Sat 12/15/2018 08:33:49 AM : [INST-TX-I2  ] 02 62 16 F5 EF 1F 2E 00 01 05 1C 00 00 00 00 00 00 00 00 00 00 B0
Sat 12/15/2018 08:33:49 AM : [INST-ACK    ] 02 62 16.F5.EF 1F 2E 00 01 05 1C 00 00 00 00 00 00 00 00 00 00 B0 06        (00)
Sat 12/15/2018 08:33:58 AM : [INST-TX-I2  ] 02 62 16 F5 EF 1F 2E 00 01 05 1C 00 00 00 00 00 00 00 00 00 00 B0
Sat 12/15/2018 08:33:58 AM : [INST-ACK    ] 02 62 16.F5.EF 1F 2E 00 01 05 1C 00 00 00 00 00 00 00 00 00 00 B0 06        (00)
Sat 12/15/2018 08:34:07 AM : [INST-TX-I2  ] 02 62 16 F5 EF 1F 2E 00 01 05 1C 00 00 00 00 00 00 00 00 00 00 B0
Sat 12/15/2018 08:34:11 AM : [16 F5 EF 1  ] Memory : Write dbAddr=0x0021 [1C] cmd1=0x2E cmd2=0x00 - Failed
 

[paulbates]

Another thing to consider is "pollution" of the master copy of Insteon network information in the ISY itself, as the original PLM slowly fell apart.

Do you have a good back up of your ISY from before the PLM started to fail? If yes

• Unplug ISY and PLM
• Factory reset and plug in the plm, then plugin the ISY
• Restore that backup
• Retry Restore PLM

Some devices may have to be factory reset to get them working, or the "01010" to go away if there was a lot of insteon management activity in this state.

Paul

[arw01]

I had one from about 3 weeks back prior to the two ALL ON events that drove me to replace it.  5:30am with an all on and the wife wokeup did not go un-noticed!

This morning with the power line still filtered not a single cannot communicate on the overnight query.

So far only once device has not taking programming and of course it's a later model one from the last couple of years and way up on the ceiling requiring the long ladder to get at.

[arw01]

I consider this closed.  Putting the filter on to stop powerline communications has made the network much more solid.

 

My last mystery is why it keeps trying to communicate with a motion sensor.  I've tried write, query etc, but it seems to want to communicate with it every day.

[rccoleman]

1 hour ago, arw01 said:

My last mystery is why it keeps trying to communicate with a motion sensor.  I've tried write, query etc, but it seems to want to communicate with it every day.

Can you successfully update it by right-clicking, selecting "write changes", and waking it up?

If it keeps switching into "I need to be updated" mode every day, are you using the "adjust scene" functionality in a program to change the way it responds?  If so, that will unfortunately and mistakenly (in my opinion) mark the motion sensor as needing an update every time and you won't be able to easily clear that state.  I just turn off writes to battery-operated devices to prevent the ISY from getting stuck trying to update my motion sensors.