LeeG

Change Sunrise to (next day)

Move the right side of the window to the right. Longitude input field does not display if window too small.

Either the RemoteLinc2 has lost its link to the PLM ... Or the PLM has lost its link to the RemoteLinc2 ... Or the Dual Band device the RemoteLinc2 is communicating through will not reach the PLM ... Put the Remotelinc2 into linking mode, right click the RemoteLinc2 Primary node and select Restore Device. This will rebuild the RemoteLinc2 link database and the PLM entry pointing to the RemoteLinc2. Have the event viewer running at LEVEL 3 to be sure command activity is traced.

Do you see events from any device when a button/paddle is pressed?

That means the Program has not been triggered. Make sure Program is Enabled and a Save is not pending. Run Tools | Diagnostics | Event Viewer at LEVEL 3. Press the RemoteLinc2 button and post the event trace. If nothing is traced move the RemoteLinc2 closer to a Dual Band device.

What does Programs | Summary page show for this Program Status and Last Run Time?

Probably from not having set the other SwitchLinc LED levels. The 0 value is what it says when never been set (the default LED level is much brighter than when set to 0). Set one of the others to 5, when update is complete move to 0.

Suggest looking at the User Guide for the Dimmer. Here is what the SwitchLinc Dimmer will do with Local On Level. Local On-Level Default = 100% (fixed brightness) The local on-level is the brightness that SwitchLinc’s connected load will come on when turned on at SwitchLinc paddle. Local on-level can be set to any one of 32 fixed brightness levels (3% to 100%) or “resume bright†(brightness prior to last being turned off). Page 12 of 17 Rev: 7/24/2012 10:26 AM To set local on level to a fixed brightness level 1) Adjust SwitchLinc to desired brightness when controlled locally 2) Tap Set button SwitchLinc will beep 3) Test by turning SwitchLinc off and then back on (via the paddle) SwitchLinc will turn on to new local on-level To set local on level to the brightness level prior to being turned off 1) Turn SwitchLinc off 2) Tap Set button SwitchLinc will beep 3) Test: a. Brighten SwitchLinc to a random brightness level (e.g. 75%) b. Turn SwitchLinc off c. Turn SwitchLinc back on Light will turn on at the defined brightness level

EricK Sure.

That is the way Scene Responders work. Take a look at the device User Guide in the area where the Local Ramp Rate is discussed. There are two modes of operation related to how the Local On Level works. Perhaps the other way would be better for you.

All battery powered devices go to sleep to save battery life. Put the Smoke Bridge into linking mode with its Set button, right click the Smoke Bridge Primary node and select Write Updates to Device. If more that one battery device exists do ONE at a time. Be sure to take the battery device out of linking mode before starting the next one. Restore Devices does all devices. There is a Restore Device for each device.

There has been a change to the firewall/anti-virus. The ISY is pushing data from the ISY to the Admin Console. This data is being blocked by the AV. The long Ramp Rate is a value of zero because the data coming from the ISY does not make it to the Admin Console. Kaspersky, Avast and others will do this. Turn the AV Off temporarily and see if that resolves the issue. There is normally a way of adding the ISY IP address to the AV so data is not blocked.

That is normal operation. Box 2 is directly controlling the load. First tap from Off turns it to the Local On Level. Next tap On goes to 100%, next tap to Local On Level. Box 1 is not directly controlling the load. Turning On this device it goes goes to Local On Level. Next tap On goes to 100% On Level, next tap to Local On Level. No mention about whether this is a Dimmer or a Relay so I assumed a Dimmer. This device has the device in box 2 as a Responder. When an On command is sent to a Responder that device goes to the defined Responder On Level. The next On command goes to the same Responder On Level. As a Responder it always goes to the defined Responder On Level. The Local On Level does not participate. Local On Level controls what the device does when the local paddle/button is pressed. Local On Level has no affect on the Responder On Level information.

Make the change to the On Level (assuming button A is selected and the ON button is being set to something other than 100%). Power cycle the KPL. I suspect a KPL that old will have issues getting a Secondary button to control the ON button with anything but 100% On (using commands). What ISY firmware is being used?

