brausse

AHHHHH, I forgot that I had set the Font size to the maximum in order to aid my failing eyesight. When I change the size back to the minimum and make the Java change, the admin console is just about a perfect size. Thanks for all the good, quick help.

Thanks for all the input. I made the java change to system and that did indeed change the font size and I can definitely read the contents, however, they are now so large that when doing something like updating a program, I only get a couple lines of code and have to continuously scroll up and down to view the program. Isn't there some way that UDI could allow the user to specify the size of the displayed text so they could match it to the computer/monitor that they use? For the time being, this is a much better solution than using the Windows Magnifier.

Hello rssorensen, did you ever get this resolved? I just replaced my PLM (second one in 2 years) and I'm having the same problem as you. thanks, ken

I got back to the 2476S / 2477D problem and this is what I found: - the 2476S Only works occasionally even when outside the box and separated from the 2477D. - if I put the X10 switch back in, it works - if I put the 2476S in another box but on the same circuit, it works There doesn't seem to be any reasoning here so I put another 2477D in and both work. Of course, the 2477D's are dual band so I suspect they are working via RF.

Thanks for the reply, when I get home, I'll remove the switches from the double ganged box to see if that fixes it.

I decided to replace an old X10 light switch so chose to buy a Insteon 2477D to replace it. Up until I replaced it, everything was working just fine. Now, I can't reliably turn on the 2476S. It sometimes responds to On/Off commands and some times I have to issue the command several times before it responds. The 2477D works just fine. These two Insteon modules are in the same electrical box. Is it possible that, being in the same box, the 2477D is interfering with the 2476S?

Thank you LeeG. I thought I looked there but I guess I didn't.

I've gone through a lot of posts discussing PLM replacement and problems and it seems like the procedure isn't exactly an exact science. A couple days ago, my system started acting up and the only thing that fixes it is to unplug the PLM and ISY994i, then plug them back in. I then do a Restore Modem (PLM) and things work for a while when I have to repeat this. I can always communicate with the ISY994i when it's acting up. I've ordered a new 2413S and would like some exact steps to replace the old one with the new one. Does anyone have such a list of steps? I only have one battery operated device so I shouldn't have to worry about doing them one at a time. Thanks for any help.

I have sent my UUID to the support email address.

No, I haven't signed up for anything that did not come with the ISY994i. I've been using X10 since I purchased it.

I've been gone from my home for almost a year and my ISY994 has performed admirably while gone. However, when I log onto it now, I get a popup window saying: Would you like to proceed with the following module actions? A10/X10 Experimental Support (21060) -- To Be Uninstalled Portal Integration - MobiLinc Connect (21073) -- To Be Installed What does this mean? I have about 10 X10 devices that I control via my ISY994 but have never purchased the X10 module. If I answer yes to this question, will they still continue to work? Also, if I answer yes and things don't work like before, can I revert back to the previous configuration?

Thanks Michel, I'll watch for it on the next update.

I'm getting some weird characters when I send an alert using the device status from several of my Insteon modules. I have the following in the alert: Water sensor ST = ${sys.node.1D 1 11 1.ST} When I run a program which uses this customized content, I get the following in the email content: Water sensor ST = €€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€On The status on the end is correct. The same characters appear when displaying the status (ST) on the following modules: 2450 IOLinc V41 EZIO6I VFF 2476S switch 2420M motion detector ... but NOT on my 2491T thermostat. I get the proper Thermostat ST=21.00. Does anyone have and idea why I get the weird characters? Thanks, Ken

I've been playing around with sending alerts when certain thermostat events happen and have found that if you use the device variable CLIHUM with the "Report Humidity" option off, you don't get anything but if you turn the option on, then CLIHUM=${sys.node.14 92 10 1.CLIHUM} will show you the humidity in an alert email.

Yesterday, I used chat to talk to Smarthome and the guy that was answering my questions said that as far as Smarthome knows, there are no problems with the 2441th. It looks like this thermostat will not be ready for prime time for a while so I think I'll stop waiting and buy a 2491T1E instead. Are there any problems with this thermostat that I should know about?

