rlebel

Following up on my 2843/Triggerlinc problems: Michel kindly tested my 2843 on his system and reported that it worked fine. Have tested everything else he concluded that he only possible weak link was my older PLM so I replaced that with a new 2413 and the 2843 now links just fine! Chalk up another mystery to the wonders of SH technology. Thanks to everyone for your help with this!

Thanks for the info about the Restore Modem command Lee. I was confused by the fact that the ISY told me I needed to put all remote devices into linking mode. In fact it appears that the Restore Modem operation does not write to anything but the PLM, so that mis-direction about the remote devices is a bug. So I did go ahead and restore the PLM. And it appears to have not helped my problem with the 2843. The tech support guy from SH was as helpful as could be, he tried linking his own 2843 and it worked properly; he even upgraded his ISY to 4.0.3 and again it worked correctly. I now have a cross-ship replacement backorder with SH but given that two 2843 have shown the same behavior I'm not so sure. I live in Santa Monica and I know UDI is somewhere in the Valley, perhaps I can bring the 2843 by for you to try?

I have the older 2412S. The link counts I have gotten are 914, 1862 (!!!), 867 and 867. So I'm guessing 867 is correct. When doing a Restore Modem does the ISY reprogram every device in the system in addition to the PLM? Why do the radio control devices need to be active? What happens if one or more devices are not accessible during the restore?

Bob, thanks for the suggestions. I did power cycle the PLM/ISY and it did not help. The Restore Modem operation seems like quite a commitment. With some 60 devices including half a dozen RF only battery powered devices it seems like getting it to run successfully would be quite a challenge. I currently have about 900 links in my PLM. And of course I would be concerned about any unrelated network activity screwing things up. Is this really a UDI recommended procedure?

Lee, is it possible I am experiencing a difference between the Triggerlinc and the 2843? I'm on the line with SH and they say there has only been one firmware since the release of the 2843. And they never make mistakes, right?

I added it to a scene as a controller, then did a factory reset (and changed nothing else) and it continued to properly control the scene.

Tried that, still same behavior - no NAK.

Take the battery out, wait, hold down the set button, install battery, wait for LED to turn on then off, release button.

Well I tried again, being very very careful to make sure nothing happened between the factory reset and the attempt to link and again I got the "02" in the first INST-SRX, no NAK. And again, no response to the type query. So I guess SH has shipped me two 2843s that don't respond properly? Seems like they might have introduced a firmware bug?

