oberkc

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.

I agree with the others...if you believe that the primary purpose of insteon and the ISY is to turn your phone into a light switch, you have missed the point. A properly designed house already has light switches in all the right pkaces, no? The power of the ISY is the ability to design a system where one does not have to turn on the lights at all, or turn them off. Alternatively, to provide one-touch activation of scenes....thus, the "automation" part of things. -lighting that comes on and off by itself, at the correct times. -scenes for various activities...movies, parties, wake-up, midnight snack, vacation, dinner, nighttime, etc... -lighting that reacts to events, such as arriving home, opening doors, playing a movie, or motion -simulation of activity while away -control of seasonal lighting In my mind, these are the basics of home automation and are completely independent of cell phone control. The deeper possibilities are, to me, a sales point only as a growth path for the future.

There are no subroutines, per-se, but one can call other programs from a program statement. Programs, individually, are IF-THEN-ELSE. I expect no problem creating a program that would accomplish your goals. If your current program forces a device to revert to a prior state, then I suspect your program is more complicated than it needs to be given your stated objectives. A simple program such as: If Time is from midnight To noon (next day) Then Turn on lights Else Turn off lights Would accomplish exactly what you describe.

I have two of the harmony hubs. No problems regarding interference. I expected none and have noticed none. Add the harmony hub without worry, I say. Furthermore, I find the hub to be the best universal remote I have ever seen and highly recommend it. Pick the elite if you value the ability to access favorite channels with one touch and don't want to use an app on a phone. Otherwise, the basic remote is quite nice. The only other remotes that I am happy with are apps on tablets communicating to the TV via itach IR devices. There are benefits and drawbacks to this approach, but I like this as well as the harmony dedicated remote. Communication FROM the hub would be relatively straight forward via IR. Program the ISY to recognize certain IR commands from the hub, and it becomes nothing more than a simple program to trigger lighting scenes from your Logitech harmony. Like the others I have made no attempt to communicate from the ISY TO the hub.

My initial inclination is to suspect two possibilities: - ON level is set to zero - communication problems - link records messed up Failure of the scene test tends to support the second or third possibilities. If you right-click on the device and "show device links table" (under diagnostics) then "compare" does it show any mismatches? Have you confirmed communication between legs of your electrical system via the beacon test (in some of the dual-band device manuals)? What else is plugged into the circuit that powers the PLM?