LeeG

Regarding the Fan speed, it sounds like the pull chain is not set for the fastest speed. The FanLinc Fan control assumes the fan is set to run at its maximum speed with the FanLinc reducing the speed. If the Fan speed pull chain is set lower than maximum the Fan may not get enough power to actually turn the fan motor. EDIT: missed this the first time. When the other Scenes are turned Off you are turning the FanLinc Fan Off. The Responder Fan On Level slider applies only when the Scene is turned On. When the Scene is turned Off the Fan is turned Off.

ubuntulinuxuser If a Mac the download unzips the file which makes it invalid to install on the ISY. There is an option to download without the unzip. If windows it is likely a firewall or AV problem. Is Avast or Kaspersky being used?

Take a look at the 2477SA1 Load Controller.

First try a Restore Device for the 2nd Floor device. The mismatch means the device has a link record at a particular link record address that does not match what the ISY thinks should be there. A Restore Device will direct the ISY to rebuild the 2nd Floor device link database. Then do another Show Device Links Table for the 2nd Floor device to see if any link record remains for the problem KeypadLinc. If not then the problem for that device should be resolved and the same approach can be used for the other device(s) as well. If there is still a link record for the problem KeypadLinc then the solution is to Delete the 2nd Floor device and add it back clean.

Assuming this is not the result of an ISY Program being triggered by the KeypadLinc ON/OFF buttons, the problem is the KeypadLinc was linked to the other devices at some point. Resetting the KeypadLinc only clears the link records in the KeypadLinc. The other devices still have link records pointing to the KeypadLinc. Define a Scene, add the KeypadLinc ON button as a Controller and one of the devices that is reacting that should not be as a Responder to the Scene. Then Remove the other device and the KeypadLinc from the Scene. If that stops the other device repeat the steps for each device that is responding that should not be.

The rewire is correct. The Smarthome diagram that shows the Red KeypadLinc wire going to the load is correct. The load could be a light, with a relay KeypadLinc the load could be a fan. The red wire from one Insteon switch never powers another Insteon device as a load because all wired Insteon devices require unswitched 120v AC. They are all basically electronic devices which must have power at all times to function. Once the wiring change is made the FanLinc should have the 2 LEDs On unless the option was selected to turn the LEDs Off. It should now be possible to link the KeypadLinc buttons to the appropriate FanLinc nodes.

"Black from ceiling fan electrical box (connected to KPL Red wire); White (pig-tailed with Neutral wires including KPL); and ground." I stopped reading when I got to this point. Nothing should be connected to the KeypadLinc Red load wire. The KeypadLinc ON/Off buttons will control the FanLinc Light node by linking the KeypadLinc ON button as a Controller with the FanLinc Light node as a Responder. By connecting the black wire going to the fan fixture to the KeypadLinc Red wire, the KeypadLinc load control circuitry must be On (ON button On) for the FanLinc to receive power. The FanLinc must receive unswitched 120v AC. The FanLinc is like an InLineLinc in that they both must be powered by unswitched 120V AC. The FanLinc nodes for the Light and for the Fan are controlled as Responders by other Controller devices being linked to them. In this case I think you plan to use the KeypadLinc ON/Off buttons to control the FanLinc Light. This is accomplished with links, not direct wiring. The fan wiring diagrams are depicting normal electrical switches. Not an electronic FanLinc.

Some basic things to verify. Run Help | About and insure Firmware and UI lines both show 3.2.6. Confirm the FanLinc was added to the ISY under 3.2.6. The state of the KeypadLinc ON button should have no affect on the ISY linking of the KeypadLinc or the FanLinc. That fact that it does indicates a wiring issue. Sounds like the KeypadLinc load red wire is controlling power to the FanLinc device. The FanLinc must have unswitched 120v AC at all times, not affected by any KeypadLinc button. Do the FanLinc LEDs cycle On and Off as the KeypadLinc ON/OFF buttons are cycled?

The FanLinc will work with any of the KeypadLincs. Likely the FanLinc is an I2CS device which requires 3.2.6 for I2CS support. The FanLinc has to be added to the ISY under 3.2.6.