And trying again, this time without auto identify. Linked as a single device. This was after factory reset, placed device near PLM/AP: Wed 04/24/2013 10:52:25 : [iNST-SRX ] 02 50 21.64.13 00.00.01 C7 11 01 LTONRR (01) Wed 04/24/2013 10:52:25 : [std-Group ] 21.64.13-->Group=1, Max Hops=3, Hops Left=1 Wed 04/24/2013 10:52:25 : [iNST-DUP ] Previous message ignored. Wed 04/24/2013 10:52:26 : [iNST-SRX ] 02 50 21.64.13 00.00.01 C7 11 01 LTONRR (01) Wed 04/24/2013 10:52:26 : [std-Group ] 21.64.13-->Group=1, Max Hops=3, Hops Left=1 Wed 04/24/2013 10:52:26 : [iNST-DUP ] Previous message ignored. Wed 04/24/2013 10:52:27 : [iNST-SRX ] 02 50 21.64.13 11.00.01 C7 06 00 (00) Wed 04/24/2013 10:52:27 : [std-Group ] 21.64.13-->11.00.01, Max Hops=3, Hops Left=1 Wed 04/24/2013 10:52:27 : [iNST-DUP ] Previous message ignored. Wed 04/24/2013 10:52:53 : [21 64 13 ] Added to list of devices to link to ISY Wed 04/24/2013 10:52:53 : [iNST-TX-I1 ] 02 62 21 64 13 0F 0D 00 Wed 04/24/2013 10:52:53 : [iNST-ACK ] 02 62 21.64.13 0F 0D 00 06 (00) Wed 04/24/2013 10:52:54 : [iNST-SRX ] 02 50 21.64.13 12.9C.44 27 0D 02 (02) Wed 04/24/2013 10:52:54 : [std-Direct Ack] 21.64.13-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Wed 04/24/2013 10:52:54 : [iNST-TX-I1 ] 02 62 21 64 13 0F 10 00 Wed 04/24/2013 10:52:54 : [iNST-ACK ] 02 62 21.64.13 0F 10 00 06 ID-REQ (00) Wed 04/24/2013 10:52:54 : [iNST-SRX ] 02 50 21.64.13 12.9C.44 27 10 00 ID-REQ (00) Wed 04/24/2013 10:52:54 : [std-Direct Ack] 21.64.13-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Wed 04/24/2013 10:53:03 : [iNST-TX-I1 ] 02 62 21 64 13 0F 10 00 Wed 04/24/2013 10:53:03 : [iNST-ACK ] 02 62 21.64.13 0F 10 00 06 ID-REQ (00) Wed 04/24/2013 10:53:03 : [iNST-SRX ] 02 50 21.64.13 12.9C.44 27 10 00 ID-REQ (00) Wed 04/24/2013 10:53:03 : [std-Direct Ack] 21.64.13-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Wed 04/24/2013 10:53:12 : [iNST-TX-I1 ] 02 62 21 64 13 0F 10 00 Wed 04/24/2013 10:53:12 : [iNST-ACK ] 02 62 21.64.13 0F 10 00 06 ID-REQ (00) Wed 04/24/2013 10:53:13 : [iNST-SRX ] 02 50 21.64.13 12.9C.44 27 10 00 ID-REQ (00) Wed 04/24/2013 10:53:13 : [std-Direct Ack] 21.64.13-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Wed 04/24/2013 10:53:17 : [21 64 13 0 ] Calibrating engine version Wed 04/24/2013 10:53:17 : [iNST-TX-I2CS] 02 62 21 64 13 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Wed 04/24/2013 10:53:17 : [iNST-ACK ] 02 62 21.64.13 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Wed 04/24/2013 10:53:17 : [iNST-SRX ] 02 50 21.64.13 12.9C.44 27 2F 00 (00) Wed 04/24/2013 10:53:17 : [std-Direct Ack] 21.64.13-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Wed 04/24/2013 10:53:18 : [iNST-ERX ] 02 51 21 64 13 12 9C 44 11 2F 00 00 01 0F FF 01 00 00 00 00 00 00 00 00 C1 Wed 04/24/2013 10:53:18 : [Ext-Direct ] 21.64.13-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Wed 04/24/2013 10:53:18 : [21 64 13 0 ] Using Database Link Table offset 0x0FF8 (reported 0x0FF8) Wed 04/24/2013 10:53:18 : [21 64 13 1 ] Start : Adding device to ISY Wed 04/24/2013 10:53:18 : [21 64 13 1 ] Finish : Adding device to ISY was Successful Wed 04/24/2013 10:53:18 : [21 64 13 1 ] Link 0 : 0FF8 [E201129C44FF0001] Saving [E201129C44FF0001] Wed 04/24/2013 10:53:18 : [21 64 13 0 ] Successfully added device Wed 04/24/2013 10:53:18 : [All ] Writing 8 bytes to devices Wed 04/24/2013 10:53:18 : [21 64 13 1 ] Link 0 : 0FF8 [E201129C44FF0001] Writing [E201129C44FF0001] Wed 04/24/2013 10:53:18 : [iNST-TX-I2CS] 02 62 21 64 13 1F 2F 00 00 02 0F FF 08 E2 01 12 9C 44 FF 00 01 E4 Wed 04/24/2013 10:53:18 : [iNST-ACK ] 02 62 21.64.13 1F 2F 00 00 02 0F FF 08 E2 01 12 9C 44 FF 00 01 E4 06 (00) Wed 04/24/2013 10:53:19 : [iNST-SRX ] 02 50 21.64.13 12.9C.44 27 2F 00 (00) Wed 04/24/2013 10:53:19 : [std-Direct Ack] 21.64.13-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Wed 04/24/2013 10:53:19 : [MNG-LNK-RSP ] 02 6F 41 A2 01 21 64 13 10 09 00 15 Wed 04/24/2013 10:53:19 : [PLM ] Group 1 : Writing Responder Link matching [21 64 13 1 ] Link 0 : 0FF8 [E201129C44FF0001] Wed 04/24/2013 10:53:20 : [21 64 13 1 ] Link 1 : 0FF0 [0000000000000000] Writing [00..............] Wed 04/24/2013 10:53:20 : [iNST-TX-I2CS] 02 62 21 64 13 1F 2F 00 00 02 0F F7 08 00 00 00 00 00 00 00 00 C1 Wed 04/24/2013 10:53:20 : [iNST-ACK ] 02 62 21.64.13 1F 2F 00 00 02 0F F7 08 00 00 00 00 00 00 00 00 C1 06 (00) Wed 04/24/2013 10:53:20 : [iNST-SRX ] 02 50 21.64.13 12.9C.44 27 2F 00 (00) Wed 04/24/2013 10:53:20 : [std-Direct Ack] 21.64.13-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Wed 04/24/2013 10:53:20 : [21 64 13 1 ] Link 2 : 0FE8 : Writing High Water Byte Wed 04/24/2013 10:53:20 : [iNST-TX-I2CS] 02 62 21 64 13 1F 2F 00 00 00 0F EF 01 00 00 00 00 00 00 00 00 D2 Wed 04/24/2013 10:53:20 : [iNST-ACK ] 02 62 21.64.13 1F 2F 00 00 00 0F EF 01 00 00 00 00 00 00 00 00 D2 06 (00) Wed 04/24/2013 10:53:21 : [iNST-SRX ] 02 50 21.64.13 12.9C.44 27 2F 00 (00) Wed 04/24/2013 10:53:21 : [std-Direct Ack] 21.64.13-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Wed 04/24/2013 10:53:22 : [iNST-ERX ] 02 51 21 64 13 12 9C 44 12 2F 00 00 01 0F EF 01 00 00 00 00 00 00 00 00 D1 Wed 04/24/2013 10:53:22 : [Ext-Direct ] 21.64.13-->ISY/PLM Group=0, Max Hops=2, Hops Left=0 Wed 04/24/2013 10:53:22 : [iNST-TX-I2CS] 02 62 21 64 13 1F 2F 00 00 00 0F EF 01 00 00 00 00 00 00 00 00 D2 Wed 04/24/2013 10:53:22 : [iNST-ACK ] 02 62 21.64.13 1F 2F 00 00 00 0F EF 01 00 00 00 00 00 00 00 00 D2 06 (00) Wed 04/24/2013 10:53:23 : [iNST-SRX ] 02 50 21.64.13 12.9C.44 27 2F 00 (00) Wed 04/24/2013 10:53:23 : [std-Direct Ack] 21.64.13-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Wed 04/24/2013 10:53:23 : [iNST-ERX ] 02 51 21 64 13 12 9C 44 11 2F 00 00 01 0F EF 01 00 00 00 00 00 00 00 00 D1 Wed 04/24/2013 10:53:23 : [Ext-Direct ] 21.64.13-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Wed 04/24/2013 10:53:23 : [iNST-TX-I2CS] 02 62 21 64 13 1F 2F 00 00 02 0F EF 08 00 00 00 00 00 00 00 00 C9 Wed 04/24/2013 10:53:23 : [iNST-ACK ] 02 62 21.64.13 1F 2F 00 00 02 0F EF 08 00 00 00 00 00 00 00 00 C9 06 (00) Wed 04/24/2013 10:53:24 : [iNST-SRX ] 02 50 21.64.13 12.9C.44 27 2F 00 (00) Wed 04/24/2013 10:53:24 : [std-Direct Ack] 21.64.13-->ISY/PLM Group=0, Max Hops=3, Hops Left=1

