Geddy

Seems like you should submit a support ticket to get assistance. It might be a bug and UDI needs to review what happened.

What do you mean? What's showing "undefined"? Where? Will you provide screen shots showing what you are talking about? It's possible you need to reboot again so that everything comes up correctly. Don't try to access Admin Console or PG3x Dashboard too soon after powering on the eisy as there are a lot of processes running. Have you attempted to re-install the node servers? Go to the "purchases" area and try "(Re)Install" on node servers that you're having issues with.

No issues here. Email notifications still working as expected. Just ran a few that are triggered by programs and they spun out an email just fine. What are you using for email server settings?

@pjjameso you can have ISY devices trigger an Alexa Routine. See some of the discussion in these threads: @dbwarner5 has a post in the first thread with the steps at the time. Perhaps they still apply.

@EW1 welcome to the Universal Devices forums. It appears there are two Sonos node servers available (Sonos and ST-Sonos). Which one are you using? I think @lilyoyo1 covers the how to achieve this. Hopefully it works with the node server you're using. If not please provide more information related to your system for which node server and what Universal Device system you are using.

As @DennisC points out I'm not sure what you're referring to as "faux Node Server" (you later say that @Javi has called it that). I don't pay much attention to Elk stuff so maybe there is something like this, but just don't know. As far as I know "node servers" run on devices outside of the ISY994 that you have and feed information into the ISY994 system. In the past it was Polylgot Cloud (of course cloud based - closed last year) or Polyglot v2 that could run on rpi systems (now also not being supported by UDI or many developers). The current offering is Polyglot v3 and available only to run on Polisy or eisy. If you want a true node server process to continue with the Elk system then you would need to get an eisy (or used Polisy) and run that way. It can clearly still push data to your existing ISY994, but the Polisy and eisy are designed to replace the ISY994 and add all the functions of node servers (not just the Elk system). Since you say you don't want to migrate to another hardware then you're somewhat limited. I expect that ISY994 + Elk Module should continue to work as it does now. Knowing that UDI is ending support for ISY994 you're at the mercy of it as it is today and if you have issues getting help here (which isn't bad, IMO). I think it would possibly be wise to consider upgrade viability for your system(s) to give you even more control than you currently have with the ISY994+Elk Module.

I've learned in this process that I prefer to make sure I log out of PG3x prior to updating anything. This way it forces me to login completely (Portal then PG3x dashboard) before I'm in the system again. It's just a process I added that usually allows me to avoid such issues. I don't know if it really does or not, but I figure it can't hurt. My thought is why have an open login on a system that you're trying to update. If you log out then only system processes should be running and nothing that I might have had open/editing/updating would be locking something that might need to be updated/overwritten. Kind of like installing a Windows program...it warns you to close all other programs before installing. How many of us actually do that though? I sure don't, but with IoX/PG3/PG3x I have made it habit to log out of anything I can if I'm not using it with hopes to avoid issues on next use. Glad #4 update/reboot worked for you.

@tlightne I think with all the issues being worked on at the moment the best way to communicate with UDI about a specific issue is through the Support Ticket process. It also allows them to troubleshoot bugs in the Z-Wave and IoX system. https://www.universal-devices.com/my-tickets/ I think you recently commented that you're going to hold off on the 5.5.7 update even though you're already on 5.5.6 and have issues. I'd suggest at least updating so UDI has information from the current release to try to resolve your issue.

It's odd that it continues to come up. And no, there's no "set"/known amount of time to allow. I remember @Javi suggesting as much as 30 minutes in the early release days of the eisy. Hopefully it's not that long now, but could be at times. Thankfully, I usually perform updates when the system isn't needed so I can work on something else and come back to it. I think others had reported this window, and I know I saw it after the first update process (I think it was on 5.5.6 though...for me at least). If you still have it then be sure you clear you Java cache too just to be certain. Since there aren't lots of posts of issues with the 5.5.7 update I think a lot are finding it worked well...or just haven't tried it yet. If you continue to get it then you might want to open a support ticket to get help and give feedback directly to UDI about this issue. Ticket link: https://www.universal-devices.com/my-tickets

