gregkinney

Yes, that is what I have done to "fix" the issues. A significant amount of my programs involve network resources and those must be spaced out about 2 seconds each in order for them to all fire correctly, so I have a slew of waits. This all makes sense now 😄

@Ross thanks, I will check that out sometime. It looks really interesting. @dbwarner5 thank you! That's great information. And it makes me angry. Goes against the logic of any other programming language I have experience with. Because it seems so backwards to me, I can never remember to use this logic and I screw it up the first time.

You're not wrong and I'm not going to pull you off the edge, however, I will say this is a 'grass is always greener' type of scenario. I had the same idea as you and attempted a switch to HA. I have also run HA for many years alongside ISY for the things the ISY coudn't do. The first thing I did was switch Zwave over to HA because ZW was SOOO bad on ISY. So many delays and missed commands. My experience with ZW on HA was that it was worse than ISY ZW. That is not everyone's experience but it was mine. The point of my story is that if you switch, it will fix some of your issues but it will create other issues. Sometimes it's worth it. I mean, the grass does come in different shades of green in different locations, right? Maybe it is a little greener for you somewhere else. Just know, it will likely not be a fix all. I continue to run ISY and HA in tandem as well as a RPi where I write my own little scripts that don't fit neatly into the ISY or HA box. I have decided this is the best approach - not cutting out any one ecosystem but using each one for their strengths.

@larryllix Thank you for the suggestion but that didn't work. I did use your idea though to simplify the program and I just picked 2:45pm so now I don't have to disable the program after it runs. @IndyMike thank you, your suggestion worked! I can never wrap my head around the fact that the 'if' keeps evaluating while the 'then' is running. Makes no sense to me. @Ross Android. It's a great app called "http shortcuts". It's free, not sure if it's on iPhone. One quick button, nothing else to do. You can pick the icon. I then also group some of them into folders.

@DennisC Yes I might have to change if I can't find a reliable way to accomplish this. But this way is pretty cool. I don't even have to open an app. The shortcuts reside next to the home screen on my phone

Just remembered I use this program by HTTP command often, and it works fine: temp hallway down 1hr - [ID 00BE][Parent 0004] If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Set 'Ecobee / Ecobee - Hallway' Setpoint Down Set 'Ecobee / Ecobee - Hallway' Schedule Mode Hold Wait 1 hour and 2 seconds Set 'Ecobee / Ecobee - Hallway' Schedule Mode Running Wait 4 seconds Set 'Ecobee / Ecobee - Hallway' Schedule Mode Running Else - No Actions - (To add one, press 'Action') #enabled

I have this program: shades down if temp over 95 - [ID 026A][Parent 006C] If 'WeatherLink / WeatherLink' Temperature > 97.0°F And From 2:45:00PM To 2:50:00PM (same day) Then Set 'Zwave / Shades - Kitchen' 28% Wait 20 seconds Set 'Zwave / Shades - Kitchen Door' Off Wait 20 seconds Set 'Zwave / Shades - Butlers' Off Wait 20 seconds Set 'Xscenes / Shades - Dining' Fast Off Wait 20 seconds Set 'Zwave / Shades - Tasha Ofc S' Off Wait 20 seconds Set 'Xscenes / Shades - Theater' Fast Off Wait 20 seconds Set 'Zwave / Shades - Mud Room' Off Wait 20 seconds Run Program 'shades study winter down' (Then Path) Wait 3 seconds Disable Program 'shades down if temp over 95' Else - No Actions - (To add one, press 'Action') #enabled The 20 second gaps are because sometimes the zwave signal seems to trip over itself - I had more success by spacing the commands out. This program runs great on its own. However, I use HTTP shortcuts on my phone to do often used tasks. So if I want to close these shades, I use my http shortcut which uses a "runThen" action from the REST API. However, it will run for maybe 30 seconds to 1 min, and then stop. It will never complete. I assumed there was a timeout or something while it was waiting to receive a completed response from the API, so I created this program, thinking it would respond immediately with a completed response: shades sun - [ID 030B][Parent 006C] If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Run Program 'shades down if temp over 95' (Then Path) Else - No Actions - (To add one, press 'Action') but it's the same end result - it runs for 30-60 seconds and stops. Does anyone have any suggestions how I can achieve my goal?

Yes, I replicated everything as before. Same LL, same outlet, the new (used) cord in the same position as previous. I will give it the weekend and then follow your disposal instructions. Good suggestion BTW. A conversation I had years ago with an insurance claim adjuster said the majority of house fires he dealt with were the result of cheap extension cords.

No strange log entries with the new extension cord. Is it safe to assume there is something wrong with that specific extension cord? And if so, is there any concern for safety? Am I ok to keep using it for other things or should I throw it away?

It wasn't wound and taped in deployment, that's only for storage. But I hear you - I'll replicate how the cord was laid out the same as before.

Ok, will be back in 18-24 hours.

I have not but I can. Just to clarify, you're suggesting plugging in a different basic 2 prong empty extension cord to see if the log entries return?

I don't have one of those but I do have one of these. Shows watts/amps/volts. Is that helpful?

What does "hang a scope" mean?

Simple extension cord!

It was the extension cord that caused the issue. I unplugged it and the repeating log entries have not happened since. Correct, it was an empty extension cord plugged into the lamplinc. It is a 2 wire, 10ft, not sure of gauge. It is on the thin side.

I did a factory reset and still had the same behavior with the logs showing on and off repeatedly. Next, I replaced the dimmer module and still have the same behavior. I'm mind blown. My next step is to unplug the empty extension cord and see what happens, then the step after that would be changing the outlet it is plugged in to. Will report back. Open to any other suggestions.