Are you clicking on the Scene name on the left side and setting button A on the right side to something other than 100%? That will not work. Button A is a Responder when the Scene name is clicked. Click the Red button A node name below the Scene name on the left side and set the Responders to whatever On Level desired when button A is a Controller.

Thanks for the scene test data. The KPL rejected (NAKed) the request to control the button. This looks like the KPL or the PLM have been reset since the KPL was added to the ISY. Suggest right click the KPL Primary node and select Restore Device to rebuild the KPL and PLM link database. Then repeat the Scene Test and see if the "Failed" result is corrected.

Yes. Right click the Scene name, select Diagnostics | Scene Test. Post the results.

You can see what each node has been assigned by entering .... http://192.168.2.3/rest/nodes/ into a browser. The username/password will be solicited. 12 B9 D 1 KPL Floor Dimmer 6 1.27.54.63 true 0 0 0 12 B9 D 1 E13 12 B9 D 3 KPL Floor Dimmer 6 - A 12 B9 D 1 1.27.54.63 true 0 0 0 12 B9 D 1 F01 12 B9 D 4 KPL Floor Dimmer 6 - B 12 B9 D 1 1.27.54.63 true 0 0 0 12 B9 D 1 F02 12 B9 D 5 KPL Floor Dimmer 6 - C 12 B9 D 1 1.27.54.63 true 0 0 0 12 B9 D 1 F03

No problem. Always use an ISY Scene to link devices. NEVER link with a Set button. In Insteon using a Direct command (which is what you are doing when turning On/Off the device) only that device responds. Does not matter that the device is linked to other devices, only that device reacts. To have multiple devices react at the same time use the Scene name that linked the devices. Set 'lamplinc' On - turns the device On Set Scene 'scenename' On - turns all the devices in the Scene On

All nodes have a number associated with them, aa bb cc x, in the ISY. Devices such as SwitchLincs, LampLincs, ApplianceLincs always have a number 1 as there is only one node per device. An 8 button KeypadLinc has 8 nodes numbered 1-8. Button A is 1 Button B is 2 Button C is 3 etc The full node identifier aa bb cc x is needed in the email messages. The 1 is for the Primary/First node. If you want to see the value of another node for the same Insteon device use its node number.

The Insteon address is printed on a piece of paper glued to the Printed Circuit Board (PCB). It is obvious. In Insteon there are Controllers which affect what Responders do. In a simple case .... KPL button C is a Controller LampLinc is a Responder Some devices such as Motion Sensors, TriggerLincs, RemoteLinc/RemoteLinc2 and others are Controller only devices. These devices cannot be turned On/Off from another device. Some devices are Responder only devices. The older ApplianceLinc, the OutletLinc Relay and others can be turned On/Off by a Controller but manual operation of these devices CANNOT affect other Insteon devices (Responder Only). Most Insteon devices are Controller/Responder devices. They can control other devices (Controller) and they can react (Responder) to other Controllers. KeypadLincs, SwitchLincs are two examples of devices that are Controller/Responder devices. When assigning a device node to a Scene as a controller device, assign the device as a Controller. The ISY assumes a Controller is also a Responder to the Scene if the device also has Responder capability. Battery devices have to be put into linking mode with the Set button to keep them awake long enough to add them to the ISY and make changes to the link records and configuration data. Battery powered devices sleep (turn Off RF circuity) to extend battery life. If they are not put into linking mode the ISY will not be able to send commands to them.

An ISY Scene was used to link the KPL button C and the LampLinc. To have both devices stay in sync control the Scene from the Program rather than an individual device.

Normally the node has an additional digit. From the UDI Wiki ... ${sys.node.11 22 AA 1.name}

If I understand the question correctly, normal Insteon operation. From MobiLinc or the Admin Console operating an individual switch is limited to that switch. For both switches to react you need to turn the Scene On/Off. This allows an individual device to be managed or a collection of devices (Scene).

There is a Broadcast message a device issues when using New INSTEON Device. Some systems have problems moving that message to the PLM (and the ISY). I have not seen that issue here so have no solution. Pressing the Set button on the device sends the Broadcast message without it being asked for so the information required is obtained when using Start Linking. Don't know why the Broadcast message does not appear with New INSTEON Device. It works here all the time so have not had the failure to see why. Some users have reported seeing the same problem and it goes away. Again, no good information about why.