Geddy

@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

@johnnyt Since you're not using IoX then updating is fine. At this point updating the Polisy or eisy (I know you don't have the eisy, just referencing it for clarification) is done by using the "Upgrade Packages" button in IoX Admin Console for the device you're using (Note...IoX is ONLY for Polisy and eisy). The main thing you need to consider is what version of PG3 are you using? If it's current then you're good in that department. If it's not then that would upgrade as well. I think we've all learned what not keeping a system updated means at this point. It's a little more time sensitive sometimes for the Polisy (and now eisy) to get those updates when you can. While it won't really impact your situation it would mean that your system would be operating with the current releases of ioX and PG3. If something changed dramatically in a future update and the upgrade path from an outdated system to a current release system broke then might require a lot of additional work and support. no benefits to your current setup since you're using ISY994 as controller. No, it's a free firmware update to IoX. I believe those were more related to PG3x (eisy) and 5.5.5 in how PG3x handles node servers differently on the eisy than the current version on Polisy. But that's only from memory of reading too many posts. Make sure you review those posts to see if you can tell if they were eisy related or Polisy if you're overly concerned.

@Methos000 Your PG3 version and frontend version are out of sync. You'll need the help from support to get things brought up to current versions for the Polisy.

@TimWing I'm not sure if it caused this, but your screenshot in your first post seemed to have "Automatically Write Changes to Devices" turned off as well. You only need the write to battery option turned off when you restore the PLM. Part of the process is to write the updated PLM information to the other devices. Wiki steps - https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:File_Menu See "Restore PLM" on that page. I would suggest turning "Automatically Write Changes to Devices" back on, but leave the battery off and try Restore PLM again. I think trying to restore the device failed because it's (probably) looking for the PLM at the old link/address because the Restore PLM process didn't send the command out to the devices to update the new PLM address/links. Did you have a backup from before you started this? (probably not needed, but just checking if you had a recent backup in case you need to restore it and try again.)

Try the setup found in the wiki: https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide#ISYs What PG3 version are you running? I think Polisy is still on 3.1.17. Make sure you add your ISY admin user and password. Otherwise, what's "all sorts of messed up"?

https://forum.universal-devices.com/forum/113-nodelink/ A 3rd party development by @io_guy.

There was a comment from @bpwwer in another thread (not looking for it at the moment), but apparently there's an issue with 5.5.5 and PG3x that impacts users with multiple node servers running. Perhaps that's your issue and sometimes one will randomly run correctly but others wont. I'd leave things alone and stop removing/reinstalling until more updates are released. You're just creating useless work for yourself.

@K-bert also make sure you pay attention to the part about battery devices! "If you have PRO Series, click on the Battery icon at the top. This will prevent ISY from trying to update programming on your RF devices which are probably in sleep mode" IoX (on Polisy and eisy) are all "pro" versions. So if you have battery devices be sure to follow this step.

@Bobby g The best way to get this answer is to open a support ticket with UDI to get required information. https://www.universal-devices.com/my-tickets

Specifically check the setting under "My Profile" when you're logged into ISY Portal. That should have preferred ISY set at the eisy UUID. If you left the default settings in the step @MrBill links you to then you shouldn't have to do this. But if you've tried doing something manually it might be a missed step and might still be pointing to the old ISY994.

@firstone Do you happen to have a (recent) backup from the Polisy before you migrated on that device? I mention recent because the IoX would probably need to be somewhat close to what you have in the eisy. Then restore that Polisy backup on the eisy. Just a thought. Rather than having to factory reset the eisy. But, if the eisy was never used what's the harm in factory reset?

@RocKKer unsure (I do not use). But here is the additional details you can review: https://github.com/UniversalDevicesInc-PG3/udi-poly-airscape/blob/master/README.md Also, looks like the node server does offer 1 month trial so you could install to see if it works and if so how it works for you before you buy.

