john410

Thanks. I got a security warning but was able to work around.

Just recently switch to Mac at home. Trying to get to my UDI device but cannot. I'm using Chrome on an iMac and when I got to the local address http://192.168.254.xxx I get clicking on "Admin Console", I get: Somehow, on my PC, I used to get a Java App to run which communicated with the UDI controller. (I never did understand how it all worked). I downloaded and installed the latest JRE on my Mac. Any help would be appreciated.

Great suggestion. I will try one incandescent and one LED and see what happens.

Thanks for the link. As one of the posts noted, I suspect the older X10 wall switch I use gets it's power by tapping into the current flowing through the load. In an incandescent bulb, that wouldn't be a problem. But, if an LED is used and a very low voltage applied, I suspect there is no current draw. Hence, there is effectively no power or insufficient power for the X10 receiver to work. And when the LED is on, perhaps the LED is introducing noise. I know X10 has many drawbacks, but I was never able to get Insteon to work in my house.

First, I'm sorry if this is not the correct forum, but the X10 forum looks dead (latest post 5 months ago). I *do* use an ISY controller to control X10 devices in my home. My question is this: I have an older X10 wall switch (no dimmer, just on/off switch) that I've had for years controlling floodlights (one fixture, two lights). I recently replaced my older incandescent floodlights with LED floodlights. At the same time, I started noticing the lights would occasionally fail to come on in the evening and/or go off in the morning. I'd say it works maybe 50% of the time. I know some of these X10 wall switches sense load and thought maybe the LED floodlights "appear" differently to the X10 switch. Again, I've never had an issue with the incandescent floodlights and the X10 switch. Also, manually pushing the button works fine. Is there any known issue with LED lights and X10? Or, is my switch just getting old and needs to be replaced?

There have been some storms recently that knocked out power to my home in the evening, when most of my X10 switches and lamps were programmed to be on. When the power comes back, the ISY starts just fine, but any lights that were on from the program remain off. I know the programs are running because the next on event works OK (e.g. a table lamp coming on at 5:00 AM). I thought the ISY was supposed to detect a power outage and set the state of the lights back to what it should be, according to the stored program. I use X10 for all but one lamp. My programs are of the type "If time is between X and Y, turn A10 on, else turn A10 off". Is there an option I should use in my programs or on the system? Should I program in a different way?

Was the error "Cannot determine Insteon engine"? That's all I ever get. I can't add Insteon LampLincs.

I have mostly X10 lamp modules. I have a couple of X10 wall switches, the push button kind, that control the outdoor lights. I also have what I think is called a ToggleLink? - it's a wall switch that you can tap up and down, and set dim level on it. I use that for my family room spot lights. Do any of these possibly have "BoosterLinc"? I was also puzzled by the X10 messages in my log when all I was doing was trying to link Insteon devices.

Yes, I am frustrated. Been trying to get Insteon stuff to work for a couple of months now. I'm the kind of guy that likes cutting edge stuff. I'm an EE by degree, have done software/firmware design and coding most of my career. I understand embedded devices, processors and electronics very well. I've read the whitepapers on Insteon and understand the protocols and why it is supposed to be more reliable. But again, that just hasn't been my experience. To use your analogy, my new tractor is broken down and won't start. My horse is doing fine. I'll stick with the horse for now. Thanks for everyone's input. I'll stay tuned to see if someone else has as bad luck as me and if they manage to find a solution.

Nope. Just tried the lamplinc on the lamp in my office, probably 60 feet or more from the PLM. Same "Cannot determine Insteon engine" message.

Thanks, but I just found out about that option myself. No luck. That's it, I've had enough screwing around with Insteon. I'm putting my X10 lamp module back on and using it instead. I'll be sending the LampLincs back to SmartHome next week.

