oberkc

I don't know whether that helps battery life, but it sure seems very possible and I suspect that it would. The trick is to find the right balance here. Do want to reset the 15-30-minute countdown after each motion detection? Are you happy to wait 10 minutes to begin watching for motion again before you reset the countdown? Note, also, that there an option to select whether to detect motion always, or only after the timeout. This will also affect the frequency which the motion sensor will transmit ON commands.

No. The updated parameters are only the response levels to be applied the next time the scene is fired from the specified controller (in this case, the PLM). No. At 9:00, the program is triggered and evaluated, where it will be FALSE. Were this program executing the THEN path when this happens, any wait condition will be halted and the ELSE path will run. Since you have no action in the ELSE path, nothing will happen beyond the program halting.

Also, if you plan to rely on the program, light sensitivity settings become almost moot. If you make the sensitivity settings too extreme, you run the risk that it is technically sunset, but the program wont execute because there is still enough light to prevent the motion sensors from firing.

Great. It is as I suspected. I agree with teken...simple first. Use scenes where you can, use programs where you must. In this case, however, you want to limit response to certain clock times (sunset to sunrise), which drives to a programmatic solution. By the way, I personally use sunset and sunrise, but have no preference for time versus light levels. I can argue for either, but the differences are trivial, in my mind. If you opt for light levels, then I would skip the program and use scenes. To use a program, first, make sure you eliminate the scene between the motion sensor and lights. Regarding your program, in logic terms, you are wanting two conditions to BOTH be true. In logical construct, this would be if time is X AND (not OR, as in your original program) motion is sensed. Interrupt....I missed your updated program in post 13. You corrected the OR to AND, and added parenthesees bracketing the two motion sensor conditions. Perfect! I expect this program to work exactly as you desire. I would take, however, one additional step...create a single scene with your four lights, all as responders. Adjust your prgroa, to turn on/off the scene, rather than the individual lights.

I SUSPECT you have some logic problems, but it is hard to say for certain without knowing WHAT you want to accomplish with this program. What do you want to happen at sunset? What do you want to happen at sunrise? Do you want the lights to respond to motion at all times, or only at certain times? Your particular program will turn the lights on at sunset (then off 20 minutes later), and will turn the lights on (then off 20 minutes later) when motion is sensed by either sensor. If the lights are on at sunrise, your program will turn them off. Making the changes suggested by teken will restart the 20 minute timer (if running) at each detection.

N8huntsman... Your program, you have a "set scene 'outdoor bar lights' on" statement initially, but fail to include the same statement after each 30 minute interval. This statement is required at each 30 minute to activate the scene at the new levels. I don't see any advantage to using multiple scenes and programs versus your creative approach. I see nothing in your program that turns the lights off. Understand, also, that if 9pm occurs while this programs is executing, it will halt.

Wow. So this is a program to keep mobilinc in line? I guess if it works for you, it is hard to argue. Certainly not a problem I have ever experienced.

While there is no question that the reliability of insteon is not 100%, I believe that this problem is solvable if you want to keep trying. There remains many questions that continue to float through my head (perhaps I missed all this discussion earlier). - what are you trying to accomplish by putting the IOLinc on the door? Is it simply a notification that the door is open or closed (if so, leave the relay disconnected)? - why do you believe you need the status of the relay? Does it serve some purpose in another program? If you have a program who's purpose you don't understand or can't remember, perhaps it is time to rethink the approach. - do you desire to remotely actuate the door, via phone or other device? If so, via what app? Do you simply trigger the IOLinc relay directly or a scene or a program? - do you have a "query all" program (possibly to trigger at 3:00am)? - is the IOLinc part of ANY scene? My temptation would be to temporarily disable that "Overhead Garage door relay off" program. Unless there is a known purpose for it, this program strikes me as suspicious. From there, I would consider taking a fresh look at your objectives. Perhaps it is time to clear out existing programs and scenes with the IOLinc and start over.

