I know this likely needs a ticket, so I'll open one in a bit, but thought others may have experienced the same or have some insight.

I've got an EISY and am using the new GUI (not IOX). I upgraded a couple of nights back to all of the latest code releases.

I have a Program that runs a couple of scenes every night, 30 minutes before Sunset. Its worked for years. After the upgrades it is not running.

I have looked through a few of the logs, but don't see any errors and it seems like our list of logs has exploded. Anyone have a quick insight where to look for an error or what might have gone wrong?

From the programs listing it shows a next run time for tomorrow at about 30 minutes before sunset, but there is no "Last Run Time" nor "Last Finish Time" documented in the EISY-UI.

I've right clicked to copy the program and I get the next dialog box, but it won't paste, so maybe another GUI error?

I have Alexa connected and have spokens set up for this Program, it will run and did last night, if I ask Alexa to run it.

Any insights?

If you right click on the program name from the left hand screen and select "Run Then", does the program run?

Yes - runs perfect. I had avoided doing so tonight for troubleshooting, but did just as you note and all the lights came on as expected. So it appears the issue is the SUNSET trigger. The last Run Time and Finish Time also updated.

Is the date and time in eisy-ui correct?

I have seen something similar happen to me, I think it corrected itself after several reboots.

Well oddly I'll have to say I can't find a time and date in the eisy-ui now that I go looking for it. I have to think that it is however, because that screen shot from after running the "then" updated to the current local time that I ran them at.

Edited September 9Sep 9 by gdntx

FWIW, I'm experiencing the same problem with programs that trigger on "SUNSET". I'll know in a couple of hours if my "SUNRISE" programs have the same issue.

I was having trouble with a sunset program also so I just set it for a specific time.

3 hours ago, Bumbershoot said:

FWIW, I'm experiencing the same problem with programs that trigger on "SUNSET". I'll know in a couple of hours if my "SUNRISE" programs have the same issue.

Sunrise is working well, it's just sunset. Per other posts there are additional releases coming quickly to get the EISY UI engine and GUI up to speed.

if you haven't already, I'd suggest editing the program, selecting "sunset" again, clicking update and then saving the program. Some of my triggers stopped working after the upgrade, but this seemed to fix them.

I opened a ticket so it is documented. I tried updating - changed to Sunrise, the program wouldn't save. I change it back to Sunset and the save goes away, it recognized that is what I already have set. I know it's beta and they are working on updates, so it'll work out in the next release or two I'm sure. Just wanted them officially be aware.

21 minutes ago, maxnorth said:

if you haven't already, I'd suggest editing the program, selecting "sunset" again, clicking update and then saving the program. Some of my triggers stopped working after the upgrade, but this seemed to fix them.

Thanks, I'll give it a try.

2 minutes ago, gdntx said:

I opened a ticket so it is documented. I tried updating - changed to Sunrise, the program wouldn't save. I change it back to Sunset and the save goes away, it recognized that is what I already have set. I know it's beta and they are working on updates, so it'll work out in the next release or two I'm sure. Just wanted them officially be aware.

I saw the same thing. I use state variables in these programs, and I was able to increment the value, save, de-increment the value, and save again.

Got a reply to my ticket already, it is a known bug being worked on.

I was provided an update to an EISY component and can confirm the Sunset bug is fixed in the next release. My program ran fine tonight. I poked around at a few other things. I could now edit and save a program just fine, so quite a few updates coming in the next releases.

Edited September 10Sep 10 by gdntx

Great news - looking forward to the update. I thought I was going mad. Same exact issue here.