OK, so I looked at the documentation some more and found the "New INSTEON Device." option. Here's what I did: Factory reset the LampLinc by holding the link button while plugging it in. Waited until it stopped beeping and released the button, lamp came on. On ISY, chose "New Insteon/A10/X10 Device" (I have X10 software option installed). On dialog, entered the address "35.99.CD", gave it a name and left the "Remove existing links option" selected. Pressed OK. Saw dialog "New Insteon Devices" and the message adding. Got the "Cannot determine Insteon engine" message. Here's the log: Sat 01/09/2016 02:32:00 PM : [35 99 CD ] Added to list of devices to link to ISY Sat 01/09/2016 02:32:00 PM : [iNST-TX-I1 ] 02 62 35 99 CD 0F 0D 00 Sat 01/09/2016 02:32:00 PM : [iNST-ACK ] 02 62 35.99.CD 0F 0D 00 06 (00) Sat 01/09/2016 02:32:09 PM : [iNST-TX-I1 ] 02 62 35 99 CD 0F 0D 00 Sat 01/09/2016 02:32:18 PM : [iNST-TX-I1 ] 02 62 35 99 CD 0F 0D 00 Sat 01/09/2016 02:32:22 PM : [35 99 CD 0 ] Failed to add device, reason 3 Sat 01/09/2016 02:32:22 PM : [All ] Writing 0 bytes to devices Sat 01/09/2016 02:34:00 PM : [iNST-SRX ] 02 50 35.99.CD 3D.C7.29 AF 0D FF (FF) Sat 01/09/2016 02:34:01 PM : [std-Direct Nack] 35.99.CD-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Sat 01/09/2016 02:34:01 PM : [iNST-DUP ] Previous message ignored. Sat 01/09/2016 02:34:30 PM : [ Time] 14:35:01 6(0)

I tried holding the link button until the first beep sounded. The LED begins flashing green. I then go back to the ISY and click finish. Still getting the "Cannot determine Insteon engine." error message. Here's the log. What's the "unexpected ACK"? Is that the source of this problem? Sat 01/09/2016 02:23:32 PM : Start Insteon Device Linking Mode Sat 01/09/2016 02:23:32 PM : [LNK-BGN ] 02 64 01 00 06 Sat 01/09/2016 02:24:09 PM : [X10-RX ] 02 52 FF 80 Sat 01/09/2016 02:24:12 PM : [LNK-STAT ] 02 53 M(01) gid=00 35.99.CD 010E 43 Sat 01/09/2016 02:24:12 PM : [35.99.CD 00] Linked device type=01.0E fw=43 Sat 01/09/2016 02:24:12 PM : [35 99 CD 0 ] Added to list of devices to link to ISY Sat 01/09/2016 02:24:12 PM : [LNK-BGN ] 02 64 01 00 06 Sat 01/09/2016 02:24:39 PM : Stop Insteon Device Linking Mode, Final processing to follow Sat 01/09/2016 02:24:39 PM : [ X10] J/Status Request (10) Sat 01/09/2016 02:24:39 PM : [iNST-TX-I1 ] 02 62 35 99 CD 0F 0D 00 Sat 01/09/2016 02:24:39 PM : [LNK-END ] 02 65 06 Sat 01/09/2016 02:24:39 PM : [std MH ] Unexpected Ack imCmd=65 cmd1= 0xCD Sat 01/09/2016 02:24:40 PM : [iNST-ACK ] 02 62 35.99.CD 0F 0D 00 06 (00) Sat 01/09/2016 02:24:44 PM : [iNST-TX-I1 ] 02 62 35 99 CD 0F 0D 00 Sat 01/09/2016 02:24:53 PM : [iNST-TX-I1 ] 02 62 35 99 CD 0F 0D 00 Sat 01/09/2016 02:24:57 PM : [35 99 CD 0 ] Failed to add device, reason 3 Sat 01/09/2016 02:24:57 PM : [All ] Writing 0 bytes to devices Sat 01/09/2016 02:24:57 PM : [All ] Writing 0 bytes to devices Sat 01/09/2016 02:25:04 PM : [iNST-SRX ] 02 50 35.99.CD 3D.C7.29 2F 0D 02 (02) Sat 01/09/2016 02:25:04 PM : [std-Direct Ack] 35.99.CD-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Sat 01/09/2016 02:25:04 PM : [iNST-DUP ] Previous message ignored.

