trocks797 Posted January 3, 2013 Share Posted January 3, 2013 Hello all. Let me apologize first if my terminology is wrong- I just joined the UD family a week ago. Anyway, I had a bag of old SwitchLinc 2476D v3.2's laying around and figured I would add them to my system. After installing the first one and factory resetting it, I attempted to link it to the ISY the same way I always have- place the ISY in linking mode and hold the top of the rocker for 10 seconds. Instead of linking (the controlled light does not flash twice), the SwitchLinc LED begins flashing. Simultaneously, a long beep is emitted from the 2413S, and it exits link mode. I have verified the switch pairs and works properly with a ControlLinc at the same outlet as the 2413S (to verify proper communication), but I can't seem to get the 2476D and 2413S to be friends. Other notes that may be of importance: -4 Access points installed in the house + 2413S -LampLinc (located 3 feet away from SwitchLinc in question) works flawlessly with ISY/2413S -ISY994i PRO running 3.2.6 Thank you all for your time! Tyler Link to comment Share on other sites More sharing options...
LeeG Posted January 3, 2013 Share Posted January 3, 2013 Try using New INSTEON Device, enter Insteon Address, Name of choice and Device Type at default Auto Discover. If that does not work, run Tools | Diagnostics | Event Viewer at LEVEL 3. Repeat the New INSTEON Device described above. Post the event trace. There are issues with certain older SwitchLinc firmware. Once added to the ISY post the SwitchLinc firmware displayed in the right pane of the Admin Console when the SwitchLinc node is selected in the My Lighting tree. Link to comment Share on other sites More sharing options...
trocks797 Posted January 3, 2013 Author Share Posted January 3, 2013 Try using New INSTEON Device, enter Insteon Address, Name of choice and Device Type at default Auto Discover. If that does not work, run Tools | Diagnostics | Event Viewer at LEVEL 3. Repeat the New INSTEON Device described above. Post the event trace. There are issues with certain older SwitchLinc firmware. Once added to the ISY post the SwitchLinc firmware displayed in the right pane of the Admin Console when the SwitchLinc node is selected in the My Lighting tree. Thank you. I tried that with no sucess. First I tried without pressing the SwichLinc rocker for 10 seconds. This is what the even log showed: Thu 01/03/2013 12:50:57 PM : ---- Initializing the linked devices ---- Thu 01/03/2013 12:50:57 PM : ---- All Linked Devices are now initialized ---- Thu 01/03/2013 12:50:57 PM : ---- Add remaining devices ---- Thu 01/03/2013 12:50:57 PM : [iNST-TX-I1 ] 02 62 0B 7A 08 0F 0D 00 Thu 01/03/2013 12:50:57 PM : [iNST-ACK ] 02 62 0B.7A.08 0F 0D 00 06 (00) Thu 01/03/2013 12:51:06 PM : [iNST-TX-I1 ] 02 62 0B 7A 08 0F 0D 00 Thu 01/03/2013 12:51:06 PM : [iNST-ACK ] 02 62 0B.7A.08 0F 0D 00 06 (00) Thu 01/03/2013 12:51:15 PM : [iNST-TX-I1 ] 02 62 0B 7A 08 0F 0D 00 Thu 01/03/2013 12:51:15 PM : [iNST-ACK ] 02 62 0B.7A.08 0F 0D 00 06 (00) Thu 01/03/2013 12:51:19 PM : ---- All Remaining Device Added ---- Thu 01/03/2013 12:51:19 PM : [All ] Writing 0 bytes to devices Thu 01/03/2013 12:51:22 PM : [ Time] 12:51:22 8(0) Then I repeated it while the LED on the SwichLinc was flashing (if that matters). I got this: Thu 01/03/2013 12:52:46 PM : ---- Initializing the linked devices ---- Thu 01/03/2013 12:52:46 PM : ---- All Linked Devices are now initialized ---- Thu 01/03/2013 12:52:46 PM : ---- Add remaining devices ---- Thu 01/03/2013 12:52:46 PM : [iNST-TX-I1 ] 02 62 0B 7A 08 0F 0D 00 Thu 01/03/2013 12:52:46 PM : [iNST-ACK ] 02 62 0B.7A.08 0F 0D 00 06 (00) Thu 01/03/2013 12:52:55 PM : [iNST-TX-I1 ] 02 62 0B 7A 08 0F 0D 00 Thu 01/03/2013 12:52:55 PM : [iNST-ACK ] 02 62 0B.7A.08 0F 0D 00 06 (00) Thu 01/03/2013 12:53:04 PM : [iNST-TX-I1 ] 02 62 0B 7A 08 0F 0D 00 Thu 01/03/2013 12:53:04 PM : [iNST-ACK ] 02 62 0B.7A.08 0F 0D 00 06 (00) Thu 01/03/2013 12:53:08 PM : ---- All Remaining Device Added ---- Thu 01/03/2013 12:53:08 PM : [All ] Writing 0 bytes to devices The only difference is the last line...time, is missing from the second attempt (if that matters). The ID number listed on the SwitchLinc is 0B.7A.08. The SwitchLinc is nowhere to be found on ISY. Thank you! Link to comment Share on other sites More sharing options...
Michel Kohanim Posted January 4, 2013 Share Posted January 4, 2013 Hi trocks797, This very much looks like communications error ... ISY retries 3 times but your SWL never responds. With kind regards, Michel Link to comment Share on other sites More sharing options...
LeeG Posted January 4, 2013 Share Posted January 4, 2013 trocks797 As Michel has already indicated the SwitchLinc did not respond to any of the attempts to send it commands. The trace entries that start with 02 6x are outbound to the device. If/when the device responds there will be 02 5x inbound messages. There are no 02 5x messages. Could be the SwitchLinc is on the opposite phase and there is phase coupling issue. Could be circuit the SwitchLinc is on has interference. Could be a defective device. The simple test is to connect the SwitchLinc to an Appliance cord (plug on one end, bare wires on the other) , plugging the Appliance cord into the PLM plug point. If it works there then phase coupling or circuit interference are likely problem areas. Link to comment Share on other sites More sharing options...
trocks797 Posted January 4, 2013 Author Share Posted January 4, 2013 Thank you all for your help. This morning, magically, I was able to connect the two. The reliability is awful, so I am trying to troubleshoot that. I wonder why the ControLinc was able to connect yesterday and operate reliably? Boggles my mind, but thank you nonetheless! Link to comment Share on other sites More sharing options...
LeeG Posted January 4, 2013 Share Posted January 4, 2013 trocks797 The ability to do some work this morning is an indication the problem has some variability over time. In other words, you got lucky. An event trace of the activity would likely have shown unreliable communication that was successful because of the multiple retries Insteon has built into the protocol. Or it could have shown good communication which would indicate the source of the problem may not have been turned On at the time. That is why I like to keep the event viewer running. The fact that something was successful does not mean the problem was not present. By unplugging devices/appliances, turning circuits off at the breaker, verifying coupling is reliable, all those time consuming things will eventually identify the source of the problem. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.