Walt N

So, Even though sunrise and sunset times are out of wack as stated earlier, all of my sunset triggered programs ran correctly. If I had not been paying attention, I would not have known that there was an issue. I am confident that this "non-issue" will clear up without a trip into a rabbit hole. Thank you all!

I just noticed the sunrise sunset times early and off different increments in my Eisy. Sunrise is one hour early, sunset is one hour 27 minutes early. The time change did occur correctly. I have not ever noticed this before but was not paying attention. I am happy to wait a day or two and look for it to magically correct. Thank you all for posting.

COULD NOT RESIST THE TEMPTATION! Updated the dongle to 7.45 using multiple steps. Deleted a Zooz multi relay out of mesh and re installed it into LR using a picture of the QRcode. Extremely easy from what I have come to expect with Zwave. I think it also picked up all of the device's attributes. I saw the LR options and used it. It appears to have installed correctly in the first LR position. ZY256, and nothing else has released smoke (yet). As before, I did install close to the dongle. I will be moving it far away to see how it performs. So far, I like what I'm seeing.

Questions are a good thing. It works just like Guy indicates as long as you are in Automations/ Programs. Speaking for myself, I did not pick up on that the first time I looked.

I had the same experience. The higher the dongle, the better the results. Now the dongle is basically in the attic at the end of a usb cable, things appear to be going well. (Single story wood framed house and outbuildings.) I did install a range extender, spread zwave devices out and around the property to leverage the mesh. I also think that it's best to do a temporary install of a new z wave devices close to the dongle, activate them and watch status change in Eisy , move them to their intended location, Eisy activate and verify. Easy to do with plug in devices. Built in devices slightly more complicated. For them I do the temp install in a metal outlet box with grounded cord. This may be extreme, but it does avoid the issue I was having with messed up device additions. I am using mostly LR rated devices and believe that I installed them in mesh instead of long range. I recently came across the across the "getting it to work" thread and am in the process of building up the courage to update UD matter dongle and re-install the zwave devices as long range. I also feel that the Eisy-ui is making the process easier, seems to make more sense.

Thank you Guy and TFJ1960! I ended up using the Admin console find/replace and found a really odd DON request for the switch in question. I have no idea how it ended up in that program. Thank you both.

I am dealing with a 2876db Icon dimmer that turns itself off every morning at 1:00 am. When I look at the log It shows a DON at 1:00 am with a 4 and 5 in the last two columns, I have looked at the other logs and don't see any potential causes. I have also looked over all programs and don't see commands asking it to DON. I have tried several hard resets, removed and installed it back into the system. I don't believe that any one is turning it on with that consistency every day. Could the switch be failing? Could there be any other place to look for a cause? Otherwise, I am extremely happy with Eisy-ui and will not have an issue removing this switch. I don't believe it has ever been part of a program or scene. Thanks for listening!

It sounds like you are looking at administrative console, look at the top bar far right "HELP" Look at the bottom of the box. Mine says "MANAGE MODULES". When I left click on it, "YOUR MODULES ARE UP TO DATE" returns. I believe that it would indicate "MANUAL UPDATE" instead of "MANAGE MODULES" if there are updates available, but don't quote me on this. Does everything appear to be working? If so, reboot for good measure and use it, keep your eyes open. I also find the wiki to be my best first look when I have questions. https://wiki.universal-devices.com/Main_Page Best of luck!

Hello All, I am happy to report that since version 1.3.11 sunset and sunrise triggers are working flawlessly. The next program runtimes also in agreement with the time requested in the programs "if Statement" Thank you UDI support and FORUM

This morning I looked and saw eisy UI 1.3.8 was available so I went for it. After the upgrade and reboot, I still found the next run time statements were advanced by 2 hours. I changed the start times in a programs "if statements" IE: 2 hours earlier, and then the next run time statement was correct in the EISY display. I gave it a shot. When I checked this evening, the programs were actually running two hours earlier than the next run time indicated, exactly the time I requested in the programs "if Statement". So at this point it is my conclusion that the next run time statement for whatever reason is advanced by 2 hours and does not make a difference. The program will actually run at the time stated in the programs "if statement" (I think?). Since I was home before sunset, I did try a sunset trigger in a program's "if statement" and it did appear to work correctly. So far everything else seems to be working correctly. Thank you ALL!

I did see the staging repository with attached request from UDI "Please do not use the Staging repo unless requested by UDI Support." They said please, so I elected not to go there. I wouldn't want to create any additional problems for UDI or myself. I'm happy to wait unless someone from UDI tells me to go for it. Thank you all!

Speaking of "next scheduled run". I was believing that a reboot was correcting my program issues. As it turns out not exactly. I did temporarily move away from "sunset and sunrise " triggers and use fixed times in all of my programs. What I have discovered is that the run time in my "if statements" and the "next scheduled run time" listed in "Programs>Summarys" are not the same. The "next scheduled run times" are two hours later than my "if statements". If I edit and save a program, the next scheduled run time will be correct for one day. I am at IOX 6.1.2_3 using beta repo. I see that some are using 6.1.2_6. How were you able to get it? Thank you all!

Good morning, For what it's worth. I am not using the ring plugin, but I do find myself having to reboot EISY-UI daily to keep my programs running. I believe that my issue is related to UD moving away from IOX and Java. I have started to use EISY-UI with the understanding that it is still a work in progress; problems are a "FEATURE". I have noticed that after reboot a program's next runtime looks good, then after that program event occurs, it's next runtime is out of whack or non existant. Again, after a reboot, the next run time is correct. I am using the beta versions and enjoy looking daily for newer versions. I believe that my issues will clear up in time. Hopefully you will benefit as well. I was comfortable with IOX, but the more I use EISY-UI the more I like it. After this issue clears, I will look into the ring plugin. Best of luck!

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!

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!