isyrocks!

Hi All, I was successfully able to upgrade to the latest version. I did first try to reboot > upgrade via tap method > watch log in SSH. I didn't have any luck. I rebooted > cleared java cache > downloaded a fresh start.jnlp and tried to upgrade over console without any luck. I then performed a factory reset (10 click on the button) and then executed the upgrade from the console and boom. Upgrade successful.

Note - I have reverted to only upgrading by tapping the Eisy power button and watching the log over ssh. I am not even attempting the console. Got a reply from Michael that it’s a known issue and there should be a fix soon. I still haven’t successfully been able to upgrade as of this morning.

Opened a ticket.

This thread seems to be related. Could be a potential caching issue? @Michel Kohanim can you take a look?

Thanks for the tips @DennisC I have done as you have suggested. I can now see that when I execute the update command something does indeed happen. However, it still seems I am not getting to 5.6.2. I seem to have several errors in my log that look like this: -----END PUBLIC KEY----- : rsa signature verification failure pkg: Invalid signature, removing repository. Unable to update repository udi Error updating repositories! Full update log attached. log.txt

Hi UD Community, I finally got a new eisy and Z-Wave/Matter USB adapter. I am upgrading from a 994i. The eisy came running v.5.5.9 of IoX. It looks like v5.6.2 is the latest release. I keep going into console and hitting upgrade and wait as long as an hour. Nothing seems to happen. I tried to reboot and hit upgrade again at least 8 or so times. My eisy seems to be stuck on v5.5.9. I haven't started the migration yet as I want to get to the latest version first. When I reboot I do get a message that there are upgrades available. I then go and select update packages and wait again. But nothing happens after several hours. Any suggestions?

@MrBill thanks for that. I was wondering if that was the case. I haven't really spent much time in the error log but will do so for this testing. I am also going to run things with the Event Viewer pulled up. I am guessing you are right and that I am overflowing things. I am calling all sorts of stuff, turning off a multitude of lights on different floors, turning off 3 harmony hubs, setting a bunch of variables, adjusting thermostats, turning off av receivers, adjusting camera motion settings, etc. etc.. @Geddy thanks for the detailed feedback and suggestions. I like the idea of "chunking" things and that makes sense and then adding the waits. Seems more of a micro service architecture approach. Might be the weekend before I make the time to get this resolved but I am assuming with this great feedback I will get it sorted.

Thanks for the suggestions. Here is my current "Lock All Doors" program. Let me take some of the advice here and do some additional troubleshooting.

Hi All, I have an "Away" program that runs when I set my alarm. The away program turns off lights, thermostats, etc. I also have it set to lock 3 Yale Assure Z-Wave Locks. My issue lies with the ISY 994i reliably locking the 3 doors. More often than not the doors do not get locked. If I manually lock the doors via the ISY or mobile app it works just fine. I think it may be related to a memory issue or that the ISY can't handle the amount of embedded operations that I am requesting it to do with the "Away" program. I tried creating a separate "Lock All Doors" program and putting a 15 sec delay between each Z-Wave Lock Door call but that hasn't seemed to solve it. Any ideas why I might be experiencing issues and how I could troubleshoot? ISY 994i v.5.3.3 Z-Wave 500