oberkc

Yes, a bit of overthinking here in my estimation. Ironically, it seems that it is often those with many years of programming experience that have trouble. It seems to me that many come in with assumptions about how the ISY works, based on experience with other operating systems and languages and, when the assumptions fail to hold up, confusion reigns.

Did not know that.

agreed.

Think of “next day” being relative to start time. Alternatively, consider the logic without “next day”...from 10:00pm to sunrise...would that suggest a start time AFTER the end time? remember, too, that there is a day-of-week aspect to this condition. Is not the full condition more like: on monday, from 10:00pm to sunrise (next day) Besides....it is less important what you believe and more important what the ISY believes. Even if you find it grammatically ambiguous, the ISY does not.

No need to do this. I don't believe there is any ambiguity. "Between 10pm and sunrise (next day)" is unambiguous. I do not see where lilyoyo1 claims it will "run else". Of course, your original conceptual program was pretty simple, but you have not posted the actual program. Furthermore, you later mentioned motion sensors which were not part of the original post. As programs include additional conditions, it can oftentimes be harder to figure out all the different triggers and logical conclusions.

There is a condition where an insteon device condition "responding is true/false" might be useful for such a program. I have not used it before, so I can only theorize. I am unsure how the ISY-994 would know whether a device is responding, but I assume that it would depend upon the frequency with which something has tried to communicate with a given device. There is also a "query" option for insteon devices. Perhaps a program running at some period of time (every hour, for example) you could query a device, hoping that frequent queries would quickly identify "non responding" devices. Then you would create a program to send a message based upon a condition that a device is non-responding.

If your only purpose is to turn lights off, I would have it in "non-toggle (off)" mode. Every press of the button sends an OFF command. But...this does not necessarily explain why it once worked and now does not, unless you think there is a possibility that this changed somehow.

I don't see anything in the programs that would cause the problem you describe. I am of the same mindset as apostolakisl...if pressing the keypad button does not turn it on/off, the button is either not in a correct toggle mode, or it has failed. I would take the steps he is recommending. Before that, confirm the button is in "toggle" mode or "non-toggle - off" mode. Additionally, open the event viewer and watch it while someone presses the keypad button. Does the event viewer register any commands? Does the keypad button flash when pressed?

This is consistent with my experience regarding how the app SHOWED the settings in response to a voice command. For me, however, I cannot control fan manually. Specifically, if I try to set the fan to medium, it starts at level 2, but reverts to level 1.

I am also more an Alexa user, but do have a single google home device. As near as I can tell, Google Home routines are triggered exclusively by voice or time. I do not see a trigger based upon a device or variable.

It appears to me that there are two sets of wire pairs coming from this device. One pair connects to the opener. The other wire pair connects to a dry-contact button. In essence, it looks like an additional wall remote where someone has already soldered leads to the buttons.

I notice that the second-generation insteon motion sensor has the option to power via usb. I did not know that battery motion sensors did not update status properly.

In addition to the response from lilyoy1, I would add that (unfortunately) not all z-wave devices have light sensors. At least, the couple that I purchased do not. Maybe others do. For the desire to trigger lights based at dusk, a couple of ideas come to mind. One, you could trigger them based upon time relative to sunset or, two, you could use an insteon motion sensor in a protected location to detect darkness (such as near a window). I have used insteon motion sensors outside for several years. I do, however, take care not to expose them directly to precipitation. I also have mostly first-generation sensors. I have experienced one failure of a motion sensor. I replaced it with a second-generation sensor. I absolutely recall that it was claimed to be rated for exterior use. I wonder what changed.

I take it from a lack of response that most, like me, cannot find a programmatic reason why your program would run true under the set of conditions described. I guess one must conclude that it is possible that something else is calling the program (then path?), that somehow the conditions from darksky are not correctly translating, or there is a bug in the ISY software. Is this program disabled? Is this program last run consistent with with the specified time at night when are calling it? When is your "$RainTodayAmountz" reset back to zero each day?

One thing that is catching my attention is that I don't see any way to extend the 30 minute time. Is this your intention? What do you mean, in statement above, "if no one presses anything"? Do you intent to have something to press in order to keep the lights on?

I understood that Z-wave devices support scenes. Having said that, I am not sure whether the ISY-994 supports z-wave scenes. I use Z-wave devices in scenes, but these scene also include insteon devices. Given this, it seems pretty intuitive that the Z-wave scene functionality goes through the controller, since z-wave and insteon cannot talk to each other. I suspect that this is true even for scenes that contain z-wave devices exclusively.

Yes, I was focusing mostly on program 1. You may be correct regarding program 2. Perhaps adding a command at the beginning of program 1 to halt program 2 would solve that problem?

Neither do I understand why you have a "'Inside / Hallway / Hallway Bathroom Light' is switched Off" in the first program. Regardless, simply pressing the switch ON again would cancel the wait condition and restart the program 30 minute count. Did you say that this was a keypad button? (I was not certain.) If so, is it a six-button or eight? Is the button triggering the program the primary (load controlling) button or one of the secondary buttons?

I just try to avoid insulation, good windows and doors, and house wrap. My air exchange happens the old fashioned way.

I don't know that the wait "fails", but you should consider the possibility that the time change retriggered you program during the wait period, at which point the program was halted. I don't know what your program looks like at this point so I can only speculate.

That is what I do. I have perceived no additional benefit with using insteon for this function, since all that I want is a simple timer, manually activated. If I wanted more sophisticated automation for the fan, I might reach a different conclusion.

Ah. I was unaware of that code. Thanks.

Code violation!? There are many, many houses with constant power to the fixture. Most of those use a switch loop to control the light, but some have a simple pull chain. There are codes requiring switches at certain locations, but these codes seem more concerned with being able to see at night rather than the inherent safety of the electrical system . I would definitley be interested in knowing what code violation this would be.

Keypad buttons have a couple of options: toggle, non-toggle (on), and non-toggle (off). The non-toggle (on) mode will cause the keypad button to always turn on when pressed. I use this mode on a couple of buttons, but I have never used it on a primary button A. Understand, too, that these "non-toggle" buttons could still be turned off by the ISY or by being a responder to a scene. I am not sure what benefit this has to simply providing unswitched power to the ceiling fixture.

Keep in mind that if you disable the folder (disarm elk) during the night, the ELSE will not trigger at sunrise+1. This may not be a problem for you, but 8 wanted to point that out.