svetter Posted January 7, 2017 Share Posted January 7, 2017 Folks, I replaced an old switch that stopped working with a new 2477D Rev 7.9i (what does that letter mean?) 3216 and receive the "isy could not determine device link table address" error while adding it. The red wire is not used (capped). Here is the level 3 trace. I'm on my second switch and get the same error (same 2477D Rev 7.9i) I've done a factory reset on the switch and tried a few more times. Here is the trace. What is my next step to diagnose. BTW, I am on v4.5.4 on the ISY. Sat 01/07/2017 05:04:57 PM : [43 15 41 ] Added to list of devices to link to ISYSat 01/07/2017 05:04:57 PM : [iNST-TX-I1 ] 02 62 43 15 41 0F 0D 00Sat 01/07/2017 05:04:57 PM : [iNST-ACK ] 02 62 43.15.41 0F 0D 00 06 (00)Sat 01/07/2017 05:04:58 PM : [iNST-SRX ] 02 50 43.15.41 3B.96.AE 2B 0D 02 (02)Sat 01/07/2017 05:04:58 PM : [std-Direct Ack] 43.15.41-->ISY/PLM Group=0, Max Hops=3, Hops Left=2Sat 01/07/2017 05:04:58 PM : [iNST-TX-I1 ] 02 62 43 15 41 0F 10 00Sat 01/07/2017 05:04:58 PM : [iNST-ACK ] 02 62 43.15.41 0F 10 00 06 ID-REQ (00)Sat 01/07/2017 05:04:58 PM : [iNST-SRX ] 02 50 43.15.41 3B.96.AE 2B 10 00 ID-REQ (00)Sat 01/07/2017 05:04:58 PM : [std-Direct Ack] 43.15.41-->ISY/PLM Group=0, Max Hops=3, Hops Left=2Sat 01/07/2017 05:05:07 PM : [iNST-TX-I1 ] 02 62 43 15 41 0F 10 00Sat 01/07/2017 05:05:07 PM : [iNST-ACK ] 02 62 43.15.41 0F 10 00 06 ID-REQ (00)Sat 01/07/2017 05:05:08 PM : [iNST-SRX ] 02 50 43.15.41 3B.96.AE 2B 10 00 ID-REQ (00)Sat 01/07/2017 05:05:08 PM : [std-Direct Ack] 43.15.41-->ISY/PLM Group=0, Max Hops=3, Hops Left=2Sat 01/07/2017 05:05:17 PM : [iNST-TX-I1 ] 02 62 43 15 41 0F 10 00Sat 01/07/2017 05:05:21 PM : [43 15 41 0 ] Calibrating engine versionSat 01/07/2017 05:05:21 PM : [iNST-TX-I2CS] 02 62 43 15 41 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0Sat 01/07/2017 05:05:29 PM : [iNST-TX-I2CS] 02 62 43 15 41 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0Sat 01/07/2017 05:05:29 PM : [iNST-ACK ] 02 62 43.15.41 10 00 00 15 15 02 62 43 15 41 1F 2F 00 00 00 00 00 01 (00)Sat 01/07/2017 05:05:38 PM : [iNST-TX-I2CS] 02 62 43 15 41 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0Sat 01/07/2017 05:05:38 PM : [iNST-ACK ] 02 62 43.15.41 1F 2F 00 00 00 00 00 00 00 00 00 00 00 D0 D0 00 D0 06 (00)Sat 01/07/2017 05:05:39 PM : [iNST-SRX ] 02 50 43.15.41 3B.96.AE 2B 2F 00 (00)Sat 01/07/2017 05:05:39 PM : [std-Direct Ack] 43.15.41-->ISY/PLM Group=0, Max Hops=3, Hops Left=2Sat 01/07/2017 05:05:39 PM : [iNST-DUP ] Previous message ignored.Sat 01/07/2017 05:05:43 PM : [43 15 41 0 ] Failed to add device, reason 9 Link to comment Share on other sites More sharing options...
stusviews Posted January 7, 2017 Share Posted January 7, 2017 Are both the firmware and UI the same version? Link to comment Share on other sites More sharing options...
Techman Posted January 7, 2017 Share Posted January 7, 2017 I've never seen a revision with a letter before. Try doing a factory reset on the switch then try to link it again. Are you doing a replace device or adding it from scratch? Is your ISY firmware and the UI both the same version? Link to comment Share on other sites More sharing options...
Brian H Posted January 8, 2017 Share Posted January 8, 2017 I have some Insteon modules that now have a letter on the revision level. I have seen an R on refurbished but these are new. 2342-232 Mini Remote. V2.0s 2635-222 On/Off Module V1.1S Link to comment Share on other sites More sharing options...
Teken Posted January 8, 2017 Share Posted January 8, 2017 In the past the letter designation was stated as being used to identify a change in component / hardware revision(s). As Brian H stated the letter ® was used to identify a refurbished device. Every 2635-222 I have on hand has the letter (S) on the white sticker from several years of production so that must mean something global to the product and isn't a intermediate change. I have several leak sensors which also have letters on them but two of them were produced in the exact same year and week yet one doesn't have the letter. I have to assume this over lap is the cut in period which we have seen so many times with firmware and its never communicated to the public until it hits the wild and someone noticed it doesn't work as expected. Regardless of the letters meaning the one thing I am happy to see is they (Smarlabs) seems to have settled on a date format that is consistent across the product line. Because there have been so many cases where the white stickers exceeded what the weeks would have allowed. Meaning there are only 52 weeks in the year - yet people were showing production weeks indicating something stupid of 63?!? Link to comment Share on other sites More sharing options...
svetter Posted January 8, 2017 Author Share Posted January 8, 2017 The UI and Firmware are at the same (latest) level. I bought a second round of switches from a different source and they also were at Rev 7.9i One 3216, the others 2916. I did several factory resets (pull, wait, push and hold until beep ends, release). I am doing an add. It will replace a burned out unit once I get it online then copy over the old links with a replace. Link to comment Share on other sites More sharing options...
svetter Posted January 13, 2017 Author Share Posted January 13, 2017 I'm still scratching my head on this one. Does anyone recommend removing the switch, adding a short cord on it and plugging it in near the ISY controller? I've also through there is line noise and would trip breakers in the house used by other Insteon devices, but with the mesh I have (scenes using this switch), that would be difficult. -Scott Link to comment Share on other sites More sharing options...
Techman Posted January 13, 2017 Share Posted January 13, 2017 I'm still scratching my head on this one. Does anyone recommend removing the switch, adding a short cord on it and plugging it in near the ISY controller? I've also through there is line noise and would trip breakers in the house used by other Insteon devices, but with the mesh I have (scenes using this switch), that would be difficult. - Scott What steps are you taking to add the switch? Have you had any previous communication problems with other Insteon devices? Link to comment Share on other sites More sharing options...
Teken Posted January 13, 2017 Share Posted January 13, 2017 I'm still scratching my head on this one. Does anyone recommend removing the switch, adding a short cord on it and plugging it in near the ISY controller? I've also through there is line noise and would trip breakers in the house used by other Insteon devices, but with the mesh I have (scenes using this switch), that would be difficult. - Scott Scott, Can you offer a little more clarification on breakers tripping? Are these AFCI / GFCI breakers that trip when Insteon signals are seen on the power line? If so there is no simple cure for such a condition besides replacing the breakers with an alternate brand. This assumes your panel can accept other third party common breaker styles. Depending upon your location and what revision of the NEC they use to enforce compliance some have replaced the AFCI / GFCI breakers with standard breakers. Where those circuits were protected by said breakers the equivalent AFCI / GFCI outlets were installed at the head of branch circuit and thus protection all down stream outlets / circuits. Again, you need to inquire and confirm going this route is acceptable and complies with all local ordinances where you reside. Keeping in mind people have been denied home owners insurance because their *Renovation* was not in compliance with electrical codes. Link to comment Share on other sites More sharing options...
svetter Posted January 16, 2017 Author Share Posted January 16, 2017 What I was trying to say (not very clearly upon a re-read) is that I would isolate parts of the house by manually tripping breakers to determine if my problem is excessive line noise, and to help locate what might be generating it. The AFCI breakers in the house only trip when I trip them. The power in the house has been very stable up until the holiday season then the Insteon mesh became unreliable. At first I thought it was the switch that went bad, but it appears to be a larger problem. What do you recommend to isolate or determine if there is line noise? Also, most of my switches are now dual band. So I am at a loss for what could be wrong. Link to comment Share on other sites More sharing options...
Techman Posted January 16, 2017 Share Posted January 16, 2017 What I was trying to say (not very clearly upon a re-read) is that I would isolate parts of the house by manually tripping breakers to determine if my problem is excessive line noise, and to help locate what might be generating it. The AFCI breakers in the house only trip when I trip them. The power in the house has been very stable up until the holiday season then the Insteon mesh became unreliable. At first I thought it was the switch that went bad, but it appears to be a larger problem. What do you recommend to isolate or determine if there is line noise? Also, most of my switches are now dual band. So I am at a loss for what could be wrong. Here's a good starting point https://wiki.universal-devices.com/index.php?title=INSTEON:_Troubleshooting_Communications_Errors https://wiki.universal-devices.com/index.php?title=INSTEON_Signal_/_Noise_Troubleshooting Link to comment Share on other sites More sharing options...
Teken Posted January 16, 2017 Share Posted January 16, 2017 Hello Scott, Have you had the chance to attach the new switch to a lamp cord and plug it into the same outlet as the 2413S PLM and see if it will add? Link to comment Share on other sites More sharing options...
svetter Posted January 17, 2017 Author Share Posted January 17, 2017 Not yet - weekend time between football was fixing a dishwasher. I certainly have the motivation having to manually clean up after ISY timers trigger (not all the lights in a scene make it to their target states). The switch is in a 4-gang j-box. I'll try to dig it out over the next couple of days. I have a grounded appliance cord I harvested from an old vac. I can use for this. Thanks for the link. I'll read that too. Link to comment Share on other sites More sharing options...
svetter Posted January 18, 2017 Author Share Posted January 18, 2017 OK.. so, I pig-tailed an appliance cord on the a uninstalled (easier than removing the switch from the 4-gang j-box) rev 7.9i switch (I own 4 at this level to have extras) and plugged it into the same outlet that the ISY modem was connected to. I factory reset the device pulling the air gap out, counting to 10, then pressing it all the way in and holding until the beep stopped. The add worked (as it finally did on the installed ones after a many attempts, but there were writes still missing to the device. The writes fail. I tried to write updates to the device 4 times and here are the 4 traces. (My next test to to try to add a device with an older firmware.) Tue 01/17/2017 06:59:46 PM : [42 D5 51 1 ] Link 0 : 0FF8 [A2003B96AEFF1F01] Writing [A2003B96AEFF1F01] Tue 01/17/2017 06:59:46 PM : [iNST-TX-I2CS] 02 62 42 D5 51 1F 2F 00 00 02 0F FF 08 A2 00 3B 96 AE FF 1F 01 79 Tue 01/17/2017 06:59:46 PM : [iNST-ACK ] 02 62 42.D5.51 1F 2F 00 02 0F FF 08 A2 00 3B 96 AE FF 1F 01 79 D0 06 (00) Tue 01/17/2017 06:59:47 PM : [iNST-SRX ] 02 50 42.D5.51 3B.96.AE 2F 2F 00 (00) Tue 01/17/2017 06:59:47 PM : [std-Direct Ack] 42.D5.51-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Tue 01/17/2017 06:59:56 PM : [iNST-TX-I2CS] 02 62 42 D5 51 1F 2F 00 00 02 0F FF 08 A2 00 3B 96 AE FF 1F 01 79 Tue 01/17/2017 06:59:56 PM : [iNST-ACK ] 02 62 51.1F.2F 00 00 02 0F (02) Tue 01/17/2017 07:00:05 PM : [iNST-TX-I2CS] 02 62 42 D5 51 1F 2F 00 00 02 0F FF 08 A2 00 3B 96 AE FF 1F 01 79 Tue 01/17/2017 07:00:05 PM : [iNST-ACK ] 02 62 42.D5.51 00 00 02 0F (02) Tue 01/17/2017 07:00:09 PM : [42 D5 51 1 ] Link 0 : 0FF8 [A2003B96AEFF1F01] *Failed Writing [A2003B96AEFF1F01] Tue 01/17/2017 07:00:13 PM : [D2D EVENT ] Event [42 D5 51 1] [ERR] [1] uom=0 prec=-1 Tue 01/17/2017 07:00:13 PM : [ 42 D5 51 1] ERR 1 Trace 2 Tue 01/17/2017 07:01:53 PM : [42 D5 51 1 ] Link 0 : 0FF8 [A2003B96AEFF1F01] Writing [A2003B96AEFF1F01] Tue 01/17/2017 07:01:53 PM : [iNST-TX-I2CS] 02 62 42 D5 51 1F 2F 00 00 02 0F FF 08 A2 00 3B 96 AE FF 1F 01 79 Tue 01/17/2017 07:01:53 PM : [iNST-ACK ] 02 62 42.D5.51 1F 00 00 02 0F FF 08 A2 00 3B 96 AE FF 1F 01 79 D0 06 (00) Tue 01/17/2017 07:01:54 PM : [iNST-SRX ] 02 50 42.D5.51 3B.96.AE 2F 00 00 (00) Tue 01/17/2017 07:01:54 PM : [std-Direct Ack] 42.D5.51-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Tue 01/17/2017 07:02:03 PM : [iNST-TX-I2CS] 02 62 42 D5 51 1F 2F 00 00 02 0F FF 08 A2 00 3B 96 AE FF 1F 01 79 Tue 01/17/2017 07:02:03 PM : [iNST-ACK ] 02 62 42.D5.51 1F 00 00 02 0F FF 08 A2 00 3B 96 AE FF 1F 01 79 D0 06 (00) Tue 01/17/2017 07:02:03 PM : [iNST-SRX ] 02 50 42.D5.51 3B.96.AE 2F 00 00 (00) Tue 01/17/2017 07:02:03 PM : [std-Direct Ack] 42.D5.51-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Tue 01/17/2017 07:02:12 PM : [iNST-TX-I2CS] 02 62 42 D5 51 1F 2F 00 00 02 0F FF 08 A2 00 3B 96 AE FF 1F 01 79 Tue 01/17/2017 07:02:12 PM : [iNST-ACK ] 02 62 42.51.1F 2F 00 00 02 (00) Tue 01/17/2017 07:02:16 PM : [42 D5 51 1 ] Link 0 : 0FF8 [A2003B96AEFF1F01] *Failed Writing [A2003B96AEFF1F01] Tue 01/17/2017 07:02:16 PM : [D2D EVENT ] Event [42 D5 51 1] [ERR] [0] uom=0 prec=-1 Tue 01/17/2017 07:02:16 PM : [ 42 D5 51 1] ERR 0 Trace 3 Tue 01/17/2017 07:03:24 PM : [42 D5 51 1 ] Link 0 : 0FF8 [A2003B96AEFF1F01] Writing [A2003B96AEFF1F01] Tue 01/17/2017 07:03:24 PM : [iNST-TX-I2CS] 02 62 42 D5 51 1F 2F 00 00 02 0F FF 08 A2 00 3B 96 AE FF 1F 01 79 Tue 01/17/2017 07:03:24 PM : [iNST-ACK ] 02 62 42.D5.51 00 00 02 0F (02) Tue 01/17/2017 07:03:33 PM : [iNST-TX-I2CS] 02 62 42 D5 51 1F 2F 00 00 02 0F FF 08 A2 00 3B 96 AE FF 1F 01 79 Tue 01/17/2017 07:03:33 PM : [iNST-ACK ] 02 62 42.D5.51 1F 00 00 02 0F FF 08 A2 00 3B 96 AE FF 1F 01 79 D0 06 (00) Tue 01/17/2017 07:03:33 PM : [iNST-ACK ] 02 62 42.D5.51 1F 00 00 02 0F FF 08 A2 00 3B 96 AE FF 1F 01 79 D0 06 (00): Duplicate or ACK for a different device Tue 01/17/2017 07:03:33 PM : [iNST-SRX ] 02 50 42.D5.51 3B.96.AE 2F 00 00 (00) Tue 01/17/2017 07:03:33 PM : [std-Direct Ack] 42.D5.51-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Tue 01/17/2017 07:03:42 PM : [iNST-TX-I2CS] 02 62 42 D5 51 1F 2F 00 00 02 0F FF 08 A2 00 3B 96 AE FF 1F 01 79 Tue 01/17/2017 07:03:42 PM : [iNST-ACK ] 02 62 42.D5.51 1F 2F 00 00 02 FF 08 A2 00 3B 96 AE FF 1F 01 79 D0 06 (00) Tue 01/17/2017 07:03:43 PM : [iNST-SRX ] 02 50 42.D5.51 3B.96.AE AF 2F FD (FD) Tue 01/17/2017 07:03:43 PM : [std-Direct Nack] 42.D5.51-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Tue 01/17/2017 07:03:43 PM : [D2D EVENT ] Event [42 D5 51 1] [ERR] [1] uom=0 prec=-1 Tue 01/17/2017 07:03:43 PM : [ 42 D5 51 1] ERR 1 Tue 01/17/2017 07:03:47 PM : [42 D5 51 1 ] Link 0 : 0FF8 [A2003B96AEFF1F01] *Failed Writing [A2003B96AEFF1F01] Tue 01/17/2017 07:03:47 PM : [D2D EVENT ] Event [42 D5 51 1] [ERR] [0] uom=0 prec=-1 Tue 01/17/2017 07:03:47 PM : [ 42 D5 51 1] ERR 0 Tracw 4 Tue 01/17/2017 07:04:23 PM : [42 D5 51 1 ] Link 0 : 0FF8 [A2003B96AEFF1F01] Writing [A2003B96AEFF1F01] Tue 01/17/2017 07:04:23 PM : [iNST-TX-I2CS] 02 62 42 D5 51 1F 2F 00 00 02 0F FF 08 A2 00 3B 96 AE FF 1F 01 79 Tue 01/17/2017 07:04:33 PM : [iNST-TX-I2CS] 02 62 42 D5 51 1F 2F 00 00 02 0F FF 08 A2 00 3B 96 AE FF 1F 01 79 Tue 01/17/2017 07:04:33 PM : [iNST-ACK ] 02 62 42.D5.51 1F 2F 02 0F FF 08 A2 00 3B 96 AE FF 1F 01 79 79 D0 06 (02) Tue 01/17/2017 07:04:33 PM : [iNST-SRX ] 02 50 42.D5.51 3B.96.AE 2F 2F 02 (02) Tue 01/17/2017 07:04:33 PM : [std-Direct Ack] 42.D5.51-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Tue 01/17/2017 07:04:42 PM : [iNST-TX-I2CS] 02 62 42 D5 51 1F 2F 00 00 02 0F FF 08 A2 00 3B 96 AE FF 1F 01 79 Tue 01/17/2017 07:04:42 PM : [iNST-ACK ] 02 62 42.D5.51 1F 2F 00 00 02 08 A2 00 3B 96 AE FF 1F 01 79 79 D0 06 (00) Tue 01/17/2017 07:04:43 PM : [iNST-SRX ] 02 50 42.D5.51 3B.96.AE AF 2F FD (FD) Tue 01/17/2017 07:04:43 PM : [std-Direct Nack] 42.D5.51-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Tue 01/17/2017 07:04:43 PM : [D2D EVENT ] Event [42 D5 51 1] [ERR] [1] uom=0 prec=-1 Tue 01/17/2017 07:04:43 PM : [ 42 D5 51 1] ERR 1 Tue 01/17/2017 07:04:47 PM : [42 D5 51 1 ] Link 0 : 0FF8 [A2003B96AEFF1F01] *Failed Writing [A2003B96AEFF1F01] Tue 01/17/2017 07:04:47 PM : [D2D EVENT ] Event [42 D5 51 1] [ERR] [0] uom=0 prec=-1 Tue 01/17/2017 07:04:47 PM : [ 42 D5 51 1] ERR 0 traces vetter@att.net Today at 7:09 PM To Scott Message bodyTue 01/17/2017 06:59:46 PM : [42 D5 51 1 ] Link 0 : 0FF8 [A2003B96AEFF1F01] Writing [A2003B96AEFF1F01]Tue 01/17/2017 06:59:46 PM : [iNST-TX-I2CS] 02 62 42 D5 51 1F 2F 00 00 02 0F FF 08 A2 00 3B 96 AE FF 1F 01 79Tue 01/17/2017 06:59:46 PM : [iNST-ACK ] 02 62 42.D5.51 1F 2F 00 02 0F FF 08 A2 00 3B 96 AE FF 1F 01 79 D0 06 (00)Tue 01/17/2017 06:59:47 PM : [iNST-SRX ] 02 50 42.D5.51 3B.96.AE 2F 2F 00 (00)Tue 01/17/2017 06:59:47 PM : [std-Direct Ack] 42.D5.51-->ISY/PLM Group=0, Max Hops=3, Hops Left=3Tue 01/17/2017 06:59:56 PM : [iNST-TX-I2CS] 02 62 42 D5 51 1F 2F 00 00 02 0F FF 08 A2 00 3B 96 AE FF 1F 01 79Tue 01/17/2017 06:59:56 PM : [iNST-ACK ] 02 62 51.1F.2F 00 00 02 0F (02)Tue 01/17/2017 07:00:05 PM : [iNST-TX-I2CS] 02 62 42 D5 51 1F 2F 00 00 02 0F FF 08 A2 00 3B 96 AE FF 1F 01 79Tue 01/17/2017 07:00:05 PM : [iNST-ACK ] 02 62 42.D5.51 00 00 02 0F (02)Tue 01/17/2017 07:00:09 PM : [42 D5 51 1 ] Link 0 : 0FF8 [A2003B96AEFF1F01] *Failed Writing [A2003B96AEFF1F01]Tue 01/17/2017 07:00:13 PM : [D2D EVENT ] Event [42 D5 51 1] [ERR] [1] uom=0 prec=-1Tue 01/17/2017 07:00:13 PM : [ 42 D5 51 1] ERR 1Trace 2Tue 01/17/2017 07:01:53 PM : [42 D5 51 1 ] Link 0 : 0FF8 [A2003B96AEFF1F01] Writing [A2003B96AEFF1F01]Tue 01/17/2017 07:01:53 PM : [iNST-TX-I2CS] 02 62 42 D5 51 1F 2F 00 00 02 0F FF 08 A2 00 3B 96 AE FF 1F 01 79Tue 01/17/2017 07:01:53 PM : [iNST-ACK ] 02 62 42.D5.51 1F 00 00 02 0F FF 08 A2 00 3B 96 AE FF 1F 01 79 D0 06 (00)Tue 01/17/2017 07:01:54 PM : [iNST-SRX ] 02 50 42.D5.51 3B.96.AE 2F 00 00 (00)Tue 01/17/2017 07:01:54 PM : [std-Direct Ack] 42.D5.51-->ISY/PLM Group=0, Max Hops=3, Hops Left=3Tue 01/17/2017 07:02:03 PM : [iNST-TX-I2CS] 02 62 42 D5 51 1F 2F 00 00 02 0F FF 08 A2 00 3B 96 AE FF 1F 01 79Tue 01/17/2017 07:02:03 PM : [iNST-ACK ] 02 62 42.D5.51 1F 00 00 02 0F FF 08 A2 00 3B 96 AE FF 1F 01 79 D0 06 (00)Tue 01/17/2017 07:02:03 PM : [iNST-SRX ] 02 50 42.D5.51 3B.96.AE 2F 00 00 (00)Tue 01/17/2017 07:02:03 PM : [std-Direct Ack] 42.D5.51-->ISY/PLM Group=0, Max Hops=3, Hops Left=3Tue 01/17/2017 07:02:12 PM : [iNST-TX-I2CS] 02 62 42 D5 51 1F 2F 00 00 02 0F FF 08 A2 00 3B 96 AE FF 1F 01 79Tue 01/17/2017 07:02:12 PM : [iNST-ACK ] 02 62 42.51.1F 2F 00 00 02 (00)Tue 01/17/2017 07:02:16 PM : [42 D5 51 1 ] Link 0 : 0FF8 [A2003B96AEFF1F01] *Failed Writing [A2003B96AEFF1F01]Tue 01/17/2017 07:02:16 PM : [D2D EVENT ] Event [42 D5 51 1] [ERR] [0] uom=0 prec=-1Tue 01/17/2017 07:02:16 PM : [ 42 D5 51 1] ERR 0Trace 3Tue 01/17/2017 07:03:24 PM : [42 D5 51 1 ] Link 0 : 0FF8 [A2003B96AEFF1F01] Writing [A2003B96AEFF1F01]Tue 01/17/2017 07:03:24 PM : [iNST-TX-I2CS] 02 62 42 D5 51 1F 2F 00 00 02 0F FF 08 A2 00 3B 96 AE FF 1F 01 79Tue 01/17/2017 07:03:24 PM : [iNST-ACK ] 02 62 42.D5.51 00 00 02 0F (02)Tue 01/17/2017 07:03:33 PM : [iNST-TX-I2CS] 02 62 42 D5 51 1F 2F 00 00 02 0F FF 08 A2 00 3B 96 AE FF 1F 01 79Tue 01/17/2017 07:03:33 PM : [iNST-ACK ] 02 62 42.D5.51 1F 00 00 02 0F FF 08 A2 00 3B 96 AE FF 1F 01 79 D0 06 (00)Tue 01/17/2017 07:03:33 PM : [iNST-ACK ] 02 62 42.D5.51 1F 00 00 02 0F FF 08 A2 00 3B 96 AE FF 1F 01 79 D0 06 (00): Duplicate or ACK for a different deviceTue 01/17/2017 07:03:33 PM : [iNST-SRX ] 02 50 42.D5.51 3B.96.AE 2F 00 00 (00)Tue 01/17/2017 07:03:33 PM : [std-Direct Ack] 42.D5.51-->ISY/PLM Group=0, Max Hops=3, Hops Left=3Tue 01/17/2017 07:03:42 PM : [iNST-TX-I2CS] 02 62 42 D5 51 1F 2F 00 00 02 0F FF 08 A2 00 3B 96 AE FF 1F 01 79Tue 01/17/2017 07:03:42 PM : [iNST-ACK ] 02 62 42.D5.51 1F 2F 00 00 02 FF 08 A2 00 3B 96 AE FF 1F 01 79 D0 06 (00)Tue 01/17/2017 07:03:43 PM : [iNST-SRX ] 02 50 42.D5.51 3B.96.AE AF 2F FD (FD)Tue 01/17/2017 07:03:43 PM : [std-Direct Nack] 42.D5.51-->ISY/PLM Group=0, Max Hops=3, Hops Left=3Tue 01/17/2017 07:03:43 PM : [D2D EVENT ] Event [42 D5 51 1] [ERR] [1] uom=0 prec=-1Tue 01/17/2017 07:03:43 PM : [ 42 D5 51 1] ERR 1Tue 01/17/2017 07:03:47 PM : [42 D5 51 1 ] Link 0 : 0FF8 [A2003B96AEFF1F01] *Failed Writing [A2003B96AEFF1F01]Tue 01/17/2017 07:03:47 PM : [D2D EVENT ] Event [42 D5 51 1] [ERR] [0] uom=0 prec=-1Tue 01/17/2017 07:03:47 PM : [ 42 D5 51 1] ERR 0Tracw 4Tue 01/17/2017 07:04:23 PM : [42 D5 51 1 ] Link 0 : 0FF8 [A2003B96AEFF1F01] Writing [A2003B96AEFF1F01]Tue 01/17/2017 07:04:23 PM : [iNST-TX-I2CS] 02 62 42 D5 51 1F 2F 00 00 02 0F FF 08 A2 00 3B 96 AE FF 1F 01 79Tue 01/17/2017 07:04:33 PM : [iNST-TX-I2CS] 02 62 42 D5 51 1F 2F 00 00 02 0F FF 08 A2 00 3B 96 AE FF 1F 01 79Tue 01/17/2017 07:04:33 PM : [iNST-ACK ] 02 62 42.D5.51 1F 2F 02 0F FF 08 A2 00 3B 96 AE FF 1F 01 79 79 D0 06 (02)Tue 01/17/2017 07:04:33 PM : [iNST-SRX ] 02 50 42.D5.51 3B.96.AE 2F 2F 02 (02)Tue 01/17/2017 07:04:33 PM : [std-Direct Ack] 42.D5.51-->ISY/PLM Group=0, Max Hops=3, Hops Left=3Tue 01/17/2017 07:04:42 PM : [iNST-TX-I2CS] 02 62 42 D5 51 1F 2F 00 00 02 0F FF 08 A2 00 3B 96 AE FF 1F 01 79Tue 01/17/2017 07:04:42 PM : [iNST-ACK ] 02 62 42.D5.51 1F 2F 00 00 02 08 A2 00 3B 96 AE FF 1F 01 79 79 D0 06 (00)Tue 01/17/2017 07:04:43 PM : [iNST-SRX ] 02 50 42.D5.51 3B.96.AE AF 2F FD (FD)Tue 01/17/2017 07:04:43 PM : [std-Direct Nack] 42.D5.51-->ISY/PLM Group=0, Max Hops=3, Hops Left=3Tue 01/17/2017 07:04:43 PM : [D2D EVENT ] Event [42 D5 51 1] [ERR] [1] uom=0 prec=-1Tue 01/17/2017 07:04:43 PM : [ 42 D5 51 1] ERR 1Tue 01/17/2017 07:04:47 PM : [42 D5 51 1 ] Link 0 : 0FF8 [A2003B96AEFF1F01] *Failed Writing [A2003B96AEFF1F01]Tue 01/17/2017 07:04:47 PM : [D2D EVENT ] Event [42 D5 51 1] [ERR] [0] uom=0 prec=-1Tue 01/17/2017 07:04:47 PM : [ 42 D5 51 1] ERR 0 Link to comment Share on other sites More sharing options...
svetter Posted January 18, 2017 Author Share Posted January 18, 2017 Old V2.5 device failed to add. Reason 3.. The device that was "added" in my previous post failed to remove. Will power cycle PLM. Link to comment Share on other sites More sharing options...
Teken Posted January 18, 2017 Share Posted January 18, 2017 Hello Scott, Can you run a PLM link compare and let the group know what that number is. Please ensure no one is moving around run the test 4-5 times. How many Insteon devices do you have in place? ========================= The highest calling in life is to serve ones country faithfully - Teach others what can be. Do what is right and not what is popular. Link to comment Share on other sites More sharing options...
svetter Posted January 18, 2017 Author Share Posted January 18, 2017 For giggles I factory reset the PLM, and when the light turned green, connected the ISY. The PLM shows connected. I then performed a "Restore Modem (PLM)" and it failed. I had fresh batteries in my door sensors and put them in linking mode. The PLM restore failed. Tried a couple of times and it ends when it cannot update a master link to a device. I'll run the link compare. I didn't see your last post until now. Maybe I went too far. Link to comment Share on other sites More sharing options...
svetter Posted January 18, 2017 Author Share Posted January 18, 2017 I have about 43 unique devices counting the 4 6or8-button keypads as one device. Link to comment Share on other sites More sharing options...
svetter Posted January 18, 2017 Author Share Posted January 18, 2017 Moving around the run as in controlling devices? Nope, hands off time. Do you mean do a link compare for one of the newly added devices? Link to comment Share on other sites More sharing options...
Teken Posted January 18, 2017 Share Posted January 18, 2017 It's too late you wiped the PLM. What is the production date of the PLM and how old is it. ========================= The highest calling in life is to serve ones country faithfully - Teach others what can be. Do what is right and not what is popular. Link to comment Share on other sites More sharing options...
svetter Posted January 18, 2017 Author Share Posted January 18, 2017 It is a V2.1 firmware date code is 1530 and Amazon says August 29, 2015 is when it was ordered. It is my second with the ISY. The last one completely went dead. This one went Red during reset then solid green. There isn't a lot (or really any) flashing lights on the ISY except on steady blue power and a quick transmit and receive when I turn a light on and off from the console. Link to comment Share on other sites More sharing options...
Teken Posted January 18, 2017 Share Posted January 18, 2017 Sounds to be another bad PLM. Submit a warranty RMA and ask for a cross dock. ========================= The highest calling in life is to serve ones country faithfully - Teach others what can be. Do what is right and not what is popular. Link to comment Share on other sites More sharing options...
svetter Posted January 18, 2017 Author Share Posted January 18, 2017 Thanks for your help. I really appreciate it. I'll swap out the PLM and then go from there. Will report back. Link to comment Share on other sites More sharing options...
stusviews Posted January 18, 2017 Share Posted January 18, 2017 It's too late you wiped the PLM. What is the production date of the PLM and how old is it. Resetting the PLM affects only the PLM, The ISY reords are intact. Sounds to be another bad PLM. Submit a warranty RMA and ask for a cross dock.. Amazon provides only a 30 day warranty. The RMA will have to be done through SH. Link to comment Share on other sites More sharing options...
Teken Posted January 18, 2017 Share Posted January 18, 2017 Correct, the OP needs to submit the RMA to SH since it's still under the two year warranty period. ========================= The highest calling in life is to serve ones country faithfully - Teach others what can be. Do what is right and not what is popular. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.