CoolToys

@DennisC and @larryllix, Ok, I see where my confusion is. I don't ever use a variable as the only condition to run a program. I use them to start timers. i.e. come home at 1 am to dark house. Front door opens lights come on, set $Front_Door = 1. Next program is Front Door Auto Off - [ID 002B][Parent 0001] If 'Area 1 / FRONT.DOOR' is switched Off And $Front_Door is 1 Then Wait 15 minutes $Front_Door = 0 Set 'House Front' Off Else - No Actions - (To add one, press 'Action') Because the front door being closed is the status change that runs the program, this works. Looking at the example I should be using integers to increment and decrement more often to make the lights more efficient/accurate when people keep moving around maybe. Since I use MSII to trigger the internal lights around the house, I think I would have the same issues, if everyone stops moving long enough lights go out. With this particular one, if the door is re-opened the program changes to "false". I think that stops the timer but more to play with. For this thread, the Sunset/Sunrise appears to have been fixed by removing all of the references, restarting the eisy and reloading. I am down to trying to get my last program working again with a mini remote.

More testing. After trying as a 4 scene, and 8 scene non-toggle, the mini remote was factory reset to 8 scene non-toggle. The admin panel always show the status as "ON". I guess it never times out? When I switch to Toggle Mode, same problem. Whatever the last press is remains the state. So maybe there isn't a way to do a one button? Other options I tried: Using another program to change the status to "OFF" so at night the first press turns it "ON". The only option is to "Write Changes". Making it a "responder" to a scene to change its "status". Doesn't work. For the wired keypad I simply added it to a scene "House_Front" so it's Status Changes to "ON" when the lights out front turn on. Then the "OFF" Button always works as it should. Down to the mini remote. It did work before upgrading to eisy. So I did like my sunrise/sunset, deleted it and all references and started over looking at old backups to make sure I was doing it the same way. No luck.

@larryllix, My understanding is the eisy continuously cycles through the programs checking the If statements, so I will test this by replacing a state with an integer in one of my programs and see what happens.

So tonight I pressed all of the buttons hoping any one of them would trigger the program. None did. When I went to the admin panel and ran the "then" part it worked perfectly, I think the program is ok. Clearly the way I am defining the "if" is the failure. Ugh.... Maybe I will try with a UD Mobile button in a couple days when I am home again.

Ah wow, thanks for the inputs, and yes @techman, that is the main screen for the hardwired "on/off", but there is at the bottom of the screen an "Led Brightness" that I set 4/2 for every keypad in the house. In the day time you can just tell when it is on, but it is bright enough to read at night. I have set the backlight to all kinds of numbers and when I close and re-open the admin panel, the screen shows 0/0 for the backlight. The led brightness that I set does stick so I am trying to figure out exactly what this means.

So Maybe the program is the problem? It's hard to test the whole thing without taking a computer to bed. That will be tonights work I guess. All variables are state, toggled to 1 with other events during the day. It stopped between the two wait statements each of the last two nights when the MB Mini or Bed Keypad was used. The Master Bed Cabinet switch works the best but still not 100% All Off - BedTime - [ID 0016][Parent 0001] If $Edit_Guest is 0 And 'Master Bed Cabinets' Status is not Off And ( 'Master Bed Keypad.On' is switched Off Or 'Master Bed Cabinets' is switched Off Or 'MB Mini - A Up' is switched On Or 'MB Mini - A Down' is switched On ) Then $Interior_Motion = 0 $Snack_Walk = 0 $Alarm = 0 $Kitchen_Motion = 0 Set 'House Front' Off Set 'Garage Lights' Off Wait 2 seconds Set 'Garage Front Porch Lite' Off Set 'Holiday Lights' Off Set 'Temp Home Night' On Set 'Back Patio' Off Set 'FamRm Dining' Off Set 'Scott's Office Lamp' Off Set 'LR Pool Table' Off Set 'HallwayOutletCurio' Off Set 'LR Center Outlet Top' Fast Off Set 'LR Center Outlet Bot' Fast Off Set 'LR Lamp Scene' Off Set 'Entry Art Niche' Off Set 'Stairwell 3 Way' Off Set 'Upstairs Hallway 3 Way' Off Wait 4 seconds Set 'Cat's Room Lamp Scene' Off Set 'Dining' Off Set 'Party Night' Off Set 'MB Closet' Fast Off Set 'Studio Fan' Off Set 'Master Bed Cabinets' Fast Off Wait 4 seconds Set 'Studio Button Light' Off Set 'Studio A' Off Set 'Studio B' Off Set 'Studio C' Off Set 'Studio Closet' Off Set 'MB Closet Hers' Fast Off Else - No Actions - (To add one, press 'Action')

