Brian H

Your problem is you can't link the RemoteLinc to your ISY994i controller but directly manually linked to your Insteon Switches will control them?

They do have a 4 piece multi-pack Insteon On/Off modules. http://www.smarthome.com/insteon-remote-control-plug-in-on-off-module-1.html

The earlier firmware always added my 2440 as a v.00. The latest firmware now finds mine as v.33 My 2440s also don't always play nice with the latest Insteon devices. It will not manually link to my Alert Modules as the ISY994i firmware doesn't support it yet. It also will not link to the latest hardware 2413S PLM unless as far away from the PLM as it can be.

I don't see your LED pattern in the WIKI page but you may want to look at it for hints. http://wiki.universal-devices.com/index.php?title=Main_Page#Front_Panel_LEDs.2FLights You may want to power down the system and reseat the SD Card. Though I would also suspect any 2413S PLM hardware version below 2.0 and over two years old a highly suspect. It could be possible the ISY994i is trying to do something with the PLM and it is crashing.

Some of the latest versions of Insteon Modules. Do have a option to have power line or RF communications turned off. As Paul pointed out. Filtering the PLM would disable its power line communications. The rest of the dual band modules will still use RF and power line. Unless new enough to habe the power line communications disabled. I tried a fairly inexpensive RF spectrum analyzer on my system. Was not overly informative. As there where all kinds of RF signals being bounced from dual band to dual band modules.

New one recently purchased, hardware above 2.0 or a new spare you had in storage that is below hardware 2.0?

You may want to try {if fairly easy} moving the EZIO 2x4 closer to the ISY994i's PLM and see if you can restore it or manually short the Input you are using and see if it registers in the programs. I have not seen anything on repairing the older 2412 PLM's or the base board. The schematic in the Modem Developers Guide {was public access for awhile from Smarthome} shows three electrolytic capacitors. C1 1000uF/25V, C5 100uF/6.3V and C8 470uF/50V C1 and C8 are the two with long leads bent parallel to the PC Board probably held by glue. The 74551 kit is a 2450 I/O Linc with a magnetic switch. A 30 foot and 10 foot piece of #22 wire. If your EZIO 2x4 is using a dry contact switch. You could just use a 2450 I/O Linc Sensor Input wired to the original switch the EZIO 2x4 was using. If you are also using one of its outputs. The I/O Linc has one relay output

Yes the Smartenit modules are built on a base Insteon PLM they purchase from Smartlabs. They add their custom daughter board in place of the Serial or USB in a standard PLM. The Smarthome PowerLinc III Rev B. Sounds like the one from the 2412 PLM. If it has a large power transformer it is definitely one from a 2412 PLM. The 2412 type main board is NOT subject to the same capacitor failures found in the 2413 PLMs. I know the Date Code format was different at times. How old is the device? Firmware 52 sounds like an early 2412 PLM version.

I would also suspect the PLM. if it is over two years old and is a 2413S. The EZIO-2x4 uses a Base 2412 or 2413 PLM from Smartlabs and a custom daughter board. So it could be possible the module has failed. Especially if built on the base 2413 board.

I suspect the power supply in the KPL is going bad. From the strange symptoms you are having. Though doing a power cycle reset. By pulling out the Set Button out. Wait maybe fifteen seconds. Then pushing it back to its normal position. The factory reset and then a restore of the KPL would see if anything changed. You should not have to do all the scenes and programs again. If you factory reset it and then restore it.

I would suspect the Fanlinc. You may want to read this fairly long thread on the Fanlinc. http://forum.universal-devices.com/topic/19738-fanlinc-damaged-8-damaged-in-total/ V1.9 was listed in the hardware revision range. Reported to have issues with symptoms similar to what you are reporting.

The hardware version 2.0 and above. Have 100uF capacitors in C7 and C13 position in place of the original 10uF ones. My 2.1 has the same questionable brand capacitors in it that where in all the versions earlier versions. We are now getting close to the two year mark for some of the above 2.0 models. We may now start getting a better idea on their useful life over the original useful life the earlier ones.

Battery operated modules go into a power saving mode. You can't query them as they will not respond. How old is your PLM? You can put one of them in the programming mode. Then do a Show device Link Table. Then do a compare to what the ISY knows that should be there.

I believe there is another thread here. Where reason 9 was the device did not provide its starting Link Database address. I do see some responses from the sensor in the starting post. So it must be communicating with the problem network. At least somewhat.

Not too common but we have seen DOA or very short in time use 2413S PLM failures reported.

Few tips many of us do. Write down the model number, six digit Insteon ID, where located. So you don't have to dig module out of hard to access areas if you need the information later. I also write down the date code and reported firmware version from the Administrative Console list of modules. Also do a Factory Reset on all new module being installed. Some module have been received with QC test links in them that where not cleared out before being sold. Older firmware modules that also could do optional X10 addresses. Have been seen with X10 addresses in them also from the factory.

No you can't. Maybe you could make a test power cord and power them up on a test setup. Add them and mark them where you intend to install them at the site.

Another possibility is some of the options are not supported by the RemoteLinc model you have. I have a few modules where some Options are listed for it but not supported. When I try to use the option. Either nothing happens or I get a warning indicating the Option is not supported in the module in question.

If the power cycle reset or Restore Device don't fix the blinking and surging. The power spike that damaged the GFCI device may have also damaged the modules controlling the LED's.

Page 7 of this manual may give you added information. http://cache.insteon.com/documentation/2342-x22-en.pdf

I have the Pro version ISY994i and have automatic writes to battery devices turned off. You should have gotten a message telling you to hold the Bright and Dim buttons when you tried to do the write updates. I found a few times where the message is not shown if the Writes to Battery Devices is turned off. So if you have a Pro version and had Automatic Writes to Battery Devices Off. You may have missed that step.

One point. Battery operated Insteon Modules are in a power saving mode and their state of On or Off may not be found until they send a signal.

1) I have used your method of finding a six digit ID myself. On things like original 2440 RemoteLinc and Controllinc. That the Start Linking method does not work. I have also used the Start Linking method with other type modules and then it found the ID when added.

I just tried again and got the same results. Near the PLM. Far away it did add fine. One thing I did see. If you have the Pro version. If the Automatic Writes to battery devices is disabled. Some of the hold bright and dim buttons messages did not appear. I had mine off and it added it to the Administrative Console but has write pending Icons next to all the buttons.

Bright and Dim Buttons as pointed out. One thing we have seen here. The older 2440 RemoteLinc does not add into the Administrative Console with the latest version of the 2413S PLM. If it is near enough to the PLM to be using Insteon RF commands. Try moving the Remotelinc as far away from the PLM as possible. Allowing a different Dual Band Module to handle the Insteon RF and pass it on by power line to the PLM. I had to go to the other end of my home and use a Range Extender in my case to process the adding a 2440 it to the Administrative Console.