LeeG

Does sound like it could be 120V on the trigger wire. Certainly worth checking with a meter. Most detectors that connect to a security panel will be switching 12V DC but these could be switching 120V AC. Do you have a manufacturer and model number? Often information can be found with google search.

The InLineLinc w/sense is expecting a 120V swing. I doubt the smoke detectors are controlling 120v AC.

If simple On/Off is all that is needed (not some form of balanced resistance) the I/O Linc Relay contacts should work. If more than one location will be controlled then one of the Simplehomenet devices that have multiple relays in the same device (EZIO4O has 4 relays as one example). There is also an IP controlled card that has relays which can be controlled through the Network Module. I have not used that card but there are several posts on this forum about it. Search for WebControl.

Try unplugging the PLM for 60 seconds first. Adding the KeypadLinc would have written the link records in the KeypadLinc and the PLM. I am beginning to have concerns over the PLM itself. If the power cycle does not work restoring the 2.8.16 backup taken before going to 3.1.10. Then a Restore Modem (PLM). After that at least one of the KeypadLincs will have to be added again because it was not in the system at 2.8.16.

If the link records match at the device then either some PLM link records are missing or the device has an issue on the powerline. The fastest solution to missing PLM links is to Delete the device and add it back to the ISY. This will establish the PLM links during the device add.

You bet. Common misunderstanding about If Control versus If Status.

An Insteon Scene alone cannot produce those results. Normally it is an ISY Program that is performing an Action along with the Scene activation causing the results you are seeing. In this case it must be something in the ELK that is turning the lights on full before the Scene is dimming them down.

timlacey Right click on the primary KeypadLinc node in the My Lighting tree, select Diagnostics | Show Device Links Table. When the display is complete click on the Compare button along the bottom of the display. After a few seconds an additional list of the link records are displayed with some designation at the beginning of each link record indicating "Identical" or "Mismatch". Lee

CJVann The Program will never run the Else clause. An If Control 'xxxxx' is switched On triggers the Program only when an On command is received from the device and the evaluation will always be True as coded. Use If Status rather than If Control. If Status triggers the Program anytime the Status changes. When the Status change results in a True evaluation of the If the Then clause runs. When the Status change results in a False evaluation of the If the Else clause run. If the Program should trigger whenever a command flows even when the Status does not change (pressing the On paddle twice for example) add an And Control ‘xxxxx’ is not switched Off to the existing If. The Program will trigger with an On command and an Off command. The If will be False with an Off command and run the Else clause. Lee

When the KeypadLinc button Movie is pressed and issues an ON (the button is not in non-toggle mode) all the responders turn on to full bright and then ramp down to full Off? Disable all Programs and repeat. Run Tools | Diagnostics | Event Viewer with Device communications events selected (most important). Press KeypadLinc Movie button and post Event log. Can you take a screen capture of the Responders On Level and Ramp Rate when the Movie button below the Scene name has been selected.

elvisimprsntr It sounds like the Scene name has been selected and the Responder On Level and Ramp Rate set there. Each Controller of a Scene has a unique set of On Level and Ramp Rates for each Responder. Click on the KeypadLinc button name below the Scene name. The Responder On Level and Ramp Rate values now displayed are associated when that KeypadLinc button is pressed. Clicking the Scene name sets the Responder values for when the Scene name is used in a Program such as a Set Scene. The ISY PLM is the Controller in that situation. Lee

polexian Using Programs | Summary tab, right click on the specific Program and select Disable Run at Startup.

That backup will not be of any use. All references to the ISY PLM were removed when doing Delete Modem (PLM). As an FYI all Insteon wired devices, Smarthome and Simplehomenet, have PLMs internal to each device. The SHN devices are built on top of a PLM shell with an SHN daughter card that fits inside the basic pluggable PLM shell. The only difference with the EZIO8SA is the scope of the function of an EZIO8SA is too large to fit on a conventional daughter card plus there are too many external connections. So the EZIO8SA is connected to an external PLM rather than an internal PLM. The ISY does not look at wired Smarthome or Simplehomenet devices as PLMs even though every device has one. All ISY references to Delete PLM and Restore PLM refer to the PLM physically connected to the ISY.

The Delete PLM function removes all references to the PLM. It is meant to be used by professional installers who use the ISY/PLM to configure an Insteon installation and wants to remove the ISY/PM totally when all Insteon device have been configured. Two solutions. Restore a backup taken before the ISY PLM was removed. Restore Modem (PLM). Or delete all devices and Scenes and rebuild from scratch.

"No joy. Factory reset, restore PLM still fails at 1%. I emailed you the event log. Could it be a bug in 3.1.12?" I doubt it. There is Insteon traffic coming into the PLM during the Restore. That should not happen. It screws up the PLM internal Next pointer. "Lee, I remember a while ago I deleted the PLM, thinking it was a bad EZIO PLM." The ISY PLM was Deleted?

There is no harm in that. Do not factory reset the ISY.

The PLM link database is/was lost. That is common to all the devices not reflecting state changes. Suggest power cycling the PLM and see if that allows a successful Restore PLM.

Do any Insteon devices show a state change? I'm thinking the PLM lost its link records for all the KeypadLincs not to show state changes. The PLM can be rebuilt using the File | Restore Modem (PLM). "So if I just push button "B", and it lights up, even though it has no assigned function, the admin console should show current state "on" vs. "off"?" Yes. The ISY creates links between all Controller nodes and the PLM when each device is added to the ISY.

starmanj The KeypadLinc button does not need to be linked to anything (except what the ISY established when the KeypadLinc was added to the ISY). If the KeypadLinc button does not change state under the Admin Console some links could have been lost in the KeypadLinc, lost in the PLM or the KPL is out of range of the ISY PLM (not likely if the device added to the ISY without errors). Is it all the KPL buttons fail to show a state change or only a single button? Lee

frustratednon-geek SmartLabs has a Pro line of Insteon devices that are available only to a Professional Insteon Installer. Perhaps a Pro installer will have access to a dimmer with higher capacity. Would take the project out of the DIY category. Lee

The error messages at the startup of 3.1.12 Admin Console are known problems that will be fixed with 3.1.13. I think the ELK module has to be installed after upgrading to 3.1.12. Also check the Admin Console Help | About and verify the firmware and UI levels both indicate 3.1.12.

Wuench I think there may be another problem. From Sunrise (current day) to Sunset (next day) spans time over two days. Perhaps the To Sunset should not be (next day)? And From Sunrise To Sunset (next day) Lee

FYI - for those that have observed the odd button numbering of the RemoteLinc2, the device does in fact use a different Button to Group number assignment from any other multiple button device. For all other multiple button devices the first button uses Group 1, second button uses Group 2, third button uses Group 3, and so on. For some reason an RL2 button A uses Group 2 and button B uses Group 1. Just the opposite of what one would expect. This was noted in an earlier post. That is why the ISY nodes appear to be numbered wrong when in fact it is the RL2 that is reversed for each group of horizontal buttons. Not likely SmartLabs will ever change this as it would create an incompatibility between new and old

BigRed76 You will need 3.1.10 or higher to support the RL2. The RL2 uses I2 linking so the use of the RemoteLinc device type will not work. Lee

boots If the PLM Factory Reset was actually successful then a Restore Modem (PLM) must be done to restore the link records in the PLM. Otherwise the ISY will not see device status changes and Scenes will not work. Sometimes the power cycle alone resolves the PLM issue and a Factory Reset is not actually successful. Lee