elliott9 Posted Saturday at 09:47 PM Posted Saturday at 09:47 PM I have been running an ISY944i for a few years, recently unboxed a brand new eisy with intent to migrate to it following these instructions: https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide Plugged the new eisy to ethernet and power, used the UD Mobile app to connect it to my ISY account. I used the IoX finder to locate the new eisy, successfully logged into the Admin console. As a first step per instructions I went to Configuration tab and chose Upgrade Packages. Prompt told me to wait half an hour and when I came back an hour later the Admin Console had logged me out. I tried to find the eisy again via the IoX finder and it is not being discovered. I waited another hour and no change, so I pulled power to eisy and reconnected power. Waited another half hour and still IoX finder not locating the new eisy. Confirmed the ethernet port has link activity lights so doubt a network issue. I am guessing update went sour. Anybody have experience in this? is there a factory reset process? Quote
Guy Lavoie Posted Saturday at 10:37 PM Posted Saturday at 10:37 PM I'd start with the java clear cache (all 3 checkboxes) first. Then manually adding the eisy in the finder "https:/192.168.x.x:8443/desc" Try that Quote
Techman Posted Saturday at 10:46 PM Posted Saturday at 10:46 PM @elliott9 It's normal for your admin console to shut down after a firmware update. After you clear your java cache download the admin console from here: https://isy.universal-devices.com/start.jnlp The admin console always needs to be updated after a firmware update Quote
elliott9 Posted Saturday at 10:58 PM Author Posted Saturday at 10:58 PM 11 minutes ago, Techman said: @elliott9 It's normal for your admin console to shut down after a firmware update. After you clear your java cache download the admin console from here: https://isy.universal-devices.com/start.jnlp The admin console always needs to be updated after a firmware update I just cleared java cache and used that link to open admin console, which opens the IoX finder. As before it does see my old ISY but the new Eisy is not discovered. Quote
elliott9 Posted Saturday at 11:06 PM Author Posted Saturday at 11:06 PM (edited) 29 minutes ago, Guy Lavoie said: I'd start with the java clear cache (all 3 checkboxes) first. Then manually adding the eisy in the finder "https:/192.168.x.x:8443/desc" Try that I just looked up the IP address in my DHCP server. Confirmed it was correct by SSHing into it, which required factory default credentials. However looks like port 8443 isn't open as IoX finder reports to "Not Found" when I ender https://192.168.x.x:8443/desc (except using my IP of course). Also browser to that location also reports nothing. I think upgrade went sideways somehow. Edited Saturday at 11:07 PM by elliott9 Quote
Techman Posted Saturday at 11:07 PM Posted Saturday at 11:07 PM Are you on a MAC or PC? ISY Not Found If IoX Launcher cannot find your device (ISY994 [EOL], Polisy, eisy): Most importantly, you need to reinstall the IoX Launcher VPN software is running on your computer or you're on a VPN network Unit is not on the same network as your compute. Perhaps you changed routers? If so: follow these instructions If not #1, please open your router page and see whether or not you see ISY994-EMS (for ISY994 [EOL]), polisy (for Polisy), or eisy (for eisy) in the list of LAN clients. If you find the IP address, then, in IoX Finder, click on the Add button and enter ISY994: http://1.2.3.4/desc (replace 1.2.3.4 with the actual IP of ISY in the router) Polisy/eisy: https://1.2.3.4:8443/desc (replace 1.2.3.4 with the actual IP of Polisy/eisy in the router) If not #2, then perhaps the unit is not powering on: ISY994: Please make sure the LED pattern is as outlined here Polisy: Reboot the unit, all 3 LEDs should get lit and then only the left most is lit. Wait for 30-60 seconds. You may hear a beep. eisy: Reboot the unit, allow 2-3 minutes for everything to boot and stabilize before attempting to open IoX Launcher If not #3, the issue is that you might have firewall/VPN or antivirus software (especially VPN) blocking network communications. Quote
Techman Posted Saturday at 11:15 PM Posted Saturday at 11:15 PM @elliott9 Try removing power from the eisy again. If that doesn't work then you should probably submit a support ticket Quote
srpronto Posted Saturday at 11:16 PM Posted Saturday at 11:16 PM I have observed the same behavior. I was going to migrate my old ISY config to the new eisy. Was able to find the device and get the admin console up. Following the directions I proceeded to to an 'Upgrade Packages'. After a two hour wait for the update to complete, the interface was timed out. I tried to run IOX Finder to no avail. I looked at my DHCP server and found that the address had changes so I flushed the cashes and powered down the eisy and restarted it. After a few minute wait I retried the connection - again with no luck. I tried explicit ip addressing with correct ports again no response. I am able to ping the eisy at the new ip address. I then SSH to the eisy and checked on the listened ports - i did not see 8443 in the list. In fact I only saw SSH. Running 'service -e' to list the running services is did not see anything that looked like IOX but I don't know what the correct service would be. I suspect that the IOX service did not restart after the upgrade. This is not an 'eisy' upgrade by any means. Does anyone have a suggestion on something that I might have missed? Quote
bmercier Posted Saturday at 11:27 PM Posted Saturday at 11:27 PM Just an FYI if you are using a Mac: After the latest mac update, users must now enable local network access for chrome and Admin Console. The permission dialog is only shown once, so if you denies/ignores it, you will need to manually enable on MAC > System Settings -> Privacy & Security -> Local Network 1 Quote
elliott9 Posted Saturday at 11:33 PM Author Posted Saturday at 11:33 PM (edited) I am on PC. but I will reiterate that the network and PC I am using were able to access the device just fine until I did the eisy update. nothing else has changed, has only been a few hours. something is up with the eisy upgrade. 17 minutes ago, srpronto said: I have observed the same behavior. I was going to migrate my old ISY config to the new eisy. Was able to find the device and get the admin console up. Following the directions I proceeded to to an 'Upgrade Packages'. After a two hour wait for the update to complete, the interface was timed out. I tried to run IOX Finder to no avail. I looked at my DHCP server and found that the address had changes so I flushed the cashes and powered down the eisy and restarted it. After a few minute wait I retried the connection - again with no luck. I tried explicit ip addressing with correct ports again no response. I am able to ping the eisy at the new ip address. I then SSH to the eisy and checked on the listened ports - i did not see 8443 in the list. In fact I only saw SSH. Running 'service -e' to list the running services is did not see anything that looked like IOX but I don't know what the correct service would be. I suspect that the IOX service did not restart after the upgrade. This is not an 'eisy' upgrade by any means. Does anyone have a suggestion on something that I might have missed? These symptoms overlap mine 100%. Even my DHCP server shows it assigned a new lease. Nothing is running to listen to port 8443: [admin@eisy ~]$ lsof -nP -iTCP -sTCP:LISTEN lsof: WARNING: access /home/admin/.lsof_eisy: No such file or directory lsof: WARNING: created device cache file: /home/admin/.lsof_eisy [admin@eisy ~]$ sudo lsof -nP -iTCP -sTCP:LISTEN Password: lsof: WARNING: access /root/.lsof_eisy: No such file or directory lsof: WARNING: created device cache file: /root/.lsof_eisy COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME mosquitto 1272 nobody 4u IPv6 0xfffff80146afea80 0 TCP *:1884 (LISTEN) mosquitto 1272 nobody 5u IPv4 0xfffff80146afe540 0 TCP *:1884->*:* (LISTEN) sshd 1389 root 3u IPv6 0xfffff80146afe000 0 TCP *:22 (LISTEN) sshd 1389 root 4u IPv4 0xfffff80026376a80 0 TCP *:22->*:* (LISTEN) mosquitto 3668 isy 10u IPv4 0xfffff80200e39540 0 TCP *:8881->*:* (LISTEN) mosquitto 3668 isy 14u IPv4 0xfffff80200e39000 0 TCP *:8882->*:* (LISTEN) mosquitto 3668 isy 15u IPv6 0xfffff80200d6aa80 0 TCP *:8883 (LISTEN) mosquitto 3668 isy 16u IPv4 0xfffff80200d6a540 0 TCP *:8883->*:* (LISTEN) [admin@eisy ~]$ netstat [-j jail] -Q [admin@eisy ~]$ netstat Active Internet connections Proto Recv-Q Send-Q Local Address Foreign Address (state) tcp4 0 128 192.168.200.194.ssh 192.168.200.142.54890 ESTABLISHED tcp4 0 0 localhost.8883 localhost.47323 ESTABLISHED tcp4 0 0 localhost.47323 localhost.8883 ESTABLISHED tcp4 0 0 localhost.8883 localhost.41361 ESTABLISHED tcp4 0 0 localhost.41361 localhost.8883 ESTABLISHED udp4 0 0 192.168.200.194.ntp *.* udp6 0 0 fe80::7195:ca40:.ntp *.* udp4 0 0 localhost.ntp *.* udp6 0 0 fe80::1%lo0.ntp *.* udp6 0 0 localhost.ntp *.* [admin@eisy ~]$ service -e /etc/rc.d/hostid /etc/rc.d/zpool /etc/rc.d/zpoolupgrade /etc/rc.d/zpoolreguid /etc/rc.d/zvol /etc/rc.d/hostid_save /etc/rc.d/kldxref /etc/rc.d/zfsbe /etc/rc.d/zfs /etc/rc.d/devmatch /etc/rc.d/cleanvar /etc/rc.d/ip6addrctl /etc/rc.d/mixer /etc/rc.d/rctl /etc/rc.d/netif /etc/rc.d/devd /etc/rc.d/resolv /etc/rc.d/rtsold /etc/rc.d/newsyslog /etc/rc.d/virecover /etc/rc.d/gptboot /etc/rc.d/motd /etc/rc.d/os-release /etc/rc.d/cleartmp /etc/rc.d/dmesg /etc/rc.d/syslogd /etc/rc.d/savecore /usr/local/etc/rc.d/dbus /etc/rc.d/utx /etc/rc.d/ntpd /etc/rc.d/sshd /etc/rc.d/cron /etc/rc.d/bgfsck Edited Saturday at 11:34 PM by elliott9 Quote
bpwwer Posted Sunday at 12:20 AM Posted Sunday at 12:20 AM @elliott9 Looks like you know a fair amount about unix like systems and how to poke around them. UDI as a couple of applications that run and manage things. You can check the log files for these. /var/udx/logs/log /var/udx/logs/debug.log This service is what actually manages the updates. If it had issues, it can leave things is a state where stuff just doesn't work. In some cases, re-booting multiple times can get it to clean things up. /var/isy/FILES/LOG is where the IoX log files are located. There are a number of them. One of these may help determine what's wrong. Quote
Guy Lavoie Posted Sunday at 01:53 AM Posted Sunday at 01:53 AM Interesting that during the first days of the 5.9.1 update, no eisy's had problems. But now, what looks like two new, out of the box units have the same issue. Did anyone notice if they were running 5.8.4 when first powered up? Quote
cutthroat Posted Sunday at 02:53 AM Posted Sunday at 02:53 AM Add me to the list of an upgrade failure. Everything was working fine, did the upgrade package and after waiting around 45 minutes still can't get into anything. Tried a reboot. debug.log is showing this. 2025-03-08 20:51:04 - DBG3|SysCall [T:40422088974336] issuing system call /usr/local/etc/isy.d/static/isy_startup.sh (../src/Kernel/SystemCall.cpp@67:execOnly()) 2025-03-08 20:51:04 - Info|Config [T:40422088974336] starting to parse file /var/isy/.env, delim = = (../src/Config/UDXConfig.cpp@20:parse()) 2025-03-08 20:51:04 - Info|UDXThread [T:40422088974336] initializing (../src/System/UDXThread.cpp@494:init()) 2025-03-08 20:51:04 - Info|UDXThread [T:40422088974336] setting scope to 2 successful (../src/System/UDXThread.cpp@186:setThreadScope()) 2025-03-08 20:51:04 - Info|UDXThread [T:40422088974336] setting joinable to true for [0] (../src/System/UDXThread.cpp@229:setJoinable()) 2025-03-08 20:51:04 - Info|UDXThread [T:40422088974336] setting joinable successful for [0] (../src/System/UDXThread.cpp@237:setJoinable()) 2025-03-08 20:51:04 - Error|Config [T:40422088974336] invalid value length (../src/Config/UDXConfigRecord.cpp@141:parse()) 2025-03-08 20:51:04 - Error|Config [T:40422088974336] could not add line: IFS= (../src/Config/UDXConfigRecords.cpp@35:parse()) 2025-03-08 20:51:04 - Info|RunConfig [T:40422088974336] changing directory to /var/isy (../src/System/UDXMain.cpp@135:main()) 2025-03-08 20:51:04 - Info|RunConfig [T:40422088974336] the system is "eisy" v.5.9.1_11, running from /var/isy (../src/System/UDXMain.cpp@143:main()) 2025-03-08 20:51:04 - Error|RunConfig [T:40422088974336] failed verifying signature (../src/System/UDXMain.cpp@147:main()) Quote
cutthroat Posted Sunday at 03:27 AM Posted Sunday at 03:27 AM ok, was able to get mine back up and working. I ssh'd in and reran the package install. sudo pkg install -f isy then rebooted. 1 1 Quote
Michel Kohanim Posted Sunday at 05:15 AM Posted Sunday at 05:15 AM As mentioned in the instructions for upgrade, please do NOT reboot till you can get back to the unit. The upgrade is about 10GB of download, decrypt, extract, and install. During this process, the unit gets rebooted at least once. So pleased please please, if you don't have the patience to wait, do NOT upgrade. If you're concerned that there's an issue with your upgrade, rather than rebooting please submit a ticket. Yes, the upgrade might take more than one hour (and even two) depending on your network speed. With kid regards, Michel Quote
elliott9 Posted Sunday at 06:04 AM Author Posted Sunday at 06:04 AM 45 minutes ago, Michel Kohanim said: As mentioned in the instructions for upgrade, please do NOT reboot till you can get back to the unit. The upgrade is about 10GB of download, decrypt, extract, and install. During this process, the unit gets rebooted at least once. So pleased please please, if you don't have the patience to wait, do NOT upgrade. If you're concerned that there's an issue with your upgrade, rather than rebooting please submit a ticket. Yes, the upgrade might take more than one hour (and even two) depending on your network speed. With kid regards, Michel We'll it is peculiar to me to not offer the user any kind of progress tracking or logs to monitor. In absent of that it seems irresponsible to give a prompt that update could take up to half in hour if in reality it could take 2 hours. My internet is plenty fast, it wouldn't take hours to download a 10g file to my PC, but I cannot speak to how the time would change on the eisy. Seeing as how I can get to the Linux system, perhaps you can provide me file(s) I need and I can SCP them to the eisy myself and attempt a local install. Or do you have another recommendation? Quote
Michel Kohanim Posted Sunday at 06:22 AM Posted Sunday at 06:22 AM Recommendation is to submit a ticket. With kind regards, Michel Quote
jkmcfadden Posted Sunday at 01:05 PM Posted Sunday at 01:05 PM Add me to the list of failed upgrades. I was on 5.8 something. I waited over an hour and nothing, so I rebooted. Still nothing. I had a backup so I could do a hard reset and reinstall, but I figured what the heck. So, I connected up my monitor and executed the command listed above by cutthroat and that worked for me. I love my eISY but I cringe and hold my breath every time I do an upgrade. It is the only time I ever have issues. I agree, some type of status should be available other than "it should take about 30 minutes". Quote
tokenworker Posted Sunday at 06:04 PM Posted Sunday at 06:04 PM (edited) Add me to the list of failed upgrades—I've had a 994 for about 10 years. I just got my EISY and it fired right up. I dutifully followed the instructions for migrating from the 994, which included a step to perform an upgrade. I saw a warning about waiting 30 minutes, but that it would continue to work. I clicked the upgrade button, and since then it has been unresponsive. I have since tried a factory reset (10 button presses), one button press for update, and five button presses for reboot. I have a 1G fiber internet connection, and my EISY is on the LAN, so it’s probably not a download speed issue. I also tried searching for the device using the mobile app, but had no luck. I can see both devices on my LAN. I tried https://192.168.0.193:8443/desc but received a refused to connect message. I guess I'll open a ticket as well—terrible new user experience. Update: I logged in with PuTTY - SSH - so eisy is still somewhat functional - Guess I'll try install command. Update: Using Putty - SSH - I tried these commands found in this forum and was able to bring the eisy back on-line. Now I'm having issues with the serial PLM not connecting. sudo pkg install -f isy sudo pkg install -f udx sudo tail -f /var/udx/logs/log ... wait till it either errors out (let me know the error) or successfully starts. If successfully starts: sudo shutdown -r now After eisy rebooted, it was instantly recognized by phone and IoX finder. Edited Monday at 12:36 PM by tokenworker Quote
elliott9 Posted Sunday at 07:44 PM Author Posted Sunday at 07:44 PM 6 hours ago, jkmcfadden said: Add me to the list of failed upgrades. I was on 5.8 something. I waited over an hour and nothing, so I rebooted. Still nothing. I had a backup so I could do a hard reset and reinstall, but I figured what the heck. So, I connected up my monitor and executed the command listed above by cutthroat and that worked for me. I love my eISY but I cringe and hold my breath every time I do an upgrade. It is the only time I ever have issues. I agree, some type of status should be available other than "it should take about 30 minutes". You have the guide handy for a hard reset? Quote
cutthroat Posted Sunday at 07:59 PM Posted Sunday at 07:59 PM 14 hours ago, Michel Kohanim said: As mentioned in the instructions for upgrade, please do NOT reboot till you can get back to the unit. The upgrade is about 10GB of download, decrypt, extract, and install. During this process, the unit gets rebooted at least once. So pleased please please, if you don't have the patience to wait, do NOT upgrade. If you're concerned that there's an issue with your upgrade, rather than rebooting please submit a ticket. Yes, the upgrade might take more than one hour (and even two) depending on your network speed. With kid regards, Michel I did not reboot my system until I got into the system via ssh and looked at the logs and saw the system crashing with core dumps. Here is the log entry when the system auto rebooted. Mar 8 20:31:31 eisy shutdown[74622]: reboot by udx_installer: Below is when the system came up from the first reboot that the upgrade script did. This is the first log entry of the core dump, note time. Mar 8 20:32:21 eisy kernel: pid 1723 (isy-freebsd-x64), jid 0, uid 349: exited on signal 11 (core dumped) ... Mar 8 20:45:31 eisy kernel: pid 36451 (isy-freebsd-x64), jid 0, uid 349: exited on signal 11 (core dumped) Mar 8 20:45:51 eisy kernel: pid 37202 (isy-freebsd-x64), jid 0, uid 349: exited on signal 11 (core dumped) Mar 8 20:46:12 eisy kernel: pid 38065 (isy-freebsd-x64), jid 0, uid 349: exited on signal 11 (core dumped) Mar 8 20:46:20 eisy reboot[38293]: rebooted by admin I didn't reboot this system too soon. Note the 14-minute time gap with constant core dumps and when I rebooted it. The upgrade process failed. Are you saying the system should core dump constantly for 2 hours? Quote
jkmcfadden Posted Sunday at 08:16 PM Posted Sunday at 08:16 PM (edited) 32 minutes ago, elliott9 said: You have the guide handy for a hard reset? Eisy:User Guide - Universal Devices, Inc. Wiki Yep - I had to do this once before. It restores it to its original setting and then you can install your most recent good backup. Good Luck! Edited Sunday at 08:17 PM by jkmcfadden Quote
Michel Kohanim Posted Sunday at 08:35 PM Posted Sunday at 08:35 PM Please do not do that. Please submit a ticket. All these variations and factory reset and reinstall etc. will not help us find the root cause. Please please please submit a ticket. With kind regards, Michel Quote
Solution Michel Kohanim Posted Sunday at 10:04 PM Solution Posted Sunday at 10:04 PM For anyone having this issue, please note that the more you fiddle with files/services, the less the likelihood that you can recover. So, please do this: 1. Press/hold the power button -> red. Click again -> blue 2. If this does not solve the issue, please SUBMIT A TICKET. This is my last message on this topic. With kind regards, Michel 3 Quote
elliott9 Posted Monday at 01:14 AM Author Posted Monday at 01:14 AM Alright I've opened ticket #26516 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.