Regarding the reset, others here tell me it is correct. I tried the flowchart method and could not get it to work. Someone in another thread recommended the method I used. What linking method should I use? I am following the instructions for the ISY, page 16: "Start Linking: The majority of Insteon devices can be added using this method..." I select the "Remove existing links" radio button, which again, the documentation says "This is the default and the best option to choose if you would like a clean start." The ISY recognizes the LampLinc when I press the link button and shows the address that is printed on it. When I click Finish, I get the error message about not recognizing the Insteon engine, whatever the heck that is. I don't know how to identify the noise makers or "signal suckers". Maybe I'm thick headed here, but as I keep noting, my X10 devices work fine. Everything I read tells me X10 is not as reliable as Insteon. I am not about to go out and invest another $100 or more in devices to try and make the power line clean when my X10 devices have worked for 15 years without any problems. How can that be. I thought the only way you could link an Insteon device is by pressing the link button on it. What is the Autodiscover method? I don't have an X10 repeater, just a phase coupler.

Was taking my Christmas lights down today and I thought I would try to get an Insteon LampLinc module to work with my living room lamp. No luck. Here's what I did: 1) Factory reset the LampLinc by plugging it in (with lamp on and connected), holding the link button. 2) LampLinc gave out long beep then stopped. 3) Released link button and lamp came on 4) On ISY, selected Start Linking 5) Pressed link button until beep sounded 6) Continue to hold link button until two beeps sounded 7) On ISY, message indicated the device was added. 8 ) Selected Add 9) Got error message: "Cannot determine Insteon engine." 10) Captured event viewer output (level 3) below Important to note: This outlet is immediately above the circuit breaker box (5 feet away at most) into which the PLC is plugged into (outlet wired directly into breaker box). I have installed a phase coupler. The X10 module works in this outlet and can be controlled by the ISY with no problem. I have posted a couple of times about my Insteon problems. Everything I read says that Insteon is far more reliable than X10. I am having exactly the opposite experience. Here's the log (tried with two different LampLinc modules): Sat 01/09/2016 12:03:03 PM : [X10-RX ] 02 52 FF 80 Sat 01/09/2016 12:03:06 PM : [LNK-STAT ] 02 53 M(01) gid=00 35.9C.41 010E 43 Sat 01/09/2016 12:03:06 PM : [35.9C.41 00] Linked device type=01.0E fw=43 Sat 01/09/2016 12:03:06 PM : [35 9C 41 0 ] Added to list of devices to link to ISY Sat 01/09/2016 12:03:06 PM : [LNK-BGN ] 02 64 01 00 06 Sat 01/09/2016 12:03:47 PM : Stop Insteon Device Linking Mode, Final processing to follow Sat 01/09/2016 12:03:47 PM : [LNK-END ] 02 65 06 : : Unexpected, ignored (65) Sat 01/09/2016 12:03:47 PM : [ X10] J/Status Request (10) Sat 01/09/2016 12:03:47 PM : [iNST-TX-I1 ] 02 62 35 9C 41 0F 0D 00 Sat 01/09/2016 12:03:48 PM : [iNST-ACK ] 02 62 35.9C.41 0F 0D 00 06 (00) Sat 01/09/2016 12:03:56 PM : [iNST-TX-I1 ] 02 62 35 9C 41 0F 0D 00 Sat 01/09/2016 12:04:05 PM : [iNST-TX-I1 ] 02 62 35 9C 41 0F 0D 00 Sat 01/09/2016 12:04:09 PM : [35 9C 41 0 ] Failed to add device, reason 3 Sat 01/09/2016 12:04:09 PM : [All ] Writing 0 bytes to devices Sat 01/09/2016 12:04:09 PM : [All ] Writing 0 bytes to devices Sat 01/09/2016 12:06:37 PM : Start Insteon Device Linking Mode Sat 01/09/2016 12:06:37 PM : [LNK-BGN ] 02 64 01 00 06 Sat 01/09/2016 12:07:13 PM : [X10-RX ] 02 52 FF 80 Sat 01/09/2016 12:07:17 PM : [LNK-STAT ] 02 53 M(01) gid=00 35.99.CD 010E 43 Sat 01/09/2016 12:07:17 PM : [35.99.CD 00] Linked device type=01.0E fw=43 Sat 01/09/2016 12:07:17 PM : [35 99 CD 0 ] Added to list of devices to link to ISY Sat 01/09/2016 12:07:17 PM : [LNK-BGN ] 02 64 01 00 06 Sat 01/09/2016 12:07:51 PM : Stop Insteon Device Linking Mode, Final processing to follow Sat 01/09/2016 12:07:51 PM : [ X10] J/Status Request (10) Sat 01/09/2016 12:07:51 PM : [LNK-END ] 02 65 06 Sat 01/09/2016 12:07:51 PM : [std MH ] Unexpected Ack imCmd=65 cmd1= 0xCD Sat 01/09/2016 12:07:51 PM : [iNST-TX-I1 ] 02 62 35 99 CD 0F 0D 00 Sat 01/09/2016 12:07:51 PM : [iNST-ACK ] 02 62 35.99.CD 0F 0D 00 06 (00) Sat 01/09/2016 12:07:53 PM : [iNST-SRX ] 02 50 35.99.CD 3D.C7.29 2F 0D 02 (02) Sat 01/09/2016 12:07:53 PM : [std-Direct Ack] 35.99.CD-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Sat 01/09/2016 12:07:56 PM : [iNST-TX-I1 ] 02 62 35 99 CD 0F 0D 00 Sat 01/09/2016 12:07:56 PM : [iNST-ACK ] 02 62 35.99.CD 0F 0D 00 06 (00) Sat 01/09/2016 12:08:05 PM : [iNST-TX-I1 ] 02 62 35 99 CD 0F 0D 00 Sat 01/09/2016 12:08:09 PM : [35 99 CD 0 ] Failed to add device, reason 3 Sat 01/09/2016 12:08:09 PM : [All ] Writing 0 bytes to devices Sat 01/09/2016 12:08:09 PM : [All ] Writing 0 bytes to devices

