oberkc

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?

My initial reaction would be to break this into two programs (I will let you figure out the variables and alarm system resources). If door is open and door is not closed then turn on light else enable second program run second program (then path) second program (normally disabled): if motion sensor is triggered then wait 2 minutes turn off light disable second (this) program else nothing Are there going to be cases here where you may have manually turned on the lights and want them to stay on regardless of whether the door subsequently opens or closes? Perhaps what you should consider is to put these into a program folder with a condition such as: If third program is true then run the programs in this folder third program if control light is turned on and control light is not turned off then nothing else nothing Hopefully, these give you some ideas how to proceed.

Kman, I don't believe that this was an insteon motion sensor (at least it was not stated as such). It sounded like a motion sensor wired to some security panel which, in turn, triggered the variable.

Only the iOS version of mobilinc supports the viewing of cameras. Android does not. I use IPCamviewer on my android phone and tablets to view cameras.

OK. This makes sense. Simple option is to tart the timer after motion is last seen. If Laundrylight is 1 Then Turn light on Else Wait 5 min Turn light off

Yes. Treat the ON and OFF buttons as a single insteon switch (apparently with the default name of "on", but it can be renamed anything you want). The progrm statement is no different than with any other switch.... If Control/status " on" is set off Then Do something

To expand upon jerlands suggestion, make sure you use CONTROL keypad is off. STATUS will not work here.

Is there a problem with temporarily unplugging the power strip? Plug the ISY into the other outlet. See if this works. Surge suppressor power strips can cause problems. Security systems? I don't know. Does the security system have a UPS?

Regarding breakers, I vaguely recall an option that yokes two breakers together in such a way that it would not be possible to disable only one.

My experience is that insteon is more robust than x10 and if x10 works, insteon will. The only exceptions that I can think would be if one has an x10 phase coupler that messes with insteon, or if one tries an insteon device in a new location. Regarding the latter exception, are there other gadgets or devices on the circuit that powers the PLM? If you put an x10 device at this exact location as the PLM, can you control it?

Do you currently have an x10 phase coupler? Some can interfere with insteon.

Ah...the real mystery comes out! I will start here. I know that I can stare at things and not see stuff, but it appears to me that the "IF Logic" is NOT the same. The variables in each are different, to start. The variables in one program start with $area_outdoor..... whereas the variables in the other start with $area_indoor.... I notice, also, that the FROM time in one is different (sunrise-9 minutes) than the other (sunrise). I notice, however, that the variables have not change since the day before, according to the variable list. I do not see this as a cause of the mystery logs, however, but thought I would mention it in case it rang a bell in your head. Like LeeG, I notice the indoor program last run time was after last finish time, yet the program is not active. Interesting (but I don't understand it). Does the "Device Control Programs" folder or the "Christmas" folder have any conditions associate with them? I agree that any changes in conditions should have affected both programs, so I don't see this as a factor. I don't see any real utility to the wait 999 hour statement in each program. The lights will cycle on and off many time before the 999 hours expire. Have you experienced times where the lights don't turn off as expected? These do not look like programs and variables from a "novice" programmer to me. Are your programs consistently working as expected, even if the program status table has these unexplained or misunderstood anomalies? Are the devices coming on and off as expected? I don't see anything programs that depends on knowing whether a program is active.

A pretty accurate summary, in my view.