This is the program I have. The Then path of "Dog lights" turns on 4 sets of lights. The Else path turns them off. The program does not work?

Here's the "Dog lights":

The lights did not go on at 6:20 am and did not go off at 7:15 am on a Friday (today).

Any idea why? Thank you.

Is the program disabled? We cannot see that parameter unless you copy to clipboard and then paste the program into the post.

Right click the program title and select "Copy to clipboard"

Dog lights - [ID 0048][Parent 0001]

If

- No Conditions - (To add one, press 'Schedule' or 'Condition')

Then

Set 'Deck lights' On

Set 'Pool lights' On

Set 'Deck Eaves Lights' On

Set 'Basement Double Door Light' On

Else

Set 'Pool lights' Off

Set 'Deck lights' Off

Set 'Deck Eaves Lights' Off

Set 'Basement Double Door Light' Off

Thank you. That's it above. There is a red mark on the left side of the icon for it, but we use this all the time via Alexa/Amazon Echo. It's not set to run at any time, though.

I don’t think you need the separate Dog Lights program.  You could just put that logic in the Dog Lights Away program.  But that’s not the problem.  I think it’s the IF statement.  The Mon-Fri section has no calendar entry and may be halting the program from running. If you meant to trigger on Mon-Fri all the time then check the “Daily” box when programming that part of the schedule.

Also, it will work better, if they are Insteon switches, if you put the lights in a scene and turn the single scene on and off. When you have 4 back-to-back Insteon commands, the Insteon traffic for them is colliding and affecting some of them not going on. That doesn't happen with a scene

It also turns them all on / off simultaneously which I like better, and not "popcorn" lights

Edited Friday at 12:47 PM1 day by paulbates

Well, I have the Dog lights program to turn on/off the 4 switches for outside lights. I've had 5 switches, and I'd like to keep that option open too, and maybe even 6 switches is a possibility.

I have this program and another that use the Dog lights program. So, if I don't have the dog lights program, and I want to change the dog lights to add/remove lights, I'd have to do that in multiple programs instead of one.

Doesn't "daily" mean every day? Or does "Daily" mean something else? I just want m-f for now.

I did not know that about the scenes. I could make this a scene, then redo the Dog Lights with the scenes, ensure that works, then check that the other versions work too. Let me see when I can do this.

@ctviggen1

Your time schedule is missing "same day" (see attached screeenshot)

Also what is the "on" after the times. That shouldn't be there

10 hours ago, ctviggen1 said:

@slimypizza is correct - This program is wrong. You have "on" but nothing after it. You've unclicked the "daily" button and it's trying to do it for a specific date, but you've apparently removed the date.

Like how you have it:

What you would expect to see:

The biggest thing about getting program help is understanding that when you share programs as screen shots it makes it a lot more difficult and time consuming for somebody to help. Sharing as text allows people to edit what you should see in a program. When @paulbates asked for it to be shared as text you only shared one of the two programs. Why not share both? They're equally important.

Lastly, beyond just enabled and disabled programs you need to also make sure that the folder they're in does not have folder conditions that make the folder false (i.e. not allowing any underlying program to run).

1 hour ago, ctviggen1 said:

I have the Dog lights program to turn on/off the 4 switches for outside lights. I've had 5 switches, and I'd like to keep that option open too, and maybe even 6 switches is a possibility.

One more thing...when you get to this many devices you might want to put a short wait between them so the Insteon traffic doesn't go bouncing into itself all at once. This is why it's suggested to make a scene. As a scene it will all happen at the same time (or near enough...I doubt the dogs care about the popcorn effect).

Thanks, daily does work. I had interpreted "daily" to mean every day, and I think it means whatever days you've selected and not the scheduled days.

But when did we get scheduled days? I don't remember that being a "thing". (For the last year, I've had one kid who has/had pediatric acute-onset neuropsychiatric syndrome, PANS, and was in so many hospitals/institutions she missed 1/2 a year of 8th grade, and meanwhile a senior in high school who was doing tons of stuff and going to multiple colleges. So, I couldn't keep up running the house and haven't kept up here.)

For instance, I didn't know you could copy a program into text.

I can see the scheduled days being very useful.

Changing everything to scenes will be quite a bit of work, because I didn't do that for many things. And my whole house will be Insteon once they have another sale (missing maybe 8 switches total, for things we really don't need to control).

Thanks for the help, and I'll work on changing everything (most? things) to use scenes.

9 hours ago, ctviggen1 said:

But when did we get scheduled days?

As long as I can remember. It is kind of an oddball option (IMO) since automation is ongoing; when you uncheck it the program looks for a specific date. It is checked by default on new programs (like "All"). If you uncheck "daily" it looks for a specific day for the program to evaluate on. Leaving it checked allows it to run "daily". If you uncheck "All" then you can check the specific days of the week (if you had a M/W/F schedule you would just select those days, but still leave "daily" checked so it ran every M/W/F.

9 hours ago, ctviggen1 said:

Changing everything to scenes will be quite a bit of work,

If you keep the number of devices low (like you have) then more than likely you won't have an issue. But it really causes problems (at least has in the past) when you have a program that triggers devices directly in rapid succession. Simply adding a "wait" can help eliminate possible Insteon traffic issues, but also adds another problem that if the program evaluates during a wait and becomes false (or the opposite of your "IF" condition) then the process might stop midway through the cycle. This is where scenes come in handy that turning on 1 scene (with many devices) will just turn on when the program triggers it. And scenes can have retries if a device doesn't come on (or react) it might retry to make sure it triggers. It's a personal preference at this point. If you adjust your program and it triggers okay with the few things you're turning on then I wouldn't make wholesale changes to make scenes out of everything. Just if you run into issues of only 2-3 of the 4 devices turning on or off then you've got to consider the scene as an option.

I'm like you in that I have not designed scenes in my system (aside from some keypad scenes). I usually only trigger 2 or 3 devices with a program and mostly in the off direction so it's not an issue for "popcorn" if something doesn't turn off exactly at the same time. Just a personal preference (again).