Hello team!

Can someone help me figure out why the next scheduled run time shows up as tomorrow and not today?

I was able to fix it by changing the logic to 24-hours before sunset…..

I have had that happen to me after the 6.1.x upgrade.

After fiddling with it for some time and trying several reboots, I finally got next runtime updating correctly, by making a same change to one of the times. I think I added a second to the time and then saved it. After it finished saving, I went back and put the item where I wanted and saved it again.

I don't remember if I ran "run if" afterwards or not, but that got the next runtime squared away.

I think there is an item in release notes for either beta or staging update repo saying it includes a fix for calculation of sunrise or sunset times.

Edited September 11Sep 11 by hart2hart

My Eisy-ui sent me down the same rabbit hole. After making a mess of things, I decided to not pay any more attention to it. Presently all of my programs seem to be running on time. I also notice that the last run times and finish times are out of whack and some programs that I know ran are not posting any last run times. I believe that a future upgrade is going to correct this issue.

I like Eisy-ui and am looking forward to using it exclusively.

All my sunset programs are also messed up. They all listing the next run time for sunset tomorrow night, instead of tonight. I made non-change updates to the programs (just hit the "update" button without an actual change so the program would then be savable), then saved them all and now they list the correct run time at sunset tonight. I suspect tomorrow I will need to do that again until such time as the firmware is fixed.

Also, programs I have that run at midnight are running twice. Once at midnight and then a second time a few seconds later. I created a test program that does nothing but send me an email at midnight with a timestamp and it also ran double. So no chance of any hidden calls to it or anything, it is a brand new program with nothing else triggering it, just midnight on the clock. I tried changing the midnight program run time to a couple seconds after midnight to see if the issue is running precisely at midnight.

For what it's worth, I have also discovered that programs where sunset is used will run for one night after eisy reboot. They will not run the next night unless I reboot eisy. To mitigate this situation, I am currently rebooting once a day and then checking for updates!

53 minutes ago, Walt N said:

For what it's worth, I have also discovered that programs where sunset is used will run for one night after eisy reboot.

My sunset-based programs appear to be working now, presumably a result of updating to UI 1.3.6

28 minutes ago, oberkc said:

My sunset-based programs appear to be working now, presumably a result of updating to UI 1.3.6

Was that in beta? Been running in production only. Any major new issues with the beta build?

34 minutes ago, DennisC said:

Was that in beta?

Yes. Minor issues, but otherwise is a LOT of new capability compared to the production version. Beta still lacks a couple of key features that make it difficult for my purposes (cannot add nodes to groups or folders, cannot see node scene membership, missing network resources) but I can fill in some of the missing features with UDMobile.

7 minutes ago, oberkc said:

Yes. Minor issues, but otherwise is a LOT of new capability compared to the production version. Beta still lacks a couple of key features that make it difficult for my purposes (cannot add nodes to groups or folders, cannot see node scene membership, missing network resources) but I can fill in some of the missing features with UDMobile.

Thanks

3 hours ago, Walt N said:

For what it's worth, I have also discovered that programs where sunset is used will run for one night after eisy reboot. They will not run the next night unless I reboot eisy. To mitigate this situation, I am currently rebooting once a day and then checking for updates!

Yes, rebooting had the same affect as resaving programs. I updated to the latest firmware drop they did earlier today that Michel says fixes it. We'll know tomorrow after my sunset programs cycle past their shut down trigger.

Presently UI 1.3.6 has not corrected this minor issue for me. I have a group of sunset related programs behaving oddly unless I reboot every day. Some of involve instion, others zwave. I am confident that this issue will be resolved with future updates. Good Times!

Thank you all!

The update UD posted yesterday did not fix the issue for me. After my programs ran at sunset last night and then sunrise this am, they are listed to run next as sunset . . .tomorrow (should be tonight).

When you determine something truly not working as expected, open a ticket to report the bug. My sunset programs weren't executing. Through a ticket Michel and team have been very responsive, found bugs and published a version for me to test. It is improving fast.

Someone above noted they weren't running the beta. With EISY-UI you need to get to the beta, it is becoming feature complete, and they need the testing and feedback to fix what's broken.

18 minutes ago, gdntx said:

When you determine something truly not working as expected, open a ticket to report the bug. My sunset programs weren't executing. Through a ticket Michel and team have been very responsive, found bugs and published a version for me to test. It is improving fast.

Someone above noted they weren't running the beta. With EISY-UI you need to get to the beta, it is becoming feature complete, and they need the testing and feedback to fix what's broken.

Yes, I have a ticket running for a few days now about this.

After one day cycle on the latest software released yesterday, it looks like the sunset issue is fixed. My programs ran last night at sunset (which proves nothing by itself because fresh off a reboot, the sunset problem didn't exist), but now today the "next run time" is correctly listed for tonight. This is where it looks like the fix worked. Prior to the update, after running the first sunset it would then list the next run time ~48 hours later.

9 minutes ago, apostolakisl said:

After one day cycle on the latest software released yesterday

Is that 6.1.2_6 ?

I had the same issue with 6.1.2_6. An eisy reboot seemed to have fixed it. All schedules now appear to be normal

3 hours ago, Guy Lavoie said:

Is that 6.1.2_6 ?

yes, updated to that from _5 I'll know after sunset tonight for sure if it is fixed.

No need to wait, you can take a look at the Programs > Summary. Look at the next scheduled run

15 hours ago, Techman said:

No need to wait, you can take a look at the Programs > Summary. Look at the next scheduled run

Yes, I listed in my first post that it shows the correct next run time. But just because it says that doesn't mean it is going to do that.

Also, it appears that programs scheduled for MN that were running twice are no longer running twice. I returned all my programs back to their pre-bug times and tonight will confirm it is fixed. But my test programs ran correctly last night.