LeeG

Glad to hear it is working. Is the device a SwitchLinc Dimmer or an InLineLinc Dimmer? Also go to Help | About an be sure there are two lines displayed Firmware: and UI (just below the firmware line) and they both say 3.1.17.

To use Auto Discover the InLineLinc has to be Deleted from the ISY and added back either using Start Linking or New INSTEON Device using Auto Discover. It will show the InLineLinc firmware level but will not change anything functionally from what you have now. The InLineLinc without Sense is a Responder Only device. It does not have Controller capability so turning the InLineLinc on manually with the On/Off buttons on the InLineLinc does not signal that change to any other device. Thus neither the ISY nor the KeypadLinc will know the InLineLinc has changed state. In Insteon turning an individual device On/Off (such as through the Admin Console) controls only that individual device. For the KeypadLinc to be aware of changes to the InLineLinc it is necessary to turn the Scene On or Off. That will turn the KeypadLinc button LED On/Off as well as the InLineLinc itself.

The KeypadLinc button is added to the ISY Scene as a Controller. The ISY assumes the Controller is also a Responder. The InLineLinc was added to the ISY by specifying an actual Device Type. This is why the firmware says v.00. It was added as an InLineLinc without sense which is why it cannot be added to the Scene as a Controller. Does the InLineLinc actually have w/sense? Why was Auto Discover not used when adding the InLineLinc to the ISY? How are the floods being turned On when the KeypadLinc button B does not indicate they are On?

A single Line (Yellow) from one breaker goes to multiple locations. These locations use different neutral runs back to the power panel.

The White neutral wire is running to all the same locations as the Black Line (or was that yellow) is running to from the single breaker?

There was a link record left behind when the Scene was deleted. Most likely the RemoteLinc since it had to be put into linking mode by pressing the Dim/Bright buttons. You can do a Show Device Links Table for the RemoteLinc and the OutletLinc. That should show which has the erroneous link record. Factory reset the device with the erroneous link and then do a Restore Device to have the ISY restore the link records that should be in the particular device. e.

The ISY will pick up support for this in a future Beta image. The last beta was 3.1.17 which is now the latest official release. Going on past history a new Beta stream will be started.

Unfortunately that is true. My latest is v.36 which does not have the feature.

Thanks Tom. That will sure simplify Secondary button LED management. I checked a v.36 KPL which does not support that feature. Looks like that support came with v.38. JoeC What is the KeypadLinc firmware level of your KPL. Lee

3.1.17 does not allow a Secondary button On Level to be changed. How public was SmartLabs in announcing this new capability in advance of its being available to the field?

Tom That would be good news. You are referring to the Secondary buttons, not the primary load control button(s). Do you know the KeypadLinc firmware Lee

In Momentary A mode the I/O Linc Relay responds to only one command, either Scene ON or Scene OFF. The Scene Responder On Level for the I/O Linc Relay (0% or 100%) dictates which command, Scene ON or Scene OFF, the Relay responds to. Remember that the Responder On Level can be different when the KeypadLinc button is the Controller versus when the Scene name is turned On/Off where the ISY PLM is the Controller.

Sorry, I don't understand question. When the ISY sends a Scene On the KeypadLinc button LED will turn On. What the I/O Linc Relay does depends on which Momentary Mode is being used and perhaps whether the door is open or closed. When the ISY sends a Scene Off the KeypadLinc button LED will turn Off. Again, what the I/O Linc Relay does depends on which Momentary Mode is being used and perhaps whether the door is open or closed. With some information on how the I/O Linc is set up, including is the I/O Linc Sensor On when the door is open or On when the door is closed, how the I/O Linc Relay responds can be answered. Also the I/O Linc User Guide covers the three Momentary Modes, A,B,C, and how the I/O Linc Relay responds to On and Off Scene commands in each Momentary Mode.

JoeC You are correct that setting the On Level to 0% will turn the Responder Off when sending a Scene On. However, as I stated before, the KeypadLinc firmware does not support that option for Secondary buttons. Has been that way since Insteon started many years ago. It is necessary to assign the Secondary KeypadLinc button as a Responder in a Scene and turn the Scene Off. Perhaps in the future SmartLabs will change the way Secondary KeypadLinc buttons respond. Until then using a Scene and turning the Scene Off is the only option. Lee

The Event Viewer is not changing the flow of messages. From the previous post there were multiple X10 message events ... X10 I All Lights On (5) Tue 2012/01/31 06:42:21 PM System Log X10 I All Lights On (5) Tue 2012/01/31 06:42:21 PM System Log X10 I All Lights On (5) Tue 2012/01/31 06:42:19 PM System Log X10 I All Lights On (5) Tue 2012/01/31 06:42:18 PM System Log Note the differences in the timestamps of the X10 events. The previous suggestion about moving the Wait before the Notify will likely resolve the multiple Notify Actions. The Program is being triggered from each X10 message but would not be sending the Notify immediately because of the Wait. Only the last X10 message will result in the Notify. There is still the open question as to why the alarm panel is sending multiple All Lights On messages. Question for the alarm panel company. I suspect that is normal because of the inherent unreliability of X10. They want to be sure the lights turn On so multiple On requests are sent.

stillen_i30 Some of the issues appear to be unrelated to Programs. For 2., where the Main door does not work and the Small door does, check the Sensor Current State column in the Admin Console before the Main door is opened and after. Does the state change from Off to On when the Main door is opened? For number 5., where not all devices respond to the Scene Fast Off, run a Scene Test on each of the Scenes. Right click on the Scene name, select Diagnostic | Scene Test. Do not overlap the tests. Let the results of the first test display before running the test on the next Scene. Do all the devices show “Succeeded� Both of these suggest communications problems rather than Program problems. If not on 3.1.17 I suggest updating. It is now the latest official release. Lee

Install another KeypadLinc at that location. Just kidding. I'm pretty sure that would be damaged as well. If the basic wiring is correct then you are looking for a connection problem. Normally a connection problem will just cause a loss of power rather than damaging of device. That is why I tend to think there is an underlying wiring issue.

Yes they do. There is a difference in load balance being tied together at the power panel versus being tied together in the box. Since there is no load involved and two KeypadLincs have been damaged it has to be source power related.

Also Line (Black) feeds from different circuit breakers should not share the same neutral (White).

Add the SwitchLinc Dimmer by selecting the specific Device Type 2478D in New INSTEON Device. That should allow the dim level to be set.

The Motion Senser Status will never be Off if the Motion Sensor is sending only On commands. If Status 'Garage Interior / Motion-Sensor' is Off

For each circuit breaker there is a White (neutral) and Black (Line). Only Whites for the same circuit breaker should ever be tied together. I would check that the wires the KeypadLinc are connected to actually belong to the same circuit breaker. I’m guessing the White and Black the KeypadLinc is connected to do not belong to the same circuit breaker circuit.

The KeypadLinc button should add to the Scene as a Responder but a Secondary KeypadLinc button cannot be turned Off with a Scene On. The Night Mode button, is that issuing an Off command? If so an Off command cannot turn On a device.

First guess would be the neutral and load powering that KeypadLinc do not belong to each other.

What is/was the KeypadLInc dimmer connected to? Sounds like the load took out both KeypadLincs.