brookbphx

I just got a brand new 2477SA1, version 0.41, and it has very similar symptoms to skunkiechris's unit in terms of never being able to successfully link. It will start to link, and things will look OK in the Event log, but then it will start NACKing. I factory reset it twice and tried linking again. No such luck. If I try to query it, it will query its status correctly. But if I try to control it or link it, I get NACK errors, and it will not be remotely controlled. Here's a capture of the last link sequence I tried: [size=85]Fri 09/14/2012 08:58:38 PM : [LNK-BGN ] 02 64 01 00 06 Fri 09/14/2012 08:59:15 PM : [LNK-STAT ] 02 53 M(01) gid=00 1A.C7.0D 090A 41 Fri 09/14/2012 08:59:15 PM : Linked: Linked 1A.C7.0D.00 type=09.0A.41 Fri 09/14/2012 08:59:15 PM : [iNST-TX-I1 ] 02 62 1A C7 0D 0F 0D 00 Fri 09/14/2012 08:59:15 PM : [iNST-ACK ] 02 62 1A.C7.0D 0F 0D 00 06 (00) Fri 09/14/2012 08:59:15 PM : [iNST-SRX ] 02 50 1A.C7.0D 13.21.82 2B 0D 02 (02) Fri 09/14/2012 08:59:15 PM : [standard-Direct Ack][1A.C7.0D-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Fri 09/14/2012 08:59:15 PM : [1A C7 D 0 ] Calibrating engine version Fri 09/14/2012 08:59:16 PM : [1A C7 D 1 ] Start : Adding device to ISY Fri 09/14/2012 08:59:16 PM : [1A C7 D 1 ] Finish : Adding device to ISY was Successful Fri 09/14/2012 08:59:16 PM : [All ] Writing 0 bytes to devices Fri 09/14/2012 08:59:16 PM : [LNK-BGN ] 02 64 01 00 06 Fri 09/14/2012 08:59:52 PM : ---- Initializing the linked devices ---- Fri 09/14/2012 08:59:52 PM : [LNK-END ] 02 65 06 : : Unexpected, ignored (65) Fri 09/14/2012 08:59:52 PM : [1A C7 D 1 ] Link 0 : 0FF8 [E201132182FF1F01] Saving [E201132182FF1F01] Fri 09/14/2012 08:59:52 PM : [iNST-TX-I2CS] 02 62 1A C7 0D 1F 2E 00 01 00 00 00 00 00 00 00 00 00 00 00 00 D1 Fri 09/14/2012 08:59:52 PM : [iNST-ACK ] 02 62 1A.C7.0D 1F 2E 00 01 00 00 00 00 00 00 00 00 00 00 00 00 D1 06 (00) Fri 09/14/2012 08:59:52 PM : [iNST-SRX ] 02 50 1A.C7.0D 13.21.82 2B 2E 00 (00) Fri 09/14/2012 08:59:52 PM : [standard-Direct Ack][1A.C7.0D-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Fri 09/14/2012 08:59:53 PM : [iNST-ERX ] 02 51 1A C7 0D 13 21 82 11 2E 00 01 01 00 00 20 00 1C FE 20 00 00 04 00 00 Fri 09/14/2012 08:59:53 PM : [Extended-Direct][1A.C7.0D-->ISY/PLM Group=0] Max Hops=1, Hops Left=0 Fri 09/14/2012 08:59:53 PM : ---- All Linked Devices are now initialized ---- Fri 09/14/2012 08:59:53 PM : [iNST-TX-I1 ] 02 62 1A C7 0D 0F 19 00 Fri 09/14/2012 08:59:53 PM : [iNST-ACK ] 02 62 1A.C7.0D 0F 19 00 06 LTSREQ (LIGHT) Fri 09/14/2012 08:59:53 PM : [iNST-SRX ] 02 50 1A.C7.0D 13.21.82 27 01 00 (00) Fri 09/14/2012 08:59:54 PM : [standard-Direct Ack][1A.C7.0D-->ISY/PLM Group=0] Max Hops=3, Hops Left=1 Fri 09/14/2012 08:59:54 PM : ---- Initializing the linked devices ---- Fri 09/14/2012 08:59:54 PM : ---- All Linked Devices are now initialized ---- Fri 09/14/2012 08:59:54 PM : [ 1A C7 D 1] OL 255 Fri 09/14/2012 08:59:54 PM : [ 1A C7 D 1] RR 28 Fri 09/14/2012 08:59:54 PM : [ 1A C7 D 1] ST 0 Fri 09/14/2012 08:59:54 PM : [All ] Writing 8 bytes to devices Fri 09/14/2012 08:59:54 PM : [1A C7 D 1 ] Link 0 : 0FF8 [E201132182FF1F01] Writing [E201132182FF1F01] Fri 09/14/2012 08:59:54 PM : [iNST-TX-I2CS] 02 62 1A C7 0D 1F 2F 00 00 02 0F FF 08 E2 01 13 21 82 FF 1F 01 01 Fri 09/14/2012 08:59:54 PM : [iNST-ACK ] 02 62 1A.C7.0D 1F 2F 00 00 02 0F FF 08 E2 01 13 21 82 FF 1F 01 01 06 (00) Fri 09/14/2012 08:59:54 PM : [iNST-SRX ] 02 50 1A.C7.0D 13.21.82 2B 2F 00 (00) Fri 09/14/2012 08:59:54 PM : [standard-Direct Ack][1A.C7.0D-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Fri 09/14/2012 08:59:54 PM : [MNG-LNK-RSP ] 02 6F 41 A2 01 1A C7 0D 09 0A 41 15 Fri 09/14/2012 08:59:54 PM : [PLM ] Group 1 : Writing Responder Link matching [1A C7 D 1 ] Link 0 : 0FF8 [E201132182FF1F01] Fri 09/14/2012 08:59:54 PM : [1A C7 D 1 ] Link 1 : 0FF0 [0000000000000000] Writing [00..............] Fri 09/14/2012 08:59:54 PM : [iNST-TX-I2CS] 02 62 1A C7 0D 1F 2F 00 00 02 0F F7 08 00 00 00 00 00 00 00 00 C1 Fri 09/14/2012 08:59:55 PM : [iNST-ACK ] 02 62 1A.C7.0D 1F 2F 00 00 02 0F F7 08 00 00 00 00 00 00 00 00 C1 06 (00) Fri 09/14/2012 08:59:55 PM : [iNST-SRX ] 02 50 1A.C7.0D 13.21.82 A7 2F FF (FF) Fri 09/14/2012 08:59:55 PM : [standard-Direct Nack][1A.C7.0D-->ISY/PLM Group=0] Max Hops=3, Hops Left=1 Fri 09/14/2012 08:59:55 PM : [1A C7 D 1 ] Link 2 : 0FE8 : Writing High Water Byte Fri 09/14/2012 08:59:55 PM : [iNST-TX-I2CS] 02 62 1A C7 0D 1F 2F 00 00 00 0F EF 01 00 00 00 00 00 00 00 00 D2 Fri 09/14/2012 08:59:55 PM : [iNST-ACK ] 02 62 1A.C7.0D 1F 2F 00 00 00 0F EF 01 00 00 00 00 00 00 00 00 D2 06 (00) Fri 09/14/2012 08:59:56 PM : [iNST-SRX ] 02 50 1A.C7.0D 13.21.82 AB 2F FF (FF) Fri 09/14/2012 08:59:56 PM : [standard-Direct Nack][1A.C7.0D-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Fri 09/14/2012 09:00:05 PM : [iNST-TX-I2CS] 02 62 1A C7 0D 1F 2F 00 00 00 0F EF 01 00 00 00 00 00 00 00 00 D2 Fri 09/14/2012 09:00:05 PM : [iNST-ACK ] 02 62 1A.C7.0D 1F 2F 00 00 00 0F EF 01 00 00 00 00 00 00 00 00 D2 06 (00) Fri 09/14/2012 09:00:05 PM : [iNST-SRX ] 02 50 1A.C7.0D 13.21.82 AB 2F FF (FF) Fri 09/14/2012 09:00:05 PM : [standard-Direct Nack][1A.C7.0D-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Fri 09/14/2012 09:00:14 PM : [iNST-TX-I2CS] 02 62 1A C7 0D 1F 2F 00 00 00 0F EF 01 00 00 00 00 00 00 00 00 D2 Fri 09/14/2012 09:00:14 PM : [iNST-ACK ] 02 62 1A.C7.0D 1F 2F 00 00 00 0F EF 01 00 00 00 00 00 00 00 00 D2 06 (00) Fri 09/14/2012 09:00:15 PM : [iNST-SRX ] 02 50 1A.C7.0D 13.21.82 AB 2F FF (FF) Fri 09/14/2012 09:00:15 PM : [standard-Direct Nack][1A.C7.0D-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Fri 09/14/2012 09:00:19 PM : [ 1A C7 D 1] ERR 1 Fri 09/14/2012 09:00:19 PM : [All ] Writing 0 bytes to devices [/size] I'm wondering if maybe I got Chris' returned unit. Probably not, as the Insteon link numbers are different. Anyway, did anyone figure a way to get around this? Is there some double-secret sequence of button pushes and commands I could be missing? Or does this really mean the unit is bad? PS: My temporary workaround is to give it an X10 address. That works! And since I was replacing a bad X10 switch, it's a pretty good temporary solution.

While the above suggestions do resolve the problem on not being able to correctly communicate with the ISY from your computer, the security implications of removing all of the port numbers in Avast are pretty severe. Basically, those are the standard web page and email ports. If you remove those ports from the list on this page, Avast will not scan them. In other words, you are basically disabling Avast scanning for all of your web and email surfing. You may think Avast Web Shield is working, because Avast says it is "Enabled". However, it is enabled and checking NOTHING. Removing the ports defeats the whole purpose of the Web Shield. You want to disable Avast Web Shield checking for communications between your computer and the ISY - but NOT between your computer and the entire internet. Here's a way to get the ISY interface to work without breaking the security provided by Avast Web Shield. (At least this worked for me) In Avast, click on "Settings" in the upper right corner. A new window will pop up. Select the "Troubleshooting" item at the bottom of the list on the left. Now, click the down arrow next to "Redirect Settings". Under Settings->Troubleshooting->Redirect Settings: [*] Put the IP address of your ISY-99 in the Ignored Addresses field under the WEB heading. Leave Ignored addresses blank for MAIL. (Note: you need to set up the ISY and/or your DHCP server in your router to always assign the same address to the ISY so that this address will always be correct). [*] If you previously cleared the Port numbers for HTTP ports, put them back. The defaults are: 80,8080,8091,8081,8008,8888,3124,3127,3128. This will restore the Avast web shield scanning security for web browsing on the standard WWW ports. [*] If you previously cleared the Port numbers for Mail ports, put them back. The defaults are: SMTP:25,587; POP:110; IMAP:143; NNTP:119 . This will restore the Avast web shield scanning security for email if you use a web application (such as Outlook or Outlook Express) on the standard Mail ports. [*] Click "OK" Under Settings->Updates->Proxy Settings [*] If you previously changed the proxy settings per the above suggestions to "Direct Connection (No Proxy)", you may choose to set it back to the default of "Auto detect (use Internet Explorer settings)". However, most people do not use proxies. So if you leave it set to Direct, chances are everything will still be OK. [*] Click "OK" If you still can't see the status updates on the UD Admin Console after making these changes, shut down and restart the Admin Console. You may also want to stop and restart the Avast Web Shield.