fitzpatri8

It doesn't look like the ISY firmware was written to support a second control scene with the Load Controller. Not to worry, you easily get the same functionality using ISY programs: 1. Unlink any devices you've already manually linked to the Load Controller Scenes 1 and 2. 2. Factory reset the Load Controller. Remove and re-add it to ISY. 3. Now, rather than link the Load Controller to responder devices, create two programs: If Control [Load Controller] is ON Set [iSY scene of your choosing] ON If Control [Load Controller] is OFF Set [2nd ISY scene of your choosing] ON

By default, each node of a multi-node device gets its own entry on the device tree. To display them together, right-click on the main on/off button and select the Group option.

When you are in the Administrative Console, you can always click on Help... UDI Wiki, then search for a keyword like Repeat. There's tons of great reference info there.

Try something like this: If Control 'Light' is switched On Then Repeat 5 times Set 'Different Light' 1 (Beep Duration) Repeat 1 times Set 'Light' Off Else - No Actions - (To add one, press 'Action') I find the beep duration of 1 will occasionally give a double-beep the first time, so don't set two different programs to indicate different things with just 1 difference in beep count! The second Repeat ends the loop. If there's no second Repeat, all instructions through the end of the program repeat.

So when it is in this half-on state, pulling the airgap out on the keypadlinc turns off the light completely? And there's no InLineLinc anywhere attached to the load?

Are you sure you didn't inadvertently wire a second dimmer to the same load?

You would need to use ISY programs to do that.

It's a brand new unit, so I take it you have a 2413s dual-band PLM? Step 1: Use the test mode on the PLM to confirm it is communicating with your Access Points or other dual-band devices. (Instructions are in the owner's manual on the Smarthome product page: http://www.smarthome.com/2413S/PowerLin ... and/p.aspx ). Then exit test mode. Step 2: Once communications are confirmed, go to the ISY Administrative Console and click Start Linking from the Link Management menu. The light on the PLM should start blinking in Multi-Link mode. Within 4 minutes go to another Insteon device in the house and hold the Set button for 3 seconds. It should beep or flash and the device should exit link mode. Do the same on another Insteon device. Step 3: On the Administrative Console window popup, select Add Devices and Keep Existing Links, then click OK. The PLM will drop out of multi-link mode. You will see status updates on screen as the ISY reads the device's link table. Did that work? If not, where in the process did you get hung up?

Mutually exclusive scenes work fine with one keypad but get more complicated on the ISY as you add additional controllers. Scenario: Secondary Button A and button B are mutually exclusive on two different keypads. Create Scene A with keypad 1 & 2 Button A both as Controllers, plus any other scene members as responders or controllers. Create Scene B with keypad 1 & 2 Button B both as Controllers, plus any other scene members as responders or controllers. Create a third scene, "MutEx Scenes A B", containing all mutually exclusive buttons (in this case, both buttons on both keypads) as Responders. Do not include other members of the mutually exclusive scenes as responders to the third scene! A single program is required for each mutually exclusive scene: If Control 'Keypad 1 Button A' is switched On Or Control 'Keypad 2 Button A' is switched On Then Wait 2 seconds Set Scene 'Mutex Keypad' Off Set Scene 'Scene A' On Else - No Actions - If Control 'Keypad 1 Button B' is switched On Or Control 'Keypad 2 Button B' is switched On Then Wait 2 seconds Set Scene 'Mutex Keypad' Off Set Scene 'Scene B' On Else - No Actions - It's doable but not convenient. When you press a button, the button turns on (confirming the button press). Next the appropriate program waits a couple of seconds for messages from the keypad to finish and turns *all* mutex buttons off. Finally, the ISY resends the original scene, turning the appropriate mutex button back on and resending the original scene command. The mutex keypad indicators blink off then on, but you shouldn't see any difference in the other responders since you are resending the identical command.

That's correct, 'vintage' Insteon SwitchLincs require a warm reset to lock in changes to the local settings. After changing the settings with the ISY, flip the circuit breaker off for a minute then back on (or 'air gap' the switch, whichever is easier for you) to put the new settings into effect at the switch. This power cycle isn't necessary if you change the local settings by tapping buttons at the switch, only when programming it remotely.

Try using pool.ntp.org as your server instead.

How many watts is the load? Is this in ordinary use, or is one of your Insteon devices in linking mode when this happens?

No, using two programs is the correct approach. If you try to use the ELSE portion of a program to handle the opposite status condition that you are using in the IF portion, it will cause the program to loop when the change in status causes the program to be re-evaluated--as you've already discovered. Consider the following example: If Control IR 255 and Status Light is Off Then Turn ON Light Else Turn OFF Light The program is re-evaluated when: a) The IR code is received by the ISY The Status of the light changed from ON to OFF, or c) The Status of the light changed from OFF to ON. Only if a and b are true will the THEN branch of your program run, as you intend. The problem is that if only a, or only b, or only c, or a and c, then the ELSE branch would execute. So when you changed the light status from within the program, the conditions changed and it ran the Else. The solution here is to use two programs and avoid using ELSE.

What is the purpose of the flash, and what event(s) should trigger it?

There's a feature built into newer dimmer switches that checks for wiring issues or incompatible loads and sounds an alarm if either are found when power is first applied. If you change the load to a standard, line-voltage incandescent then power-cycle it, if the alarm doesn't sound, then you know the previous was an incompatible bulb or transformer.

That should work if you use status of the keypad button as a secondary condition to trigger a program.

The logistics get complicated. What exactly constitutes a scene being on? If it is turned on, then one or more devices get brightened or dimmed, is it on (because all the contained devices are still 'on') or is it now considered off? If all the lights in a scene are off, then are adjusted individually to match the settings of a scene, should the scene be considered on or off? What about scenes with multiple controllers with different device settings (ISY scene has light 1 at 50%, but a controller within the scene has light 1 set to 45%), which level constitutes On and when should it display Off? I imagine the path of least resistance is to let users to write the rules for themselves using a program.

If you right-click on a program in the ISY's administrative console, one of the options is "Copy to Clipboard". Once you do that, you can paste it into a response here. Rand's reply offers step-by-step instructions on how to make this work. If one of the steps doesn't make sense to you, speak up and someone can clarify.

Since making some system changes today (adding and deleting scenes, adding new IRLinc Transmitter scenes), I can no longer see the device tree on my ISY after I log in. Programs are still running and I can see and edit programs and use other interface features, but whenever I return to the Main tab I get a blank screen with a System Busy message at the bottom. I've power cycled both the ISY and the PLM with no change, cleared the java cache, tried bringing up the admin console using the app and the online link, all with the same result. Any other ideas? Thanks, Tom

There are multiple kinds of InLineLincs. Only the InLineLinc with Sense can be used as a controller.

Currently, the software that offers house graphics uses a desktop computer to set up and configure layout and control locations. Take a look at Indigo Touch or HSTouchPad on the iTunes Store for examples. HomeSeer offers a plug-in to work with the ISY, but it would require leaving a PC running HomeSeer running 7/24. Since the ISY is itself a webserver, another option is to simply code your own web page with control links embedded. Take a look at TouchSwitch for an example.

The two programs with the circle & slash are just disabled. Click on each and put a checkmark in the Enable box (on the right, next to the Schedule Condition Action Comment buttons).

Is there another condition in the program that would prevent it from running on the day it stops? Can you cut & paste the actual program in a message here?

That could also be the AC unit generating power line noise that looked like a programmed x10 code. Even if you didn't program an x10 address, it could have one left over from testing at the factory. To test this theory out, perform a factory reset on the OL and restore its links table using the ISY restore feature, then retest.