I have four flood lights that are supposed to turn on at sunset and off at sunrise. I have two programs controlling these actions. After updating my Polisy to the eisy-UI, the programs don't work. Do I need to delete the programs and remake them? I tried adding specific times and that also failed.

Before deleting anything, check Configuration > System > Time/Location (latitude/longitude and time zone) survived the upgrade. Sunset/sunrise triggers depend entirely on that location data; if it got reset or blanked, the schedule never fires and the programs sit idle—which matches your symptoms and also explains why hard-coded times failed. Also confirm the two programs aren't disabled in the Summary tab, and right-click > Run (If) to see whether they evaluate true. If the location is intact and the programs run manually but not on schedule, the clock/time zone is the next thing to verify.

A few more things to check:

1. Are any programs running on time, or are these the only programs you have and no programs are running?

2. Navigate to the programs that are not running and select it. You should see: Activity - Status - Last Run Time. What do these say?

Just a note, if you have a time or sunrise/sunset set and you right click and Run If, the program will only show True if those conditions are met. In other words, it needs to be in that time window.

Try coping and pasting the program here.

So the time was not something I expected to get lost in the backup. Got that sorted. I'll see if they go off on time.

Now I'm having trouble with the Eisy UI. Programs are not saving. I modified a program, hit the save button, it cycles. I click on a different program and am asked if I want to discard the changes. I hit cancel, save again, and am asked if I want to discard changes again. Works fine in the Admin Module, but that goes away shortly.

Since completing the most recent update, I have had an issue with a couple time-based programs not executing during the current day cycle but as it advances past midnight, it executes the following day. The programs are on 2 separate eisy's and perform the same so have deduced that it is related to the updates that were performed on each and appears to be an issue related to when the eisy is restarted. The program is to increase the outdoor lighting to 100% and turn off landscape lighting at 11:01pm and If I look at the program execution details, the "last run" shows nothing and the "next run" is showing for the following day, even though it should be showing for execution later the same day. When it initially occurred, I restarted both eisy's and it again skipped running later that same day but when the eisy is left to run, the program runs properly the following day and each day thereafter, until restarted again, so assume there must be some sort of bug occurring.

I would suggest checking the eisy-ui log on the System Tab for hints.

I have the same problem. I have a daily program which runs at 10:00 PM every night and this program has been running for 7 or 8 years. When my system reboots on Sunday at 3:30 AM (I do this for other reasons), instead of scheduling this program to run later in the day, it delays it for 36 hours until the next day. This started sometime in the last couple of months, I didn't notice it right a way so I can't pin it on a particular release. I have an open ticket with support regarding this.

7 hours ago, JP said:

I have the same problem. I have a daily program which runs at 10:00 PM every night and this program has been running for 7 or 8 years. When my system reboots on Sunday at 3:30 AM (I do this for other reasons), instead of scheduling this program to run later in the day, it delays it for 36 hours until the next day. This started sometime in the last couple of months, I didn't notice it right a way so I can't pin it on a particular release. I have an open ticket with support regarding this.

What version of eisy-ui, IoX & UDX are you on?

While I experienced that also, it was corrected for me some time ago. If System in the menu shows upgrade available, try doing the upgrade.

If you are current with no upgrade available, try making a minor change to the program and re-saving it.

I’m on the latest and have made changes to the program, mostly by changing the time by a minute or two.

For future reference, reload all programs has a new api /rest/programs/reload that removes the reboot requirement. Will be added as a button/command in a future update.