Thanks for the quick reply on a weekend. Program enabled shows "ON" Run at startup "-" Activity "idle" Status "false" Path " " Last run time " " Last finish time " " Next scheduled run " " Firmware version v.3.2.6 After more testing, if I change IR_021 to IR_003, the program runs. Then if I change it back to IR_021, it does not run. I'm beginning to see what's happening, IR_021 is not the same as Hex code 021 in the trace. I find that IR_010 is really Hex Code 0000. Now all I have to do is find the mapping of the standard IR codes that comes with the ISY. OK, chalk it up to a newbie with regard to the ISY. I found the codes under Configuration/IR and it turns out that IR_014 = 33 which is HEX 0x0021 (as seen in the trace) for Channel Down. Please close this problem.

I have an ISY994i/IR Pro ******* If I run the following program, and press IR_021, If IR 'IR_021' is Pressed Then Send X10 'M2/Off (11)' Else - No Actions - (To add one, press 'Action') I get the following entry in the Diagnostic event viewer Sun 06/17/2012 04:13:58 PM : [ IR] 0021 Press ******* If I run the following program, and press IR_006, If X10 'K5/Off (11)' is Received Or IR 'IR_006' is Pressed Then Send X10 'M2/Off' (11)' Else - No Actions - (To add one, press 'Action") I get the following entrys in the Diagnostic event viewer Sun 06/17/2012 04:15:13 PM : [ IR] 0006 Press Sun 06/17/2012 04:15:13 PM : [ X10] M2 Sun 06/17/2012 04:15:13 PM : [ X10] M2/Off (11) Sun 06/17/2012 04:15:13 PM : [X10-RSP ] 02 63 0E 00 06 Sun 06/17/2012 04:15:14 PM : [X10-RSP ] 02 63 03 80 06 Why doesn't the the first program respond to the IR_021 press? You can see that the ISY994i receives the IR_021 keypress but doesn't do anything. In the case of program 2, it receives the IR_006 and sends the proper X10 commands. I've tried exiting the admin console, rebooting the ISY, deleteing and re-adding the program, but nothing works.

Thanks for the help. I can't seem to trace down the source of the noise but I've added 3 more modules around the house and after I added them, the switch hasn't failed. I see it do retries some times but at least it doesn't fail. I plan on adding more devices so hopefully, that will continue to improve the one switch.

