oberkc

Well, I thought momentary C would be just what you needed. According to my understanding, the proper command to actuate the door would be based upon sensor input, but you tried it and did not do this. So.... Given this, you could potentially solve this problem programmatically. Create a "close" program and an "open" program. Each program would first evaluate the status of your door and, if already closed, the "closed" program would do nothing. If already open, the "closed" program would close the door (by sending an ON command). The "open" program would work opposite this. Perhaps this approach could solve your problem?

I don't think this needs to be complicated and should not require a variable. How about: if time is from sunset to midnight <<<hopefully, later than latest sunsets and time is from 7:00pm to midnight then turn on light else nothing

Momentary C mode is the only mode that I am aware that changes relay responses based upon sensor input. If I recall correctly, there is a little LED that is either on or off based upon the sensor input. Does this LED change state when the gate is open and closed? Is the LED on when the gate is open or when it is closed? (I must admit that I am unsure why it is important to you to establish this relationship.) As you initially tried, create a scene with the sensor as controller and keypad button as responder. That will cause the sensor to trigger the keypad when the sensor changes state. No. The sensor status should be accurately reflected without a query. If not, then I cannot help but wonder if the sensor is actually changing state or, if it is, whether the signal is reaching the ISY. Having responded to these specific questions, I will offer the opinion that you might be taking a less-than-ideal approach to your problem. This is not unlike a garage door to me. It sounds as if you want a single keypad button to perform double duty: to control the gate, and to display current status of the gate. It sounds as if you want the keypad button to be ON when the gate is open and OFF when the gate is closed. I assume that the gate controller closes a circuit when the gate is anything but fully closed (that is, "open" is defined as not fully closed). I am hoping that your IOLinc sensor node is ON when the gate is not fully closed and OFF when the gate is fully closed. If these things are all true, I recommend reading the wiki article on programming for a garage door and treat this the same.

I find scenes easier to manage when it is necessary to swap or add/delete devices for whatever reason. I tend to design my programs, as much as possible, without reference to individual devices. So long as my scenes are up-to-date, I generally don’t have to change programs when a different device s introduced.

First, given your requirements, I don't believe that there can be a scene relationship between the motion sensor and switch. Make sure that there is none. I think lilyoyo1 has found good method. Use the manual toggle of the switch (on) to disable the motion program. Use the manual toggle of the switch (off) to re-enable the program (after five-second wait). if control switch is turned on and control switch is not turned off then disable motion sensor program else wait 5 seconds enable motion sensor program Then, use a program to control response to motion sensor if control motion sensor is switched ON then turn on bathroom light wait some nominal period of time turn off bathroom light (note...this motion program will retrigger every time motion is sensed. So long that the retrigger is within the wait period, it will restart the wait clock. Also note, it may be useful for you end-of-day cleanup program to re-enable the motion program, should someone leave the light on overnight.)

My recommendation is to think through your requirements before programming. Programming is a lot easier when you know what you are trying to accomplish. It sounds as if you have a single motion detector and a single light switch, correct? - what do you want to happen when motion is detected? -what do you want to happen when you manually toggle the switch on? Off? -do you want thelights to turn on and off automaticaly? When and under what conditions do you want the lights to turn off?

Perhaps you could get by with a single program, but it may depend on for how long you want the fan to stay off when manually toggled...until the next temperature cycle to exceed 90?..next day?...indefinitely? Also, why do you care whether the fan is off (or on low) as a decision factor? If it is hot, turn on the fan!

There is no way to use a scene status to trigger anything. The theory is that there is no such thing (or at least a consensus on what constitutes) scene status, on or off. For this, I pick a few key members of a scene and use those as indicators that a scene is on. To be clear, this is true only if there are wait states or repeats in the program. Otherwise, the program continues to completion. i tend to do things much like lilyoy1...if I have an event that I want to supersede the motion sensor, then I disable the motion program. This likely requires all motion events to be program-driven rather than scene-driven...it is not easy to tell a scene responder to stop being so.

No programs running at the time of the opening garage door? Hmmm. I would certainly look at scenes per paulbates suggestion. Click on the IOLinc relay from the admin panel and see if is unexpectedly part of a scene. I suppose you could remove the IOLinc from the ISY and perform a factory reset. Before adding it back, observe if the door stops opening by itself. If door continues self-opening, it sounds as if you have external factors in play. If door ceases the uncommanded opening, add it back to the ISY (not adding it to any scenes or programs) and see if the door start the uncommanded actions. If so, this points to some interaction between the two. If not, add it back to your scenes. Continue this process until the problem appears again or, better yet, this solves the problem. If it happens regularly at a predictable time, open the event viewer and watch for clues at that time. Or, if you know when it happened, check the logs for insteon commands (not just programs) at the times when the door opens. I assume, also, that you are not experiencing everything turning on...just the GDO. Correct? I was wondering aloud whether you are seeing the results of one of those ALL-ON issues.

