stusviews

Devices do report back after scene commands. Otherwise Status wouldn't work in programs. And in some cases, a scene is the only way to control the status of, for example, a keypad button.

Scene transmit signals to all members of the scene concurrently and are inherently faster than programs. Programs are the best only choice if conditions must be met. BTW, I have a scene that turns off nearly all of my more than 100 devices. In particular, the scene turns off nearly all interior lights except those in the bedroom (and a few others).

It's great that it worked. The usual procedure is to power up the PLM first, then the ISY.

You can also link a universal garage door opener receiver such as one from Genie, Chamberlain, GTO or Liftmaster to a Homelink button and connect the receiver to the sense terminals of an I/O Linc.

What is the device? What is the load?

Control requires a manual "change of state." Sense detects any "change of state" even if the change is caused by a scene. Post your program(s). Right click on the program name, select Copy to Clipboard, paste into your reply. Also describe any scene(s) that the responder is a member of.

Did you click on the + to the left of the Leak Sensor?

Use control, not state.

Both Chamberlain ans Liftmaster have (line voltage) switches that respond to Homelink buttons. The switch can be used to trigger a Micro Module. Another alternative is to link the Homelink button to an X10 switch.

The Leak Sensor has three nodes; Dry, Heartbeat and Wet. The nodes should already be labeled.

The first program tests if the garage door is open between midnight and sunrise. It the garage door is open, then the 5 minute timer starts after which the second program starts and tests if the garage door is still open. If it is, then the program closes the door. Program 1 If From 12:00:00AM To Sunrise (same day) And Status 'GG / Devices / GG Garage 1 Sensor' is On Then Wait 5 minutes Run Program 'test2' (If) Else - No Actions - (To add one, press 'Action') Program 2 If Status 'GG / Devices / GG Garage 1 Sensor' is On Then Set 'GG / Devices / GG Garage 1 Sensor / GG Garage 1 Relay' On Else - No Actions - (To add one, press 'Action')

That's great. Browsing to http://isyshould not take you, "to some website." Unless you set a port, you should arrive at the ISY Dashboard. Did that not happen?

Browse to http://isy If that works or not then post back. We'll go from there.

The device is an I/O Linc. Sending an On to the relay is independent of the sensor. What doesn't work, the I/O Linc or the program?

Which specific camera? Which DVR?

If you have a statement that causes the If condition to become false, then "the current atomic statement group will complete" means that everything in that statement will execute even if only one element caused the condition to become false. For example, if a statement runs a second program that changes the condition part way through, the rest of that second program will continue to run. The same is true if one member of a scene causes the condition to become false. All members of the scene will still respond to the statement command.

Deleting the PLM erases all link between the PLM and your devices. If you have a backup, then you can restore those links. If not, then you'll need to add all your device to the ISY. There's no need to restore the PLM because it has no records.

I use a 2-wire extension cord cut in half with the plug end going to the device being tested and receptacle end connected to the load. I also plug a lamp into the receptacle. On a 2-wire extension cord, the side with the rib is neutral and the smooth side is line. On a 3-wire extension cord, the wires are color coded. BTW, a ground wire is not needed for testing.

A state variable can be a triigger, an integer variable cannot. So, if you run a program, then the program can test if an integer variable has a particular value. But you can't run a folder, so you can't test the value of an integer variable. A state variable doesn't depend on running anything. If the value of the state variable becomes true, then then the program runs itself and/or the programs in a folder are permitted to run.

There's no doubt that the program ran. Did you actually do a search (Find/Replace) for the errant program? Post the program, too. And the folder condition.

Do you have another program that refers to the one that should not have run? Tip: You can search by right clocking on My Programs, selecting Find/Replace, selecting Programs.

I rarely issue a direct command to a device. Also, I wanted to keep the program simple. This is the program: If Control 'IN / Devices / IN Front BathFan' is switched On Or Control 'IN / Devices / IN Front Hall KPL Light / IN Front HallC BathFan1' is switched On Or Control 'IN / Devices / IN Front Hall KPL Light / IN Front HallD BathFan2' is switched On Then Wait X minutes Set Scene 'IN / Scenes / IN Front BathFan' Off Else - No Actions - (To add one, press 'Action')

Each time an On is sent, the timer restarts. (In my case, there's a fan scene) If Control 'Fan' is switched On Then Wait X minutes Set Scene 'Fan' Off Else - No Actions - (To add one, press 'Action')

An occasional red amidst green happens occasionally. RF communication between the devices is good, but not great. If you can get any two devices to respond correctly in both directions, then you have effectively bridged the opposite legs of the split, single-phase electric supply. It doesn't matter how other devices respond to the 4-tap test.

A device has powerline connectivity if it's connected to the powerline. There is no test that determines whether or not the signal is being interfered with. Only trial and error can solve that problem. The beacon/4-button test is a test of RF only. If the responding device blinks at all, then there is RF communication from the initiating device to the responding device (it's a good idea to test in both directions). If the responding device remains unlit, then there is no RF communication between the devices. That does not mean that there is also no powerline communication. The color of the responding LED is used to determine if the devices are or are not on opposite legs of the split, single-phase electric supply.