oberkc

Are you speaking of accessing your ISY outside your home network? have you enabled internet access? When you do so, a window will pop up giving you the address. I recall, also, that address being available under the configuration tab. You can't get to the admin panel, but you can see your devices and programs, etc....

Like sub-routine, I use sunrise and sunset. One could also use motion sensors (with built-in light sensors) to transmit a signal when "dark" to trigger the lights to come on. I understand that weatherbug also includes a configurable dark parameter which could be used to trigger lights (requires the weatherbug module).

No. This would be a code violation. If dimming is required, the plug-in modules are your only option.

That is probably the best way. Scenes are not avaailable as program conditioms.

Looks good to me. I don't believe so The two options of which I am aware would be motion sensors or weatherbug data. Motion sensors generally have light sensors. Weatherbug data requires the additional module, My gut sense would be that weatherbug data might work a little better, in that I understand that you could better define "dark", using some scale (0 - 100?). On the other hand, depending on where you live, you may not have a good source of data close by.

Your program condition will evalate at these points. The results will be dependent on the entire set of conditions of your program. If this is the only condition in your program, then it will do as you say.

I agree. The programming would likely be pretty straight forward. if status "pump sensor" is on then wait duration of time notify else Unfortunately, I have no direct experience with any 220V sensor.

Just in case this has not been clear to you, scene settings (on and ramp rates) can be different, depending on which controller is initiating the scene. In the ISY admin panel, look at the device tree. Choose the scene, itself, and confirm the settings. These are the settings when controlled by the ISY, such as manually or from a program. Now click on the controller keypad device button within that scene. Are the scene settings the same? These are the settings that will govern the response when initiated by the keypad. Check the setting for the light in question.

The fact that you were successful with one tends to rule out procedural issues. In my mind, this leaves hardware failure (batteries?) or communication problems. Assuming that you do not have a hardware failure: How much farther away is your second triggerlinc from an RF reciever (access point, dual band device) than the first? Do you have more than one RF device and are they on two legs of your electrical system? Have you tried locating the triggerlinc near the first, to see if you could link from there?

I generally find an outlet behind the bed and use extension cords, as necessary. Hopefully, you have such an option. What are you using as controllers?

Plug both into the same module?

It sounds like you have the bug. We may have to start an ISY-anonymous.

This sounds like one of those pesky PLM problems. Besides unplugging and plugging back in, I cannot help much. Be sure cables are securely connected, and in the correct places.

I believe it doesn't matter. I think the IOLinc has terminals for both possibilities, so you simply connect your existing sensor to the terminals that work for you.

Yes, it does (provide nice interface). Yes, it does (keep track). It takes time and thought for all of us.

I had no idea there was a limit to the number of programs. Regardless, I am quite confident that each program in the folder counts towards whatever limits there may be. While I am sure one can get to 300 programs, I suspect one would have to be extremely extreme (or extremely inefficient) to reach this.

Based on reading of this forum, it seems the response you got from smarthome is a common one. I find it interesting that they claim not to be experts on the ISY, yet are pretty quick to blame it. Given the way you created programs, you are correct. There is no reason to have any of the KPL-A buttons controllers in your second scene. The program takes care of that. However, I suspect you are seeing a slight delay in your device response due to the reliance on programs. I believe you can experience a quicker response by taking better advantage of scenes. I think I would keep your "all lights KPL" scene as is, with the four devices as responder. To your "All Lights" scene, I would add the four KPL-A buttons as controllers. After this, eliminate your second and third programs. Having the KPL-A buttons as controllers in the scene will cause the scene to come on and go off without a program, anytime one of the KPL-A buttons is pressed. It will also keep the KPL buttons synced. Keeping the first program will still toggle the KPL-A buttons to be on anytime one of the other devices is switched on locally. Fortunately, the way I understand insteon to work, this will not cause the entire "all lights" scene to come on. I think you will find this approach to be faster and simpler. I have no definite explanation why adding the fourth KPL did not work (I think it should have), but cannot help but suspect that there are residual links or X-10 addresses in some of your devices. Without knowing more about how it failed, though, this is just speculation.

