apostolakisl Posted Wednesday at 11:41 PM Posted Wednesday at 11:41 PM I did the upgrade packages. It says I am on 5.9.1 at this point. I forget what I was on before. This is a new eisy, only had it less than 2 weeks. It says it did an upgrade and it required a reboot (which I did). Now I try to go to http://eisy.local/ and it says "site can't be reached". I tried putting in the local ip address of eisy and it is also a dead end. Quote
Techman Posted yesterday at 12:04 AM Posted yesterday at 12:04 AM Are you on Windows or a MAC Make sure you don't have a VPN that's enabled This is the window you should see when you enter "http://eisy.local" from your browser Quote
Techman Posted yesterday at 12:10 AM Posted yesterday at 12:10 AM @apostolakisl Can you access your eisy config file: eisy.local:8443/WEB/sysconfig.txt If so, what's your FeeBSD, UDX, and ISY versions? Quote
apostolakisl Posted yesterday at 12:11 AM Author Posted yesterday at 12:11 AM I have a router to router vpn between my home and office. But I can't see how that would mess it up. I am currently local to isy and on the same subnet. 1 minute ago, Techman said: @apostolakisl Can you access your eisy config file: eisy.local:8443/WEB/sysconfig.txt If so, what's your FeeBSD, UDX, and ISY versions? no, that doesn't work either but I can still get to pg3x by putting the local ip address:3000 Quote
Techman Posted yesterday at 12:14 AM Posted yesterday at 12:14 AM I would think it's either the VPN or you're not on the same network as the eisy Quote
apostolakisl Posted yesterday at 12:14 AM Author Posted yesterday at 12:14 AM And of course Iox launcher has no problem finding it. 2 minutes ago, Techman said: I would think it's either the VPN or you're not on the same network as the eisy definitely on the same network. no problem using local ip address:3000 to launch pg3x Quote
Techman Posted yesterday at 12:19 AM Posted yesterday at 12:19 AM The launcher is java based, the eisy-ui is browser based Quote
apostolakisl Posted yesterday at 12:24 AM Author Posted yesterday at 12:24 AM 4 minutes ago, Techman said: The launcher is java based, the eisy-ui is browser based either way, the launcher only finds ISY's on the same subnet. But looking at the history of updates, it seems like 5.9.1 is not new in the last 24 hours (or even close to that) and that is what isy admin console says I am on. Unless this has nothing to do with the ISY firmware version but rather something else on the eisy box. Quote
sjenkins Posted yesterday at 02:53 AM Posted yesterday at 02:53 AM 2 hours ago, apostolakisl said: either way, the launcher only finds ISY's on the same subnet. But looking at the history of updates, it seems like 5.9.1 is not new in the last 24 hours (or even close to that) and that is what isy admin console says I am on. Unless this has nothing to do with the ISY firmware version but rather something else on the eisy box. did you try substituting eisy.local for your local ip adress? that works more consistently for me Quote
Techman Posted yesterday at 03:11 AM Posted yesterday at 03:11 AM @apostolakisl Try doing another update packages After that, if you're still having an issue do a power cycle on the eisy Quote
apostolakisl Posted yesterday at 04:09 AM Author Posted yesterday at 04:09 AM 1 hour ago, sjenkins said: did you try substituting eisy.local for your local ip adress? that works more consistently for me yes 1 Quote
mbking Posted yesterday at 03:28 PM Posted yesterday at 03:28 PM I'm having the same issue after updating this morning. I checked my ISY version and it's still 5.9.1_18, so it doesn't seem anything new was installed during the update. I don't think the new upgrade files are out there yet. @bmercier can you verify Upgrade Packages is installing eisy-ui? Doesn't appear to be. Quote
apostolakisl Posted yesterday at 03:29 PM Author Posted yesterday at 03:29 PM I did a power cycle on eisy and still no UI. Am I supposed to be doing the "developmental packages" here? I just did the standard package upgrade. Quote
dbong Posted yesterday at 06:19 PM Posted yesterday at 06:19 PM Same here. No easy-ui after updating packages. Quote
Techman Posted yesterday at 07:45 PM Posted yesterday at 07:45 PM Take a look at these links: Eisy:User Guide - Universal Devices, Inc. Wiki Eisy:User Guide - Universal Devices, Inc. Wiki Quote
apostolakisl Posted yesterday at 08:22 PM Author Posted yesterday at 08:22 PM (edited) 38 minutes ago, Techman said: Take a look at these links: Eisy:User Guide - Universal Devices, Inc. Wiki Eisy:User Guide - Universal Devices, Inc. Wiki As instructed, I did upgrade packages (not developer one). eisy.local in a web browser does not work. Nor does http://xxx.xxx.xxx.xxx. or https://xxx.xxx.xxx.xxx where the x's are the lan ip of ISY. And Iox finder does not find my isy at any address except the usual https://xxx.xxx.xxx.xxx:8443. If I try to manual add to Iox Finder http://xxx.xxx.xxx.xxx and https://xxx.xxx.xxx.xxx it does not find anything. Nor does it find http://eisy.local or https://eisy.local In a web broser https://eisy.local:8443/desc finds my ISY and it gives me a bunch of configuration information that starts off looking like: In summary, eisy is not responding to anything on port 80 and 443, but it responding to 8443 using both lan ip and eisy.local. So eisy just isn't listening on port 80 and 443. Edited yesterday at 08:25 PM by apostolakisl Quote
rob7419 Posted yesterday at 08:36 PM Posted yesterday at 08:36 PM Have tried several times today with multiply reboot and I'm not having any success with the upgrade packages, UDX logs when hitting the "Upgrade Packages" button & eisyui status output: [admin@eisy ~]$ sudo tail -f /var/udx/logs/log Thu Jul 24 15:18:45 CDT 2025|/usr/local/etc/udx.d/static/udxops_main.sh: restoring system files .... Thu Jul 24 15:18:45 CDT 2025|/usr/local/etc/udx.d/static/udxops_main.sh: removing .pkgsave files from .... Thu Jul 24 15:18:48 CDT 2025|/usr/local/etc/udx.d/static/udxops_main.sh: cleaning package cache ... Thu Jul 24 15:18:48 CDT 2025|/usr/local/etc/udx.d/static/udxops_main.sh: upgrading eisy complete ... Thu Jul 24 15:18:48 CDT 2025|/usr/local/etc/udx.d/static/udxops_main.sh: making sure the bootloader is current ... Thu Jul 24 15:18:48 CDT 2025|/usr/local/etc/udx.d/static/udxops_main.sh: checking the boot loader for /dev/nda0p1 ... Thu Jul 24 15:18:48 CDT 2025|/usr/local/etc/udx.d/static/udxops_main.sh: mouting ms dos file system (for boot) ... Thu Jul 24 15:18:48 CDT 2025|/usr/local/etc/udx.d/static/udxops_main.sh: existing bootloader is current, nothing to be done ... Thu Jul 24 15:18:48 CDT 2025|/usr/local/etc/udx.d/static/udxops_main.sh: unmounting boot parition ... Thu Jul 24 15:18:48 CDT 2025|/usr/local/etc/udx.d/static/udxops_main.sh: checking whether or not we need to reboot after upgrade .... Jul 24 15:33:11 CDT 2025|/usr/local/etc/udx.d/static/udx_cmd_processor: processing command upgrade.polisy;-;;-;;-;;-; Thu Jul 24 15:33:11 CDT 2025|/usr/local/etc/udx.d/static/udxops_main.sh: wifi.ops is not being called as a comamnd Thu Jul 24 15:33:11 CDT 2025|/usr/local/etc/udx.d/static/udxops_main.sh: starting upgrading eisy ... Thu Jul 24 15:33:11 CDT 2025|/usr/local/etc/udx.d/static/udxops_main.sh: sanity checking os packages ... Thu Jul 24 15:33:11 CDT 2025|/usr/local/etc/udx.d/static/udxops_main.sh: sanity checking eisy ... Thu Jul 24 15:33:12 CDT 2025|bash: running eisy sanity check ... Thu Jul 24 15:33:12 CDT 2025|bash: Fixing pkg repos ... Thu Jul 24 15:33:12 CDT 2025|bash: pkg.conf already has IGNORE_OSVERSION ... Thu Jul 24 15:33:12 CDT 2025|bash: FreeBSD-base.conf is AOK ... Thu Jul 24 15:33:12 CDT 2025|bash: FreeBSD.conf is AOK ... Thu Jul 24 15:33:12 CDT 2025|bash: FreeBSD-udx.conf is AOK ... Thu Jul 24 15:33:12 CDT 2025|bash: udi.conf no signature is AOK ... Thu Jul 24 15:33:12 CDT 2025|bash: udi.conf is AOK ... Thu Jul 24 15:33:12 CDT 2025|bash: isy version is ok ... Thu Jul 24 15:33:12 CDT 2025|bash: eisy sanity check done ... Thu Jul 24 15:33:12 CDT 2025|/usr/local/etc/udx.d/static/udxops_main.sh: pkg.conf already has IGNORE_OSVERSION ... Thu Jul 24 15:33:12 CDT 2025|/usr/local/etc/udx.d/static/udxops_main.sh: making sure we have the right repositories ... Thu Jul 24 15:33:12 CDT 2025|/usr/local/etc/udx.d/static/udxops_main.sh: FreeBSD-base.conf is AOK ... Thu Jul 24 15:33:12 CDT 2025|/usr/local/etc/udx.d/static/udxops_main.sh: FreeBSD.conf is AOK ... Thu Jul 24 15:33:12 CDT 2025|/usr/local/etc/udx.d/static/udxops_main.sh: FreeBSD-udx.conf is AOK ... Thu Jul 24 15:33:12 CDT 2025|/usr/local/etc/udx.d/static/udxops_main.sh: udi.conf no signature is AOK ... Thu Jul 24 15:33:12 CDT 2025|/usr/local/etc/udx.d/static/udxops_main.sh: udi.conf is AOK ... Thu Jul 24 15:33:14 CDT 2025|/usr/local/etc/udx.d/static/udxops_main.sh: making sure we have the right pkg version ... Thu Jul 24 15:33:14 CDT 2025|/usr/local/etc/udx.d/static/udxops_main.sh: pkg pkg is current ... Thu Jul 24 15:33:14 CDT 2025|/usr/local/etc/udx.d/static/udxops_main.sh: checking whether or not we have a new version for udx ... Thu Jul 24 15:33:14 CDT 2025|/usr/local/etc/udx.d/static/udxops_main.sh: pkg udx is current ... Thu Jul 24 15:33:14 CDT 2025|/usr/local/etc/udx.d/static/udxops_main.sh: OS is up to date at 1401000 Thu Jul 24 15:33:14 CDT 2025|/usr/local/etc/udx.d/static/udxops_main.sh: backup system files ... Thu Jul 24 15:33:14 CDT 2025|/usr/local/etc/udx.d/static/udxops_main.sh: upgrading ud core packages ... Thu Jul 24 15:33:14 CDT 2025|/usr/local/etc/udx.d/static/udxops_main.sh: checking for the availability of updates for isy ... Thu Jul 24 15:33:14 CDT 2025|/usr/local/etc/udx.d/static/udxops_main.sh: checking for the availability of updates for libwebsockets ... Thu Jul 24 15:33:14 CDT 2025|/usr/local/etc/udx.d/static/udxops_main.sh: checking for the availability of updates for mosquitto ... Thu Jul 24 15:33:14 CDT 2025|/usr/local/etc/udx.d/static/udxops_main.sh: checking for the availability of updates for pg3x ... Thu Jul 24 15:33:14 CDT 2025|/usr/local/etc/udx.d/static/udxops_main.sh: checking for the availability of updates for udx ... Thu Jul 24 15:33:14 CDT 2025|/usr/local/etc/udx.d/static/udxops_main.sh: checking for the availability of updates for wifibox-alpine ... Thu Jul 24 15:33:14 CDT 2025|/usr/local/etc/udx.d/static/udxops_main.sh: checking for the availability of updates for node18 ... Thu Jul 24 15:33:14 CDT 2025|/usr/local/etc/udx.d/static/udxops_main.sh: checking for the availability of updates for daemonize ... Thu Jul 24 15:33:14 CDT 2025|/usr/local/etc/udx.d/static/udxops_main.sh: checking for the availability of updates for iox_matter_bridge ... Thu Jul 24 15:33:14 CDT 2025|/usr/local/etc/udx.d/static/udxops_main.sh: upgrading other packages ... Updating FreeBSD-base repository catalogue... FreeBSD-base repository is up to date. Updating FreeBSD-udx repository catalogue... FreeBSD-udx repository is up to date. Updating udi repository catalogue... udi repository is up to date. All repositories are up to date. Checking for upgrades (6 candidates): ...... done Processing candidates (6 candidates): ...... done Checking integrity... done (0 conflicting) Your packages are up to date. Thu Jul 24 15:33:17 CDT 2025|/usr/local/etc/udx.d/static/udxops_main.sh: upgrading packages successful ... Thu Jul 24 15:33:17 CDT 2025|/usr/local/etc/udx.d/static/udxops_main.sh: checking base packages ... Updating FreeBSD-base repository catalogue... FreeBSD-base repository is up to date. Updating FreeBSD-udx repository catalogue... FreeBSD-udx repository is up to date. Updating udi repository catalogue... udi repository is up to date. All repositories are up to date. Checking integrity... done (0 conflicting) The most recent versions of packages are already installed Thu Jul 24 15:33:18 CDT 2025|/usr/local/etc/udx.d/static/udxops_main.sh: upgrading base successful ... Thu Jul 24 15:33:18 CDT 2025|/usr/local/etc/udx.d/static/udxops_main.sh: restoring system files .... Thu Jul 24 15:33:18 CDT 2025|/usr/local/etc/udx.d/static/udxops_main.sh: removing .pkgsave files from .... Thu Jul 24 15:33:21 CDT 2025|/usr/local/etc/udx.d/static/udxops_main.sh: cleaning package cache ... Thu Jul 24 15:33:21 CDT 2025|/usr/local/etc/udx.d/static/udxops_main.sh: upgrading eisy complete ... Thu Jul 24 15:33:21 CDT 2025|/usr/local/etc/udx.d/static/udxops_main.sh: making sure the bootloader is current ... Thu Jul 24 15:33:21 CDT 2025|/usr/local/etc/udx.d/static/udxops_main.sh: checking the boot loader for /dev/nda0p1 ... Thu Jul 24 15:33:21 CDT 2025|/usr/local/etc/udx.d/static/udxops_main.sh: mouting ms dos file system (for boot) ... Thu Jul 24 15:33:21 CDT 2025|/usr/local/etc/udx.d/static/udxops_main.sh: existing bootloader is current, nothing to be done ... Thu Jul 24 15:33:21 CDT 2025|/usr/local/etc/udx.d/static/udxops_main.sh: unmounting boot parition ... Thu Jul 24 15:33:21 CDT 2025|/usr/local/etc/udx.d/static/udxops_main.sh: checking whether or not we need to reboot after upgrade .... ^C [admin@eisy ~]$ sudo service eisyui status eisyui does not exist in /etc/rc.d or the local startup directories (/usr/local/etc/rc.d), or is not executable [admin@eisy ~]$ Quote
Techman Posted yesterday at 10:26 PM Posted yesterday at 10:26 PM @apostolakisl Are you on a windows or mac, what version What browser are you using Have you tried turning off VPN? Quote
mmb Posted 23 hours ago Posted 23 hours ago (edited) On 7/23/2025 at 5:41 PM, apostolakisl said: I did the upgrade packages. It says I am on 5.9.1 at this point. I forget what I was on before. This is a new eisy, only had it less than 2 weeks. It says it did an upgrade and it required a reboot (which I did). Now I try to go to http://eisy.local/ and it says "site can't be reached". I tried putting in the local ip address of eisy and it is also a dead end. I may have missed a post, can anyone confirm @bmercier is including the UI in Upgrade Packages from the AC console? I assumed we still had to SSH into the EISY to add and install the UI pkg? Thanks! ---> Never mind I indeed missed a post. Things are changing quickly! <--- Edited 23 hours ago by mmb Quote
apostolakisl Posted 23 hours ago Author Posted 23 hours ago 1 hour ago, Techman said: @apostolakisl Are you on a windows or mac, what version What browser are you using Have you tried turning off VPN? Based on the other posts in here, it appears that "upgrade packages" is not putting the eisy-ui on the system. Quote
rob7419 Posted 23 hours ago Posted 23 hours ago I am assuming that what this post is referring to, I would proceed with the manual installation now that it is listed as "Beta" but the newest version 0.5.9 is not available for download on this thread. 1 Quote
Techman Posted 23 hours ago Posted 23 hours ago 14 minutes ago, apostolakisl said: Based on the other posts in here, it appears that "upgrade packages" is not putting the eisy-ui on the system. Being that you're unable to access the eisy config file leads me to believe that you have an issue other than "upgrade packages" as this has been accessible prior to eisy-ui https://eisy.local:8443/WEB/sysconfig.txt Quote
BobM99 Posted 21 hours ago Posted 21 hours ago Same here: "eisy.local refused to connect." Can connect to this, though: https://eisy.local:8443/WEB/sysconfig.txt Windows 11, Chrome browser, no VPN. Quote
bmercier Posted 21 hours ago Posted 21 hours ago My apologies, I'm pretty sure the update is not going through due to a missing dependency. We are releasing a major upgrade next week which includes an upgrade to the OS. That will fix the installation of eisy-ui using "Upgrade Packages". In the mean time, if you are familiar with ssh, you can upgrade this way: sudo pkg install eisyui sudo service isy restart After the above, you may have to manually start eisy-ui if the install did not start it automatically: sudo service eisyui start 2 Quote
apostolakisl Posted 20 hours ago Author Posted 20 hours ago (edited) 55 minutes ago, bmercier said: My apologies, I'm pretty sure the update is not going through due to a missing dependency. We are releasing a major upgrade next week which includes an upgrade to the OS. That will fix the installation of eisy-ui using "Upgrade Packages". In the mean time, if you are familiar with ssh, you can upgrade this way: sudo pkg install eisyui sudo service isy restart After the above, you may have to manually start eisy-ui if the install did not start it automatically: sudo service eisyui start That worked. Now I just need to figure out how this works. First impression, I clicked to create a tile and got a list of my nodes. Every folder was fully expanded by default. The standard admin console seems to do this too. This kind of defeats the whole idea of putting things in folders. You should have them all default to closed and let the user drill down to what they want. Having all the folders expanded is almost the same as not having folders. Edited 20 hours ago by apostolakisl Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.