Ooops, perhaps it would help if I typed the device address correctly! But it still fails, near the PLM/AP piggyback with auto identify: Wed 04/24/2013 10:41:58 : [21 64 13 ] Added to list of devices to link to ISY Wed 04/24/2013 10:41:58 : [iNST-TX-I1 ] 02 62 21 64 13 0F 0D 00 Wed 04/24/2013 10:41:58 : [iNST-ACK ] 02 62 21.64.13 0F 0D 00 06 (00) Wed 04/24/2013 10:42:02 : [iNST-SRX ] 02 50 21.64.13 00.00.01 C7 11 01 LTONRR (01) Wed 04/24/2013 10:42:02 : [std-Group ] 21.64.13-->Group=1, Max Hops=3, Hops Left=1 Wed 04/24/2013 10:42:02 : [iNST-DUP ] Previous message ignored. Wed 04/24/2013 10:42:03 : [iNST-SRX ] 02 50 21.64.13 00.00.01 C7 11 01 LTONRR (01) Wed 04/24/2013 10:42:03 : [std-Group ] 21.64.13-->Group=1, Max Hops=3, Hops Left=1 Wed 04/24/2013 10:42:03 : [iNST-DUP ] Previous message ignored. Wed 04/24/2013 10:42:04 : [iNST-SRX ] 02 50 21.64.13 11.00.01 C7 06 00 (00) Wed 04/24/2013 10:42:04 : [std-Group ] 21.64.13-->11.00.01, Max Hops=3, Hops Left=1 Wed 04/24/2013 10:42:04 : [iNST-DUP ] Previous message ignored. Wed 04/24/2013 10:42:13 : [iNST-TX-I1 ] 02 62 21 64 13 0F 0D 00 Wed 04/24/2013 10:42:13 : [iNST-ACK ] 02 62 21.64.13 0F 0D 00 06 (00) Wed 04/24/2013 10:42:13 : [iNST-SRX ] 02 50 21.64.13 12.9C.44 27 0D 02 (02) Wed 04/24/2013 10:42:13 : [std-Direct Ack] 21.64.13-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Wed 04/24/2013 10:42:13 : [iNST-TX-I1 ] 02 62 21 64 13 0F 10 00 Wed 04/24/2013 10:42:14 : [iNST-ACK ] 02 62 21.64.13 0F 10 00 06 ID-REQ (00) Wed 04/24/2013 10:42:14 : [iNST-SRX ] 02 50 21.64.13 12.9C.44 27 10 00 ID-REQ (00) Wed 04/24/2013 10:42:14 : [std-Direct Ack] 21.64.13-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Wed 04/24/2013 10:42:17 : [iNST-SRX ] 02 50 14.23.A0 12.9C.44 07 6F 2B (2B) Wed 04/24/2013 10:42:17 : [std-Direct ] 14.23.A0-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Wed 04/24/2013 10:42:17 : [ 14 23 A0 1] CLIHUM 43 Wed 04/24/2013 10:42:26 : [iNST-TX-I1 ] 02 62 21 64 13 0F 10 00 Wed 04/24/2013 10:42:26 : [iNST-ACK ] 02 62 21.64.13 0F 10 00 06 ID-REQ (00) Wed 04/24/2013 10:42:26 : [iNST-SRX ] 02 50 21.64.13 12.9C.44 27 10 00 ID-REQ (00) Wed 04/24/2013 10:42:26 : [std-Direct Ack] 21.64.13-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Wed 04/24/2013 10:42:35 : [iNST-TX-I1 ] 02 62 21 64 13 0F 10 00 Wed 04/24/2013 10:42:35 : [iNST-ACK ] 02 62 21.64.13 0F 10 00 06 ID-REQ (00) Wed 04/24/2013 10:42:35 : [iNST-SRX ] 02 50 21.64.13 12.9C.44 27 10 00 ID-REQ (00) Wed 04/24/2013 10:42:35 : [std-Direct Ack] 21.64.13-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Wed 04/24/2013 10:42:39 : [21 64 13 0 ] Cannot determine device type Wed 04/24/2013 10:42:39 : [21 64 13 0 ] Failed to add device, reason 2 Wed 04/24/2013 10:42:39 : [All ] Writing 0 bytes to devices