When programming keypads I find this but at the bottom I have LED Brightness too. LED brightness I get, and set that up. I can't figure out why this is here and what it does. Thanks

What is the difference if I use an integer for $night and make it = 1 or a state for $night and make it = 1 when the if statement is IF $Night = 1 THEN Do "What Scott says to do". Isn't it going to run either way?

So as I found with the sunrise to sunset program, something was lost in translation when migrating from the ISY to the eisy. I deleted the V.39 four scene remote, added it back and left it in its default state and tested this to see if it would turn off the light, yes it worked, so I have reprogrammed as @JCBond suggested, and used the "control" option as he showed for the buttons instead of "status". I think status is a held value and control is a temporary value so it can resend over and over. Also note that I needed to set both conditions to "on" as the switch didn't ever send "off" and that may have been the issue all along. MB Keypad Status Toggle - [ID 0002][Parent 0001] If 'MB Mini - A Down' is switched On Or 'MB Mini - A Up' is switched On Then Set 'Scott's Office Lamp' Off Else - No Actions - (To add one, press 'Action') UPDATE - Well the bummer is it still doesn't properly trigger the program, so maybe it is the program itself and I am getting way too fancy with it trying to mimic a human walking the house turning off lights?

Since doing the delete, reset eisy, reload the if statements for sunset to sunrise does appear to work, I did follow @apostolakisl idea of a single reference point for sunset to sunrise, and I used the same idea to set a new program for "peak power" which is currently 4-9pm, and has lots of implications in other programs. Doing this, if the power company changes the times with the time change, then I only need to correct in one place. Thanks for the idea. While @apostolakisl made a program, I made a state of "Night". and then zero it out at sunrise with two programs. The same for "peak power". One less line to watch in the event viewer and the event is only true in that moment so it seams like less processing for the eisy. Sunset Night Time - [ID 000C][Parent 0001] If Time is Sunset - 5 minutes Then $Night = 1 Else - No Actions - (To add one, press 'Action')

Removed the sunrise to sunset conditions in the three programs and reloaded them. So far so good. More testing in an hour after sunset. Just for fun on one of the three I did what @Andy P said and put the sunset to sunrise in a and (...) no change. As of now all working after delete, restart and then add the condition back. Correction edit, none of them are activating in the day time. Only tested front door so far at night and it worked fine. On the road again will do a thorough test in a few days.

Did that, and the correct program runs. That is why I started this thread.

Like I said, many ways to skin the cat, just trying to figure out why sunset to sunrise not working. I like the simplicity of Sunset = Dark, Sunrise ¬ Dark idea, but I will go through this step by step and try to figure out if I have the same variables or triggers elsewhere in the program, or at least find a way to make this work. I hope.