iostream212 Perhaps some additional detail would be useful. Is it limited to time driven programs, device event driven programs. Are the Last Run Times updated but no function performed. Could the PLM be hung up such that device related actions by programs do not occur. Is manual control of devices through the admin console still possible. What happens if a program is started manually through the admin console. Knowing more of the specifics could help someone provide a direction for analysis. biredale Since I have no idea what the OP is describing I have even less information as to what "Same" means. If you can provide additional detail it would be very helpful. For both, knowing what ISY firmware is being used would be useful.

From the KeypadLinc User Guide Buttons can be set to Beep Mode so KeypadLinc will beep every time a button is used. (Default = Off) If KeypadLinc in 6-Button Configuration Simultaneously tap the B and C buttons KeypadLinc will beep Keypad’s Beeper will toggle to on (if was off) or off (if it was on) If KeypadLinc in 8-Button Configuration Simultaneously tap the D and E buttons KeypadLinc will beep Keypad’s Beeper will toggle to on (if was off) or off (if it was on)

I suggest opening a ticket for UDI support.

What URL are you using to bring up the Admin Console on 2.18.16? You may be invoking 3.2.6 Admin Console now that it is the latest official release. Click Help | About and see what it shows for Firmware and UI levels.

Welcome to the world of ISY. The File | ISY Backup should have displayed a popup window requesting the subdirectory where the backup should be written. What OS is being used? What level Java is installed?

Sure. For a 6 button KeypadLinc there are five ISY nodes defined in the My Lighting tree. The first node represents the ON/OFF buttons. The ON/OFF buttons use the same Group number (01) so they are represented by one node. The ON button sends an On command for Group 01. The OFF button sends an Off command for Group 1. Each of the 4 Secondary KeypadLinc buttons has a unique ISY node. This means that for a six button KeypadLinc there are 5 nodes in the My Lighting tree. Only the ISY node representing the ON/OFF buttons has the Replace with ... option. This node represents the complete KeypadLinc for things like Replace with... and Delete as the activity applies to the entire KeypadLinc.

jwagner010 It is necessary to get the correct Insteon Engine value only once and only on some devices. There should be no need to do that again once established on 3.2.6.

robandcathy When Start Linking was clicked did a popup come up with a Finish button at the bottom? Also does Help | About show 3.2.6 or Firmware and UI?

"Is there a way to isolate button 1 from the function of turning on the locally connected load?" No.

CTBigman Just a thought, be sure you right click on the KeypadLinc primary load control node. That node has the Replace with ... option. Secondary KeypadLinc button nodes do not have the Replace with option as an individual button cannot be replaced.

You can use your existing PLM with the 994i. I did that when moving to a 994. Could have done a Restore Modem (PLM) to the new PLM as well. Take a backup of the 99i and restore to the new 994i. I suggest getting the 99i to the latest official release 3.2.6 before taking the backup. Send an email to sales@universal-devices.com with the UUID of the 99i and the new 994i. They can transfer the X10 module to the new 994i.

For whatever it is worth the 01 19 40 is for a SwitchLinc Dimmer with firmware v.40.

I would have expected a Restore Modem (PLM) to have cleared any old information. Are the link records with the non-existing addresses active (E2 or A2).

Add the KeypadLinc with the Auto Discover option. That way the KeypadLinc firmware level will be listed and there should be 8 nodes when the device add completes.

Are you pressing the air gap switch only flush with the frame and not pushing it into its active position below the level of the frame while holding the Main and H buttons pressed.

ELA The Show PLM Links Table is susceptible to Insteon traffic reaching the PLM adversely affecting the count. The internal NEXT pointer in the PLM used to sequentially read the link records is altered by Insteon traffic reaching the PLM that requires the PLM to search its link database. Causes link records to be skipped (low count) or the same records to be read multiple times (high count). It is necessary to run Show PLM Links Table multiple times with Count to verify a specific count can be reproduced which is usually accurate. The PLM does not compress the link database as records are deleted and added. It would be common to have Insteon addresses which are no longer in the system. A Restore Modem (PLM) will effectively compress the PLM link database as the database is reset and only active records written back.