Well, I switched devices (1) because I have mounted the first one on a door and (2) to see if the problem was specific to the first device. I'll stick to 21.64.13 for testing now, but don't have any idea what to try next.

Thanks again. The sensor was about 4 feet away from a dual band dimmer when I tried the link. I have deleted and retried many times. This time I tried to link it with it positioned a few feet from my PLM, which has an AP piggybacked to it, using auto identify mode. I will also note that I have successfully linked motion detectors and RL2s with identical setups. Wed 04/24/2013 09:58:02 : [iNST-SRX ] 02 50 21.64.13 00.00.01 C7 13 01 LTOFFRR(01) Wed 04/24/2013 09:58:02 : [std-Group ] 21.64.13-->Group=1, Max Hops=3, Hops Left=1 Wed 04/24/2013 09:58:02 : [iNST-DUP ] Previous message ignored. Wed 04/24/2013 09:58:03 : [iNST-SRX ] 02 50 21.64.13 00.00.01 C7 13 01 LTOFFRR(01) Wed 04/24/2013 09:58:03 : [std-Group ] 21.64.13-->Group=1, Max Hops=3, Hops Left=1 Wed 04/24/2013 09:58:03 : [iNST-DUP ] Previous message ignored. Wed 04/24/2013 09:58:04 : [iNST-SRX ] 02 50 21.64.13 13.00.01 C7 06 00 (00) Wed 04/24/2013 09:58:04 : [std-Group ] 21.64.13-->13.00.01, Max Hops=3, Hops Left=1 Wed 04/24/2013 09:58:04 : [iNST-DUP ] Previous message ignored. Wed 04/24/2013 09:58:05 : [iNST-SRX ] 02 50 14.BB.A4 00.00.02 C7 11 02 LTONRR (02) Wed 04/24/2013 09:58:05 : [std-Group ] 14.BB.A4-->Group=2, Max Hops=3, Hops Left=1 Wed 04/24/2013 09:58:05 : [ 14 BB A4 2] DON 2 Wed 04/24/2013 09:58:05 : [ 14 BB A4 2] ST 255 Wed 04/24/2013 09:58:05 : [iNST-SRX ] 02 50 14.BB.A4 00.00.02 C7 11 02 LTONRR (02) Wed 04/24/2013 09:58:05 : [std-Group ] 14.BB.A4-->Group=2, Max Hops=3, Hops Left=1 Wed 04/24/2013 09:58:05 : [iNST-DUP ] Previous message ignored. Wed 04/24/2013 09:58:05 : [iNST-SRX ] 02 50 14.BB.A4 11.00.02 C7 06 00 (00) Wed 04/24/2013 09:58:05 : [std-Group ] 14.BB.A4-->11.00.02, Max Hops=3, Hops Left=1 Wed 04/24/2013 09:58:06 : [iNST-SRX ] 02 50 14.BB.A4 11.00.02 C7 06 00 (00) Wed 04/24/2013 09:58:06 : [std-Group ] 14.BB.A4-->11.00.02, Max Hops=3, Hops Left=1 Wed 04/24/2013 09:58:06 : [iNST-DUP ] Previous message ignored. Wed 04/24/2013 09:58:23 : [21 64 19 ] Added to list of devices to link to ISY Wed 04/24/2013 09:58:23 : [iNST-TX-I1 ] 02 62 21 64 19 0F 0D 00 Wed 04/24/2013 09:58:23 : [iNST-ACK ] 02 62 21.64.19 0F 0D 00 06 (00) Wed 04/24/2013 09:58:32 : [iNST-TX-I1 ] 02 62 21 64 19 0F 0D 00 Wed 04/24/2013 09:58:32 : [iNST-ACK ] 02 62 21.64.19 0F 0D 00 06 (00) Wed 04/24/2013 09:58:41 : [iNST-TX-I1 ] 02 62 21 64 19 0F 0D 00 Wed 04/24/2013 09:58:41 : [iNST-ACK ] 02 62 21.64.19 0F 0D 00 06 (00) Wed 04/24/2013 09:58:45 : [21 64 19 0 ] Failed to add device, reason 3 Wed 04/24/2013 09:58:45 : [All ] Writing 0 bytes to devices

