Failed to add device, reason 3

[Rob Devlin]

Good evening.  I just purchased 4 new 2635-222 on/off controllers for my Christmas lights.  I cannot get any of them to link up with my ISY.  I've tried other devices in the same outlet and have not had any issue.  I've tried factory resetting and that has not helped.  I'm running version 5.3.0 of the firmware.  Log is below.

Sat 11/21/2020 20:52:05 : Start Insteon Device Linking Mode
Sat 11/21/2020 20:52:05 : [LNK-BGN     ] 02 64 01 00 06 
Sat 11/21/2020 20:52:20 : [LNK-STAT    ] 02 53 M(01) gid=00 54.A2.55 0237 48 
Sat 11/21/2020 20:52:20 : [54.A2.55 00] Linked device type=02.37 fw=48
Sat 11/21/2020 20:52:20 : [54 A2 55 0  ] Added to list of devices to link to ISY
Sat 11/21/2020 20:52:20 : [LNK-BGN     ] 02 64 01 00 06 
Sat 11/21/2020 20:52:39 : Stop Insteon Device Linking Mode, Final processing to follow
Sat 11/21/2020 20:52:39 : [LNK-END     ] 02 65 06 : : Unexpected, ignored (65)
Sat 11/21/2020 20:52:39 : [INST-TX-I1  ] 02 62 54 A2 55 0F 0D 00
Sat 11/21/2020 20:52:39 : [INST-ACK    ] 02 62 54.A2.55 0F 0D 00 06                 (00)
Sat 11/21/2020 20:52:40 : [INST-SRX    ] 02 50 54.A2.55 30.DE.5F AF 0D FF           (FF)
Sat 11/21/2020 20:52:40 : [Std-Direct Nack] 54.A2.55-->ISY/PLM Group=0, Max Hops=3, Hops Left=3
Sat 11/21/2020 20:52:40 : [INST-TX-I2CS] 02 62 54 A2 55 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6
Sat 11/21/2020 20:52:40 : [INST-ACK    ] 02 62 54.A2.55 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6 06 LNK-ON (01)
Sat 11/21/2020 20:52:41 : [INST-SRX    ] 02 50 54.A2.55 30.DE.5F 2F 09 01    LNK-ON (01)
Sat 11/21/2020 20:52:41 : [Std-Direct Ack] 54.A2.55-->ISY/PLM Group=0, Max Hops=3, Hops Left=3
Sat 11/21/2020 20:52:41 : [LNK-BGN     ] 02 64 01 00 06 
Sat 11/21/2020 20:52:42 : [LNK-STAT    ] 02 53 M(01) gid=00 54.A2.55 0237 48 
Sat 11/21/2020 20:52:42 : [INST-TX-I1  ] 02 62 54 A2 55 0F 0D 00
Sat 11/21/2020 20:52:42 : [LNK-END     ] 02 65 06 
Sat 11/21/2020 20:52:42 : [Std MH      ] Unexpected Ack imCmd=65 cmd1= 0x55
Sat 11/21/2020 20:52:42 : [INST-ACK    ] 02 62 54.A2.55 0F 0D 00 06                 (00)
Sat 11/21/2020 20:52:43 : [INST-SRX    ] 02 50 54.A2.55 30.DE.5F AF 0D FF           (FF)
Sat 11/21/2020 20:52:43 : [Std-Direct Nack] 54.A2.55-->ISY/PLM Group=0, Max Hops=3, Hops Left=3
Sat 11/21/2020 20:52:47 : [INST-TX-I1  ] 02 62 54 A2 55 0F 0D 00
Sat 11/21/2020 20:52:47 : [INST-ACK    ] 02 62 54.A2.55 0F 0D 00 06                 (00)
Sat 11/21/2020 20:52:47 : [INST-SRX    ] 02 50 54.A2.55 30.DE.5F AF 0D FF           (FF)
Sat 11/21/2020 20:52:47 : [Std-Direct Nack] 54.A2.55-->ISY/PLM Group=0, Max Hops=3, Hops Left=3
Sat 11/21/2020 20:52:47 : [54 A2 55 0  ] Failed to add device, reason 3
Sat 11/21/2020 20:52:47 : [        Time] 20:52:52 0(0)
Sat 11/21/2020 20:52:47 : [All         ] Writing 0 bytes to devices
Sat 11/21/2020 20:52:47 : [All         ] Writing 0 bytes to devices
Sat 11/21/2020 20:52:47 : [All         ] Writing 0 bytes to devices
 