Correct! Yep. the issue that @garybixler posted was a "subscription" issue probably had nothing to do with updates. If you followed the URL posted previously (http://ip.of.the.isy:8080/rest/subscriptions) then the result is the .xml for what is using the subscription slots. There have been many posts about there being a limit for simultaneous connections. Typically Portal will always occupy one slot. Others might be node servers, other mobile apps using port forward, and then there's admin console (if local). It's usually a random occurrence, but @garybixler implied that it's been happening more recently. If it continues to happen try to narrow down when it happens and open a support ticket. It shouldn't be happening often.

I believe there is a 10 sub limit. It’s possible some node servers aren’t releasing correctly and you get the error. They should eventually clear, but it can happen if you’re keeping admin console open a while. It can also happen after a reboot as nodes try to update and push data to IoX. Next time you get it (or just to check) see what you get using this URL: http://IP.of.the.ISY:8080/rest/subscriptions Make sure you use your device IP. I think updates would have resolved other issues, but not the subscription issue.

Are you using any mobile apps and have a lot of node servers installed? Do you get this soon after a reboot/restart or randomly? It’s possible there are a lot of things trying to connect at once and limiting the subscriptions connecting to the ISY/IoX process. There was a URL given recently to check, but I forget what it was in relation to. I think @MrBill referenced the URL. (Sorry mobile at the moment so unable to search forums to look for it)

@mbking I experienced the same thing last night. It should give you a force update option. What version is your app?

Can report same empty, white box pops up briefly.

@PB11 try deleting the .state files and trying again. https://wiki.universal-devices.com/index.php?title=Main_Page#Admin_Console_Minimized/Invisible_and_Cannot_be_Restored

macOS sometimes doesn't handle IoX Launcher correctly. Had you connected to the ISY994 via IoX Launcher in the past? You may need to clear the cache and run start.jnlp again (for both Win and MAC computers) since it's a new device. Also, there were issues with the eisy (at initial release) that the wifi wasn't announcing itself. I'm not sure if that's been corrected or not, but you might need to add it manually in the MAC side. There was also an issue with PG3x handling some node servers when it was using the wifi setup, but I think that has also been resolved. Since I ended up putting the eisy in the same location I had my ISY994 for years I just used the hardwire LAN connection. As part of my migration I went from wifi to wired while the unit was off then performed the update once it was hardwired. I just mention the above as prior cases if you should have other unexplained issues that you might want to power down and use wired LAN (if you can) and see if that changes your experience. Glad it's working!

Not sure how large your install is, but mine isn't huge and the restore took less than 5 minutes. If it was 24 hours then something went wrong. You might be best served with a support ticket just to be certain something isn't messed up with the device and that you're up to date with firmware. https://www.universal-devices.com/my-tickets

Read the first post of this thread. Does that help?

Have you rebooted the whole device or power cycled? If you can access admin console on configuration tab there should be a "reboot" for eisy or Polisy. If that doesn't work then I shutdown the device and pulled the power for ~10 seconds and everything came up working.

@JMcKain I think next it might be a file association issue. I think I've seen this before, but I forget how it was resolved. And then I seem to think it was macOS related. I don't know how to reset the file associations in Win11, but figure should be same as win10: Settings > Apps > Default Apps > Choose defaults by file type Look for .jnlp and make sure it's associated with "Java(TM) Web Launcher".

You might want to completely remove Java from your computer. Go through the uninstall process, but also look for the Java Uninstall Tool (https://www.java.com/en/download/uninstalltool.jsp) to completely check the computer. Clear java cache (checking all 3 boxes) Uninstall Java Run Java Uninstall Tool Reboot the computer Reinstall Java Download fresh start.jnlp file. Run start.jnlp Open IoX Launcher I think sometimes the launcher is put into a strange state in the Java world and it loses the location. There's other steps to resolve this, but I don't know them as easily as just uninstalling and re-installing. That's worked for me in the past. Make sure any 3rd party Firewall and/or Anti-virus systems are off during the install part. I haven't had issues with just Windows Defender/Windows Firewall running, but I don't run Win11 yet. I'm (still) on Win10 Pro.

The "Migration backup" is only created if you're migrating locally or from Polisy to eisy ("You can migrate locally on the same Eisy / Polisy or to another Eisy / Polisy.") in this section of the wiki - https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Preparing_for_Migration_from_Eisy_/_Polisy There is no migration backup when coming from the ISY994. My guess is that when you run the Z-Wave backup on the ISY994 that it saves a file (I don't know, never used z-wave on ISY994). If so, then I'd say this is where you restore the Z-wave backup. Not just an ISY994 backup. If the Z-Wave backup process doesn't make its own file, but puts a z-wave backup into the ISY994 backup that you run then it should be included in there. It could be just missing the words "Z-Wave backup" in that step. I don't know. Since it is kind of unclear perhaps somebody that used Z-Wave on the ISY994 can chime in to help or you can open a ticket to get clarification on the process.

Make sure you follow the migration steps in the wiki: https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Preparing_for_Migration_from_ISY-994 Then on the eisy you should follow these directions: https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Migrating I did not use Z-wave in my ISY994 so did not have to worry about those steps so can't help directly. But the steps should be enough to follow. They were originally in this post so perhaps some discussion there would help with more details. I'm not sure what directions you are referring to.

@tome glad that worked. Not sure about your next question as I don’t have more than one user. I know there is mention of them in the ISY Cookbook, but I’m not sure how it is really implemented and meant to be used as I think they have all the same rights. Do you have a need/reason to have more than just admin user login? If not, I wouldn’t worry about it. I also seem to recall that even though you add a user ID or add users the list doesn’t repopulate with those user IDs or show them being used. You just have to try them out. Most will just reset the admin password and not worry about other users.

Try the default admin/admin user/password. I think it resets during the process. First thing to check once you do get in is to confirm UI and Firmware match (help -> about).