Is this what you WANT, what IS, BOTH, or NEITHER.? The decision of scene versus program comes down to what you WANT to happen. If your desire is to limit response to motion to certain TIMES (clock), then a program is your only option. If you want to limit response to motion to periods of lights as detected by the motion sensor, then either a program or scene can accomplish this, all dependent, as stusviews notes, the sensitivity setting of the motion sensor. In fact, the motion sensor, itself, can limit response ONLY based on ambient light. If you want conditions beyond this (time, home or away, manual intervention, override), you will need a program. My perceptions over the years reading posts is that many don't spend enough time deciding what they want to happen. My recommendations are to consider the possibilities. Are you happy with motion sensors that trigger always, or during the dark? Do you want the ability to manually override the motion sensors and leave the lights on until you choose otherwise? Do you want the ability to manually disable the response to motion , should the need arises? Do you want the lights to stay on so long that motion is continuously detected? Would you rather limit response to time?

The other day, I think I saw some bulbs that connected directly to a bluetooth device (presumeably, phone or tablet). I was not that interested so I did not take a lot of mental notes. I bring it up only as an example of a bulb that requires no hub. Range, obviously, would be more limited.

If your lights and sensors are in a scene, then there is no reason to have a program to turn them ON. On the other hand, deleting the scene and using a program can add great flexibility to when the lights turn on and off and at what levels. If you have a program AND a scene, then you have the potential for some unexpected results.

If your program is not causing your lights to turn off when the motion sensor sends the off command, yet the lights still turn off, the only explanation I can think is that your lights and sensors are in a scene together. Is this possible?

Forgive the stupid question...does scene "all on off" include the IOLinc?

I do not believe there is a way to "SYNC" the remotelinc, for the resons stated earlier. A programmatic solution would not sync it either. Instead, I would take a different approach. First, I would take the remotlinc out of the scene. Second, I would consider putting the remotelinc into non toggle mode (not absolutely necessary, but may help simplify programming). Once done, a couple of programs such as: If control remotelinc is switched on (Or off, depending on toggle mode of remotelinc) and status keypad button is on then turn off scene else nothing If Control remotelinc is switched on and status of keypad button is off then turn on scene else nothing

What "phase coupler" do you have installed? When performing factory reset, I am not sure if lamp plugged in matters. When adding to ISY, only hold button until first beep.

I am not sure that the remotelinc, being a battery device, listens for insteon signals (other than when in linking mode). Therefore, I do not believe the remotelink will act as reponder and stay in sync. A programmatic solution may be only option.

My experience is that there is little to do to speed up programs. On the other hand, total response time is also impacted more noticeably by communication delays between the various components, including the PLM. Since programs require communication first from the trigger device to the PLM, then from the PLM to the responder device, program responses will take longer and there is not much you can do about that. My guess is that if you are seeing a difference between a direct scene response and a program response that is a second difference, that you are probably not going to be able to improve on that too much. If it is two seconds or more, I would focus on optimizing your electrical system so that communications are as good as they can be.

Larrylix, Your example, then, begs the question: what is an "executive"? Certainly, the ISY can CALL other programs manually, or within programs (aka nested if, or subroutine). So, how does " executive" differ from "surprise magic"?

I was not suggesting elimination of the program. Instead I suggested elimination of the variable, using program status (true/false) in place of the variable (0, 1) as the program condition.

I can see nothing wrong programmatically. I expect the variable to be 0 at sunrise to sunset, and 1 from sunset to sunrise. It is not doing this? Is it possible that you have other programs that are triggered by this variable and affecting the value? Next sunset, check to see what other programs run besides this one. Perhaps one of those programs changed the value back to 0? FYI, I find little need for this variable. I would simply have a program: if from sunset to sunrise then nothing else nothing Then, I would simply use program status (TRUE or FALSE) as a program condition to indicate light or darkness.

Do I understand it correctly that your micro modules are turning ON, but not OFF? Have you tried temporarily removing the LED bulbs to see if that improves response?

I definitely would not like the motion sensors showing the 1011 symbol. Are you putting them into linking mode when you attempt to write updates? How close are they to the nearest dual band device? Still, the motion sensors do not sound like the cause of your problem if the lights are turning ON in response to motion, but not OFF in response to a program timer. Did you test your micro modules or only the motion sensors? What load is on the micro module? LED? Fluorescent?

I think that if I were interested in controlling my lights with the harmony, I would simply do so via IR. Teach the ISY a few IR commands and create a couple of simple programs...instant control.

It speaks insteon hub, I understand, but not plain insteon.

This is my concern, as well.