LeeG

Great to hear its working. Thanks for taking the time to post back. Others will benefit from knowing the solution.

There is no direct equivalent to the X10 All On All Off. Define an ISY Scene with the devices that should react and issue a Scene On or Scene Off. Some devices such as thermostats, I/O Lincs operating garage doors and the like would not normally be controlled by an All On or All Off

wswartz The Adjust Scene statement should specify the Motion Sensor - Sensor node in the 'In Scene' parameter and the dimmer node name in the 'Set' parameter. If the Scene name was specified in the 'In Scene' parameter the On Level for the Scene name (when a Program uses the Scene name) is affected. To change how the dimmer responds to the Motion Sensor - Sensor node it has to be identified as the Controller in the 'In Scene' parameter.

Factory reset the 2-wire SwitchLinc. Right click the SwitchLinc node name and select Restore Device.

oaklandjeff Right click the ISY Scene name, select Diagnostics | Scene Test. This test takes several seconds to complete. When done it will show if each Responder to the Scene was a Success or Failure. If the Scene Test works it indicates all the required link records have been written and are working. If the Scene Test fails it can mean a link record problem or a serious comm. problem. When a Scene Test is successful but the using the Scene is not reliable for a particular Responder it usually means a communications problem with that device. Direct commands and Scene Test commands have multiple retries built into the protocol. Controlling a Scene with On/Off does not have those retries so issues with comm show up quickly. The 2-wire devices are RF only so they have to be in reliable range of a Dual Band device. Try moving a spare Access Point closer to where this 2-wire device is located.

Below the ISY Scene name is listed the node name for the virtual SwitchLinc. When the paddle on this SwitchLinc is pressed it is acting as a Controller, directing the load controlling SwitchLinc what to do. Each Controller has a unique set of Responder values. I expect when the virtual SwitchLinc node name is selected the Responder On Level and Responder Ramp Rate will reflect what is actually happening. This is actually a feature of Insteon. It allows each Controller to affect its Responders in a unique way. When the Scene name is selected the Responder values being set apply to when the ISY PLM is the Controller. These would have an effect when the Scene name is controlled with a Program or through the Admin Console.

The commands used to set the Local On Level and Local Ramp Rate are Peek/Poke which are used to read and write device memory. These commands directly set memory such that the device is not aware of the changes. A power cycle establishes the new values. For devices with the newest firmware that supports the I2CS Insteon protocol (the latest in Insteon evolution) the Peek/Poke commands have been eliminated altogether. The newer devices use Extended configuration commands to set values like Local On Level and Local Ramp Rate. These commands instruct the device to change the respective values without the application (ISY) knowing anything about where the data is actually being stored. Now the device is directly aware the values are being changed, adjusting the values currently being used. There are always exceptions in Insteon. The above information is accurate but does not always apply to data changed with Peek/Poke. Link record data is often written with Peek/Poke (until I2CS came along) and have immediate effect because link records are accessed each time they are used.

In Insteon every Controller has a unique set of On Level and Ramp Rate values for each Responder. These values are stored in each Responder link database keyed to the Controller Insteon address. This gives Insteon great flexibility in controlling Responders and demonstrates just how much work the ISY does under the covers whenever a Scene is created. The Local On Level and Local Ramp Rate are stored in the Controller in an area of device memory outside the link database. What is sometimes missed is that the Controller is the ISY PLM itself when the ISY Scene Name is used in a Program or controlled from the Admin Console.

Thanks for the trace data. Exactly what was needed. That old SwitchLinc will not react to the programmatic change in Local On Level and Local Ramp Rate without a power cycle. Makes that particular SwitchLinc not capable of doing what you want.

1) I was using "adjust scene" because I wanted the entire scene to turn on..namely the KPL button light to come on during the time the under cabinet lights are on AND set it to 50%. Why is that not correct? 2) How do I make sure the KPL button shows the light is on if this is not correct? The Adjust Scene statement can change only one item at a time. It is coded to set the Local On Level to 50% so when the SwitchLinc On paddle is pressed the SwitchLinc turns On to 50%. If the KPL button press should also turn the SwitchLinc On to 50% during this time another Adjust Scene is needed, specifying the KeypadLinc button in the 'In Scene' parameter and the SwitchLinc in the 'Set' parameter. Same with the RemoteLinc button. If it should turn the SwitchLinc On to 50% during this time a third Adjust Scene statement is needed, specifying the RemoteLinc button in the 'In Scene' parameter and the SwitchLinc in the 'Set' parameter. If the ISY Scene name is used in a Program then another Adjust Scene statement is needed, specifying the Scene name in the 'In Scene' parameter and the SwitchLinc in the 'Set' parameter. The various On Level values are stored in different places. Thus a separate Adjust Scene statement is needed to change each location to 50%. At the end of the time period another series of Adjust Scene statements is needed to put each value back to 100%. If the ISY Scene has the SwitchLinc, the KeypadLinc button and the RemoteLinc button as Controllers turning the SwitchLinc On/Off with the SwitchLinc paddle will turn the KeypadLinc button On/Off.

parkersmith My v.40 KPL Relay also has the different backlight level presentation and it does change the LED Backlight level. There has been criticism/confusion about the on/off level presentation since the on and off levels cannot be changed independent of each other. Perhaps this is an attempt to present a more meaningful option for LED Backlight level. Again, the new % backlight level is setting the LED Backlight level on my v.40 KPL Relay.

Apparently Smarthome makes the latest update available to groups of users at a time, perhaps to avoid overloading their servers (only a guess). I've been on 2.9.59 for a few days, maybe more. Things have been hectic around here so it could be a week or more. Received Device Definition update to 2.9.50 today.

Is the Under Cabiniet SwitchLinc the load control device and is it being controlled from one of the other Controllers. Each Controller has its own On Level so if controlled from the KPL button or RL button those responder values need to be changed as well.