@TRI0N replied to your post of this same issue in the IoX support thread, but glad you started one here. I haven't had the same problem so can't help. I wasn't able to control the hue devices after initial update, but just had to restart the node server and it then allowed control through admin console and UD Mobile just fine. Since you're reinstalling are you sure that you're finding the bridge properly? Make sure you press the button on the bridge then restart the node server. When you install it is it stay "disconnected" in current status? Click on the log then change to "debug" and then "start" do any errors show up in the log on the screen? I'm not sure how much @xKing is around, but maybe you can send a log package to him to see if there's something fishy on your install that's not allowing it to connect. Others on the support thread they haven't had this issue so it's user specific currently.

@Davey A couple of things to check first: What's the firmware for IoX? Have you updated it before you tried to migrate into eisy? Current release is 5.5.5. There were some issues with earlier IoX versions that caused migration issues, but they've been fairly good as of late. If you just received the eisy and didn't update it prior to migration you might be having such issues. You said you moved the eisy and plugged in the network cable...had you initially set it up on wifi and then changed it to hard wire when you moved it to where the old ISY994 was? That shouldn't matter, but again, if it was older IoX it could be an issue. Make sure that your firmware and UI match (help -> about) - They should as long as you're using IoX Launcher (start.jnlp), but always need to make sure. Do you have a lot of battery devices that you tried to migrate? (I don't so can't help you there, but think that's been slowing some down as well) I think there's a way to turn off writing to battery devices and it might stop the update process from happening next time. Though you do need to make sure all battery devices are migrated properly.

Make sure you refresh the page. Maybe even hard refresh depending on your browser (Chrome (and edge) is CTRL + F5). Somebody earlier reported the issue and after removing a node server that wasn't in use something triggered it to match. But I just ran the update (no issues other than restarting Hue node server) and refreshed the page and showed 5.5.5 just fine.

@rahnee looks like IoX 5.5.5 is good to go now.

I 100% agree. Thankfully I do not rely on node servers so haven't worried about such issues. They really seem great for people that need them and rely on them. My system isn't that complicated and not spread between multiple ecosystems that would require node servers to monitor/control everything through ISY. I think most (as with PG2) have always just taken the leap of faith a little more blindly and trusted that there would be support for the systems they're using. To me, I've always looked at node servers as something somebody made to support their system. They then offered it to others at large through PGC/PG2. With the development of PG3/PG3x UDI gave those developers a way to get paid for their development and (ongoing) support. Some have probably been more diligent with their development and support than others. But at the end of the day I see this more as an individual offering rather than company offerings and at that level feel that ongoing usability and support should be hopeful at best. Case in point that @bpwwer mentions at least one has recently decided to abandon development and turn their offerings over to others. Sadly, people that had purchased those node servers might now have to wait for them to be usable again. I highly doubt that many individual developers have a true license that is in place. I would assume it's under an blanket license agreement with UDI as a part of the developer level process. You bring up a lot of great and valid points for your situation and concerns. Others just take the leap of faith and keep on trucking.

Do you mean trial before you buy? Or something specific to the license? @palayman many node servers do offer a trial period. This gives you the ability to install and make sure they work before you commit. That information is usually seen in the details of each node server. Elk (for example) shows this: So you can try it for a month then pay $30 to have ongoing access to it.

What kind of "disaster waiting to happen" are you envisioning? My eisy+ZMatter sits in a cabinet and doesn't get moved/touched/adjusted. So it's a set it and forget it device. Minimal disaster ability to inflict issues with it (for my install). Do you have an issue with other USB devices randomly falling out of the port they're inserted in? If so, something else is wrong. I've never had a USB device disconnect without exerting some force to remove it from the host device. I'd say this is the same for eisy + ZMatter dongle. I haven't measured it, but there are 4 total USB ports available. ZMatter takes one and PLM takes another. My ZMatter sits off the rear USB port and the PLM is in one of the 3 on the side. I'm not sure how many USB devices you plan to plug into the eisy, but there are still 2 perfectly usable ports available. And if you're worried about the ZMatter taking up space there are USB extension cables to remove the dongle from the eisy unit itself. Personally, I feel the eisy is a nice little update from the Polisy. It's a much smaller footprint and only the ZMatter antenna add to the height. It's only slightly larger than the ISY994, but has a ton of new capacity. Sure, it's not as big or bulky (or shiny) as the Polisy, but it's just as good (if not better depending on what can be run in parallel down the road).