prairiecode Posted January 22, 2015 Share Posted January 22, 2015 Hi folks, I have a new 2-wire SwitchLinc 2474DWH. Just installed today. It appears to work fine. My 994i detects it immediately as expected when I start linking. However, after a little while, I get "Cannot determine device linkt table address." I've Googled this and tried the other suggestions: factory reset the SwitchLinc, power cycle the 994i and PLM, and none of them help. RF signal strength should not be an issue; I have lots of 3-wire 2477D switches (which double as access points) in the house. I had one other 2-wire switch that took a try or two to link (but not giving me this error), but I consistently cannot get this one to work. Any ideas? Here's the detailed event log: Thu 01/22/2015 04:58:02 PM : Start Insteon Device Linking Mode Thu 01/22/2015 04:58:02 PM : [LNK-BGN ] 02 64 01 00 06 Thu 01/22/2015 04:58:11 PM : [LNK-STAT ] 02 53 M(01) gid=00 28.D2.BE 0124 42 Thu 01/22/2015 04:58:11 PM : [28.D2.BE 00] Linked device type=01.24 fw=42 Thu 01/22/2015 04:58:11 PM : [28 D2 BE 0 ] Added to list of devices to link to ISY Thu 01/22/2015 04:58:11 PM : [LNK-BGN ] 02 64 01 00 06 Thu 01/22/2015 04:58:18 PM : Stop Insteon Device Linking Mode, Final processing to follow Thu 01/22/2015 04:58:18 PM : [INST-TX-I1 ] 02 62 28 D2 BE 0F 0D 00 Thu 01/22/2015 04:58:18 PM : [LNK-END ] 02 65 06 Thu 01/22/2015 04:58:18 PM : [Std MH ] Unexpected Ack imCmd=65 cmd1= 0xBE Thu 01/22/2015 04:58:19 PM : [INST-ACK ] 02 62 28.D2.BE 0F 0D 00 06 (00) Thu 01/22/2015 04:58:20 PM : [INST-SRX ] 02 50 28.D2.BE 33.5F.0F 27 0D 02 (02) Thu 01/22/2015 04:58:20 PM : [Std-Direct Ack] 28.D2.BE-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Thu 01/22/2015 04:58:24 PM : [INST-TX-I1 ] 02 62 28 D2 BE 0F 0D 00 Thu 01/22/2015 04:58:24 PM : [INST-ACK ] 02 62 28.D2.BE 0F 0D 00 06 (00) Thu 01/22/2015 04:58:24 PM : [INST-SRX ] 02 50 28.D2.BE 33.5F.0F 2B 0D 02 (02) Thu 01/22/2015 04:58:24 PM : [Std-Direct Ack] 28.D2.BE-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Thu 01/22/2015 04:58:24 PM : [28 D2 BE 0 ] Calibrating engine version Thu 01/22/2015 04:58:24 PM : [INST-TX-I2CS] 02 62 28 D2 BE 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Thu 01/22/2015 04:58:24 PM : [INST-ACK ] 02 62 28.D2.BE 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Thu 01/22/2015 04:58:33 PM : [INST-TX-I2CS] 02 62 28 D2 BE 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Thu 01/22/2015 04:58:33 PM : [INST-ACK ] 02 62 28.D2.BE 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Thu 01/22/2015 04:58:42 PM : [INST-TX-I2CS] 02 62 28 D2 BE 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Thu 01/22/2015 04:58:42 PM : [INST-ACK ] 02 62 28.D2.BE 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Thu 01/22/2015 04:58:46 PM : [28 D2 BE 0 ] Failed to add device, reason 9 Thu 01/22/2015 04:58:46 PM : [All ] Writing 0 bytes to devices Thu 01/22/2015 04:58:46 PM : [All ] Writing 0 bytes to devices Link to comment Share on other sites More sharing options...
LeeG Posted January 22, 2015 Share Posted January 22, 2015 None of the commands that require an Extended message in response are receiving the Extended message. With the 2474DWH being RF only and Hops Left=1 it appears to be on the opposite 120v leg compared to the PLM. Something in the Insteon network is not moving the Extended messages between the 120v legs. Is the PLM a 2412 or 2413? Link to comment Share on other sites More sharing options...
prairiecode Posted January 22, 2015 Author Share Posted January 22, 2015 It's a 2413S. Strange that - the device that must be relaying it is working fine. I'm assuming I'm seeing something like this: PLM (leg A) -- wire -- some device leg A -- RF -- some device leg B -- RF -- 2474DWH right? Link to comment Share on other sites More sharing options...
LeeG Posted January 23, 2015 Share Posted January 23, 2015 I cannot be certain about which leg from that one event trace. The Standard length messages are getting a response from the device. Thu 01/22/2015 04:58:18 PM : [INST-TX-I1 ] 02 62 28 D2 BE 0F 0D 00Thu 01/22/2015 04:58:18 PM : [LNK-END ] 02 65 06 Thu 01/22/2015 04:58:18 PM : [Std MH ] Unexpected Ack imCmd=65 cmd1= 0xBEThu 01/22/2015 04:58:19 PM : [INST-ACK ] 02 62 28.D2.BE 0F 0D 00 06 (00)Thu 01/22/2015 04:58:20 PM : [INST-SRX ] 02 50 28.D2.BE 33.5F.0F 27 0D 02 (02) - Standard message response - I2CS device The Extended messages are not getting a response from the device. Thu 01/22/2015 04:58:24 PM : [INST-TX-I2CS] 02 62 28 D2 BE 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0Thu 01/22/2015 04:58:24 PM : [INST-ACK ] 02 62 28.D2.BE 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00)Thu 01/22/2015 04:58:33 PM : [INST-TX-I2CS] 02 62 28 D2 BE 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0Thu 01/22/2015 04:58:33 PM : [INST-ACK ] 02 62 28.D2.BE 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00)Thu 01/22/2015 04:58:42 PM : [INST-TX-I2CS] 02 62 28 D2 BE 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0Thu 01/22/2015 04:58:42 PM : [INST-ACK ] 02 62 28.D2.BE 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00)Thu 01/22/2015 04:58:46 PM : [28 D2 BE 0 ] Failed to add device, reason 9 Could try a Factory Reset of device, then use New INSTEON Device. Enter Insteon address 28.D2.BE, Name of choice, and Auto Discover. The command sequence is slightly different using New INSTEON Device. Link to comment Share on other sites More sharing options...
Techman Posted January 23, 2015 Share Posted January 23, 2015 What type of loads are the switches controlling, they will only work with incandescent lighting. Link to comment Share on other sites More sharing options...
prairiecode Posted January 23, 2015 Author Share Posted January 23, 2015 I tried the New INSTEON Device approach too -- same exact result. There are LED bulbs behind this device. I have tried it with the lights on and off. It seems to work otherwose.... Link to comment Share on other sites More sharing options...
LeeG Posted January 23, 2015 Share Posted January 23, 2015 The device cannot draw the required power through an LED. Change to an incandescent load. Link to comment Share on other sites More sharing options...
stusviews Posted January 23, 2015 Share Posted January 23, 2015 or halogen. Link to comment Share on other sites More sharing options...
prairiecode Posted January 23, 2015 Author Share Posted January 23, 2015 You all might be right -- I eventually solved this, in a rounabout way, I guess. I am building out my Insteon network, and happened to install a switch in a box that's just about 2 feet away. That box has a 3-wire switch in it, and once that switch was installed, the 2-wire switch was 1 hop away instead of 3 and started working perfectly. Link to comment Share on other sites More sharing options...
Techman Posted January 23, 2015 Share Posted January 23, 2015 The 2 wire switch will not work reliably when used with LED bulbs. Link to comment Share on other sites More sharing options...
Dean Posted July 12, 2015 Share Posted July 12, 2015 I am having similar problems with no recognition of the Insteon engine. I AM able to manually link the Insteon 2 wire switch to a regular 3 wire switch across the hall and it works perfectly. Why would it not link through the ISY if the other switch can see/hear it? Link to comment Share on other sites More sharing options...
LeeG Posted July 12, 2015 Share Posted July 12, 2015 What is a "regular 3 wire switch"? Is this an Insteon device? If so what number? Normally that message is a comm issue. Can you post an Event Viewer at LEVEL 3 taken when attempting to add device. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.