stusviews

Are you using a scene or a program to control the light?

If Control 'motion sensor' is switched On And Sense 'other light' is not On Then turn it on wait turn it off

Updates are likely to complete while the battery powered device is still in linking mode. Use a tap or two to end that mode before trying to update the next device.

The next time the console appears unresponsive, glance in the bottom, left corner. The ISY may be busy deleting links and doing other chores.

Scenes are device links and do not require the ISY to process. Scenes do not require that the ISY even be turned on to run. Scenes actually eliminate a layer to deal with.

In order to initiate the 4-tap test.

There is no way to prevent a wired load from responding to a manual On (or Off). But you could set the default On-level to 0%. That can only be done with a dimmer. And it won't stop a fast on from turning the load on. The only solution may be to disconnect and/or remove the loads. Or replace them with non-white bulbs

If control device is on (or off), then disable program x.

Any device that has access to a web browser can interact with the ISY HTML interface, but Java is required for the Administrative Console. Windows is not required.

EricK, "I want to press a kpl button (g), wait 5 minutes and if a door sensor is on send a notification" Thus, if 5 minutes have elapsed after pressing the button and the sensor is on, then send the notification. That's not the same as "if both devices are on send a notification after 5 minutes has elapsed." “ I know you think you understand what you thought I said but I'm not sure you realize that what you heard is not what I meant”

The powerline frequencies of INSTEON (131.65 kHz) and X10 (120 kHz) are close enough that a bridge for one is effectively a bridge for the other. However, some X10 active couplers (they're also a booster) actually interfere with the INSTEON signal.

If control g is on Then wait 5 minutes run program 2 diasabled program 2 (runs only if called from another program) If sense door sensor is on

Yup

Chopping the waveform, as a TRIAC does even at full brightness, does not alter the timing of the zero crossing.

You can have 100 Access Points and dual-band devices and still not have the opposite legs of the split, single-phase electric supply bridged (although that's unlikely with a 100 devices). The only ways of ensuring that the opposite legs are coupled is an intimate knowledge of the physical wiring or the easy to perform 4-tap test.

Some people can replace a light switch, some can replace a spark plug. Some can even play a Xylophone. Some can do none of that, other's can do it all. That said, it's relatively easy to duplicate everything the SmartLinc can do using an ISY except running a scene remotely. You'll need a app for that, such as MobiLinc. An important difference is that the SmartLinc is basically an INSTEON controller. The ISY is not. It's an INSTEON manager that allows you to easily create scenes that respond to changes in your INSTEON network such as a button or paddle push or signal from a device such as a Motion Sensor or thermostat. In that respect, it more closely resembles HouseLinc. SmartLinc scenes are created by adding the devices to the scene manually. The ISY requires that you first add the device to the ISY, either manually or by ID and then add them to the scenes you create. Once that's done you can easily change the On-Level and/or ramp rate of any device that has that capability. You can easily drag and drop devices in and out of scenes and even more. But, the ISY adds programming abilities. Plenty of help is available in the User's Manual and especially on this forum. You can make the transition from SmatLinc to ISY one scene at a time or you can factory reset each device as you add it to the ISY. The latter is the recommended approach, but that may depend on how many devices and scenes you have.

That's correct. With the With the jumper removed, the Open/Close Sensor, as it's now called, will send an On to scene 1 when activated and an off to scene 2 when decactivated (close to the magnet).

Non-dimmable CFLs will not last as long using a dimmer as a TRIAC dimmer chops the waveform even at full brightness. So, if you're waiting for them to burn out, keep them on longer

I just read your reply and tested the programs. The programs still function correctly. Did you move the jumper? How long did you wait between openings?

If Status 'Sitting Room / Sitting KPL (DB) Lights' is not 20% won't work because there's no trigger. I was thinking of something simple, such as: If KPL main button is switched off, then turn off (scene that includes) Dim button

These programs ran successfully (I didn't include the schedule for simplicity. I used 5 second to save time. I also used a device in program 2 instead of a scene). Program 1 If Control 'Triggerlinc' is switched On And Status 'Device 1" is not On Then Run Program 'Program 2' (Then Path) Else - No Actions - (To add one, press 'Action') Program 2 If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Disable Program 'Program 1' Set 'Device 1' On Wait 5 seconds Set 'Device 1' Off Enable Program 'Program 1' Else - No Actions - (To add one, press 'Action') Because this is a temporary condition, you need only be concerned about the primary device.

Status only works if that button or a scene that contains that button is activated. Status is not a 24/7 monitor (as I thought it was). How about if the trigger is the KPL Off button?

A Micro Module can easily fit in the Elk cabinet.

Solid green indicates that the program is running and the premise is true. Solid red indicates that the program is running and the premise is false.

The red LED will blink more rapidly in unlinking mode than in linking mode. The difference is not difficult to discern.