Brian H

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.

Is this the original 2440 RemoteLinc or the one of the latest RemoteLinc2 models? If it is a any model RemoteLinc2. Try holding the SET button until it beeps. Then add it to your ISY setup. When added. All the buttons will show up as nodes. Then you can make individual scenes from within the Administrative Console. It does sound like you are trying to follow the linking information in the manuals. As Teken thought. Manual linking information is not used when an ISY interface is being used.

Strange things happen when the PLM is dead or on its way out. Sometimes power cycling it may make it work for a short additional time. Another symptom of PLM failure is its Link Database is almost completely empty. There is a 13 page thread here on the PLM failures and how some of us have repaired them.. http://forum.universal-devices.com/topic/13866-repair-of-2413s-plm-when-the-power-supply-fails/

Is a common issue with the 2440 RemoteLinc and the latest 2413S PLM's. Try getting it as far away from the PLM as possible. So it has to go through a different Dual Band Module and can't use RF directly to the PLM. That is how I had to do mine. At the other end of the house. So the PLM was using a power line signal to the far away Dual Band Module and it did the RF communications to the 2440 in the linking mode.

I did not see the 2475DA2 (Insteon Category 01, Sub Category 25) 10V Ballast Dimmer in the drop down list of modules in (RC2) 4.5.3 Firmware. I don't use the 5.0.? Alpha firmware so it may or may not be in it. From the FCC Database The module has the small RF Daughter Board in it. With the pig tail antenna. If the module is mounted inside a metal fixture. I doubt Insteon RF would reach it reliably.

You are still going to need a PLM. As it will be needed to send the Insteon RF commands along with Insteon power line commands. Maybe a small 277 volt to 120 volt step down transformer can power it. Even if the transformer doesn't pass the power line signals correctly.

Did you wake them up before trying the restore? One thing we have found out. The 2413S PLM may not restore the old 2440 RemoteLinc if it is close to it. Move the 2440 Remotelinc as far away from the 2413S as you can. So another Dual Band device is processing the RF to and from the 2440 RemoteLinc and is sending the commands over the power lines to the 2413S. I had to move mine to the other end of the house. Where an Access Point handled the RF to and from the 2440 RemoteLinc. Mine failed completely when next to the 2413S PLM.

Are you trying to use the Administrative Console or the Dashboard. Both are available for the firmware you downloaded. The Administrative Console is where you do what you want to do. Did you clear the Java Cache after the update?