[Brian H]

Have you tried the other method to add modules?

Link Menu. Add new Insteon Device. Put in the six digit Insteon module ID number. Auto Discover?

[Rob Devlin]

Yes.  I have tried it both ways.  Same result either way.

[Techman]

6 hours ago, Rob Devlin said:

Yes.  I have tried it both ways.  Same result either way.

What version of the ISY firmware and UI are you running?

Try doing a factory reset on the device before you link it.

[Rob Devlin]

I'm running 5.3 firmware and UI.

I've tried a factory reset and that didn't help.

[Techman]

1 hour ago, Rob Devlin said:

I'm running 5.3 firmware and UI.

I've tried a factory reset and that didn't help.

Try moving the device to a different location / outlet then try to add it. Don't plug anything into the device until after it's linked to the ISY 

Do you get any error messages in the admin console when you tried to add the devices?

 

Edited November 23, 2020 by Techman

[Dr.Mike]

Im having the same problem trying to link a I/O Linc 2450.  I have two, and have been unable to link either one.  Tried both ways; 1) specify the device ID and auto discovery, and 2) the more generalized link option in the Link management tab.    

[Rob Devlin]

I've tried in many different locations throughout the home with the same result.  I have existing Insteon devices that I'm able to link up on these various circuits with no problem.  This issue is consistent on all 4 of the new ones I just purchased which has me extra curious about this issue.

Admin console gives me a "The following devices cannot be added, cannot determine Insteon engine" error.

I tried linking all 4 at once and many other combinations as well just to see if there would be a different outcome, but no luck.

[palayman]

You may want to try Add New Insteon Device but instead of auto discover put it the device type, 2635-222, as well as the ID. This worked for someone in the past.

[Brian H]

10 hours ago, Dr.Mike said:

Im having the same problem trying to link a I/O Linc 2450.  I have two, and have been unable to link either one.  Tried both ways; 1) specify the device ID and auto discovery, and 2) the more generalized link option in the Link management tab.    

What firmware are you using and does the UI match?

The 2450 is a power line only module. Have you tried on in the same outlet as the PLM is in?

[Brian H]

Rob,

You may want to open a support ticket with UDI and see if they can look at your original post. To see if anything strange is in the information exchanged between the ISY994i and the modules in question.

Your log shows there is communications between the modules and the ISY994i. Could be 5.3.0 has an issue or Smarthome changed things in the modules firmware and the ISY994i doesn't recognize it.

[Michel Kohanim]

@Rob Devlin,

Sat 11/21/2020 20:52:43 : [Std-Direct Nack] 54.A2.55-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 ... this is a Nack. Usually related to the device not having any load attached.

With kind regards,
Michel

[Rob Devlin]

I was able to get 1 of the 4 2635-222 units to connect yesterday by isolating it from the home's power supply and letting it communicate via RF only.  It worked only once and the other 3 will still not connect.

 

[Techman]

4 hours ago, Rob Devlin said:

I was able to get 1 of the 4 2635-222 units to connect yesterday by isolating it from the home's power supply and letting it communicate via RF only.  It worked only once and the other 3 will still not connect.

 

You may have something that's creating noise on your powerline. Do you have a UPS, Computer, or other electronics plugged into the same circuit as your PLM?  Take a look at the following troubleshooting tips

 

INSTEON: Troubleshooting Communications Errors

Communication Problems with INSTEON Devices

The INSTEON protocol is a much more robust communication protocol than the older X10 protocol that it replaces. However, INSTEON users will sometimes find that while their INSTEON devices seem to communicate reliably between themselves, the ISY will report "Communication Errors" on their power line network. There are multiple reasons for this:

