LeeG

Harry Is this one of the new 2475SDB Dual Band InLine Linc Relay devices? What is the device type shown by the Admin Console? Lee

Harry When a KeypadLinc button is pressed the KeypadLinc is the Controller and whatever devices have been linked to the Scene are Responders and react to the button press. Insteon commands flow from the KeypadLinc to the Responders and back to the KeypadLinc. When a Scene is used from the Admin Console the ISY PLM is the Controller and the same Responder devices (and any other Controllers of the ISY Scene) react to the commands that flow from the ISY PLM to the Responders and back to the ISY PLM. Assuming the KeypadLinc button was added to the ISY Scene as a Controller (not a Responder) it should control the same Responder devices as controlling the Scene name from the Admin Console. Lee

How about something like this. I set the dimmer to a 30 second ramp rate for test purposes and set the Waits to the same increment. Each 30 seconds the light ramps up an additional 20% over the ramp time period. The maximum ramp time is now 8 minutes. Set the device ramp rate to 8 minutes, set the Wait time to 8 minutes and the light should ramp from Off presumably to full bright over a 40 minute period. If Time is 6:00:00AM Then Set 'ICON Dimmer 1' 20% Wait 30 seconds Set 'ICON Dimmer 1' 40% Wait 30 seconds Set 'ICON Dimmer 1' 60% Wait 30 seconds Set 'ICON Dimmer 1' 80% Wait 30 seconds Set 'ICON Dimmer 1' On Else - No Actions - (To add one, press 'Action')

Sorry for the slow response. To tell you the truth I took a nap! I do not use AVAST but there are a number of posts on this forum that describe possible solutions. Use the forum Search facility and look for AVAST.

The ISY needs access to the Internet. You do not need to be able to control the ISY from the Internet. When Purchase Modules is selected it displays a web based screen from the UDI site listing the available modules.

IIf the Start Linking popup does not appear there is likely a problem with the router or AV that is blocking the data the ISY is trying to push out to the Admin Console, AVAST is a common blocker, There are others, If the ISY cannot push the data out to the Admin Console it does not see the response from the PLM entering linking mode and the popup is not displayed. What AV are you using? EDIT: the blinking LED on the PLM indicates it entered linking mode. It times out on its own after 4 minutes (?). By that time the devices that were to be identified should have been done by that time. None of that can proceed until the issue with the popup not appearing is resolved.

That happens when Start Linking is initiated and not ended with the Finish button. NO interaction with any other ISY function should occur while in Start Linking. If Configuration tab can be accessed go there and click on Reboot in System section. If that is not an option power cycle the ISY.

I have not tested this but it should work. This assumes the I/O Linc Sensor is On when the door is Open which it should be using the wire combinations in the first post. You can confirm that by looking at the Green LED at the I/O Linc wire connections. The Green LED is On when the Sensor is On. If Time is Sunset And Status 'IO Linc1-Sensor' is On Then Set 'IO Linc1-Relay' On Else - No Actions - (To add one, press 'Action') There are examples on the Wiki that implement the single KPL button technique. I don't like idea so I don't jump into those questions.

Turn Off Relay follows Input. When the door starts to open the magnetic switch closes which turns on the I/O Linc Sensor which turns On the Relay (Relay follows input) which stops the door movement. Part of the door safety features.

The If Control variant reacts to commands as they are received from the device. The If Status variant reacts as the device state changes and it also allows for static state checks. In the following example of If Control anytime the RemoteLinc button 4 is pressed ON and it is between Sunrise and Sunset the Then clause will run. Only when the button is actually pressed and an ON command is sent will this Program trigger. If Control 'RemoteLinc-2 - 4' is switched On And From Sunrise To Sunrise (same day) Then - No Actions - (To add one, press 'Action') Else - No Actions - (To add one, press 'Action') In the following example of If Status when the device Status changes when the RemoteLinc button 4 is pressed ON and it is between Sunrise and Sunset the Program triggers, like the first example. One difference is the Then or Else clause can run depending on whether the state change makes the If True or False. An OFF button 4 press also triggers the Program because the state changed but the Else clause would run because the If is False with a state change to OFF. Also because Status is state based, the Program will also trigger at Sunrise and at Sunset if the state of the RemoteLinc button 4 is ON at those times. If Status 'RemoteLinc-2 - 4' is On And From Sunrise To Sunrise (same day) Then - No Actions - (To add one, press 'Action') Else - No Actions - (To add one, press 'Action') The results obtained are very different between the two examples. The Program is coded based on the results you want. You can get a trigger only when a button is pressed and you can trigger based on state. Just depends on the desired results. In some respects it is similar to the EZSrve Attribute Value where the state can be checked using FF (ON) or 00 (OFF) or 1104 for a button 4 On press Group command. Similar to the difference between If Status and If Control. The GUI in ISY is much more user friendly and does not require a knowledge of the numeric command numbers or On/Off Level values. I think you will be very happy with the ISY. The Wiki has a good explanation about the If Control and IF Status along with the other Program functions.

