Geddy

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

Did you launch admin console before trying to launch PG3x? Did you reboot the eisy or power cycle? if you got the message that updates were needed it probably hadn’t finished updating yet. Make sure you give a good amount of time before trying to launch admin console again.

Mostly it's up to personal preference and what you're used to or what you're using. If you're starting fresh/new then you need to research what you want to achieve out of a system and what system would work best for you. Only you know that (at this point). So not much here to help you figure that out until you know what you want/need in a system. These forums are more support than "pre-sales" research. As such most here will be biased (more than likely) and just tell you what you can do with eisy and the ISY foundation that you might remember. The best place to get info is through the UD website. I think you spoke volumes though when you say "simple system to setup". If you're truly starting from scratch and don't have any automation or switches in the house then you've got to look for a total system that will fit your goals and desires. If that's Insteon and then if you want the ISY system (in the eisy) for the largest option for customization then we'll see you back here once you've installed your devices and have your eisy setup. I think the prevailing fact is (you'll probably see it in a few posts in Coffee Shop asking what system to install) all systems have faults. It's what fits your wants, needs, and budget the best will be the best for YOU.

Well, if you're able to do all that you're doing and running Linux on a Mac then just google how to run jnlp files on java v8 for linux. Don't know if it works, but better than nothing. You've got to figure large majority of users here will be Windows or Mac users that don't dabble in linux. I'm sure the vocal linux users will chime in to say I'm wrong, but whatever, you're all |33+. I'm not sure why the aversion of just installing java to use to gain access to the system. It's not like you're some of these that sit with admin console open endlessly tweaking/watching/monitoring the system. Just install Java, access admin console to make your changes, clear java cache then delete the install. You've added a million steps to try to avoid the simple process. Hope you get it sorted out!

I understand this was to be a warning that the update is still in process. I've never personally seen it so haven't experienced that or any lockup. Depending on how long it had been since the initial pushing of the button it could have interrupted the process. I would suggest pressing the eisy power button once (this is the update process using the "multi function button"). Give it "a while". I know I gave it over 15 minutes on my attempted update. Then part of the process is to reboot the device. I'm not one to randomly pull the power so I press the multi function button 6 times to shut it down. Once the power light was red I pulled the power. Waited ~10 seconds and plugged it back in. For my update I was able to access admin console again, but PG3x was not loading so did power cycle the eisy. It then ran (and continues to run) perfectly. NOTE: Since I was able to get into Admin Console, @Michel Kohanim does confirm the "reboot" option on Configuration tab is the same as a power cycle (for those that have the eisy (or polisy) in hard to reach locations).

@leecast on the programs that you're running right click and select "copy to clipboard" and post them in a reply here. Maybe some of the programming gurus can help sort things out. Also, what model motion sensor are you using? I think the 1st version had some issues with the ISY994 and figure it might still have issues with eisy. I've never used Insteon motion sensors so don't know much about the issues they were causing, but sounds like it might be what you're experiencing.

@gviliunas Power cycle the polisy/eisy. I just ran the update to get a feel for what happened. I had similar issue that could get into admin console without issue and PG3x (eisy) wouldn't load. Shut down (6 button presses for the eisy), pulled power, waited a few seconds, plugged in. All works fine. @DennisC - I can confirm that I have 4 node servers running and all came up running/connected after reboot. I know you were asking on another thread specifically to multiple node servers coming back up correctly. They appear to be fine.

@gviliunas Make sure to give it a lot of time. Have you been able to log back into Admin Console yet? I think there are a lot of things being updated with this release given the issues of the past weekend. So I'd give this update a little extra time.

@asbril clear your java cache (check all three boxes in the process) and run start.jnlp again (probably a clean/new download just to be sure) and it will work.

@TSinclair looks like this finally got implemented into IoX with 5.5.6 release..."wider node selection boxes"

Just to be sure - currently there's no need to add any microSD card to the eisy. (Pic from UDI site) Interesting that it was left off the UD site as far as specs go (nice catch @tazmanto link it to the specs posted last year). Mine is mostly covered up by the ZMatter dongle currently so didn't want to shut it down to test adding a card. @MrBill interesting thought to have used that to migrate. Would have probably been a bigger programming issue rather than the restore backup option.

Same place it's always been - https://wiki.universal-devices.com/index.php?title=Main_Page Currently the best way to get node servers to link YoLink to your ISY is through eisy. You can continue to use your current ISY994 if you cannot get all the parts needed through the Canada distributor for UDI. I think others had said some items were not currently in stock. That I'm not sure. I don't use YoLink so don't know the process. I would assume so, but you need to read their site first to figure out how to make their system work.

What are you trying to achieve? If what you have is "working good" are you just wanting to upgrade your system to the current offerings from Universal Devices? If that's the case, then you would want an eisy+ZMatter dongle+PLM Kit Being that your in Canada you will need to see if the Canada distributor has the parts you need before you go too much further in your questions. If you're wanting to add YoLink and CAO Wireless tags to your system you will need the eisy to run Node Servers. I'm not sure if there was a YoLink node server in PG2 that would possibly run on a rpi system, but that's no longer supported so the current route is eisy with Polyglot V3x (PG3x). You can see from the forum area for Polyglot V3 what other node servers are available once you get an eisy. The Polisy is no longer available unless you buy from other sources where people might be selling their Polisy as they upgrade to the eisy. Sounds like it might be worth your time to read Universal Devices' website! https://www.universal-devices.com/

Not sure what questions didn't get answered in the post you mention. All questions were answered then the thread had additional posts about unrelated items; yes, it was locked. What's your question? It's hidden and more of a statement. As answered in the @johnnyt post - you can run Polisy (or eisy) and still control your ISY994 with node servers. Your issue seems to be uncertainty around ZMatter/Z-wave - You can run Z-wave through ZMatter on the Polisy/eisy, but note that you would need to control that with IoX running on the Polisy/eisy. Your ISY99 would NOT control Z-wave because it would not be controlled by the ISY994 device. You have 2 different hubs controlling 2 different systems. Do you currently have Z-Wave board on your ISY994 and controlling Z-Wave items? Do you want to "migrate" them to Polisy/ZMatter? I don't know what your real question is there as it's hidden in a bunch of strange statements. Maybe link to the statements that you're quoting (or attempting to quote). It would help anybody reading your post. I guess the answer to this is what are you migrating? Do you have Z-Wave devices on the ISY994 that you're migrating? You never clearly identify what you're migrating. The migration process is fairly simple on the surface consideration. Sure, the process has some flaws, but they're being worked out. ISY994 Insteon Migration - moves ONLY Insteon devices to IoX Z-Wave Migration - moves ONLY Z-Wave devices to ZMatter If you're trying to run a partial system in the new Polisy+ZMatter then I would not suggest that you later try to migrate Z-Wave from something else to ZMatter because you would have an existing setup that would be overwritten. That's fairly simple when you think of migrating. If you migrate an existing system into another existing system the later is overwritten by the new migration process. If you are NOT running any Z-Wave on the ISY994 and only Insteon then you would just migrate the Insteon devices to Polisy/IoX. That would not overwrite anything you have setup on ZMatter. In that process you are only restoring the Insteon backup made from the ISY994. From my own experience: I am currently running the eisy. I started using ZWave with the eisy and installed ZMatter and added two (2) Z-Wave outlets. I then migrated my ISY994 to IoX. I only had Insteon devices on my ISY994. I moved the Serial PLM over with the USB to Serial Connector cord (similar to the kit offered by UDI) restored my backup and checked everything out. It was very simple at the time I attempted the process. I believe the whole process took about 30 minutes because I took my time (and needed to relocate the eisy to where the ISY994 was previously). I think my migration was around IoX 5.5.3 just for version information. I later took my Polisy to my father-in-law's house and performed an ISY994 to IoX (on Polisy) migration for a simple install in less than 20 minutes. His IoX version was 5.5.4 during the migration process. Based on my recent experience it's quite simple. Sure, there might be some issues now with IoX 5.5.5 so don't press the "upgrade packages" button at the moment. At least not until we hear more from UDI about a release (this issue is being discussed elsewhere so let's keep that discussion in the support thread). If this doesn't answer your "questions" please rephrase your questions without the useless statements. Or at least link to the quotes you're inserting so we can read the context that you're pulling them from.

IoX = ISY on Anything (as announced/documented by UDI) It is specifically meant for ISY running on Polisy and eisy as of now. It's not deemed backwards compatible with ISY994 so that remains simply "ISY", but specifically for ISY994 devices. Remember that ISY is a service, ISY994 is the device running the ISY service. Polisy and eisy are devices running the ISY and Polyglot services. Each of those services have different version values. IoX appears to be able to stay at the same version for Polisy and eisy. At least to this point. People with Polisy and eisy have all been able to update to 5.5.5. In the initial release of the eisy both PG3x and PG3 had identical PG3 version numbers. PG3x (eisy) has since been updated to 3.1.22 while PG3 (Polisy) remains at 3.1.17. Yes, it gets confusing, but not really that much as all the "Current Release" posts are in the Current Release area of the forums. So it's easy to see what's "current". (That's by design!) I think I'm going to lock this thread now because it's kind of drifted off course. I think @johnnyt got the answer to the original question.

PG3/PG3x is different than IoX versions. PG3 refers to the Polyglot version running the node servers. Polisy is PG3 and (I think) is currently 3.1.17 eisy is PG3x and currently 3.1.22