oberkc

I would not be looking at access points for any issues you are having with hop count. I would look, instead, for powerline communication problems.

I mounted mine on the door frame, low, near the floor. It is not necessary to mount it to concrete.

I agree that the included instructions don't apply when using an ISY-99. I also found the instructions regarding the colored wires to be confusing, at best. I am not sure that i agree that these terms don't apply. NO would apply your second example, in my mind (close when magnet is near). NC would refer to your first example (closed when magnet is away). I suspect, too, that much of your issues are related to the way the IOlinc operates outside the control of universal devices. The relay, for example, does not report status.

I am curious which "box" you have...is it the signalinc? Is it wired into two breakers from your panel?

Are you sure that it is necessary to include the "stop program" command? My recollection is that initiating a "run program" will interrupt an ongoing wait statement.

is your variable defined as an "integer" or "state"? I believe this program would work as you expect if the variable is a "state" type.

Perhaps, also, that program is being called by another program, such as: if ... then run sunset program

I understand that integer variables will not TRIGGER a program evaluation, but STATE programs will. For example, your program C1 has in it only a condition based on an integer variable. If my understanding is correct, this program will NOT execute, because there is nothing to trigger an evaluation. Perhaps this is why your series of programs is getting stuck? But, as I said, I have yet to need variables and can speak only based on things I have read around here. Hopefully, others can confirm this.

I stared at this set of programs for a while and am having trouble following the logic. What is the purpose of the two variables? Perhaps including some explanation as to the purpose of the various programs would help spur broader response. I don't use variables in any of my programming, but I understand there are two types: integer and state. What types are your two variables? If integer, this could explain why you are not getting the response you expect.

It could be a lot of things, but my first thought is to make sure you have the latest version of firmware for the isy. I recall the bulb being added relatively recently.

This is how I would do it. I understand that there is no such thing as "scene status", so one must look for triggers from the individual scene controllers. No better way is coming to mind.

It works with mine. Please note that both have sections in this forum, under third party products. I would imagine, also, that one could find a good description on mobilinc at the app store and play store.

I use mobilinc. I also continue to use conductor, but I understand that it is no longer supported.

Good catch. I forgot about the bulblinc option.

My understanding is that zigbee support IS pretty limited. If I recall correctly, I believe it may be limited to certain energy monitors. Hopefully, others can confirm with greater certainty. This allows all the apple fans to start claiming that the iPhone is the first device to allow one to control a lightbulb through their smartphone.

I agree with bmiller...this likely does not come directly from a panel, but another fixture or outlet. The wiring you describe is pretty common based on my limited experience. It is known as a switch loop. Yes, an inlinelinc is likely your only option without running additional conductors.

That was my assumption, but I was not certain. Given this, I agree with your conclusion: I don't think this statement will accomplish the desired goal.

LED christmas lights can sometimes glow, as well. If you get enough strung together, then not. Some have suggested plugging in an incandescent nightlight into the same outlet. Others suggest plugging in an unused power supply or charger. Others appear to go as far as to add a resistor. If you have glowing LED problems, try one of those approaches as your skills and interest dictate.

If you did this, then the outletlinc will turn on and off with the keypad button. Effects from programs will be in addition to this. I am not familiar with the statement "stop program". Does this stop any ongoing execution of a program, or more broadly disable the program? My assumption is the former, in which case, this may not do what you expect. What are you expecting to happen when "keypad linc D" is switched on, if anything?

on mine, top is switched. Agree on the concern about the test load. If it is a low-power LED, it could continue to glow, even when off.

Tedious is the word I would use. If I had multiple programs that required seasonal adjustments, I would probably go ahead, but I have basically two folders that use yearly conditions, and it is not that difficult making the once-per-year adjustment. I think you are making a good decision (for now) to skip the variable approach. Become proficient with some of the basis things: the boolean logic (and, or, parenthesees, if, then, else), understanding what triggers a program, knowing the difference between "status" and "control", avoiding loops, effects and consequences of "wait" statements, etc.... Once there, then relook at the suggested variable program.

I believe apostolakisl is absolutely correct...your program will not perform as you expect. With hope that this will help better understand why... There are program triggers (when will a program perform an evaluation) and program results (what are the results of the evaluation). Triggers and evaluations are both dictated by the program conditions (if statement). Your first program will trigger twice, and only twice: on January 4th 2013, and on December 15th, 2030. This program will do nothing between these two points in time. Once triggered, the evaluation will be "true" on the first date (thus running the "then" statement) and will be "false" on the second date (thus running the "else" statement). Bottom line...this program will turn your outlet on when january 4th 2013 rolls around, and will do nothing (empty else statement) in 2030. It will be, simply, a one-time event. Your second program has a couple of problems. First, it will run (trigger) continuously between the "from" and "to" times, meaning it will run from 2013 until 2030 without stopping each January. Second, it will ALWAYS evaluate as "false", because it can never meet both conditions at the same time. This is because you chose "AND" rather than "OR". "AND" requires both conditions to be true in order for the entire condition to be true. Because of this, the second program will do nothing more than send out "off" commands four times daily between December 2013 and January 2030. I also agree with apostolakisl that, short of writing a bunch of amazing programs such that he has done, I have not found a way for ISY to handle your sort of problem. I have taken a different approach. I have simply decided that I am going to be accessing the ISY several time a year regardless, and that I am too lazy to generate the set of programs necessary. Therefore, I simply create a single-year program for holiday lights, and update it each year.

I use keypad buttons as conditions in programs. These keypad buttons are not part of any scene that I created (besides, apparently, the one described by LeeG as a consequence of adding the keypad to the ISY database). The ISY appears to have no trouble keeping track of status.

I apologize for being unclear. The intent of my question was to as about the consistency in the AMOUNT of time she takes, not the start time. For example, does she ususally take around three hours to accomplish her tasks? If so, how about returning the thermostat to energy-saving mode three hours after she enters her elk code?

How about time? Is the cleaning lady consistent in the amount of time it takes? How about motion? Lack of motion for a set period suggests the cleaning lady has left.