My suggestion is to start with the wiki. Your desire is a pretty common one. It is also a capability I have incorporated into my own system. Here is the link: It is based on a keypad, which I believe to be the best insteon device to control a garage door. Yes, it involves "scene". One makes the keypad button a controller of the IOlinc. In a second scene, the keypad button a responder to the relay. Check it out and see if it makes any sense.

My suggestion is to start with the wiki. Your desire is a pretty common one. It is also a capability I have incorporated into my own system. Here is the link: It is based on a keypad, which I believe to be the best insteon device to control a garage door. Yes, it involves "scene". One makes the keypad button a controller of the IOlinc. In a second scene, the keypad button a responder to the relay. Check it out and see if it makes any sense.

I can probably answer a few of these questions... When the ISY boots up, it can request status from the devices in your "my lighting" list. I guess this gives you the option to enable this capability. You can also schedule a query. Check your programs. I suspect you have a scheduled query already. I would expect forums to be a place where we can all share our questions and experiences. I would expect the wiki and user manuals, instead, to be the places where explanation of features and use is likely found. From the wiki: "In the new firmware, a program which is set to run at startup will likewise evaluate the If condition to determine which path to take, defaulting to the Then clause in the absence of a condition. " I would expect such a program to run only immediately after a startup, only once (until next reboot) and, in your case, to execute the "then" statement. It sounds as if yours will do as you want. Again, I tend to view the wiki as this document.

When breaking the timer portion into a separate program without conditions, the timer continues to run even if the first program turns false (such as at sunrise). Given my suspicions that your program will not work as you desire, I guess this makes it "better". Could it be done with one program? Maybe. I just find the two-program solution to be simple and elegant. If you want a single program, you might try: ( Control 'Driveway_Motion1-Sensor' is switched On or Control'Driveway_Motion2-Sensor' is switched On ) And From Sunset To Sunrise (next day) Then Set 'Driveway_LightsPath' On Wait 10 minutes Set 'Driveway_LightsPath' Off Else - Set 'Driveway_LightsPath' Off The difference with the two-program and single-program approaches it when the light comes on less than ten-minutes before sunrise. The two-program approach will keep the light on for the full ten-minute countdown. The one-program approach shuts the light off at sunrise, regardless of how long it has been on. BTW, if asked what is the most common programming question on this forum, I would guess it to be related to motion sensors. It is well worth a search and review. There is also a good article in the wiki.

I suspect that you will find that new coding to be faulty, as well. While you don't believe that this is the cause of your problem, I can think of no better theory at this point, so perhaps it is worth an experiment. If you are up for it, try something like: If ( Control 'Driveway_Motion1-Sensor' is switched On or Control'Driveway_Motion2-Sensor' is switched On ) And From Sunset To Sunrise (next day) Then run "new program" (then path) Else - No Actions - (To add one, press 'Action') Create a second program, called "new program" (or whatever you want): if then Set 'Driveway_LightsPath' On Wait 10 minutes Set 'Driveway_LightsPath' Off else See if this solves your problems. Don't forget to get rid of your other program.

Probably. My recollection is that the configurable EMail message came along somewhere 2.8.1x Postscript: list of enhancements for each build: http://forum.universal-devices.com/viewtopic.php?p=6475#6475 Looks like configurable EMail came in 2.8.7

Not in my estimation. You condition requires BOTH the parenthetical condition and the sunrise/sunset condition to be true (because of the AND statement). When sunrise occurs, forcing an evaluation of your program's "if" condition, it will evaluate as false, because it is not between sunset and sunrise. This is the case, even if the parenthetical-grouped-or condition is true for any reason. In fact, is this not exactly how you designed it? You do not want it to trigger ("then") between sunrise and sunset, correct? Is this not the sole purpose for having the sunset/surnise condition? Therefore, any evaluation peformed between sunrise and sunset will, by design, be false, and run the "else" path. Alternatively, what do you expect to happen if the motion sensor detects motion at sunrise + 1 second? Would you expect the program to evaluate as true, or false? Why?

I believe the universal devices wiki represents the users manual. Status represents the last run of the program, regardless of how long ago. A status of "true" indicates it last run the "then" condition. A status of false, "else". Regarding the email question, I understand that customizable message were part of a recent software upgrade, but I have not investigated personally. Which version are you running?