The ISY has If/Then/Else. If does not have If/Then/Else/If. Programs can be triggered by a specific command from a specific button (Control) or a change in state (Status). Either of these can be ANDed to only trigger during a particular time frame. Setting aside that If/Then/Else/If does not exist, a single button press (Control) triggers a Program when the button is pressed. It does not trigger a Program hours later although that can be programmed with ISY Programs it is not the default action of Control. The Status Action is based on device state. A Program can be triggered when Status changes with the Then or Else clause driven depending on whether the IF Status is True or False. I would disagree with the idea that Scenes should not be used to link device together. Linking devices together directly with Scene is the most normal use of Insteon. Going through an ISY Program introduces a small delay while the Program is invoked and it issues whatever Actions are appropriate. There are many very good uses for ISY Programs and they should be used but not to the exclusion of device to device direct control with Scenes.

EZSrve Areas will equate to ISY Folders. Devices and ISY Programs can be assigned to ISY Folders in whatever association you want. ISY Scenes link devices together just like an Insteon Scene. Multiple Insteon Scenes can be defined using one ISY Scene. Scenes can be controlled from ISY Programs using Actions. I should note that Scenes can be run from EZSrve Actions as well. Although apparently they are not being used that way they are presented in a similar fashion on the ISY. There is an ISY Program Action to control Insteon. Much of an ISY Action is defined using pulldowns. For an Insteon Action the devices and Scenes are listed and selected from a pulldown (like the EZSrve). Insteon Actions can be command based (Control) or device state (Status). There is no limit to the number of ISY Actions that can be defined in an ISY Program. ISY Programs can be triggered by Events (Insteon, ELK, X10, IR, Variables, and others) using the Condition button to define and they can be triggered by Time using the Schedule button to define and a combination of the two ANDed and ORed. Whether a Program uses device Direct commands or Scenes is your choice. Whatever is appropriate for the situation. Scenes have the advantage of simultaneous reaction of responders. The ISY User Guide available online and the UDI Wiki have an excellent collection of How To’s and examples. The Wiki has a section on how to add devices which is very handy for those devices that have special needs. This just skims the surface. Some things will be similar to the EZSrve in concept, some will not. Some of the ISY Program traits are a little different particularly in the area of Wait and Repeat but they are well documented in the Wiki.

One way to determine if it is the device or the location is to connect it to an Appliance cord. Plug on one end and bare wires on the other. Wire nut the device to the Appliance cord and plug it in next to the PLM. If it works there it is location related. If it does not work try a Factory reset of the device before getting a replacement. While the device is out double check the Insteon address looking for 8’s for B’, that sort of thing.

The check box controls the Dusk/Dawn messages. If Night Mode is checked (Always) there is no Dusk/Dawn message. Also note that the ambient light level must exist light or dark for at least 3.5 minutes before either message is sent when operating in Night Only mode. EDIT: to check the basic operation of Night Only mode put the Motion Sensor under a light such as a desk light and leave it exposed for 4 minutes. This may not generate a message as it depends on the ambient level before putting it under the light. Then cover the MS with something totally opaque. In approx 3.5 minutes a Dusk message should be sent. Put the MS back under the light and approx 3.5 minutes there should be a Dawn message. The actual Sensitivity value is trial and error depending on how dark it should be to get the Dark message.

For the RemoteLinc the Name is your choice The Insteon Address is found in the battery box along the bottom edge. Remove the bottom battery to see label.

Is Jumper 5 in place and if so what is the Night Mode check box state, and what is the Darkness Sensitivity value?

Brian Great pickup. Did not think to look at his web site. It specifically notes firmware 2D and above is needed for a Secondary button to control the On Level and Ramp Rate of the local load. Thanks Lee

Do you have a later level KeypadLinc that can be used as a test? With the same ISY and UI code the only difference I can see is the KPL is at a lower firmware level than my v36.

My 6 button KPL is at v36. Might be a difference in KPL firmware capability.

