Monday at 01:48 AM5 days I have not yet found a means to copy a program text on EISY-UI, so I have a screenshot.I have a program that has been in place for several years and has worked as expected. I wanted a program to close blinds at 8pm or sunset, whichever is later and this program has done so. It has even worked as recently as a few weeks ago. No changes have been made since first creating it.The program is below. I expect this program to trigger at sunset, 8pm, and 11:59pm. Tonight (it is now 9:41)The program shows last run at 7:36pm (presumably the calculated sunset time) and ran false (expected). I expected this program also to trigger at 8pm and evaluate true. Yet, it apparently did not. Blinds are still open. Last run at 7:36 was false.Did something change in the program logic execution recently? Am I missing something?
Monday at 02:14 AM5 days Which version are you running? At some point a sunset/sunrise issue was introduced and I think it’s fixed in the staging repository versions.
Monday at 09:27 AM5 days Author 7 hours ago, hart2hart said:Which version are you running?I am on the latest Beta version. At this point, I do not know how to check the time or sunset time or location from the EISY-UI, but I must assume EISY-US-predicted sunset was 7:36 and logs show that it ran at that time. I do not know why else it would have ran at that time.One of my questions is why, regardless of sunset, did it NOT run at 8pm?
Monday at 12:05 PM5 days @oberkc , I know you said this program worked previously, but...Shouldn't the sunset trigger be an "or" instead of "and"?Edit: Never mind, I get it now. Edited Monday at 01:31 PM5 days by IndyMike
Thursday at 10:09 AM2 days Author Whatever it was turns out to be fixed in the beta version released last night.
Thursday at 04:36 PM2 days On 9/21/2026 at 4:27 AM, oberkc said:I am on the latest Beta version. At this point, I do not know how to check the time or sunset time or location from the EISY-UI, but I must assume EISY-US-predicted sunset was 7:36 and logs show that it ran at that time. I do not know why else it would have ran at that time.One of my questions is why, regardless of sunset, did it NOT run at 8pm?I was using the Beta versions as of late last week thru the middle of this week and was having all kinds of program anomalies.. programs were changing state but with no history of running, etc. Others weren't running correctly and UDM was showing different states etc.. really weird stuff. Upgraded to the staging Repo and all things have gone back to normal. fyi.
Thursday at 05:24 PM2 days Author 43 minutes ago, dbwarner5 said:I was using the Beta versions as of late last week thru the middle of this week and was having all kinds of program anomaliesThe recent past has brought me a lot of issues. I don't know if it was coincidental with my loss of the Java Admin console or something else. This program is one. A few of my PG3 (twinkly, govee, maybe others) have lost connection to some (but not all) devices. Less reliable and consistent device response. It is hard for me to imagine this being related to software updates, but it sure has been frustrating and time-consuming. On the other hand, the EISY_UI is really maturing and the login process is much less troublesome and much faster. I remain hopeful that the problems will work themselves out.
Create an account or sign in to comment