Can't add 2635-222

captainc · February 10, 2019

I am trying to add the 2635-222 and it comes back as it can't find the insteon engine. the address is 40.02.30 and i can't understand because:

this unit worked at my other house that has a ton of insteon products, both using 994/IR pro 5.0.14.

I have added a few other insteon items this fall including the outdoor module and installed ok. Using a Fluke 125B scope so i can see the signal and it is good, no noise.

Have filterlincs all over the place, phase couplers, range extenders, etc. factory reset the 2635

below is the level 3 event viewer for trying to add:

Sat 02/09/2019 07:15:02 PM : [40 2 30 ] Added to list of devices to link to ISY
Sat 02/09/2019 07:15:02 PM : [INST-TX-I1 ] 02 62 40 02 30 0F 0D 00
Sat 02/09/2019 07:15:02 PM : [INST-ACK ] 02 62 40.02.30 0F 0D 00 06 (00)
Sat 02/09/2019 07:15:02 PM : [INST-SRX ] 02 50 40.02.30 3C.49.6D AF 0D FF (FF)
Sat 02/09/2019 07:15:02 PM : [Std-Direct Nack] 40.02.30-->ISY/PLM Group=0, Max Hops=3, Hops Left=3
Sat 02/09/2019 07:15:02 PM : [INST-TX-I2CS] 02 62 40 02 30 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6
Sat 02/09/2019 07:15:02 PM : [INST-ACK ] 02 62 40.02.30 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6 06 LNK-ON (01)
Sat 02/09/2019 07:15:03 PM : [INST-SRX ] 02 50 40.02.30 3C.49.6D 2F 09 01 LNK-ON (01)
Sat 02/09/2019 07:15:03 PM : [Std-Direct Ack] 40.02.30-->ISY/PLM Group=0, Max Hops=3, Hops Left=3
Sat 02/09/2019 07:15:03 PM : [LNK-BGN ] 02 64 01 00 06
Sat 02/09/2019 07:15:04 PM : [LNK-STAT ] 02 53 M(01) gid=00 40.02.30 0237 48
Sat 02/09/2019 07:15:04 PM : [INST-TX-I1 ] 02 62 40 02 30 0F 0D 00
Sat 02/09/2019 07:15:04 PM : [LNK-END ] 02 65 06
Sat 02/09/2019 07:15:04 PM : [Std MH ] Unexpected Ack imCmd=65 cmd1=BEEP 0x30
Sat 02/09/2019 07:15:04 PM : [INST-ACK ] 02 62 40.02.30 0F 0D 00 06 (00)
Sat 02/09/2019 07:15:05 PM : [ Time] 19:15:07 42(0)
Sat 02/09/2019 07:15:05 PM : [INST-SRX ] 02 50 40.02.30 3C.49.6D AF 0D FF (FF)
Sat 02/09/2019 07:15:05 PM : [Std-Direct Nack] 40.02.30-->ISY/PLM Group=0, Max Hops=3, Hops Left=3
Sat 02/09/2019 07:15:09 PM : [INST-TX-I1 ] 02 62 40 02 30 0F 0D 00
Sat 02/09/2019 07:15:09 PM : [INST-ACK ] 02 62 40.02.30 0F 0D 00 06 (00)
Sat 02/09/2019 07:15:09 PM : [INST-SRX ] 02 50 40.02.30 3C.49.6D AF 0D FF (FF)
Sat 02/09/2019 07:15:09 PM : [Std-Direct Nack] 40.02.30-->ISY/PLM Group=0, Max Hops=3, Hops Left=3
Sat 02/09/2019 07:15:09 PM : [40 2 30 0 ] Failed to add device, reason 3
Sat 02/09/2019 07:15:09 PM : [40 2 30 ] Added to list of devices to link to ISY
Sat 02/09/2019 07:15:09 PM : [INST-TX-I1 ] 02 62 40 02 30 0F 0D 00
Sat 02/09/2019 07:15:09 PM : [All ] Writing 0 bytes to devices
Sat 02/09/2019 07:15:09 PM : [All ] Writing 0 bytes to devices
Sat 02/09/2019 07:15:09 PM : [INST-ACK ] 02 62 40.02.30 0F 0D 00 06 (00)
Sat 02/09/2019 07:15:10 PM : [INST-SRX ] 02 50 40.02.30 3C.49.6D AF 0D FF (FF)
Sat 02/09/2019 07:15:10 PM : [Std-Direct Nack] 40.02.30-->ISY/PLM Group=0, Max Hops=3, Hops Left=3
Sat 02/09/2019 07:15:10 PM : [INST-TX-I2CS] 02 62 40 02 30 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6
Sat 02/09/2019 07:15:10 PM : [INST-ACK ] 02 62 40.02.30 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6 06 LNK-ON (01)
Sat 02/09/2019 07:15:10 PM : [INST-SRX ] 02 50 40.02.30 3C.49.6D 2F 09 01 LNK-ON (01)
Sat 02/09/2019 07:15:10 PM : [Std-Direct Ack] 40.02.30-->ISY/PLM Group=0, Max Hops=3, Hops Left=3
Sat 02/09/2019 07:15:10 PM : [LNK-BGN ] 02 64 01 00 06
Sat 02/09/2019 07:15:12 PM : [LNK-STAT ] 02 53 M(01) gid=00 40.02.30 0237 48
Sat 02/09/2019 07:15:12 PM : [INST-TX-I1 ] 02 62 40 02 30 0F 0D 00
Sat 02/09/2019 07:15:12 PM : [LNK-END ] 02 65 06
Sat 02/09/2019 07:15:12 PM : [Std MH ] Unexpected Ack imCmd=65 cmd1=BEEP 0x30
Sat 02/09/2019 07:15:12 PM : [INST-ACK ] 02 62 40.02.30 0F 0D 00 06 (00)
Sat 02/09/2019 07:15:12 PM : [INST-SRX ] 02 50 40.02.30 3C.49.6D AF 0D FF (FF)
Sat 02/09/2019 07:15:12 PM : [Std-Direct Nack] 40.02.30-->ISY/PLM Group=0, Max Hops=3, Hops Left=3
Sat 02/09/2019 07:15:17 PM : [INST-TX-I1 ] 02 62 40 02 30 0F 0D 00
Sat 02/09/2019 07:15:17 PM : [INST-ACK ] 02 62 40.02.30 0F 0D 00 06 (00)
Sat 02/09/2019 07:15:17 PM : [INST-SRX ] 02 50 40.02.30 3C.49.6D AF 0D FF (FF)
Sat 02/09/2019 07:15:17 PM : [Std-Direct Nack] 40.02.30-->ISY/PLM Group=0, Max Hops=3, Hops Left=3
Sat 02/09/2019 07:15:17 PM : [40 2 30 0 ] Failed to add device, reason 3
Sat 02/09/2019 07:15:17 PM : [All ] Writing 0 bytes to devices
Sat 02/09/2019 07:15:17 PM : [All ] Writing 0 bytes to devices
Sat 02/09/2019 07:17:57 PM : [INST-SRX ] 02 50 4F.67.C3 3C.49.6D 05 6F 23 (23)
Sat 02/09/2019 07:17:57 PM : [Std-Direct ] 4F.67.C3-->ISY/PLM Group=0, Max Hops=1, Hops Left=1