According to the flowchart, three successive presses should cause the led to slowly flash green, red, then green for each press respectively. I could never get the led back to flashing green once it flashed red. A tap was the only thing I could do once it was flashing red, and that took it back to steady green, starting the whole sequence over again.

Will do. Thanks for your help.

Yes, it was a brand new (out of the box) LampLinc module. When I couldn't get the factory reset to work using the flowchart in the instructions, I posted a question in the SmartHome forums. Someone there told me about the factory reset method where you hold the link button and plug it in. Don't know if that's what allowed me to successfully add this module, but I'm going to do it for all my Insteon lamp modules as I get more comfortable with Insteon. I'm going to add one device at a time and let the programs run for a few days to make sure everything is working. Thanks, John

Michel: The one thing I did differently today was that I did a factory reset of the lamplinc with the lamp plugged in. I held the linking button and plugged it in with a lamp plugged into the lamplinc that was on. Long beep for maybe 8 seconds. When the beep stopped, I released the link button and the lamp came on at 100%. I then selected "Start Linking" and pressed the link button. That worked. And yes, Automatic is checked. Thanks, John

As stated above, linking works now. At least for this device. Don't know what's different. As I stated in a previous post of my Insteon problems, an X10 lamp module is on this very same circuit (was actually in the same wall outlet) and it operated just fine from the ISY program. Could the X10 lamp module being on the same circuit (about 8 feet away) be the problem? Could that be attenuating the Insteon signal? If anything, I would think just the opposite would be true, since Insteon is supposedly more reliable than X10. I will experiment with other devices today and see what happens. I'm still not at all comfortable with Insteon - seems flaky.