• The ISY communicates to the INSTEON devices on a power line network via the SmartHome PLM (PowerLinc Modem). The PLM can be less tolerant of weak INSTEON signals and power line "noise" (interference) than the actual INSTEON switch devices themselves.
• The PLM and ISY require reliable "acknowledgements" of their "requests" to the INSTEON devices. When these are not properly received for any reason, the ISY will display an error. Sometimes this will prevent the completion of an ISY function.

Due to these characteristics, a power line network must be as free as possible from substantial interference or signal loss, in order for the ISY to provide error-free INSTEON device monitoring and control.

The following tips may be helpful if communication problems are encountered:

• Move the PLM to a different outlet and one that's not shared with other transformers and power supplies
• Do not plug a PLM into a power strip that has any type of surge-suppression incorporated, as this can weaken the INSTEON signals. Likewise, certain models of GFCI outlets have also been reported to degrade INSTEON signals (this, however, is not true for all GFCIs). To provide for surge protection for the PLM, ISY, and all of your INSTEON devices, consider using a "whole house" surge suppressor. This can often be supplied and installed by your electric power utility for a minimal charge.
• If you have old SignaLincs and Access Points, remove them and instead use dual band devices

The next points are probably some of the most important:

• Use power line filtering devices (such as the SmartHome Filterlinc) on all potential signal “sinks” and noise generating devices in your home. Devices such as computer power supplies, televisions, home theater systems, etc, can all act as “signal sinks” that degrade the INSTEON signals on your power line network. Conversely, devices such as low voltage halogen lighting, CFLs (compact fluorescent light bulbs), etc, can generate interference patterns on your power line network that can cause the PLM or even other INSTEON devices to miss INSTEON control signals, which get lost in the background noise on the power line. Even if you have previously installed some power line filters on your system, you may find that more may be required if problems still persist. Also, remember that the bottom outlet on the FilterLinc is the “filtered” outlet.
• For hard-wired halogen or fluorescent lighting, in-line noise suppressors can be used (such as the Levition Noise Block model 6287).
• Some CFLs are prone to producing much higher levels of power line noise than others. CFLs that are producing excessive line noise can be replaced with those that produce less interference.

 

INSTEON Signal / Noise Troubleshooting

Our support department gets a fair amount of calls with question on INSTEON signal troubleshooting. The problems that the customers are experiencing are related to noise on the powerline and not an issue with the ISY. I wanted to provide a few points that you may find helpful in troubleshooting communication issues to your INSTEON devices from the ISY.

We tend to look to noise at the culprit when things start to become intermittent with device communication.

Example: Today 3 or my 5 devices turned on in a scene but yesterday everything worked fine.

Tools to look for noise.

1) Place an INSTEON keypad in link mode and watch the flashing cadence. It should flash on and off about every second. When noise is present the flash cadence will be all over the place. It might flicker instead of flash and it might stay off to 5 or 10 seconds at a time then flash fast. (to put a keypad in link mode you just press and hold the set button in for 5 seconds)

2) Some INSTEON devices actually have a function called flash on traffic. This will cause the LED on the device to flash when it see powerline traffic and in some cases it can show noise also.

3) Query a device in the ISY and it should query very fast. If it takes 20 seconds (it should take a second or two) then you may have noise of phase bridging issues.

What to do to identify Noise.

1) I find the easiest way to get to the bottom of the cause is to look for the idenitifier like the flashing on the keypad then go to the breaker panel and turn off the first breaker. Look to see if the flashing goes back to normal. If not then turn that breaker on and turn off the next. Keep doing it until the keypad flashes at a normal cadence. Note: Try not to switch the breaker that controls the keypad you are watching. If you go through all of the breakers and you have found the cause then it may be the circuit the keypad is on. In this case you unplug any device plugged into that circuit and see if one of the plug in loads is the cause. Once you find it you can simply buy a plug in filter and filter that device.

In closing, there doesn’t have to be a device that you just added that causes the problem. It could be a device you have had for years and one day it starts to throw noise on the powerline. I had a customer that had a Sonic Care tooth brush and then the brush was in the charger it destroyed communication to 120 switches in his house. This is just one example and there are other stories like this with simple plugin loads that start to produce noise on their own.