elliott9

Alright I've opened ticket #26516

You have the guide handy for a hard reset?

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?

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. 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

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.

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.

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?

I was experiencing the same thing cap60552 mentioned in that every spoken was responding with "there are multiple devices by that name, which one?". This would continue even if I repeated myself and no matter which device I was trying to interact with. I did not do the troubleshooting (unlinking and what not) that cap mentioned but instead came here to find this thread. I just checked again and all of my spokens phrases are working properly. I have made not changes and bmercier says he has not changed anything on my behalf so it seems likely to me that Amazon has having some kind of cloud issue that has since recovered. I'll keep an eye out through the day and speak up if I experience another occurrence.

Thanks. PM sent.

I am experiencing identical symptoms starting this morning. I am running 4.7.3

Well now I am a sad panda. It seems like Universal Devices could had overcome this Amazon shortcoming with an Alexa Skill. Now a Smart Home skill, just a normal skill so you can use the phrase "Ask [skillName] for status of [thing]. I guess I'll live.

For the past year I have been using the Alexa v2 Smart Home skill to set most of my devices with the "Alexa, turn on X" or "Alexa, turn off Y". Whenever I wanted the status of something I had the normal ISY skill installed and I would ask for it by "Alexa, ask Izzy for status of X" to which she would respond On/Off. I have since replaced by Alexa v2 Smart Home Skill with the Alexa v3 Smart Home skill and I can turn devices on/off with no problem. However I have lost my ability to get the status of anything. The old ISY skill delinked itself with the my.isy portal and attempting to relink it says the ISY Skill obsolete. In the my.isy portal I have enabled Live Update feature and then tried things like "Alexa, what is the status of X" and "Alexa, is Y off?" but none of that works. So two questions: Can I still use Alexa to retrieve the status of ISY devices and scenes? Is so... What is the phrase I should use to do so?

Ah! My firmware was 4.4.6 but my UI was older. I grabbed the new UI, reset my location, and recyned NTP and all fixed!

The box rechecks itself within a microsecond and the save button never enables itself (remains unclickable). Can you point me to the most proper place to report a bug to UDI?

My ISY has the system time off by 1 hour. Location is set to pre-defined location USA, AZ, Phoenix and polling pool.ntp.org daily. I can see the problem, DST is checked as on and in Arizona we do not observe DST. If I click to uncheck the DST box the Admin Console will re-check it immediately. If I wait a few seconds (for the Busy message to go away) the box remains checked and the time remains off. I am able to manually set the time (or sync it to my PC) which corrects the time but as soon as NTP polls it gets reverted back to 1 hour off. I tried setting a custom location but using Google Maps to convert my address to GPS Coordinates but the Admin Console tells me my longitude value is wrong.

Am I safe to assume the instructions linked above would work identically if I am replacing an ISY994i with a ISY994i PRO? If there a recommended time to perform this where the Transfer of Module will take less time? (eg do the guys not work weekends or perhaps?)