Tried it today and linking worked! I did a factory reset of the lamplinc (hold link button and plug in). Then I selected "Start Linking" and pressed the link button on the lamplinc. Here's the log output: Wed 12/30/2015 09:12:01 AM : Start Insteon Device Linking Mode Wed 12/30/2015 09:12:01 AM : [LNK-BGN ] 02 64 01 00 06 Wed 12/30/2015 09:12:49 AM : [LNK-STAT ] 02 53 M(01) gid=00 35.9E.1E 010E 43 Wed 12/30/2015 09:12:49 AM : [35.9E.1E 00] Linked device type=01.0E fw=43 Wed 12/30/2015 09:12:49 AM : [35 9E 1E 0 ] Added to list of devices to link to ISY Wed 12/30/2015 09:12:49 AM : [LNK-BGN ] 02 64 01 00 06 Wed 12/30/2015 09:13:56 AM : Stop Insteon Device Linking Mode, Final processing to follow Wed 12/30/2015 09:13:56 AM : [iNST-TX-I1 ] 02 62 35 9E 1E 0F 0D 00 Wed 12/30/2015 09:13:56 AM : [LNK-END ] 02 65 06 Wed 12/30/2015 09:13:56 AM : [std MH ] Unexpected Ack imCmd=65 cmd1= 0x1E Wed 12/30/2015 09:13:56 AM : [iNST-ACK ] 02 62 35.9E.1E 0F 0D 00 06 (00) Wed 12/30/2015 09:13:57 AM : [iNST-SRX ] 02 50 35.9E.1E 3D.C7.29 2F 0D 02 (02) Wed 12/30/2015 09:13:57 AM : [std-Direct Ack] 35.9E.1E-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Wed 12/30/2015 09:14:01 AM : [iNST-TX-I1 ] 02 62 35 9E 1E 0F 0D 00 Wed 12/30/2015 09:14:01 AM : [iNST-ACK ] 02 62 35.9E.1E 0F 0D 00 06 (00) Wed 12/30/2015 09:14:01 AM : [iNST-SRX ] 02 50 35.9E.1E 3D.C7.29 2F 0D 02 (02) Wed 12/30/2015 09:14:01 AM : [std-Direct Ack] 35.9E.1E-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Wed 12/30/2015 09:14:01 AM : [35 9E 1E 0 ] Calibrating engine version Wed 12/30/2015 09:14:01 AM : [iNST-TX-I2CS] 02 62 35 9E 1E 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Wed 12/30/2015 09:14:01 AM : [iNST-ACK ] 02 62 35.9E.1E 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Wed 12/30/2015 09:14:02 AM : [iNST-SRX ] 02 50 35.9E.1E 3D.C7.29 2F 2F 00 (00) Wed 12/30/2015 09:14:02 AM : [std-Direct Ack] 35.9E.1E-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Wed 12/30/2015 09:14:02 AM : [iNST-ERX ] 02 51 35 9E 1E 3D C7 29 15 2F 00 01 01 0F FF 00 A2 00 3D C7 29 FF 1C 00 D7 Wed 12/30/2015 09:14:02 AM : [Ext-Direct ] 35.9E.1E-->ISY/PLM Group=0, Max Hops=1, Hops Left=1 Wed 12/30/2015 09:14:02 AM : [35 9E 1E 0 ] Using Database Link Table offset 0x0FF8 (reported 0x0FF8) Wed 12/30/2015 09:14:02 AM : [35 9E 1E 1 ] Start : Adding device to ISY Wed 12/30/2015 09:14:02 AM : [35 9E 1E 1 ] Finish : Adding device to ISY was Successful Wed 12/30/2015 09:14:02 AM : [35 9E 1E 1 ] Link 0 : 0FF8 [A2003DC729FF1F01] Saving [A2003DC729FF1F01] Wed 12/30/2015 09:14:02 AM : [35 9E 1E 1 ] Link 1 : 0FF0 [E2013DC729010001] Saving [E2013DC729010001] Wed 12/30/2015 09:14:02 AM : [iNST-TX-I2CS] 02 62 35 9E 1E 1F 2E 00 01 00 00 00 00 00 00 00 00 00 00 00 00 D1 Wed 12/30/2015 09:14:02 AM : [iNST-ACK ] 02 62 35.9E.1E 1F 2E 00 01 00 00 00 00 00 00 00 00 00 00 00 00 D1 06 (00) Wed 12/30/2015 09:14:03 AM : [iNST-SRX ] 02 50 35.9E.1E 3D.C7.29 2F 2E 00 (00) Wed 12/30/2015 09:14:03 AM : [std-Direct Ack] 35.9E.1E-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Wed 12/30/2015 09:14:03 AM : [iNST-ERX ] 02 51 35 9E 1E 3D C7 29 15 2E 00 01 01 0F FF 00 A2 1C FE C7 29 FF 02 01 D7 Wed 12/30/2015 09:14:03 AM : [Ext-Direct ] 35.9E.1E-->ISY/PLM Group=0, Max Hops=1, Hops Left=1 Wed 12/30/2015 09:14:03 AM : [iNST-TX-I1 ] 02 62 35 9E 1E 0F 19 00 Wed 12/30/2015 09:14:03 AM : [iNST-ACK ] 02 62 35.9E.1E 0F 19 00 06 LTSREQ (LIGHT) Wed 12/30/2015 09:14:04 AM : [iNST-SRX ] 02 50 35.9E.1E 3D.C7.29 2F 01 FF (FF) Wed 12/30/2015 09:14:04 AM : [std-Direct Ack] 35.9E.1E-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Wed 12/30/2015 09:14:04 AM : [35 9E 1E 0 ] Successfully added device Wed 12/30/2015 09:14:04 AM : [D2D EVENT ] Event [35 9E 1E 1] [OL] [255] uom=0 prec=-1 Wed 12/30/2015 09:14:04 AM : [ 35 9E 1E 1] OL 255 Wed 12/30/2015 09:14:04 AM : [D2D EVENT ] Event [35 9E 1E 1] [RR] [28] uom=0 prec=-1 Wed 12/30/2015 09:14:04 AM : [ 35 9E 1E 1] RR 28 Wed 12/30/2015 09:14:04 AM : [D2D EVENT ] Event [35 9E 1E 1] [sT] [255] uom=0 prec=-1 Wed 12/30/2015 09:14:04 AM : [ 35 9E 1E 1] ST 255 Wed 12/30/2015 09:14:04 AM : [D2D EVENT ] Event [35 9E 1E 1] [OL] [255] uom=0 prec=-1 Wed 12/30/2015 09:14:04 AM : [ 35 9E 1E 1] OL 255 Wed 12/30/2015 09:14:04 AM : [D2D EVENT ] Event [35 9E 1E 1] [RR] [28] uom=0 prec=-1 Wed 12/30/2015 09:14:04 AM : [ 35 9E 1E 1] RR 28 Wed 12/30/2015 09:14:04 AM : [All ] Writing 16 bytes to devices Wed 12/30/2015 09:14:04 AM : [35 9E 1E 1 ] Link 0 : 0FF8 [A2003DC729FF1F01] Writing [A2003DC729FF1F01] Wed 12/30/2015 09:14:04 AM : [iNST-TX-I2CS] 02 62 35 9E 1E 1F 2F 00 00 02 0F FF 08 A2 00 3D C7 29 FF 1F 01 CB Wed 12/30/2015 09:14:04 AM : [iNST-ACK ] 02 62 35.9E.1E 1F 2F 00 00 02 0F FF 08 A2 00 3D C7 29 FF 1F 01 CB 06 (00) Wed 12/30/2015 09:14:04 AM : [iNST-SRX ] 02 50 35.9E.1E 3D.C7.29 2F 2F 00 (00) Wed 12/30/2015 09:14:04 AM : [std-Direct Ack] 35.9E.1E-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Wed 12/30/2015 09:14:04 AM : [MNG-LNK-RSP ] 02 6F 40 E2 00 35 9E 1E 01 0E 43 15 Wed 12/30/2015 09:14:04 AM : [PLM ] Group 0 : Writing Controller Link matching [35 9E 1E 1 ] Link 0 : 0FF8 [A2003DC729FF1F01] Wed 12/30/2015 09:14:05 AM : [35 9E 1E 1 ] Link 1 : 0FF0 [E2013DC729010001] Writing [E2013DC729010001] Wed 12/30/2015 09:14:05 AM : [iNST-TX-I2CS] 02 62 35 9E 1E 1F 2F 00 00 02 0F F7 08 E2 01 3D C7 29 01 00 01 AF Wed 12/30/2015 09:14:05 AM : [iNST-ACK ] 02 62 35.9E.1E 1F 2F 00 00 02 0F F7 08 E2 01 3D C7 29 01 00 01 AF 06 (00) Wed 12/30/2015 09:14:05 AM : [iNST-SRX ] 02 50 35.9E.1E 3D.C7.29 2F 2F 00 (00) Wed 12/30/2015 09:14:05 AM : [std-Direct Ack] 35.9E.1E-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Wed 12/30/2015 09:14:06 AM : [MNG-LNK-RSP ] 02 6F 41 A2 01 35 9E 1E 01 0E 43 06 Wed 12/30/2015 09:14:06 AM : [PLM ] Group 1 : Writing Responder Link matching [35 9E 1E 1 ] Link 1 : 0FF0 [E2013DC729010001] Wed 12/30/2015 09:14:06 AM : [35 9E 1E 1 ] Link 2 : 0FE8 [0000000000000000] Writing [00..............] Wed 12/30/2015 09:14:06 AM : [iNST-TX-I2CS] 02 62 35 9E 1E 1F 2F 00 00 02 0F EF 08 00 00 00 00 00 00 00 00 C9 Wed 12/30/2015 09:14:06 AM : [iNST-ACK ] 02 62 35.9E.1E 1F 2F 00 00 02 0F EF 08 00 00 00 00 00 00 00 00 C9 06 (00) Wed 12/30/2015 09:14:06 AM : [iNST-SRX ] 02 50 35.9E.1E 3D.C7.29 2F 2F 00 (00) Wed 12/30/2015 09:14:06 AM : [std-Direct Ack] 35.9E.1E-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Wed 12/30/2015 09:14:06 AM : [35 9E 1E 1 ] Link 3 : 0FE0 : Writing High Water Byte Wed 12/30/2015 09:14:06 AM : [iNST-TX-I2CS] 02 62 35 9E 1E 1F 2F 00 00 00 0F E7 01 00 00 00 00 00 00 00 00 DA Wed 12/30/2015 09:14:07 AM : [iNST-ACK ] 02 62 35.9E.1E 1F 2F 00 00 00 0F E7 01 00 00 00 00 00 00 00 00 DA 06 (00) Wed 12/30/2015 09:14:07 AM : [iNST-SRX ] 02 50 35.9E.1E 3D.C7.29 2F 2F 00 (00) Wed 12/30/2015 09:14:07 AM : [std-Direct Ack] 35.9E.1E-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Wed 12/30/2015 09:14:07 AM : [iNST-ERX ] 02 51 35 9E 1E 3D C7 29 15 2F 00 01 01 0F E7 00 00 00 00 00 00 00 00 00 D9 Wed 12/30/2015 09:14:07 AM : [Ext-Direct ] 35.9E.1E-->ISY/PLM Group=0, Max Hops=1, Hops Left=1 Wed 12/30/2015 09:14:07 AM : [iNST-TX-I2CS] 02 62 35 9E 1E 1F 2F 00 00 00 0F E7 01 00 00 00 00 00 00 00 00 DA Wed 12/30/2015 09:14:07 AM : [iNST-ACK ] 02 62 35.9E.1E 1F 2F 00 00 00 0F E7 01 00 00 00 00 00 00 00 00 DA 06 (00) Wed 12/30/2015 09:14:08 AM : [iNST-SRX ] 02 50 35.9E.1E 3D.C7.29 2F 2F 00 (00) Wed 12/30/2015 09:14:08 AM : [std-Direct Ack] 35.9E.1E-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Wed 12/30/2015 09:14:08 AM : [iNST-ERX ] 02 51 35 9E 1E 3D C7 29 15 2F 00 01 01 0F E7 00 00 00 00 00 00 00 00 00 D9 Wed 12/30/2015 09:14:08 AM : [Ext-Direct ] 35.9E.1E-->ISY/PLM Group=0, Max Hops=1, Hops Left=1 Wed 12/30/2015 09:14:08 AM : [iNST-TX-I2CS] 02 62 35 9E 1E 1F 2F 00 00 02 0F E7 08 00 00 00 00 00 00 00 00 D1 Wed 12/30/2015 09:14:08 AM : [iNST-ACK ] 02 62 35.9E.1E 1F 2F 00 00 02 0F E7 08 00 00 00 00 00 00 00 00 D1 06 (00) Wed 12/30/2015 09:14:09 AM : [iNST-SRX ] 02 50 35.9E.1E 3D.C7.29 2F 2F 00 (00) Wed 12/30/2015 09:14:09 AM : [std-Direct Ack] 35.9E.1E-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Wed 12/30/2015 09:14:09 AM : [All ] Writing 0 bytes to devices Wed 12/30/2015 09:14:56 AM : [All ] Writing 0 bytes to devices

