Link Management, start linking menu appears then disappears

[nowandthen]

Been a while since I added an Insteon device. Trying to add a new Insteon switch. I click Link Management, then Start Linking. Linking window opens for a few seconds then closes. I unplugged the ISY then let it reboot. Tried again, window stayed open but it did not see the device (after putting device into linking mode well within 4 minutes). Next attempt reverted back to linking window closing after a few seconds. Any ideas?

 

Firmware version 3.2.6. I see 3.3.10 is available but I hate having to go through the update process. Is there a bug in 3.2.6 with regards to linking?

[LeeG]

There were many functional additions, new device support and bug fixes between 3.2.6 and 3.3.10. Take a look at the 3.3.x link below. It lists each 3.3.x release from 3.3.10 to 3.3.1 with what was added and fixed at each increment.

 

viewtopic.php?f=25&t=9366

 

There are also things fix in each of the 4.0.x images that have come out since 3.3.10.

 

I think the Start Linking problem you are seeing as far as not staying up is due to the Finish button not being clicked on the previous Start Linking session.

[nowandthen]

Thanks Lee,

 

Upgrade to 3.3.10 was a bit of a challenge, not sure why this is always an issue for me, I must be kind of dense. LOL

 

I did eventually get the system up and running again, run on start up has turned on lighting (upgrade knocked out the ISY at sunset).

 

BUT... motions sensors "see" me, but lights do not turn on. UGH! And I still can't link the new switches. This is extremely frustrating!

 

This is why I HATE to upgrade the firmware, something always goes wrong.

 

I'm rebooting the ISY again.

[nowandthen]

After reboot I get the system in safe mode message again. UGH!

[nowandthen]

Message says most likely my PLM is defective. My PLM has been working just fine until I tried to add the switches.

[nowandthen]

Unplugged PLM and yet another reboot and ISY is now responding to motion sensors. I am afraid to try and add the switches. Giving up for today.

[LeeG]

Start Linking puts the PLM into linking mode. If the new device cannot reach the PLM it may stay in linking mode for several minutes. Power cycle PLM and ISY. Insure PLM is powered before powering ISY. Then use New INSTEON Device to add the new device. New INSTEON Device does not have the side effects Start Linking can have if dealing with a comm problem.

 

What type of device is being added that is having the problems?

 

The easiest way to test a new device is to connect it to an Appliance cord (plug on one end, bare wires on the other). Plug the Appliance cord into the PLM plug point which eliminates questions of comm.

[nowandthen]

I have 2 new 2477S ON -OFF relay switches. They control florescent lights. I always have to add noise filters on florescent lights, these do not have them yet so I took the bulbs out as they are hardwired. Hope that prevents interference during linking. But even with switches off (florescent lights off) the linking window closes after a few seconds, sometimes almost instantaneously.

 

I unplugged the ISY and PLM. Plugged the PLM in, waited a couple of minutes. It doesn't seem to do anything after a few seconds, bright LED then dull LED, but still I waited a while. Then I plugged the ISY in. It took a minute or two to settle down, was running "run on power up routines", as the hall lights I was using shut off. The hot recirc pump turns on then times out. Kind of strange as it is X10, but let's not get side-tracked.

 

So I tried New Insteon Device: I entered the device address, gave it a name and choose the type of device, says adding but after about 10 seconds I get an error message that states "Cannot determine Insteon Engine". I also tried auto discover. No luck. The devices are in my detached garage but my system communicates with other Insteon devices in the garage. And why would that have any effect on the Start Linking window closing so quickly?

 

Lee, I appreciate your help. Any more ideas? I don't think it is Java or corrupt software installation as this problem existed with the previous version. Do I try clearing java again?

[LeeG]

When Start Linking does not stay up it is usually because the Finish button was not clicked. The Finish button must be clicked regardless of whether communication with the device has been successful or not. The popup closing is usually what happens the next time Start Linking is initiated without clicking Finish.

 

It sounds like there is a comm problem to the new switches. These are going to be I2CS devices which use extended commands that may not have been used with other devices in the garage. Stick with New INSTEON Device. Run Tools | Diagnostics | Event Viewer at LEVEL 3. Factory reset one of the new switches. Using New INSTEON Device enter the Insteon address, Name of choice and Device Type at default Auto Discover. Post the event trace.

 

I’m pretty sure the device is not responding to the extended message with the required information.

[nowandthen]

Lee, I forgot to mention I did click the finish button but no luck. Tried it several times.

 

Here's the Event Viewer data after following your instructions:

 

Fri 04/26/2013 05:46:43 PM : [22 a5 11 ] Added to list of devices to link to ISY

Fri 04/26/2013 05:46:43 PM : [iNST-TX-I1 ] 02 62 22 A5 11 0F 0D 00

Fri 04/26/2013 05:46:43 PM : [iNST-ACK ] 02 62 22.A5.11 0F 0D 00 06 (00)

Fri 04/26/2013 05:46:43 PM : [iNST-SRX ] 02 50 22.A5.11 0F.9D.42 A7 0D FF (FF)