@apostolakisl, I use the variables/state integers to verify multi layered conditions and allow for timers for some events. Lutron used to have a "vacation learning mode". When I traded to ISY/Insteon, the way to mimic that was multi layered series of programs. I tried the "else" but it did other things and didn't allow me to have the door come on after hours. I don't know how you turn your light off in your example so here is the longer explanation of how I set mine up. Door opens, light off the $Front_Door integer of "1" is set. Then I have a program that checks for $Front_Door="1" waits 15 minutes, checks the door is closed and then sets $Front_Door back to "0" and turns off the lights. If the lights are on due to another program all of this is skipped. There are also two states $Occupied, $Guest and $Away that determine if the house is occupied by only me and my wife then program "Home" runs turning on the lights as I like them. If there are guests in that part of the house, then "guest" runs. If both are zero then away runs. Away doesn't turn on any lights that can't be seen outside of the house, and sets the thermostats to different settings as well. It is a multi zone HVAC system. When $guest="0" then that section isn't heated or cooled. Ultra cheapo energy move on my part. Using this approach, if the light is on and Home (or Guest) programs are running, then the door open program doesn't run. If the light is off, the program runs and sets $Front_Door. Then another program above runs. This way the eisy is "aware" if the light is already on and a program has already triggered lights or if the Home/Guest programs did not run and can automatically return to the state it was in. If I enter the geofence area and "Away" is active, it goes to "Home" automatically. If I don't use the state variable and "home" program is running, I open the front door, then close it, the light will go off before I want it to depending on how you turn off the light. I am sure there are other ways to skin this cat, but until the eisy upgrade this has worked the best and most reliable. I will remove the sunset/sunrise line and try the "Dark" mode option later today. Thanks again for the ideas and insights.

I used an Insteon 2450 contact closure. When someone presses the doorbell it goes through the closure and sends and insteon "on" command, that triggers a "door bell" program that makes an Insteon siren chime. It is very loud and I had to put acoustic tape over it. The other side of the 2450 is used to open the door. I put in a door lock that uses an electric relay. I can hit a button on my UDI mobile to run a program "buzz in" that opens the lock for 2 seconds. I did end up removing the stock doorbell switch and installing the Lorex (Ring Style) door bell so I could see who I was buzzing in on the 15" Echo in the kitchen.

Here is the wiki for the steps to try. You may need to reset the PLM to new and simply try again. But Out of memory can also be related to a device no longer in a program. Look at the programs that say "out of memory" for any // not found errors. If a device is missing or changes for some reason that will do it. https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:File_Menu#Restore_Devices

@MrBill and @DennisC are correct, but if it was working, did you follow the thread here or the wiki to replace a PLM. Mine recently died as well and I needed to follow all of the steps.

@oberkc, no green arrow, and yes I have done that more than once, thanks for reminding me to look at the basics. @apostolakisl, interesting idea, to run a separate program for Dark. That way I can see if it is "true" separately in the details. Also I could simply use sunset to set a state variable of $Dark and sunrise to return it to "0". The $Front Door state is used to start a 15 minute timer in another program to turn all the lights back off. That is why I also check if the switch is on first. I don't want it going off any time someone manually turns it on or a scene already has it on. I agree the order shouldn't matter but you never know. I did already try to add a notification line each time the door opens and the program runs. That worked just fine I got the notice each time the program ran and I verified "true" was also on the program in the details panel. It is possible the Elk status of the door is also in a scene that I have missed, and it is also possible that the program just didn't restore from the ISY backup to the eisy perfectly. When I get home tonight I will remove and replace the Sunset to Sunrise program first just to check, but even if it works I like your solution better and will rewrite all three of the programs that way.

@Brian H, Thanks. I didn't think about mesh v wireline only modes. I will look at that tomorrow. For the short term I just deleted it because it was doing odd things. The PLM is the Serial with USB to serial adapter and the PLM and eisy are on the a phase with the 2450 on the b phase. I have a repeater about half way between as the crow flies. One of the many things that went stupid when i upgraded from ISY to eisy.

@JCBond yup tried that and still didn't work. The other remote is in toggle mode but set as controller for the scenes. It works fine. The one I use upstairs doesn't appear to accept the change to toggle mode, so maybe that is the issue. For the money I'll order another one and see what happens.