Firmware and UI version: Insteon_UD994 v.4.3.26 (2015-10-13-11:35:11) Product: ISY 994i (1120) - OpenADR (21010) -A10/X10 for INSTEON (21060)

Well, I installed a phase coupler thinking that would help with my Insteon woes. It has not, though it did improve my X10 - I can now control an X10 lamp module from an old X10 RF transmitter that didn't work before. So it would appear the coupler is helping something. First, I started with no Insteon devices defined in my ISY. I then did the following: Unplugged the ISY and PLM Unplugged the serial line from the PLM Did a factory reset on the PLM: While holding the link button in on the PLM, I plugged it in - it beeped constantly for about 5 - 10 seconds and stopped, beeped once and then I released the link button. Plugged in the serial line between the PLM and ISY Plugged in the ISY From the admin console, selected Link Management -> Start Linking Took a brand new Lamp Linc dimmer module out of the box and plugged it in to my lamp, and then into the wall - the light came on. Pressed and held the link button for about 5 seconds. It showed up in the list of devices to add (see attachment 1) I clicked Finish. Waited about 10 seconds and got the message "The following devices could not be added. 35.9E.1E LampLinc. Cannot determine Insteon engine". (See attachment 2) It seems the communication is working because the ISY sees the LampLinc when I press the link button. But when I click Finish, I get the error. I *must* be doing something wrong. I can't believe 4 lamplinc modules are bad. Again - and I can't stress this enough - all of my X10 devices work fine throughout my 3800 square foot home. I cannot get Insteon to work.

Wow. Your setup is way bigger than mine! Thanks for your help LeeG. I'll post back here with my results, once I get everything setup.

Thanks for your response. After re-reading the section in the ISY manual about scenes and cross-linking, I think it makes sense to setup a virtual 3-way switch using a scene. I have no idea what group number gets assigned or how that all works, but I'll just follow the instructions and hope for the best. I guess if I setup a program to turn that light on, the program will have an action that says "turn on Scene xxx". Likewise for off. As far as the rest of my devices such as lamp linc modules, which will be run by programs, making them part of a scene just doesn't make sense. My program will say "If time is 'sunset', turn on lamp linc module A". Don't see where a scene is going to help.