Thanks for the suggestion Lee. I first saw the problem with 4.0.2, then I upgraded to 4.0.3. Both times I checked that the UI and firmware were 4.0.2 then 4.0.3. FWIW the device type lists as 2843-222 Open/Close Sensor v.00. I just tried linking another one to my ISY and I again noticed that auto detect did not work. I wonder if SM in their wisdom changed the device code? Here is the log from when I specified the device type and it did link, but with only one device: Wed 04/24/2013 08:42:57 : [iNST-SRX ] 02 50 21.64.13 13.00.01 C7 06 00 (00) Wed 04/24/2013 08:42:57 : [std-Group ] 21.64.13-->13.00.01, Max Hops=3, Hops Left=1 Wed 04/24/2013 08:42:57 : [iNST-DUP ] Previous message ignored. Wed 04/24/2013 08:43:03 : [21 64 13 ] Added to list of devices to link to ISY Wed 04/24/2013 08:43:03 : [iNST-TX-I1 ] 02 62 21 64 13 0F 0D 00 Wed 04/24/2013 08:43:03 : [iNST-ACK ] 02 62 21.64.13 0F 0D 00 06 (00) Wed 04/24/2013 08:43:04 : [iNST-SRX ] 02 50 21.64.13 12.9C.44 27 0D 02 (02) Wed 04/24/2013 08:43:04 : [std-Direct Ack] 21.64.13-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Wed 04/24/2013 08:43:04 : [iNST-TX-I1 ] 02 62 21 64 13 0F 10 00 Wed 04/24/2013 08:43:04 : [iNST-ACK ] 02 62 21.64.13 0F 10 00 06 ID-REQ (00) Wed 04/24/2013 08:43:04 : [iNST-SRX ] 02 50 21.64.13 12.9C.44 27 10 00 ID-REQ (00) Wed 04/24/2013 08:43:04 : [std-Direct Ack] 21.64.13-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Wed 04/24/2013 08:43:13 : [iNST-TX-I1 ] 02 62 21 64 13 0F 10 00 Wed 04/24/2013 08:43:13 : [iNST-ACK ] 02 62 21.64.13 0F 10 00 06 ID-REQ (00) Wed 04/24/2013 08:43:13 : [iNST-SRX ] 02 50 21.64.13 12.9C.44 27 10 00 ID-REQ (00) Wed 04/24/2013 08:43:13 : [std-Direct Ack] 21.64.13-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Wed 04/24/2013 08:43:22 : [iNST-TX-I1 ] 02 62 21 64 13 0F 10 00 Wed 04/24/2013 08:43:22 : [iNST-ACK ] 02 62 21.64.13 0F 10 00 06 ID-REQ (00) Wed 04/24/2013 08:43:23 : [iNST-SRX ] 02 50 21.64.13 12.9C.44 27 10 00 ID-REQ (00) Wed 04/24/2013 08:43:23 : [std-Direct Ack] 21.64.13-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Wed 04/24/2013 08:43:27 : [21 64 13 0 ] Calibrating engine version Wed 04/24/2013 08:43:27 : [iNST-TX-I2CS] 02 62 21 64 13 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Wed 04/24/2013 08:43:27 : [iNST-ACK ] 02 62 21.64.13 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Wed 04/24/2013 08:43:27 : [iNST-SRX ] 02 50 21.64.13 12.9C.44 27 2F 00 (00) Wed 04/24/2013 08:43:27 : [std-Direct Ack] 21.64.13-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Wed 04/24/2013 08:43:28 : [iNST-ERX ] 02 51 21 64 13 12 9C 44 11 2F 00 00 01 0F FF 01 E2 01 12 9C 44 FF 00 01 EC Wed 04/24/2013 08:43:28 : [Ext-Direct ] 21.64.13-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Wed 04/24/2013 08:43:28 : [21 64 13 0 ] Using Database Link Table offset 0x0FF8 (reported 0x0FF8) Wed 04/24/2013 08:43:28 : [21 64 13 1 ] Start : Adding device to ISY Wed 04/24/2013 08:43:28 : [21 64 13 1 ] Finish : Adding device to ISY was Successful Wed 04/24/2013 08:43:28 : [21 64 13 1 ] Link 0 : 0FF8 [E201129C44FF0001] Saving [E201129C44FF0001] Wed 04/24/2013 08:43:28 : [21 64 13 0 ] Successfully added device Wed 04/24/2013 08:43:28 : [All ] Writing 8 bytes to devices Wed 04/24/2013 08:43:28 : [21 64 13 1 ] Link 0 : 0FF8 [E201129C44FF0001] Writing [E201129C44FF0001] Wed 04/24/2013 08:43:28 : [iNST-TX-I2CS] 02 62 21 64 13 1F 2F 00 00 02 0F FF 08 E2 01 12 9C 44 FF 00 01 E4 Wed 04/24/2013 08:43:28 : [iNST-ACK ] 02 62 21.64.13 1F 2F 00 00 02 0F FF 08 E2 01 12 9C 44 FF 00 01 E4 06 (00) Wed 04/24/2013 08:43:29 : [iNST-SRX ] 02 50 21.64.13 12.9C.44 27 2F 00 (00) Wed 04/24/2013 08:43:29 : [std-Direct Ack] 21.64.13-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Wed 04/24/2013 08:43:29 : [MNG-LNK-RSP ] 02 6F 41 A2 01 21 64 13 10 09 00 15 Wed 04/24/2013 08:43:29 : [PLM ] Group 1 : Writing Responder Link matching [21 64 13 1 ] Link 0 : 0FF8 [E201129C44FF0001] Wed 04/24/2013 08:43:30 : [21 64 13 1 ] Link 1 : 0FF0 [0000000000000000] Writing [00..............] Wed 04/24/2013 08:43:30 : [iNST-TX-I2CS] 02 62 21 64 13 1F 2F 00 00 02 0F F7 08 00 00 00 00 00 00 00 00 C1 Wed 04/24/2013 08:43:30 : [iNST-ACK ] 02 62 21.64.13 1F 2F 00 00 02 0F F7 08 00 00 00 00 00 00 00 00 C1 06 (00) Wed 04/24/2013 08:43:30 : [iNST-SRX ] 02 50 21.64.13 12.9C.44 27 2F 00 (00) Wed 04/24/2013 08:43:30 : [std-Direct Ack] 21.64.13-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Wed 04/24/2013 08:43:30 : [21 64 13 1 ] Link 2 : 0FE8 : Writing High Water Byte Wed 04/24/2013 08:43:30 : [iNST-TX-I2CS] 02 62 21 64 13 1F 2F 00 00 00 0F EF 01 00 00 00 00 00 00 00 00 D2 Wed 04/24/2013 08:43:30 : [iNST-ACK ] 02 62 21.64.13 1F 2F 00 00 00 0F EF 01 00 00 00 00 00 00 00 00 D2 06 (00) Wed 04/24/2013 08:43:31 : [iNST-SRX ] 02 50 21.64.13 12.9C.44 27 2F 00 (00) Wed 04/24/2013 08:43:31 : [std-Direct Ack] 21.64.13-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Wed 04/24/2013 08:43:32 : [iNST-ERX ] 02 51 21 64 13 12 9C 44 12 2F 00 00 01 0F EF 01 00 00 00 00 00 00 00 00 D1 Wed 04/24/2013 08:43:32 : [Ext-Direct ] 21.64.13-->ISY/PLM Group=0, Max Hops=2, Hops Left=0 Wed 04/24/2013 08:43:32 : [iNST-TX-I2CS] 02 62 21 64 13 1F 2F 00 00 00 0F EF 01 00 00 00 00 00 00 00 00 D2 Wed 04/24/2013 08:43:32 : [iNST-ACK ] 02 62 21.64.13 1F 2F 00 00 00 0F EF 01 00 00 00 00 00 00 00 00 D2 06 (00) Wed 04/24/2013 08:43:33 : [iNST-SRX ] 02 50 21.64.13 12.9C.44 27 2F 00 (00) Wed 04/24/2013 08:43:33 : [std-Direct Ack] 21.64.13-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Wed 04/24/2013 08:43:33 : [iNST-ERX ] 02 51 21 64 13 12 9C 44 11 2F 00 00 01 0F EF 01 00 00 00 00 00 00 00 00 D1 Wed 04/24/2013 08:43:33 : [Ext-Direct ] 21.64.13-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Wed 04/24/2013 08:43:33 : [iNST-TX-I2CS] 02 62 21 64 13 1F 2F 00 00 02 0F EF 08 00 00 00 00 00 00 00 00 C9 Wed 04/24/2013 08:43:33 : [iNST-ACK ] 02 62 21.64.13 1F 2F 00 00 02 0F EF 08 00 00 00 00 00 00 00 00 C9 06 (00) Wed 04/24/2013 08:43:34 : [iNST-SRX ] 02 50 21.64.13 12.9C.44 27 2F 00 (00) Wed 04/24/2013 08:43:34 : [std-Direct Ack] 21.64.13-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Wed 04/24/2013 08:44:01 : [iNST-SRX ] 02 50 14.23.A0 12.9C.44 07 6F 2A (2A) Wed 04/24/2013 08:44:01 : [std-Direct ] 14.23.A0-->ISY/PLM Group=0, Max Hops=3, Hops Left=1