@DennisC,Yes I wrote this for the exact situation that you mentioned and @Goose66you are correct. If the lights are already on and I open the door I don't want to run this program. I have a two other programs that turn the outside lights on with other conditions, i.e. we are home or alarm is set so it looks like we are home. This program is only to work if the lights are off and someone rings the bell and I open the door like my mother showing up at 3 am. Yup it happens. @apostolakisl, As background all of this worked on my ISY just fine. The problems started when I upgraded to the eisy and changed the ELK module to the ELK node. While 99% of the new elk node is way cooler and lets me do more things. the one odd ball thing is that none of the three programs with sunrise to sunset programs work any more. The new i3 outlet also randomly turns back on from time to time, but Steve Lee thinks my lamp doesn't have enough of a load so the auto sensor is kicking on. I am on the road today, and home tomorrow so I will try @garybixleridea to re arrange the "if" and put the sunset to sunrise command first. If the house is dark and I enter the house the ISY used to turn lights on at night for 15 minutes with a program I labeled "late arrival". Now that program also ignores the sunset to sunrise stamens and does it 24x7. I don't know why. The same for leaving my bedroom at odd hours. That is my "auto snack" program that used to work at night only and now works 24x7. The MSII's did fail to transfer and I had to delete all four of them and relink them so maybe there is something there so I will double check that. Late Arrival and Auto Snack both use the MSII inputs. Possibly I linked them to scenes but that doesn't explain the front door which is an elk sensor not an MSII. I will do the searches tomorrow when I get home and see if somehow the new elk node changed the code or if there is a //error somewhere that I missed or if I linked any MSII to a scene for testing and forgot to unlink after I fixed the // error lines in the programs. I might also delete the sunset to sunrise lines in the program, reboot and then add it back in just in case there is some latent binary that didn't transfer to the eisy. None of the MSII transferred, so clearly there are some odd issues with the upgrade. Thank you all for looking at this and giving me ideas to look at.

So as a status, it can activate the lights 24x7? That makes zero sense to me, If opening the door causes a condition and the program runs it should run. But just for fun here is the updated version and same problem. Open door 3:44 pm and lights turn on. The Niche is the landscape lighting which also turns on. Front Door Open - [ID 0013][Parent 0001] If 'Area 1 / FRONT.DOOR' is switched On And 'Entry Front Door Light' Status is Off And From Sunset + 5 minutes To Sunrise - 5 minutes (next day) Then $Front_Door = 1 Set 'Entry Front Door Light' On Set 'Garage Front Porch Lite' On Set 'Courtyard Niche Top' On Set 'Courtyard Niche Bottom' On Else - No Actions - (To add one, press 'Action')

Roller Shades Manufacturer : Graywind Model: Roller Shades with Zigbee Motor Support Page https://www.graywindblinds.com/pages/contact Commands requested "up", "down". "Favorite", Status requested "battery low". Sold on Amazon, Alexa Compliant, Alexa discovered and operated as soon as powered up in programming mode. Amazon shows as yooksmart smart device, manufacturer says same as "IKEA" also. eisy 5.7.0 w USB Zmatter finds them and lists them as "unavailable". https://www.amazon.com/stores/page/FCD06F74-9BD9-470A-B117-07AF4C4218E4?ingress=2&visitId=4356e004-e963-4dfb-a403-c8724130777d&ref_=ast_bln 11/1/24 Update, IoX 5.8.4 sees all of them, and lists them as "Main". but when selected the options are identify and query, and nothing happens.

Like @garybixler, I ordered the Graywind window coverings. I got the Zigbee motors, and added the USB adapter to my eisy. When I hunt for zigbee devices it it quickly found and listed as ZB34677.unavailable with an option to "interview" with a choice of seconds. Any ideas, manufacturer says it is ZigBee for Alexa but it appears to use wifi for that part. I have reached out to Graywind. Ideally I just want to add the shades to a scene. I did try to do the interview plugged in just in case the batteries went to sleep too fast. While digging around the forum, I found notes that the antennas had different color bands. I don't see any colors on the antenna. I added a request to add the blinds in Zigbee support and opened a ticket for the antenna question.

Here it is, If the light is already on, I don't want it to trigger program and turn off the lights unexpectedly. Front Door Open Copy - [ID 000C][Parent 0001] If 'Area 1 / FRONT.DOOR' Logical Status is Violated And 'Entry Front Door Light' Status is Off And From Sunset + 5 minutes To Sunrise - 5 minutes (next day) Then Set 'Entry Front Door Light' On $Front_Door = 1 Set 'Garage Front Porch Lite' On Set 'Courtyard Niche Top' On Set 'Courtyard Niche Bottom' On Else - No Actions - (To add one, press 'Action')