OK, the new switch also quit responding to commands so it's not a bad switch so we are back to the noise theory. I've been running a trace when testing and have noticed that when the switch quits working, I get an "ERR 1" line. What is that? Fri 05/25/2012 08:14:58 AM : [iNST-SRX ] 02 50 1C.C2.15 1B.FD.4D 2B 13 00 LTOFFRR(00) Fri 05/25/2012 08:14:58 AM : [standard-Direct Ack][1C.C2.15-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Fri 05/25/2012 08:14:58 AM : [ 1C C2 15 1] ST 0 Fri 05/25/2012 08:23:37 AM : [iNST-TX-I1 ] 02 62 1C C2 15 0F 11 FF Fri 05/25/2012 08:23:37 AM : [iNST-ACK ] 02 62 1C.C2.15 0F 11 FF 06 LTONRR (FF) Fri 05/25/2012 08:23:41 AM : [ 1C C2 15 1] ERR 1 Fri 05/25/2012 08:26:15 AM : [iNST-TX-I1 ] 02 62 1C C2 15 0F 11 FF Fri 05/25/2012 08:26:15 AM : [iNST-ACK ] 02 62 1C.C2.15 0F 11 FF 06 LTONRR (FF) ------ No response after this ------- If this is a noise problem and the noise disappears, why doesn't the switch start working again. Why do I have to do a "delete from ISY, factory reset, reconfigure switch" to get it back? Thanks, Ken

Hello Lee, I've replaced the 2476S switch on the fluorescent light with my spare one and so far, it's working just fine. It looks like I may have received a bad switch. Do I contact AARTECH about replacing it if the replacement continues to work? Thanks Ken

It didn't take long (about 15 minutes) for the 2476S to stop responding to on/off commands with the load wire still disconnected. I tried registering it again and it doesn't work. I'm going to put my other 2476S in this circuit and see what happens. Ken Thu 05/24/2012 04:48:00 PM : ---- Initializing the linked devices ---- Thu 05/24/2012 04:48:00 PM : ---- All Linked Devices are now initialized ---- Thu 05/24/2012 04:48:00 PM : ---- Add remaining devices ---- Thu 05/24/2012 04:48:00 PM : [iNST-TX-I1 ] 02 62 1C BF 16 0F 0D 00 Thu 05/24/2012 04:48:00 PM : [iNST-ACK ] 02 62 1C.BF.16 0F 0D 00 06 (00) Thu 05/24/2012 04:48:08 PM : [iNST-TX-I1 ] 02 62 1C BF 16 0F 0D 00 Thu 05/24/2012 04:48:08 PM : [iNST-ACK ] 02 62 1C.BF.16 0F 0D 00 06 (00) Thu 05/24/2012 04:48:17 PM : [iNST-TX-I1 ] 02 62 1C BF 16 0F 0D 00 Thu 05/24/2012 04:48:17 PM : [iNST-ACK ] 02 62 1C.BF.16 0F 0D 00 06 (00) Thu 05/24/2012 04:48:21 PM : ---- All Remaining Device Added ---- Thu 05/24/2012 04:48:21 PM : [All ] Writing 0 bytes to devices

I removed the load wire (red) and then did a "start linking" to register it. It registered the first try and now responds to on/off commands from the ISY. I've seen this happen before so I'll leave the load wire disconnected for a day or so to see if the problem comes back. I have some X10 XPNR noise reducers which I used on X10 installations to help with noise on fluorescent lights. Would these filters also work for Insteon? I've included the trace file because when I try to attach it, this web page doesn't allow me to attach a *.txt file. Thanks, Ken Thu 05/24/2012 04:30:59 PM : [LNK-BGN ] 02 64 01 00 06 Thu 05/24/2012 04:31:24 PM : [iNST-SRX ] 02 50 1C.BF.16 00.00.01 CB 17 01 LTMCON (UP) Thu 05/24/2012 04:31:24 PM : [standard-Group][1C.BF.16-->Group=1] Max Hops=3, Hops Left=2 Thu 05/24/2012 04:31:24 PM : [iNST-SRX ] 02 50 1C.BF.16 00.00.01 CB 17 01 LTMCON (UP): Process Message: Ignored Thu 05/24/2012 04:31:24 PM : [standard-Group][1C.BF.16-->Group=1] Max Hops=3, Hops Left=2 Thu 05/24/2012 04:31:32 PM : [LNK-STAT ] 02 53 M(01) gid=00 1C.BF.16 021C 41 Thu 05/24/2012 04:31:32 PM : Linked: Linked 1C.BF.16.00 type=02.1C.41 Thu 05/24/2012 04:31:32 PM : [iNST-TX-I1 ] 02 62 1C BF 16 0F 0D 00 Thu 05/24/2012 04:31:32 PM : [iNST-ACK ] 02 62 1C.BF.16 0F 0D 00 06 (00) Thu 05/24/2012 04:31:32 PM : [iNST-SRX ] 02 50 1C.BF.16 1B.FD.4D 2B 0D 02 (02) Thu 05/24/2012 04:31:32 PM : [standard-Direct Ack][1C.BF.16-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Thu 05/24/2012 04:31:32 PM : [1C BF 16 0 ] Calibrating engine version Thu 05/24/2012 04:31:32 PM : [1C BF 16 1 ] Start : Adding device to ISY Thu 05/24/2012 04:31:32 PM : [1C BF 16 1 ] Finish : Adding device to ISY was Successful Thu 05/24/2012 04:31:32 PM : [All ] Writing 0 bytes to devices Thu 05/24/2012 04:31:32 PM : [LNK-BGN ] 02 64 01 00 06 Thu 05/24/2012 04:31:33 PM : [iNST-SRX ] 02 50 1C.BF.16 00.00.01 CB 18 00 LTMCOFF(00) Thu 05/24/2012 04:31:33 PM : [standard-Group][1C.BF.16-->Group=1] Max Hops=3, Hops Left=2 Thu 05/24/2012 04:31:51 PM : [ 1C BF 16 1] SMAN 0 Thu 05/24/2012 04:31:51 PM : ---- Initializing the linked devices ---- Thu 05/24/2012 04:31:51 PM : [LNK-END ] 02 65 06 : : Unexpected, ignored (65) Thu 05/24/2012 04:31:51 PM : [1C BF 16 1 ] Link 0 : 0FF8 [A2001BFD4DFF1F01] Saving [A2001BFD4DFF1F01] Thu 05/24/2012 04:31:51 PM : [1C BF 16 1 ] Link 1 : 0FF0 [E2011BFD4DFF1F01] Saving [E2011BFD4DFF1F01] Thu 05/24/2012 04:31:51 PM : [iNST-TX-I2CS] 02 62 1C BF 16 1F 2E 00 01 00 00 00 00 00 00 00 00 00 00 00 00 D1 Thu 05/24/2012 04:31:52 PM : [iNST-ACK ] 02 62 1C.BF.16 1F 2E 00 01 00 00 00 00 00 00 00 00 00 00 00 00 D1 06 (00) Thu 05/24/2012 04:32:01 PM : [iNST-TX-I2CS] 02 62 1C BF 16 1F 2E 00 01 00 00 00 00 00 00 00 00 00 00 00 00 D1 Thu 05/24/2012 04:32:01 PM : [iNST-ACK ] 02 62 1C.BF.16 1F 2E 00 01 00 00 00 00 00 00 00 00 00 00 00 00 D1 06 (00) Thu 05/24/2012 04:32:01 PM : [iNST-SRX ] 02 50 1C.BF.16 1B.FD.4D 2B 2E 00 (00) Thu 05/24/2012 04:32:01 PM : [standard-Direct Ack][1C.BF.16-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Thu 05/24/2012 04:32:01 PM : [iNST-ERX ] 02 51 1C BF 16 1B FD 4D 11 2E 00 01 01 00 00 00 00 1C FF 20 00 00 06 00 00 Thu 05/24/2012 04:32:01 PM : [Extended-Direct][1C.BF.16-->ISY/PLM Group=0] Max Hops=1, Hops Left=0 Thu 05/24/2012 04:32:02 PM : ---- All Linked Devices are now initialized ---- Thu 05/24/2012 04:32:02 PM : [iNST-TX-I1 ] 02 62 1C BF 16 0F 19 00 Thu 05/24/2012 04:32:02 PM : [iNST-ACK ] 02 62 1C.BF.16 0F 19 00 06 LTSREQ (LIGHT) Thu 05/24/2012 04:32:02 PM : [iNST-SRX ] 02 50 1C.BF.16 1B.FD.4D 2B 01 FF (FF) Thu 05/24/2012 04:32:02 PM : [standard-Direct Ack][1C.BF.16-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Thu 05/24/2012 04:32:02 PM : ---- Initializing the linked devices ---- Thu 05/24/2012 04:32:02 PM : ---- All Linked Devices are now initialized ---- Thu 05/24/2012 04:32:02 PM : [ 1C BF 16 1] OL 255 Thu 05/24/2012 04:32:02 PM : [ 1C BF 16 1] RR 28 Thu 05/24/2012 04:32:02 PM : [ 1C BF 16 1] ST 255 Thu 05/24/2012 04:32:02 PM : [ 1C BF 16 1] OL 255 Thu 05/24/2012 04:32:02 PM : [ 1C BF 16 1] RR 28 Thu 05/24/2012 04:32:02 PM : [All ] Writing 16 bytes to devices Thu 05/24/2012 04:32:02 PM : [1C BF 16 1 ] Link 0 : 0FF8 [A2001BFD4DFF1F01] Writing [A2001BFD4DFF1F01] Thu 05/24/2012 04:32:02 PM : [iNST-TX-I2CS] 02 62 1C BF 16 1F 2F 00 00 02 0F FF 08 A2 00 1B FD 4D FF 1F 01 93 Thu 05/24/2012 04:32:02 PM : [iNST-ACK ] 02 62 1C.BF.16 1F 2F 00 00 02 0F FF 08 A2 00 1B FD 4D FF 1F 01 93 06 (00) Thu 05/24/2012 04:32:03 PM : [iNST-SRX ] 02 50 1C.BF.16 1B.FD.4D 2B 2F 00 (00) Thu 05/24/2012 04:32:03 PM : [standard-Direct Ack][1C.BF.16-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Thu 05/24/2012 04:32:03 PM : [MNG-LNK-RSP ] 02 6F 40 E2 00 1C BF 16 02 1C 41 06 Thu 05/24/2012 04:32:03 PM : [PLM ] Group 0 : Writing Controller Link matching [1C BF 16 1 ] Link 0 : 0FF8 [A2001BFD4DFF1F01] Thu 05/24/2012 04:32:03 PM : [1C BF 16 1 ] Link 1 : 0FF0 [E2011BFD4DFF1F01] Writing [E2011BFD4DFF1F01] Thu 05/24/2012 04:32:03 PM : [iNST-TX-I2CS] 02 62 1C BF 16 1F 2F 00 00 02 0F F7 08 E2 01 1B FD 4D FF 1F 01 5A Thu 05/24/2012 04:32:03 PM : [iNST-ACK ] 02 62 1C.BF.16 1F 2F 00 00 02 0F F7 08 E2 01 1B FD 4D FF 1F 01 5A 06 (00) Thu 05/24/2012 04:32:04 PM : [iNST-SRX ] 02 50 1C.BF.16 1B.FD.4D 2B 2F 00 (00) Thu 05/24/2012 04:32:04 PM : [standard-Direct Ack][1C.BF.16-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Thu 05/24/2012 04:32:04 PM : [MNG-LNK-RSP ] 02 6F 41 A2 01 1C BF 16 02 1C 41 15 Thu 05/24/2012 04:32:04 PM : [PLM ] Group 1 : Writing Responder Link matching [1C BF 16 1 ] Link 1 : 0FF0 [E2011BFD4DFF1F01] Thu 05/24/2012 04:32:04 PM : [1C BF 16 1 ] Link 2 : 0FE8 [0000000000000000] Writing [00..............] Thu 05/24/2012 04:32:04 PM : [iNST-TX-I2CS] 02 62 1C BF 16 1F 2F 00 00 02 0F EF 08 00 00 00 00 00 00 00 00 C9 Thu 05/24/2012 04:32:04 PM : [iNST-ACK ] 02 62 1C.BF.16 1F 2F 00 00 02 0F EF 08 00 00 00 00 00 00 00 00 C9 06 (00) Thu 05/24/2012 04:32:05 PM : [iNST-SRX ] 02 50 1C.BF.16 1B.FD.4D 2B 2F 00 (00) Thu 05/24/2012 04:32:05 PM : [standard-Direct Ack][1C.BF.16-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Thu 05/24/2012 04:32:05 PM : [1C BF 16 1 ] Link 3 : 0FE0 : Writing High Water Byte Thu 05/24/2012 04:32:05 PM : [iNST-TX-I2CS] 02 62 1C BF 16 1F 2F 00 00 00 0F E7 01 00 00 00 00 00 00 00 00 DA Thu 05/24/2012 04:32:05 PM : [iNST-ACK ] 02 62 1C.BF.16 1F 2F 00 00 00 0F E7 01 00 00 00 00 00 00 00 00 DA 06 (00) Thu 05/24/2012 04:32:05 PM : [iNST-SRX ] 02 50 1C.BF.16 1B.FD.4D 2B 2F 00 (00) Thu 05/24/2012 04:32:05 PM : [standard-Direct Ack][1C.BF.16-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Thu 05/24/2012 04:32:06 PM : [iNST-ERX ] 02 51 1C BF 16 1B FD 4D 11 2F 00 01 01 0F E7 00 00 00 00 00 00 00 00 00 D9 Thu 05/24/2012 04:32:06 PM : [Extended-Direct][1C.BF.16-->ISY/PLM Group=0] Max Hops=1, Hops Left=0 Thu 05/24/2012 04:32:06 PM : [iNST-TX-I2CS] 02 62 1C BF 16 1F 2F 00 00 00 0F E7 01 00 00 00 00 00 00 00 00 DA Thu 05/24/2012 04:32:06 PM : [iNST-ACK ] 02 62 1C.BF.16 1F 2F 00 00 00 0F E7 01 00 00 00 00 00 00 00 00 DA 06 (00) Thu 05/24/2012 04:32:06 PM : [iNST-SRX ] 02 50 1C.BF.16 1B.FD.4D 2B 2F 00 (00) Thu 05/24/2012 04:32:06 PM : [standard-Direct Ack][1C.BF.16-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Thu 05/24/2012 04:32:07 PM : [iNST-ERX ] 02 51 1C BF 16 1B FD 4D 11 2F 00 01 01 0F E7 00 00 00 00 00 00 00 00 00 D9 Thu 05/24/2012 04:32:07 PM : [Extended-Direct][1C.BF.16-->ISY/PLM Group=0] Max Hops=1, Hops Left=0 Thu 05/24/2012 04:32:07 PM : [iNST-TX-I2CS] 02 62 1C BF 16 1F 2F 00 00 02 0F E7 08 00 00 00 00 00 00 00 00 D1 Thu 05/24/2012 04:32:07 PM : [iNST-ACK ] 02 62 1C.BF.16 1F 2F 00 00 02 0F E7 08 00 00 00 00 00 00 00 00 D1 06 (00) Thu 05/24/2012 04:32:08 PM : [iNST-SRX ] 02 50 1C.BF.16 1B.FD.4D 2B 2F 00 (00) Thu 05/24/2012 04:32:08 PM : [standard-Direct Ack][1C.BF.16-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Thu 05/24/2012 04:32:08 PM : [All ] Writing 0 bytes to devices

It's kind of strange that this is the only device that is having the communication problem. There is a 2450 and a 2456S3 on the opposite side of the wall on the same circuit and they have never had a problem. The only difference that I can see is this switch is controlling a fluorescent light. What can I do to further trace this problem? I have an extra 2476S that isn't installed yet. Would you suggest that I try it on the same light or on one right next to it? I have both a fluorescent light and an incondescent light right next to this switch on the same circuit. As an after thought, here's what is probably a newbie question. If the switch is not communicating with the ISY, then how does the ISY trace show the address of the switch (1C.BF.16)? I delete the device from the ISY, which should erase all knowledge of that device, then run the start linking process which immediately shows the 1C.BF.16 device. This seems to indicate that the ISY is getting some kind of response from the 2476S.

I was able to get the 2476S to configure and it shows up as V.41. I then issued a couple on/off commands and it stopped communicating again. I then tried a delete/factory reset/configure and this time turned the diagnostic trace on. I can see the switch communicating but it never shows up in the admin console of my ISY994i/IR Pro. There is an error message that you might make some sense of, it says: Thu 05/24/2012 02:44:07 PM : [LNK-END ] 02 65 06 : : Unexpected, ignored (65) Trace file: 2476S - 1C.BF.16 Thu 05/24/2012 02:43:28 PM : [LNK-BGN ] 02 64 01 00 06 Thu 05/24/2012 02:43:45 PM : [LNK-STAT ] 02 53 M(01) gid=00 1C.BF.16 021C 41 Thu 05/24/2012 02:43:45 PM : Linked: Linked 1C.BF.16.00 type=02.1C.41 Thu 05/24/2012 02:43:45 PM : [iNST-TX-I1 ] 02 62 1C BF 16 0F 0D 00 Thu 05/24/2012 02:43:45 PM : [iNST-ACK ] 02 62 1C.BF.16 0F 0D 00 06 (00) Thu 05/24/2012 02:43:54 PM : [iNST-TX-I1 ] 02 62 1C BF 16 0F 0D 00 Thu 05/24/2012 02:43:54 PM : [iNST-ACK ] 02 62 1C.BF.16 0F 0D 00 06 (00) Thu 05/24/2012 02:44:03 PM : [iNST-TX-I1 ] 02 62 1C BF 16 0F 0D 00 Thu 05/24/2012 02:44:03 PM : [iNST-ACK ] 02 62 1C.BF.16 0F 0D 00 06 (00) Thu 05/24/2012 02:44:07 PM : ---- Initializing the linked devices ---- Thu 05/24/2012 02:44:07 PM : [LNK-END ] 02 65 06 : : Unexpected, ignored (65) Thu 05/24/2012 02:44:07 PM : ---- All Linked Devices are now initialized ---- Thu 05/24/2012 02:44:07 PM : ---- Initializing the linked devices ---- Thu 05/24/2012 02:44:07 PM : ---- All Linked Devices are now initialized ---- Thu 05/24/2012 02:44:07 PM : [All ] Writing 0 bytes to devices Thu 05/24/2012 02:44:07 PM : [All ] Writing 0 bytes to devices Thu 05/24/2012 02:44:07 PM : [All ] Writing 0 bytes to devices

I just purchased all of the Insteon equipment I'm working with so I'd hope it is up to date on firmware but if I ever get the 2476S configured again, I'll check the firmware version. The 2476S seems to quit communicating at random intervals. I will be using it for a while, testing programs etc when suddenly, it will no longer respond to any commands. At first, I thought it was either a bridging problem or a noise problem so I've switched that circuit onto the same phase as my PLM but the problem is still there. I've also changed all of my CFL bulbs back to standard ones to eliminate a possible source of noise. The device is not working right now so I've moved the PLM right next to the switch and then did a delete, factory reset reconfigure but it won't configure now. If I wait for a while and try it again, eventually, it will start working. It works fine from the manual switch. This switch is controlling a fluorescent light in my kitchen. Could that be the problem? I ordered this switch because the site documentation said it could be used with CFL's and fluorescent.