Might need 2.9.59 to get support for all the PLMs. I know some have tried using a 2412N SmartLinc which is also listed as supported now but it is not working. Expect support for that in a future drop but others have reported using standard PLMs successfully. Don't know what level HL was being used

parkersmith Click Help | About, verify the Firmware and UI both indicate 3.3.8. If not clear the Java cache and adjust the URL to invoke the Admin Console for 3.3.8. Not all device firmware levels support a programmatic change to KPL LED backlight level. What is the firmware level of the 2487S? Also try a right click on the Primary node and select Diagnostics | Query Insteon Engine. This will insure the ISY knows what Insteon Engine the device contains. Can make a difference in how the LED backlight level is set. If all else fails run Tools | Diagnostics | Event Viewer at LEVEL 3. Change the backlight level to something other than the current value. Post the event trace. There is a fix in 3.3.8 for this issue on some of the KPLs. Need to see if the fix applies to this variant of KPL.

Ebay. You might consider keeping it. Smarthome is now providing HouseLinc free and it now supports any of the standard PLMs (no longer need the special PLM that ends in H). There is some Insteon network diagnostics that might be useful. There are issues trying to share a device between HL and the ISY so how useful this might be is an open question but it is an option. If you ever get a Simplehomenet/Smartenit device the USB PLM could be used with the free SHN Utility Suite to do some SHN device configuration the ISY does not support, such as setting the Relay timers on the EZIOxx devices so the relays can be used to control garage doors and the like.

Is the xxx.xxx.xx.x value being used the Modem WAN IP address?

I have seen that work on a PC but I have serious doubts with an ISY. Also all converters are not equal, even on a PC some work some do not. Some work some of the time but create intermittent PLM communication issues. Considering the total investment in Insteon I think you are asking for trouble for such a small savings. The convertor will always be an open question, is the convertor responsible for this symptom. It is NOT a supported ISY configuration.

ferdies The symptom continues on 3.3.8 because it is not an ISY problem. When a device can be turned On remotely but cannot be turned Off it is usually the Load the device is Controlling. When powered the load generates enough interference such that the Off command is not received. What type of load is the SwitchLinc Dimmer controlling?

parkersmith To turn a Secondary KeypadLinc button On/Off from the Admin Console or Program it is necessary to assign that Secondary KPL button to a Scene as a Responder and turn the Scene On/Off. Secondary KeypadLinc button LEDs CANNOT be turned On and Off with a Program or the Admin Console Direct command. The Insteon Direct On/Off commands do not have a placeholder for button number making it impossible to specify a button number to turn On/Off. An Insteon Direct command to a KPL is assumed by the KPL to be controlling the Load and Load control buttons (ON/OFF for 6 button, Main A for 8 button). Setting the LED Backlight level adjusts the overall LED intensity of all buttons . It controls how bright all the buttons are when On and Off. The KPL hardware/firmware requires a minimum separation of 8 for low/high numbers. The KPL values can be set otherwise but the KPL itself always operates as though there is a difference of 8 between the On and Off LED backlight level. That is so the difference between a button being On and a button being Off is always visually detectable.

That is the correct way to make the Scene. Exactly how I made the test Scene I posted and traced. The 3 wires going into the box, two were retasked to provide 120v unswitched power to that SwitchLinc and the third is capped? Apostolakisl suggestion at the end of his last post ensures that the environment is clean, with no possibilities of something being left behind during the various iterations. If that does not result in correct operation then a detailed analysis of device content as that sequence should work.

funkadelic oberkc is right on about some older devices having to be power cycled before the change to Local On Level takes affect. There are some other possiblilites as well. Right click the SwitchLinc Dimmer node in the My Lighting tree, select Diagnostics | Query Insteon Engine. Run Tools | Diagnostics | Event Viewer at LEVEL 3. Change the Program to some other value than 30% as the ISY will not write a value it thinks has already been set. Use 25% or 35%. Right click on Program name and select Run Then. Post the event trace. The technique for physically updating the Local On Level has changed over time. I suspect the v.27 firmware does not handle the new technique. The event trace will show the commands being used to set the 25%/35%. That should tell us if the SwitchLinc has to be power cycled to pick up the Local On Level change. You can also pull the air gap switch for at least 30 seconds and push it back in. Be careful not to push the air gap switch past the level of the frame to avoid an unwanted reset.

TheWabit “I have it set to "sunset to 830pm same day" (condition) set in scene "under cabinet" under cabinet to 50% They dont come on†The Adjust Scene statement that is setting the On Level to 50% does not actually turn the Scene On. A second Program statement “Set Scene ‘xxxxx’ On is needed to turn the Scene device On. As oberkc said it is best to post the actual Program as I am assuming the Adjust Scene is coded correctly and the Set Scene On is missing.

apostolakisl "can't explain the fact that jef000 seems to be indicating the light did switch off when he pushed switch 2 even though the load is on switch 1 and there is no indication switch 1 did anything." There would be no Insteon indication of switch 1 doing anything since switch 2 is the Controller. The PLM would not pass communication between the two switches to the ISY. Marking the Responder switch Status On or Off is only because the ISY thinks they are linked. That is why I am sure the ISY does not think they are linked. The result can happen if there is a half/broken link with a Responder On Level of 0%. Switch 1 would turn Off with the half/broken link but not turn On because of the 0% On Level. You could walk OP through the Show Device Links Table process for both devices to see what actually exists in the link database. If not the result of half/broken link then wiring of the first attempt at a 3-way is in question.

Click Programs | Variables tab. Then select either the Integer or State tab depending on the type of Variable to be defined. Click the Add button at the bottom of the pane, enter Name, Init and Value as desired. Then click Save