The new value was not written to the KeypadLinc. See the Red events in my trace which are absent in yours. Does Help | About show Firmware and UI both at 3.1.13? Sun 12/11/2011 01:05:02 PM : [iNST-ACK ] 02 62 12.B9.0D 0F 11 BA 06 LTONRR (BA) Sun 12/11/2011 01:05:03 PM : [iNST-SRX ] 02 50 12.B9.0D 19.70.15 2B 11 BA LTONRR (BA) Sun 12/11/2011 01:05:03 PM : [standard-Direct Ack][12.B9.0D-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Sun 12/11/2011 01:05:03 PM : [ 12 B9 D 1] ST 186 Sun 12/11/2011 01:05:03 PM : [All ] Writing 2 bytes to devices Sun 12/11/2011 01:05:03 PM : [12 B9 D 1 ] Memory : Write dbAddr=0x02A9 [bA] cmd1=0x00 cmd2=0x00 Sun 12/11/2011 01:05:03 PM : [12 B9 D 1 ] Using engine version i1 for 'KeypadLinc White 6 Button' Sun 12/11/2011 01:05:03 PM : [iNST-ACK ] 02 62 12.B9.0D 0F 28 02 06 SET-MSB(02) Sun 12/11/2011 01:05:03 PM : [iNST-SRX ] 02 50 12.B9.0D 19.70.15 2B 28 02 SET-MSB(02) Sun 12/11/2011 01:05:03 PM : [standard-Direct Ack][12.B9.0D-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Sun 12/11/2011 01:05:03 PM : [iNST-ACK ] 02 62 12.B9.0D 0F 2B A9 06 PEEK (A9) Sun 12/11/2011 01:05:04 PM : [iNST-SRX ] 02 50 12.B9.0D 19.70.15 2B 2B 35 PEEK (35) Sun 12/11/2011 01:05:04 PM : [standard-Direct Ack][12.B9.0D-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Sun 12/11/2011 01:05:04 PM : [iNST-ACK ] 02 62 12.B9.0D 0F 29 BA 06 POKE (BA) Sun 12/11/2011 01:05:04 PM : [iNST-SRX ] 02 50 12.B9.0D 19.70.15 2B 29 BA POKE (BA) Sun 12/11/2011 01:05:04 PM : [standard-Direct Ack][12.B9.0D-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Sun 12/11/2011 01:05:04 PM : [iNST-ACK ] 02 62 12.B9.0D 0F 24 00 06 (00) Sun 12/11/2011 01:05:05 PM : [iNST-SRX ] 02 50 12.B9.0D 19.70.15 2B 24 00 (00) Sun 12/11/2011 01:05:05 PM : [standard-Direct Ack][12.B9.0D-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Sun 12/11/2011 01:05:05 PM : [12 B9 D 1 ] Memory : EPROM Refreshed

Thanks for the confirmation. That is very strange. Lets see if the ISY is actually changing the associated KPL memory. Run Tools | Diagnostics | Event Viewer with Level: Device communications events selected. Change the On Level to something, 80% just to have a different value and post the event trace.

When devices are operating in a multi-way (3-way, 4-way, etc) configuration all the devices must be added to an ISY Scene as a Controller. ISY assumes a Controller is also a Responder. Adding a device as a Responder does not allow it to control other devices. Also note that Insteon devices in a multi-way configuration do not use the traveler wire. The wiring must be adjusted so each Insteon device receives un-switched 120V AC. Item 1 ISY Scene A (Scene name your choice) KeypadLInc A (load control in 8 button mode) as Controller Another Dimmer as Controller Item 2 ISY Scene B (Scene name your choice) Dimmer 1 as Controller Dimmer 2 as Controller Item 3 ISY Scene C (Scene name your choice) KeypadLinc Secondary Button B as Controller Kitchen Dimmer as Controller Living Room Dimmer as Controller All the Controllers in a given Scene are cross-linked automaticlly by the ISY. This allows all Controllers to control all other Controller devices and all status LEDs stay in sync. Once the correct links are established then any remaining communications issues can be addressed. For now turn Off any remote notification by the LG appliances. Don't know if that is powerline communication or RF communication. Do not want either possibility for now.

In the image below Scene Controller “KeypadLinc White 6 Button – A†has been selected, the list of Responders to Button A is displayed, “KeypadLinc White 6 Button†is the load control button on the KeypadLinc set to 85%. It is this line that shows 85% that reverts back to 100% if Button B is selected and then Button A is clicked again?

Because the responder(s) still have the link records created by the Set button the RemoteLinc2 is able to control them although only part of the Scene (Group) protocol is functional. Except where needed for specific devices manual Set button links should not be done as the ISY is not aware of them. I suggest defining an ISY Scene, adding the RemoteLinc2 as a Controller with the other devices as Responders.

You clicked on the Start Linking Icon. This is the function where devices are being added to the ISY by using the Set button on the device to notify the ISY of its existence. The correct way to get out of that is to click Finish. Go to Configuration and reboot the ISY (Reboot button in System section). It may be necessary to Reboot more than once. If the Configuration tab is not displayed or cannot be reached power cycle the ISY again.