any suggestions would be appreciated.

thanks

kclenden · February 10, 2019

The Event Viewer indicates that the device is responding to the ISY. And those responses are consistently the same so I don't think this is a communication problem. The Event Viewer makes it look like you used the "Link Management>New INSTEON Device" menu option, and typed in the address of the device, but I can't tell if you used "Auto Discover" as the "Device Type". If you did, I'd suggest specifying the exact device type:

image.png.64e3c61702835f5415b980db510f4a11.png

smokegrub · February 10, 2019

Please don't be offended, but I have mistaken the device address on more than one occasion. I would confirm it.

Techman · February 10, 2019

The error message indicates a communications problem between the PLM and the DEVICE

Take a look at this video troubleshooting video https://www.youtube.com/watch?v=NMx5yHTU2g4

captainc · February 11, 2019

i got the address correct. i even took another 2635-222 out of the outlet that has worked well for a couple of years and put this one in it's place and tried to link it and it doesn't work

i tried new insteon device using the address and model number, same problem

did the linking on the isy admin console and then holding the set button until long beep, same problem

i bought a new 2635-222 and it would not add to my isy at this house, same problem as listed previously. so i took it to my other house and that isy (same everything) it recognized it no problem so i took a 2635 from that house and brought it here so i know it has worked for a while. i did try a number of times on the linking video and that's how i got the event viewer log

the problem continues with this one. it's almost like this isy won't recognize new versions of the 2635-222.

kclenden · February 11, 2019

10 hours ago, Techman said:

The error message indicates a communications problem between the PLM and the DEVICE

Take a look at this video troubleshooting video https://www.youtube.com/watch?v=NMx5yHTU2g4

That video doesn't apply to the OP's problem. You'll note early in the video, Steve mentions that the PLM is not receiving any SRX records. If you look at the OP's Event Viewer log, you'll see SRX records. The device is clearly talking to the PLM. The issue is that the ISY doesn't seem to understand the device's response.