Okay, I have 4.0.3 and just got my first 2843-2 Open/Close sensor. When I link it I only get the "Opened" device, no "closed" device. I have the 2843-2 in multi scene mode and the "open" device, as expected, never turns off - but I do see a DON message whenever I move the magnet away. I am linking with "New Insteon Device" and selecting device type 2843. Tried several times, deleting the device each time. What am I doing wrong?

The continuous support by UDI makes their products a tremendous value - I just ordered my $99 994i upgrade - $99!!! Compare for example Apple forcing us to upgrade hardware at full price every few years to get their free/cheap OS upgrades! Thanks!

Thanks for the suggestion, but actually I guess I can also skip the variable and just use button status as a proxy for the scene. I just tried that and it seems to work just fine.

I have a number of scenes that are controlled by multiple (about eight) KPLs. Sometimes I need a program to be activated along with the scene and the technique I have used so far is that I have a big "OR" for all of the control events. Is there an easier way?

Okay, previous posts have suggested that the light data from Weatherbug data can to strange, but right now I am getting a report from station SNTMN that the light is 0.3% and of course there is no way to compare to a number less than 1. By the way, it is pretty bright outside now. I'm on the coast in Santa Monica so I need to use this nearby station so that I get a good reading when we are fogged in, stations further inland will be sunny. I guess I may have to depend on the 2420M light sensor.

It would be nice if somewhere we could see the current engine version of all devices, maybe in topology?

Hi, I'm afraid I have not been keeping up with the betas recently, but since I'm getting some new devices online I thought I'd get the i2cs capability going. However, I am wondering exactly what this note "You might have to remove devices and then add them back to ISY" means. Is that only to active i2cs devices? And is it safe to assume that devices I purchased before March 2012 don't have i2cs?

The file is 4.5MB on my Mac.

Since I am not home I decided to try a remote update to 3.1.10. It sits at 1% for a while then I get "Upgrade failed: failed uploading file (reported written size is invalid).

Do you support the 2444 wireless remotes?

Been there, tried that. Nope.