I do not think anything has change in the new 5.x software here. a "status" condition would trigger upon any CHANGE in status, whether from ON>>>OFF or OFF>>>ON and would trigger both THEN and ELSE actions. I believe this is true in software v4x and v5x. "Control" conditions, however, would require the "not" condition in order to cover both ON and OFF commands. All the confusion I have noticed over the years is in regards to the "control" conditions.

If this program is running true regardless of KPL-B status, I would consider the possibility that the ISY is not seeing the actual status of this keypad. This program should run true only when the motion sensor is switched off and KPL-B is OFF at that time. If something else is happening, I do not see this as a program problem.

Yes, you used parentheses around BOTH. The difference is that the first program has no "or" conditions. Consider the following logical statement: "I will go to bed when I get home and lock the doors or when I get to a hotel". What conditions must be met in order for this to be true (to go to bed)? Either: 1) go home and lock the doors, or 2) get to a hotel. If "go home" is condition A, "locking the doors" is condition B, and "finding a hotel" is condition C, this would be written as: A and B or C. Do you remember math from elementary school? The results of 3x2+4 are different than 3x(2+4), right? The same is true in logic...A and B or C has different results than A and (B or C). This is mostly true. For the second code to be true, either 1) $Int_1 must equal 1 and it must be between sunset and sunrise and side sensor is switched on or 2) patio sensor is switched on or 3) west gate sensor is switched on I have little doubt that Larryllix has found your solution

Well, I would have to assume that something triggered your program "garage lights on" (then path) at 8:30. Twenty minutes later, the lights would turn off, as programmed. Given your first program, the only way (from the programs you have shown) that this could happen is that , at 8:30pm, $int_1=1, sunset has already occurred, and someone must have triggered the driveway sensor. The value of $int_1 at 8:50 is irrelevant. You likely have a misplaced parentheses. Why do you bracket the entire condition in parentheses? Given the way it is currently written, "rear motions active" will be true any time that "patio" or "west gate" sensors are triggered, regardless of the state of the variable, sunset or sunrise, or how much daylight there is.

Personally, I don't think the order matters in this case. Your conditions were joined by "and", so all must be true. Order should not matter. I can see some cases, where one is not careful with "or" and parentheses, where order of commands could matter, but not here.

There is no limitation that I am aware that would keep you from doing this. I also believe that this must be done via programs. I am with lilyoyo1 on this. Logically, you want HHPD to be on if either of the other two buttons are on, and you want HHPD off if both of the other two buttons are off. The program would look something like if status HH is on or status PD is on then set HHPD on else set HHPD off

Probably a good rule-of-thumb, but I am not ready to say "never". Still, I don't think that is the problem here. My argument typically is the condition side of things: in most cases, I don't see a strong reason to check that a light is off before turning it on. I see little harm in turning on a light that is already on, but a higher potential of unintended consequences by insisting checking that the light is off before turning it on. In the case of proj964' program, I would simply eliminate the middle condition if I feared that the program is halting execution due to the condition flipping back to false.

I agree with statements 1) and 2). I am not sure about statement 3). My understanding is that the THEN actions would continue to completion UNLESS there was a WAIT or REPEAT action within. Since there is no wait or repeat, I expect that this program would complete the entire THEN clause, even though the condition was retriggered and is now false. I also agree that it is the upper pane that represents your program as it exists, and that I would not be concerned with the lower pane. What I don't understand is why it would, without any apparent user interaction, change a condition from "is off" to "is 100%".

I am out of ideas. I have not seen a program change itself like this.

Unfortunately, I don't use 4.X software any more, and cannot compare it to what I see on my admin panel. I recall ON and OFF program options for relay devices, not percentages, but my memory could be faulty.

Is it a dimmer or relay? I cannot help but wonder what would happen if you remove it again, then add it by putting the ISY into linking mode, then putting the switch into linking mode.

Out of curiosity, how did you initially add this switch to the ISY? What device does the ISY think it is? Is it possible that the ISY thinks is something different that what it actually is? (It is just a hunch, but I wonder if this is a possible cause of the behavior you describe.)

to set the responder levels for the remote, make sure you have selected the controlling remote button in you device list. responder levels can be different for each controller.

The problem is not because the variable remains equal to 1. The problem is more likely because, when the program turns on the light, the condition suddenly becomes false and interrupts the WAIT action. (There are also a couple of other potential problems.) A simple solution is to remove the second line from the condition. The solution I would choose is to break this into two programs. The first program would keep the existing condition, but change the THEN action to do nothing more than call the second program. The second program would have no conditions, but would have the THEN actions from the original program.

Not sure there is a “best” way. You could use a program. Lilyoyo1 points out an advantage of this approach. You could use scenes (may be a little faster and will still work should the ISY fail for some reason). Bringing the echo into the mix creates additional considerations. I expect you would need something like the portal account, or mobilinc cloud account added to your ISY. You could then configure alexa to run a program or turn on a scene.

There is. I recall it available from the right-click on the device>>>show links. This reads the links directly from the device. Once shown, you would have an option to "compare" to the ISY records. They should match.