You can see the ISY try twice to link with the device, and each time the responses contain exactly the same data. If there were a communication problem, either there would be no responses, or you would expect the responses to be different because of line noise. That's not happening. So it seems like the ISY really can't determine the device's Insteon Engine from the response it's getting from the device.

Techman · February 11, 2019

7 minutes ago, captainc said:

i got the address correct. i even took another 2635-222 out of the outlet that has worked well for a couple of years and put this one in it's place and tried to link it and it doesn't work

i tried new insteon device using the address and model number, same problem

did the linking on the isy admin console and then holding the set button until long beep, same problem

i bought a new 2635-222 and it would not add to my isy at this house, same problem as listed previously. so i took it to my other house and that isy (same everything) it recognized it no problem so i took a 2635 from that house and brought it here so i know it has worked for a while. i did try a number of times on the linking video and that's how i got the event viewer log

the problem continues with this one. it's almost like this isy won't recognize new versions of the 2635-222.

What ISY firmware and UI are you running?

The device is compatible with 4.7.3 ISY firmware.

Do a factory reset on the module then ty plugging into a different outlet. Don't press the set button on the module, just enter the modules address into the ISY and then try linking

kclenden · February 11, 2019

It might also be helpful to know what version your PLM is at each house, as well as how old they are. Just use "Tools>Diagnostics>PLM Info/Status" to get the version.

captainc · February 11, 2019

