Tuesday at 06:52 PM3 days Just did the upgrade (insteon, zwave, plugins). Everything went fine. No issues.Gary
Tuesday at 07:56 PM3 days @JimTurner It's possible that Java ran out of memory, try either increasing the Java memory allocation or deleting part of your log file
Wednesday at 06:27 PM2 days My first eisy upgraded without any issues, following the upgrade procedure. The second eisy completed the upgrade, but after two reboots, eisy.ui was reported as not found. After performing 6x presses of the multifunction button to shut down the eisy, pulling and reconnecting power, the eisy booted fine and eisy.ui is now accessible.
Yesterday at 07:55 PM1 day Just did an update packages from eisy ui. It seemed to go fine, didn't take terribly long. Though I needed to restart all my plugins after the update. Something I hadn't seen before is that opening the admin console told me that iox finder was on the new version and iox was still on the old (6.1.1/6.1.2) It asked if I wanted to update iox, I said yes. I was then able to immediately re-open the admin console, so I don't know what update happened, couldn't have ben much in that ime. I have seen the opposite of that message before where I had to clear out Java. I believe this is the first time I have updated from the eisy upgrade packages vs the admin console trigger, not sure what if anything that changes.
20 hours ago20 hr That is interesting, I had to clear java as usual...I updated about a week ago, with no issues.
20 hours ago20 hr Author 5 hours ago, apostolakisl said:Just did an update packages from eisy ui. It seemed to go fine, didn't take terribly long. Though I needed to restart all my plugins after the update. Something I hadn't seen before is that opening the admin console told me that iox finder was on the new version and iox was still on the old (6.1.1/6.1.2) It asked if I wanted to update iox, I said yes. I was then able to immediately re-open the admin console, so I don't know what update happened, couldn't have ben much in that ime. I have seen the opposite of that message before where I had to clear out Java. I believe this is the first time I have updated from the eisy upgrade packages vs the admin console trigger, not sure what if anything that changes.What version did you upgrade from?
7 hours ago7 hr Just updated. Took about 15 minutes from start to reboot! First look at programs in eisy-ui looks good. Great job UD team!
7 hours ago7 hr 13 hours ago, Guy Lavoie said:What version did you upgrade from?6.1.1-6.1.2 Edited 7 hours ago7 hr by apostolakisl
5 hours ago5 hr In the new eisl-ui, there are 3 update repositories. Production, Beta, and Staging. This give UD the ability to tell you they could use your help or you need a feature/fix not yet ready for all users the Beta level or in rare cases the Staging level. The reason I asked is the 6.1.2 only shows under the Staging level from my view.
1 hour ago1 hr On 8/24/2026 at 1:54 PM, Sticklizard said:I'm glad to finally see the web UI gain access to programs and better access to devices/scenes. I do have some trouble reading the screen due to recent eye surgery. I can magnify but many of the colors are too dim on my display to be read easily.Try changing to light mode Alt + t. (theme)
1 hour ago1 hr Upgrade failed, and I'm still on 6.0.5From the AC, I clicked to "upgrade packages" then went to SSH to look at the logs, as it was over an hour and nothing seemed to be happening.I am running I0X 6.0.5_10, and the /var/log/messages shows that only one file updated:polisy pkg[17912]: udx upgraded: 4.5.0_7 -> 5.0.0I rebooted my Polisy, waited until everything finished discovering (20 min), and then clicked to Upgrade Packages again, this time IoX presented a different message: (see attached file)I accepted by clicking Yes, and after 90 minutes, still no activity in the /var/log/messages file.I rebooted a second time, and click again to upgrade, no difference, nothing is upgrading according to the /var/log/messages fileThoughts?
1 hour ago1 hr Author A Polisy won't upgrade from a menu. You need to do it from the command line, using ssh.sudo pkg upgrade udx isy eisyui pg3xThis is explained earlier in this thread.
1 hour ago1 hr When I go to SSH and issue:sudo pkg upgrade udx isy eisyui pg3xI supply my admin credentials, and then SSH shows"No repositories are enabled"Figured it out, I had to issue: sudo repo.util prod to first activate the repository.Upgrade went fine after that, and all is working including integration to Home Assistant. Appreciate the support from this forum. Edited 45 minutes ago45 min by Peter Henneberry
Create an account or sign in to comment