Fri 04/26/2013 05:46:43 PM : [std-Direct Nack] 22.A5.11-->ISY/PLM Group=0, Max Hops=3, Hops Left=1

Fri 04/26/2013 05:46:43 PM : [iNST-TX-I2CS] 02 62 22 A5 11 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6

Fri 04/26/2013 05:46:43 PM : [iNST-ACK ] 02 62 22.A5.11 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6 06 LNK-ON (01)

Fri 04/26/2013 05:46:43 PM : [iNST-SRX ] 02 50 22.A5.11 0F.9D.42 27 09 01 LNK-ON (01)

Fri 04/26/2013 05:46:43 PM : [std-Direct Ack] 22.A5.11-->ISY/PLM Group=0, Max Hops=3, Hops Left=1

Fri 04/26/2013 05:46:47 PM : [22 A5 11 0 ] Failed to add device

[LeeG]

The following trace is what the beginning should look like. The message in Blue is missing.

 

Click Help | About and verify both Firmware and UI indicate 3.3.10

 

 

Fri 04/26/2013 09:10:19 PM : [22 8b e0 ] Added to list of devices to link to ISY

 

Fri 04/26/2013 09:10:19 PM : [iNST-TX-I1 ] 02 62 22 8B E0 0F 0D 00

 

Fri 04/26/2013 09:10:19 PM : [iNST-ACK ] 02 62 22.8B.E0 0F 0D 00 06 (00)

 

Fri 04/26/2013 09:10:19 PM : [iNST-SRX ] 02 50 22.8B.E0 22.80.0B AB 0D FF (FF)

 

Fri 04/26/2013 09:10:19 PM : [std-Direct Nack] 22.8B.E0-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

 

Fri 04/26/2013 09:10:19 PM : [iNST-TX-I2CS] 02 62 22 8B E0 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6

 

Fri 04/26/2013 09:10:19 PM : [iNST-ACK ] 02 62 22.8B.E0 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6 06 LNK-ON (01)

 

Fri 04/26/2013 09:10:20 PM : [iNST-SRX ] 02 50 22.8B.E0 22.80.0B 2B 09 01 LNK-ON (01)

 

Fri 04/26/2013 09:10:20 PM : [std-Direct Ack] 22.8B.E0-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

 

Fri 04/26/2013 09:10:20 PM : [LNK-BGN ] 02 64 01 00 06

 

Fri 04/26/2013 09:10:21 PM : [LNK-STAT ] 02 53 M(01) gid=00 22.8B.E0 011C 41

 

Fri 04/26/2013 09:10:21 PM : [iNST-TX-I1 ] 02 62 22 8B E0 0F 0D 00

 

Fri 04/26/2013 09:10:21 PM : [LNK-END ] 02 65 06

[nowandthen]

Both are 3.3.10

[LeeG]

Power cycle PLM and ISY, bring PLM up first. Repeat Event Viewer at LEVEL 3 and New INSTEON Device. Do not attempt any Start Linking. Post the new event trace.

[nowandthen]

Went to power down ISY and PLM. The PLM Led was off. Is that normal? For some reason I thought it was always at a low level of green, but I normally don't look at it.

 

How do I know when the PLM has rebooted? Or is it ready to go as soon as power is applied? I've been giving it a couple of minutes before powering up the ISY. The ISY seems to take several minutes to settle down as it runs "run at power up routines". The PLM LED occasionally blinks as the ISY comes up and runs routines.

 

Here's the log:

 

Fri 04/26/2013 06:55:30 PM : [ 21 C5 DF 1] ST 134

Fri 04/26/2013 06:56:08 PM : [22 a5 11 ] Added to list of devices to link to ISY

Fri 04/26/2013 06:56:08 PM : [iNST-TX-I1 ] 02 62 22 A5 11 0F 0D 00

Fri 04/26/2013 06:56:08 PM : [iNST-ACK ] 02 62 22.A5.11 0F 0D 00 06 (00)

Fri 04/26/2013 06:56:17 PM : [iNST-TX-I1 ] 02 62 22 A5 11 0F 0D 00

Fri 04/26/2013 06:56:17 PM : [iNST-ACK ] 02 62 22.A5.11 0F 0D 00 06 (00)

Fri 04/26/2013 06:56:17 PM : [iNST-SRX ] 02 50 22.A5.11 0F.9D.42 A7 0D FF (FF)

Fri 04/26/2013 06:56:17 PM : [std-Direct Nack] 22.A5.11-->ISY/PLM Group=0, Max Hops=3, Hops Left=1

Fri 04/26/2013 06:56:17 PM : [iNST-TX-I2CS] 02 62 22 A5 11 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6

Fri 04/26/2013 06:56:17 PM : [iNST-ACK ] 02 62 22.A5.11 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6 06 LNK-ON (01)

Fri 04/26/2013 06:56:18 PM : [iNST-SRX ] 02 50 22.A5.11 0F.9D.42 27 09 01 LNK-ON (01)

Fri 04/26/2013 06:56:18 PM : [std-Direct Ack] 22.A5.11-->ISY/PLM Group=0, Max Hops=3, Hops Left=1