the plm are a couple of years old (that's all they last for me) and i use to have a spare for when it goes but don't now.

it is v2.1

i did the factory reset a couple times on the 2635, have tried numerous outlets including the same on the plm is plugged into

isy is 5.0.14

Sub-Routine · February 11, 2019

If it fails to manually link to a SwitchLinc then the device is faulty and SH will replace it under warranty. They will not replace it if you haven't tested it that way.
I use an extension cord cut in half and wire-nut the switch into the middle, hot and neutral with no load connected, plug the On/Off module in the socket, also connected to hot and neutral, then plug it in the wall. That's as good as you are going to get communications.

kclenden · February 11, 2019

On 2/9/2019 at 7:44 PM, captainc said:

Sat 02/09/2019 07:15:02 PM : [INST-TX-I1 ] 02 62 40 02 30 0F 0D 00 ISY gives "Get INSTEON Engine" command to PLM to send to Device
Sat 02/09/2019 07:15:02 PM : [INST-ACK ] 02 62 40.02.30 0F 0D 00 06 (00)  PLM confirms to ISY that it will send command to Device
Sat 02/09/2019 07:15:02 PM : [INST-SRX ] 02 50 40.02.30 3C.49.6D AF 0D FF (FF)  PLM passes response from Device to ISY (Device replied that it doesn't recognize the PLM address)
Sat 02/09/2019 07:15:02 PM : [Std-Direct Nack] 40.02.30-->ISY/PLM Group=0, Max Hops=3, Hops Left=3  This is UD's parsing of the reply from the Device
Sat 02/09/2019 07:15:02 PM : [INST-TX-I2CS] 02 62 40 02 30 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6  ISY gives "Enter Linking Mode" command to PLM to send to Device
Sat 02/09/2019 07:15:02 PM : [INST-ACK ] 02 62 40.02.30 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6 06 LNK-ON (01)  PLM confirms to ISY that it will send command to Device
Sat 02/09/2019 07:15:03 PM : [INST-SRX ] 02 50 40.02.30 3C.49.6D 2F 09 01 LNK-ON (01)  PLM passes response from Device to ISY (Devices replied that it has entered linking mode)
Sat 02/09/2019 07:15:03 PM : [Std-Direct Ack] 40.02.30-->ISY/PLM Group=0, Max Hops=3, Hops Left=3  This is UD's parsing of the reply from the Device
Sat 02/09/2019 07:15:03 PM : [LNK-BGN ] 02 64 01 00 06 ISY tells Device to start linking as controller for group 1
Sat 02/09/2019 07:15:04 PM : [LNK-STAT ] 02 53 M(01) gid=00 40.02.30 0237 48 Device replies linking completed as controller and that its Device Category is 02, its Device Subcategory is 37 and its Firmware Revision is 48 (Note that the Category and Subcategory match what the 2635-222 user manual says they should be)
Sat 02/09/2019 07:15:04 PM : [INST-TX-I1 ] 02 62 40 02 30 0F 0D 00 Now that it should be in the device's DB, the ISY again gives "Get INSTEON Engine" command to PLM to send to Device
Sat 02/09/2019 07:15:04 PM : [LNK-END ] 02 65 06 ISY tells Device to exit linking mode
Sat 02/09/2019 07:15:04 PM : [Std MH ] Unexpected Ack imCmd=65 cmd1=BEEP 0x30 I don't think this is relevant. I see similar message during my linking experiments
Sat 02/09/2019 07:15:04 PM : [INST-ACK ] 02 62 40.02.30 0F 0D 00 06 (00)  PLM confirms to ISY that it will send command to Device
Sat 02/09/2019 07:15:05 PM : [ Time] 19:15:07 42(0)
Sat 02/09/2019 07:15:05 PM : [INST-SRX ] 02 50 40.02.30 3C.49.6D AF 0D FF (FF)  PLM passes response from Device to ISY (Device replied that it doesn't recognize the PLM address) - but it should be because of the linking done above
Sat 02/09/2019 07:15:05 PM : [Std-Direct Nack] 40.02.30-->ISY/PLM Group=0, Max Hops=3, Hops Left=3  This is UD's parsing of the reply from the Device
Sat 02/09/2019 07:15:09 PM : [INST-TX-I1 ] 02 62 40 02 30 0F 0D 00 For a third time, ISY gives "Get INSTEON Engine" command to PLM to send to Device
Sat 02/09/2019 07:15:09 PM : [INST-ACK ] 02 62 40.02.30 0F 0D 00 06 (00)  PLM confirms to ISY that it will send command to Device
Sat 02/09/2019 07:15:09 PM : [INST-SRX ] 02 50 40.02.30 3C.49.6D AF 0D FF (FF)  PLM passes response from Device to ISY (Device replied that it doesn't recognize the PLM address) - but it should be because of the linking done above
Sat 02/09/2019 07:15:09 PM : [Std-Direct Nack] 40.02.30-->ISY/PLM Group=0, Max Hops=3, Hops Left=3  This is UD's parsing of the reply from the Device
Sat 02/09/2019 07:15:09 PM : [40 2 30 0 ] Failed to add device, reason 3

Above is my analysis of your linking attempt. It appears that messages between the PLM and On/OFF Module are getting through without a problem. Here are the steps represented in the Event Viewer:

ISY asks the Device about its INSTEON Engine
Device replies that it doesn't recognize the address of the PLM
ISY tells the device to enter linking mode
Devices says OK
ISY tells the device to add the PLM address to its DB
Device says OK
ISY tells device to exit linking mode
ISY asks the Device about its INSTEON Engine
Devices again replies that it doesn't recognize the address of the PLM
ISY asks the Device about its INSTEON Engine
Devices still replies that it doesn't recognize the address of the PLM
ISY gives up

I can't quite tell from your posts exactly what you've tried, but here's what I think you've tried:

Bought a 2635-222 and it wouldn't link at house #1 (tried three different ways - with address & auto discover, with address & device type, without address but actually pressing SET on device - and you've tried plugging this device into outlets that worked before as well as the same outlet as the PLM)
Bought a second 2635-222 and it also wouldn't link at house #1
Took the second 2635-222 to house #2 and it linked without problem
Brought back a 2635-222 that has been working at house #2. What did you do with this device? Were you able to link it at house #1?

I don't think the issue is with the ISY. It can only react to the messages that it receives and according to the Event Viewer it never receives a message that tells it the device's INSTEON Engine. So it would seem either the PLM or the On/Off Module are at fault.

It can't hurt to try Sub-Routine's suggestion to try manually linking a Switch to the On/Off Module. But based on your experience having a new On/Off Module that won't link at house #1 but will link at house #2, my guess is that the Switch will successfully link to the On/Off Module. And if that's the case, then Smarthome won't let you return it. Then I guess your next move would be to contact UD support and have them look at your Event Viewer results.

captainc · February 13, 2019

thanks for everyones input, i am going to order a new plm and use this one as a spare. see if that works. btw i got my isy z wave module for this house today to build out the locks and some other items and even though the process takes a little longer it is solid.

captainc · February 27, 2019

Got my new plm 2413s today it is ver 2.4 versus my old one which was v2.1

after getting it set up i was able to add the 2635-222 easy on the first time.

nothing else changed, it was the modem.

kclenden · February 27, 2019

Thanks for the update. Others with similar problems will benefit from your follow-up.

Sign In

Can't add 2635-222

Recommended Posts

captainc

Link to comment

kclenden

Link to comment

smokegrub

Link to comment

Techman

Link to comment

captainc

Link to comment

kclenden

Link to comment

Techman

Link to comment

kclenden

Link to comment

captainc

Link to comment

Sub-Routine

Link to comment

kclenden

Link to comment

captainc

Link to comment

captainc

Link to comment

kclenden

Link to comment

Archived

Recently Browsing

Who's Online (See full list)

Forum Statistics

Browse

Activity