MrBill

This can’t work for eisy/ISY. The alternate email address can be used by a device connected to iMessage eco system (i.e. an Apple device logged into iMessage). If a non-Apple device sends a text message to the alternate address it will either fail, or end up being converted email and land in the email box i.e. the dummy gmail you suggest creating. I’ve used Pushover since long before the Notification plugin, but if you’re insistent not using a 3rd party install the UD mobile app and use the Notification feature.

A few improvements, a variable isn’t really needed. ------------------------------------------------- Motion turns On Switch If 'Motion Detector' is switched On (Control) Then Set 'Test Switch' On Wait 1 minute Set 'Test Switch' Off ------------------------------------------------- Override - Stop the Timer If 'Test Switch' is switched On (Control) And ‘Test Switch’ status is On Then Disable ‘Motion turns on Switch’ Stop program 'Motion turns on Switch' ** if light is on and on toggle is pressed ** I’m not sure you need both disable and stop, but disable is definitely needed. (Disable may or may not also stop, try it I can’t remember off the top of my head.) point to consider: the way you had the program, even tho you stopped the program, it would still retrigger next time there is motion. ------------------------------------------------- Set Variable >>>> (to prevent motion restarting timer) If 'Test Switch' is switched off And 'Test Switch' Status is off. Then Wait 10 seconds Enable program ‘Motion turns on switch’ ** if light is turned off once, the motion will not be reenabled, and light will stay off. ** If switch is turned off, then turned off again, then re-enable the motion. ** to always re-enable to motion just delete the “and” line in the if statement. ** the wait 10 seconds lets you get away without the motion turning the light on for 1 minute. ------------------------------------------------- Disable is under Programs on the menu. Without Disabling the program addition motion will retrigger it. Stop only interrupts the wait, and prevents the off statement from being run. another consideration: I assume you’re using an Insteon motion (which I don’t have) batttery powered motions typically don’t retransmit often to save battery. I’m not sure if the delay can be adjusted. But keep that in mind when figuring out the delay the light stays on, it must be at least as long as the time period the motion waits to transmit again.

Are you utilizing the portal geofence? With perhaps Locative? Or the UD mobile App then YES the program should run when KBM Home changes state. So leaving and anrriving and time triggers will both trigger the program. I’d change the end time to 11:59:59 pm, for one it’s easier to understand at a glance, second there was once wonkyness with 12:00:00 AM and next day/same day. I don’t remember the details but I think it got fixed.

I’ve been thinking about this issue and only have two suggestions left: leave it alone and don’t fiddle with it as @paulbates suggests. If that doesn’t solve it, then please delete the saved programs, then click save, close the admin console, delete the admin console, clear the Java cache, redownload and install a fresh copy of the admin console, then configure the time zone in the admin console and add a test program, save it and leave it alone. also please create an integer variable called test or something and have the then statement set test = test + 1 so that you can determine the program is in fact not firing. Maybe the underlying problem is the program is running but there’s a communication issue.

You might open a ticket with support, it should work easily. Been using it for many years—so the function does indeed work.

Right, in each case the first ‘if’ element makes the program true, which causes ‘then’ to run. The second ‘if’ element makes the program false, which causes ‘else’ to run.

Add to program: schedule change “time is” to “from” “To” will magic appear, allowing something like ‘from sunset for 4 hours”

In the upper right corner of the first screenshot it shows your next sunset to be at 7:52 pm, I’m not sure why with the offset you have set it would show about 30 min after, but it looks correct. BTW, if you haven’t discovered this: if Sunset to Sunrise then Turn on something else Turn off something “then” will run at sunset, “else” will run at sunrise. those two things are the only things the program does, specifically it does not enforce that “something” will remain on during that time, it only send 1 on command and one off command at the times listed. obviously, something like sunset to 11pm will work just fine too.

@CWM please check your chain of folders above this program. If any are disabled folders (IF condition in folder if is false) the program will not run either automatically or manually selecting “run then”. I suspect you have that issue. also check your time zone in the configuration section and then reboot the ISY. @Ross thanks for the kind words.

Please right click the program name in the program tree and choose copy to clipboard. Paste that here in a reply.

5.3.0 is pretty old. many bugs have been repaired since. at some point you should consider upgrading. The most important question is what happens when you attempt to turn the scene on or off via the buttons in the admin console? does it work from there? Next move to the programs tab and click then right click the program name, choose Run Then and then do it again and Choose Run Else. did it work from here?

to add to @Brian H comments, the fastest way to know if you have Pro vs non-pro is to look at the admin console ribbon... if you see these two buttons at the end of the ribbon you have pro, if they are missing you have non-pro. The second fastest way to check is Help>About.... the section about product will contain the word "pro" probably on the first line of that section. If you don't have pro, it can't be added anymore because the 994 is deprecated.

that sounds like a GUI defect.... please open a ticket to best document for UDI. Include screenshots and virtually the same report you've made here. https://www.universal-devices.com/my-tickets/

If you read many HA forum or reddit posts, someone will inevitably say they use a SD card on a Pi4 for HA... and the replies will go nuts with people posting that it is an insane practice to even think about running HA on an SD card, and that the only correct method is to use an NVMe SSD. That said, I run HA on a microSD card... first one failed after about 18 months, second one is a better quality card. At my son's house his first failed after about 12 months, the second a better quality card failed in under 30 days (I'm guessing that was manufacturing defect). One thing about HA tho is I always have a current backup because they occur every night automatically and upload to google drive. (there's a nice add on for that) the ISY994 is on it's way out. but in general I've been harping for 4 or 5 years that a high quality card with an A1 rating should be used. Watch out for the fake claims and fake names made by manufacturers tho, the memory card industry using fancy marketing names to attract and upgrade buyers.... A1 rating is the thing to look for.

I disagree. With an ISY994 it's not a question of IF, but WHEN. The most problematic thing an ISY is constantly write and re-write log files. Over time that will result in failure. New larger cards with the A1 rating will help, but not completely alleviate the issue. (note the ISY doesn't have the hardware component to take advantage of A2 rating features, A1 is fine which is what most 32gb and smaller cards have anyway.) It's also worth noting that my logfile turnovers were much smaller prior to node servers. Prior to nodeserver the log file had months worth of entries. After nodeservers the logfile held less than 24 hours.