Fri 04/26/2013 06:56:18 PM : [LNK-BGN ] 02 64 01 00 03

Fri 04/26/2013 06:56:18 PM : [22 A5 11 0 ] Failed to add device

 

Note PLM LED is off.

[LeeG]

I suggest opening a ticket with UDI support.

 

Fri 04/26/2013 06:56:18 PM : [LNK-BGN ] 02 64 01 00 03

 

The PLM message is now there as it should be but the last character should be 06; in your trace it is 03. My PLM command reference does not list an 03. The device response that should follow the PLM command is missing but I don't know if that is a PLM issue or device issue with the 03 in the last byte.

[nowandthen]

Lee,

 

Thanks for taking the time to help me I appreciate it!

 

By the way, I think my PLM is dying or something is shutting it down? The LED was off again and none of the lights would respond from my RedEye or Mobilinc Pro. A reboot of both fixed it, the LED is on for now.

 

Maybe PLM is the problem?

 

I will open a ticket with UDI support.

 

Thank you!

[LeeG]

I think it is a PLM problem. In all the years I have looked at PLM traces either the last byte returned by the PLM is an 06 for a command that is accepted or a 15 for a command that is not accepted. Never seen an 03 as the last byte and it is not listed in my PLM command reference. The problem is my PLM command reference is rather old and there could be additional valid codes that I am not aware of.

[nowandthen]

Called Insteon support this morning. He thinks the PLM is going bad. We couldn't get it to reset, tried a restore PLM and it failed. Now my PLM is really messed up. LOL Finally got the PLM "working", restore PLM is proceeding. I have a lot of "failed to communicate with".

 

This evening the PLM LED was off. It must be on it's last legs. cycled power and it is back up, who knows for how long.

 

I will order a new PLM and keep my fingers crossed.

 

Lee, I forgot to ask about the 03 code, sorry.

[nowandthen]

I have my new PLM in hand. I read through the How-to on replacing the PLM. Seems straight forward.

 

Last Saturday Insteon Support had me try to perform a factory reset on the old PLM and then a restore PLM. It didn't go very well. I finally got the PLM limping along until the new one arrived. A few programs run, many others do not. Many "complaints" of "can't communicate with" but later, most got resolved. However, I still couldn't communicate with most devices either through the ISY computer interface or through smartphone programs.

 

Question: If I do a restore with the new PLM will it likely be OK? This assumes the original problem is with the old PLM and the new one will fix the issues described above. Of course I do not have a recent back up. I was very good at doing them regularly but had no reason to log onto the ISY for several months so no recent back up. Murphy's law. So just because many programs and devices don't work at the moment is the ISY file still good to load into the new PLM?

[LeeG]

"Question: If I do a restore with the new PLM will it likely be OK? This assumes the original problem is with the old PLM and the new one will fix the issues described above."

 

Yes, assuming your assumption is correct.

 

Unless you have some reason to believe the integrity of the ISY information is in question a Restore ISY is not needed. A Backup should be taken before changing PLMs. Remember that every device reference to the PLM has to be changed from the old to new PLM Insteon address so the Restore Modem (PLM) may run awhile.

[nowandthen]

No guts no glory...

 

So I get this error message: Could not open config file to read [/CONF/FF0504.REC] Could not open file [/CONF/FF0504.REC]

 

I did do a backup before removing the old PLM.

[Michel Kohanim]

Hi nowandthen,

 

We also got your ticket but all emails were bounced.

 

Unfortunately this is a very classic case of PLM dying or already dead. This I guarantee you and thus you will need to order a new PLM.

 

With kind regards,

Michel

[nowandthen]

More guts...

 

I rolled back my ISY from 3.3.10 to 3.2.6. Then loaded my last 3.2.6 back up 12-12-12. It loaded, it complained about devices no longer hooked up (Christmas stuff) but loaded. Then I did a restore PLM. It went a lot farther than before but still got the error message mentioned above. However the progress bar continues to advance. Progress is slow (was also slow before error message). Maybe I bailed too early the last time not realizing it would continue. Keeping my fingers crossed. Advances at a rate of about 1% every 30 seconds.

[nowandthen]

Hi nowandthen,

 

We also got your ticket but all emails were bounced.

 

Unfortunately this is a very classic case of PLM dying or already dead. This I guarantee you and thus you will need to order a new PLM.

 

With kind regards,

Michel

Hi Michel,

 

I have the new PLM. The problem was the error message I got when I tried to restore. Please read my post just before and just after yours. I've rolled back the firmware to 3.2.6 and loaded a 5 month old 3.2.6 backup file. Can you explain the error message "Could not open config file to read [/CONF/FF0504.REC]" and should I be concerned? It seems to be restoring the PLM albeit to an old backup.

 

Thanks

[Michel Kohanim]

Hi nowandthen, so very sorry ...

 

Please telnet to ISY, login, and type the following:

RF /CONF/FF0504.REC

 

This is an X10 device that's no longer there.

 

With kind regards,

Michel