gdntx

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.

As noted by @Ross fixes are on the way. I was able to test a future release yesterday to confirm for the developers. Keep an eye on the Beta repo for the next versions and they will likely be in there.

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.

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

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.

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.

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.

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.

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?

By the way - to fix the issue, I rebooted my EISY.

I had similar problems replacing a switch last week. Seems the java console has some issues. Open the relatively new "UD Mobile" app on your smart phone and I bet you'll see the switch. Might have been able to see the old one there too.

This sounds like a familiar problem. Are you in the Java console? If so, it was changed some time back, but not well documented. The Write Changes button doesn't do much. After making your adjustment, click on the actual button "On Level" or "Ramp Rate" after making your adjustments. It will write your changes.

Likely issues with the scene - if ISY gets the command from Alexa, Alexa did its part and triggered. Its up ISY and your switches to react to and execute the scene.

Alexa has been pretty solid for many years for setting up and using the spokens. I don't think I could live without it. Having said that, I'm tired of Amazon having all of my information. As soon as the new Apple TV is out, I'm upgrading and going to attempt to move to HomeKit as the heart of my automation to get rid of Alexa. I've had HomeAssistant in place for about a year, but have done very little with it. I did investigate enough to find it has an integration back to ISY and can be used for voice commands. Home Assistant will likely be what I use to pull in more devices in the house - alarm, Sonos, etc and enhance my routines beyond lighting which has been my focus for many years.

No add ons running against my EISY other than Mobilinc Pro. I opened a case. No issues found so far, but next time it hangs, I'll check with SSH before I reboot. If I can connect, Michel has given me some commands to check a few things. Looks like trying to ensure systems are still running - isy, udx, and checking ports. I had another problem tonight, in the Java console. I had to replace a switch. Went through the normal motions, add switch, replace switch, and it appeared to work, but no matter what I did it would not show up in the list of switches, making it look like it had not worked. Every time I opened the Java console, it showed up in a dialog box saying new switch. I opened UD Mobile and it was there fully replaced and operational. It operated in my programs and macros. I finally rebooted the EISY (it had only been a couple days) and it now shows up - new switch, fully replaced the old one.