Sub-Routine

If you want to view the KPL links you can use the menu Tools | Diagnostics | Show Device Links Table and use the Compare button. Or open the Tools | Diagnostics | Event Viewer, press the KPL button, and watch for errors. That may be quicker if your KPL has many links. If the AL is still in the KPL then use Restore on the KPL. You could pull the plug on the ISY, but of course that is not recommended The process will eventually time out. Yes, it was because the AL was unplugged. It probably did time out if you waited 10 minutes. Again you could open the Tools | Diagnostics | Event Viewer and see what the ISY is doing before taking drastic measures. Also of note is that the ISY does not rely on the Admin Console being open to perform it's job. Once a process is started the ISY will run it until completion or failure whether or not you are watching it. Rand

Yes. Create a scene and put the KPL button in it. Then you can turn the scene and thus the KPL button On/Off. If you are going to do this in a program that checks the Status of the button then you will want to Wait at least 2 seconds before you switch the scene. Rand

aLf, Yes, if you would have plugged in the device to remove it from the scene (or remove the scene) the ISY would be able to delete the links in that device. You could have plugged it back in during the System Busy sequence and all should turn out well. If you remove the device from My Lights the ISY will remove all the links to it in all your other devices and will not attempt to communicate with the removed device. This is intended for failed devices. If the device is still alive you should factory reset it before using it again because it will still contain all the old (now broken) links. Rand

The risk is low. The worst that would happen is that some linked devices might have links left in them from the old device and some time would be wasted whenever a scene containing the removed device is called. If the device is missing and you try to remove it from a scene the ISY makes, afaik, up to 5 attempts to contact that device and remove the scene links, thus it can add up to some time. Using Remove does not do a such error recovery on the removed device. Only on the linked devices does the ISY go through so much trouble. Rand

The ISY maintains a Status for buttons according to the last press reported. Using Control to watch for a press and Status for the KPL button is the correct protocol. So when the KPL button is switched the program runs and if the CL button isn't switched at the same time the Else Actions will execute. Using two programs will accomplish this more efficiently than using Else. Else has many uses but this is not one of them. Rand

Okay, I misunderstood. I thought you wanted the Else to run if the CL is switched Off when the KPL is On. This may be what you would like: If Control 'MBDR Controller (1)' is switched On And Status 'Megan Home' is On Then Run Program 'BedTimeCommon' (If) Wait 10 seconds Set 'Megans Room Bath' 30% Set 'Megans Room Overhead' On Set 'Megans Room Lava Lamp' On Send Notification to All Else - No Actions - (To add one, press 'Action') If Control 'MBDR Controller (1)' is switched On And Status 'Megan Home' is Off Then Run Program 'BedTimeCommon' (If) Wait 10 seconds Set 'MBDR Air Filter' On Else - No Actions - (To add one, press 'Action') Rand

If you put the program in a folder and place the Status 'Megan Home' is On as a Condition to the folder (remove from program) the program will only run when that is True. As it is now the program will be triggered whenever the ControLinc button is pressed and whenever the Status 'Megan Home' changes. Rand

Joe, check out this Wiki page: SwitchLinc_Emulates_Countdown_Timer Rand

OH NO! aLf, did this eventually time out? This could be a bug. Which firmware do you have installed? To remove a failed device it is recommended to right click on the device and select Remove. That will remove the device from all scenes and the PLM. Rand

Hello m_later, This is very indicative of a failed switch and I can only guess that it is coincidental with your addition of an ISY. You can try a factory reset on the device but I doubt if it will fix it. When setting the local level and rate with the ISY the switch will need to be power cycled before the new settings are used. Rand

The Mutually Exclusive buttons would not be used in a scene, but to select one of several scenes, usually using the same group of lights. See this Wiki article: What_are_Mutually_Exclusive_Buttons. Rand

You could put all your controllers in one program and then check that program to be true. Status Off Check If Status 'Family Room KPL 2' is Off And Status 'House Remote 2' is Off And Status 'Living Room CL 2' is Off Then - No Actions - (To add one, press 'Action') Else - No Actions - (To add one, press 'Action') Motion On If Control 'Motion Sensor 2-Sensor' is switched On And Program 'Status Off Check' is True Then Set Scene 'Kitchen Motion' On Else - No Actions - (To add one, press 'Action') Motion Off If Control 'Motion Sensor 2-Sensor' is switched Off And Program 'Status Off Check' is True Then Set Scene 'Kitchen Motion' Off Else - No Actions - (To add one, press 'Action') Then you only need to maintain the Status Off Check program. Rand

Good Deal! Rand

Hi silberda, Though you can't see it the password prompt is probably open. Type in your username, press tab, password, tab, enter. Then you should be able to resize the window. Rand

Yes, but the IOLinc sends a command when switched. It would be better to create a scene with the IOLinc sensor as Controller and the KPL button as Responder. Then it will work without the ISY. Rand

This program will toggle the KPL button according to the LampLinc status. If Status 'Living Room LampLinc' is not Off Then Set Scene 'KPL Button' On Else Set Scene 'KPL Button' Off Rand

The only KPL button you can control in a scene is the main (load) button. The secondary buttons don't have levels/rates so they are not available in the responder pane. The button is displayed in the upper pane only to display it's current status. Rand

That could be a cause for concern. Did you add a new TV or PC? Sometimes even small devices can introduce noise. Of course it could be the PLC had a heart attack. With the ability to program a PLC comes some risk. That's good to hear! Rand

If you add the button as a Controller it doesn't disappear, it's in the tree on the left side of the screen. When you add the KPL button as a controller it's state cannot be changed so it is not displayed in the list of responders. When you expand the scene in the tree and select the KPL button you can use 'Copy Scene Attributes' or you can select different levels/rates than the scene as controlled by the ISY. If the KPL button is in the scene it should follow scene On/Off. If it's not in the scene then add the KPL button to the scene as a responder. Again, add the KPL button to the scene as a responder. No, you aren't programming wrong. KPL buttons can become pretty complicated to control. With only one LampLinc it's pretty simple but when multiple devices are involved it becomes a quandry and a matter of personal preference as to when the button should be on or off. Rand

Hi Moshe, welcome to our forum. Before I had an ISY I had software that used a PLC. The PLC is basically a PLM with some additional RAM to store a few timers. My communications were 100%. When I changed to the ISY with a PLM I began to experience comm failures. Perhaps it's not the best way to do things but I plugged an AccessPoint right into the PLM and re-synced the 2nd AP. I was surprised that I had to move AP#2 to a different circuit. That was it, back to 100%. I've been using it that way for nearly two years now (with several different PLMs) with no problems. Rand

Joe, right-click on the device and select Remove. Or, if you have a replacement, add that to the ISY, select the failed device, right-click and select Replace with new device. Rand

ryarber, please try adding the switch to the scene it thinks it belongs to and then removing it from said scene. Rand

I believe that indicates a UpNP conflict. Rand

I was thinking of the OutletLinc as well but I doubt if they broadcast any changes. I don't have any to test with. Gregoryx? It could well be a better way to keep the kids from changing the state. It does appear as if Smarthome is rolling out more devices that do broadcast on changes like the INSTEON-In-LineLinc-On-Off-Module-Non-dimming-w-Sense. I don't see any remarks as to local control on it though. Rand

No, the address should not have a port number since the update unless you change the port to that number. The new default https is port 443 and does not need to be appended to the address. If you change port 443 it is displayed in About as previously. See the Advanced_Configuration_Guide to read and change port assignments (CWP). Sorry for the confusion. Rand