@IndyMike I went to check what type of bulbs were installed and had forgotten - we removed the two lamps a couple weeks ago so there was only an extension cord plugged in with nothing plugged in to the extension cord. We will likely add the lamps back in the future so I want to keep the module in place. I'll try @paulbates suggestion and factory reset and go from there.

I was checking my log this morning to see what time a certain light turned on when I saw this. 'Izzy Bedside Lamps' is an Insteon dimmer module 2457D2. As you can see, it repeatedly is showing the status alternating betweeen 'Off' and '100%'. It does this for many hours then stops, then starts back up the next day. The time that it starts and stops is not the same each day. The actual state of the device during these times is 'Off'. I searched my programs and confirmed that it is not involved in any programs. I was trying to decide between factory resetting it or simply replacing it (I have spares sitting in the closet) but figured I would ask here first if anyone has had this experience before. Rooms / Izzy / Izzy Bedside Lamps Status 100% Fri 2024/08/09 05:19:11 AM System Unknown Rooms / Izzy / Izzy Bedside Lamps Status Off Fri 2024/08/09 05:19:12 AM System Unknown Rooms / Izzy / Izzy Bedside Lamps Status 100% Fri 2024/08/09 05:19:15 AM System Unknown Rooms / Izzy / Izzy Bedside Lamps Status Off Fri 2024/08/09 05:19:16 AM System Unknown Rooms / Izzy / Izzy Bedside Lamps Status 100% Fri 2024/08/09 05:19:17 AM System Unknown Rooms / Izzy / Izzy Bedside Lamps Status Off Fri 2024/08/09 05:19:18 AM System Unknown Rooms / Izzy / Izzy Bedside Lamps Status 100% Fri 2024/08/09 05:19:19 AM System Unknown Rooms / Izzy / Izzy Bedside Lamps Status Off Fri 2024/08/09 05:19:23 AM System Unknown Rooms / Izzy / Izzy Bedside Lamps Status 100% Fri 2024/08/09 05:19:24 AM System Unknown Rooms / Izzy / Izzy Bedside Lamps Status Off Fri 2024/08/09 05:19:25 AM System Unknown Rooms / Izzy / Izzy Bedside Lamps Status 100% Fri 2024/08/09 05:19:26 AM System Unknown Rooms / Izzy / Izzy Bedside Lamps Status Off Fri 2024/08/09 05:19:27 AM System Unknown

Thank you everyone for your input. Yes @Goose66 I am familiar with the two-program structure and will use that moving forward to achieve what I want. I guess if I see it the way you see it, as a benefit, it can be used to my advantage. I think my black-and-white logic brain was having a hard time with that.

I found out from another forum post recently that I have been using the 'wait' function incorrectly. I had assumed that 'wait' was the same logic as other programming languages where it temporarily stalls the running program for a period of time. But @TJF1960 pointed out that if there is a 'wait' in the 'then', the program will re-evalate if the 'if' changes. My goal in some of my programs is to have a 'wait' in the 'then' which will simply stall the program for a period of time, and not keep evaluating whether the 'if' is true during this 'wait' time. Can someone help me accomplish this? My only thought was if it was split up into two programs, where the second program did not have any 'if' logic to evaluate. Wondering if there is a cleaner way. I have noticed that if the 'if' is a time, it will still use the 'wait': living kodi clean nightly - [ID 0272][Parent 0073] If Time is 3:33:33AM Then Resource 'living.kodi.on' Wait 6 seconds Resource 'living.kodi.clean' Else - No Actions - (To add one, press 'Action') #enabled And also, for some reason this works: office bath fan 7.5 - [ID 0159][Parent 01C2] If 'Rooms / Office / Office Bath Fan' is switched Fast Off Then Wait 2 seconds Set 'Rooms / Office / Office Bath Fan' On Wait 7 minutes and 30 seconds Set 'Rooms / Office / Office Bath Fan' Off Else - No Actions - (To add one, press 'Action') Which leaves me thoroughly confused.

@TJF1960 I understood wait was like when I write a sleep function in python...it would literally keep the program in the current state until the time passed. Thank you for educating me otherwise. I've got a few programs to go re-write and a lot to learn. @EWhite I'm sorry to have hijacked your post with my ignorance. I hope you get it figured out.

PROGRAM 1 If $coop_hum > 65 And $coop_hum > $outside_hum And 'Whitehouse / main' Temperature > 40.0°F And Fan is Off Then Set 'MQTT / ChickCoop3' On Wait 5 minutes and 30 seconds Else Wait 5 minutes and 30 seconds PROGRAM 2 If 'MQTT / ChickCoop1' Temperature > 85.00°F And 'MQTT / ChickCoop1' Temperature < 120.00°F And Fan is Off Then Set 'MQTT / ChickCoop3' On Wait 5 minutes and 30 seconds Else Wait 5 minutes and 30 seconds PROGRAM 3 If Fan is On And 'MQTT / ChickCoop1' Temperature < 85.00°F And $coop_hum < 65 Then Set 'MQTT / ChickCoop3' Off Wait 5 minutes and 30 seconds Else Wait 5 minutes and 30 seconds

@TJF1960 @EWhite Wouldn't it be much simpler to do it without the variables, and just limit the amount of times the program can run? It looks like there is some logic above based on 5 minutes and 30 seconds, so what if it was: if humidity is > x AND temperature is > x then turn fan on wait 5 minutes and 30 seconds else turn fan off wait 5 minutes and 30 seconds

Can't you just use both temperature AND humidity in the if statement? if humidity is > x AND if temperature is > x then turn fan on The program should check the logic in the 'if' even if only one of the pieces has changed value, then if both statements are true, it will execute 'then'.