johnnyt Posted January 20, 2023 Posted January 20, 2023 I'm still on 994i and only using Polisy for PG3/Node servers. Can I just upgrade to latest version (5.5.4 as of today) and everything should work fine? Or am I committed to doing a migration if I do that? I'm not sure if there's anything to gain in terms of bug fixes but thinking this is a way to take a baby step to get that part of the process done and make sure everything works fine starting with that. Then, as a subsequent baby step after that, could I install my zmatter board and test it with IoP and a couple of devices not in use with 994i, i.e. starting from scratch as though I had just bought the Polisy?
lilyoyo1 Posted January 20, 2023 Posted January 20, 2023 (edited) 2 hours ago, johnnyt said: I'm still on 994i and only using Polisy for PG3/Node servers. Can I just upgrade to latest version (5.5.4 as of today) and everything should work fine? Or am I committed to doing a migration if I do that? I'm not sure if there's anything to gain in terms of bug fixes but thinking this is a way to take a baby step to get that part of the process done and make sure everything works fine starting with that. Then, as a subsequent baby step after that, could I install my zmatter board and test it with IoP and a couple of devices not in use with 994i, i.e. starting from scratch as though I had just bought the Polisy? The latest firmware for the 994 is 5.3.4 for those using zwave devices with the 500 series zwave. For those using zwave devices with the 300 series board the latest firmware is 5.0.16c. 5.5.4 is for polisy and EISY users only. @Geddyis it possible to add a note in red for polisy/EISY firmwares that the latest firmwares are for polisy/EISY users. The way it currently reads, it can be misread as if it can used for any system. Personally, If you're not well versed with what you're doing, I'd leave it alone until you're more comfortable with migrating or start from scratch. Depending on whether you use insteon or zwave, you can cause more issues than you solve with baby steps. With that said, yes, you can use unused devices with eisy to test while you have your isy994 connected.. if you use insteon, just make sure you have a second plm for your eisy Edited January 20, 2023 by lilyoyo1 1
johnnyt Posted January 21, 2023 Author Posted January 21, 2023 2 hours ago, lilyoyo1 said: 5.5.4 is for polisy and EISY users only. @lilyoyo1 I'm referring to updating my Polisy, not my 994i. I mentioned the 994 to make the point that I'm not using IoP on the Polisy. (I probably should have just said that.) If possible, I'd like to try the zmatter board to confirm it works before I even attempt a migration, not to mention make sure my Polisy upgrades okay. I think I read of some ending up bricked doing upgrades relatively recently. Mine bricked doing BIOS upgrade several months ago because I have one of the early models that needed a special chip mailed to me in order to get the latest BIOS installed. Then, when I got it, there was a picture of where it goes but no instructions that said I had to remove it after it finished booting. I ended up with NO Polisy / Node Servers for about a month while I waited *twice* for the chip to get to me. What if something else related to early h/w version (or any other multitude of reasons) causes a problem not caught yet because so far everyone else trying is not in same situation I am? With the following amount of stuff running on my 994i, I'm definitely waiting until things are more stable before I do the migration but am also in a hurry to get there because the 994i is (has been) struggling to say the least. I'm also going to do as many steps as I can *before* I do the migration to rule out or solve problems that might occur before what I fear will be - assuming no hardware problems - a multi day process.
johnnyt Posted January 23, 2023 Author Posted January 23, 2023 I'll add that my Polisy is at 5.4.5. I don't think I've updated it since last spring, adding to my worries that Murphy's Law will apply here.
johnnyt Posted February 9, 2023 Author Posted February 9, 2023 Let me ask my question differently. Given I'm not yet using IoP but I am using PG3 for 6 node servers (on a Polisy) and those need to keep working, does upgrading to the latest IoX version - now at 5.5.5: 1) offer any benefits, other than getting it out of the way (since I do plan to move to IoP)? 2) have any cost? I did see there were problems using PG3 when 5.5.5 came out but appears those were fixed a week ago now.
Solution Geddy Posted February 9, 2023 Solution Posted February 9, 2023 @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. 14 minutes ago, johnnyt said: 1) offer any benefits, other than getting it out of the way (since I do plan to move to IoP)? no benefits to your current setup since you're using ISY994 as controller. 14 minutes ago, johnnyt said: 2) have any cost? No, it's a free firmware update to IoX. 15 minutes ago, johnnyt said: I did see there were problems using PG3 when 5.5.5 came out but appears those were fixed a week ago now. 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. 1
ShawnW Posted February 9, 2023 Posted February 9, 2023 1 hour ago, johnnyt said: Let me ask my question differently. Given I'm not yet using IoP but I am using PG3 for 6 node servers (on a Polisy) and those need to keep working, does upgrading to the latest IoX version - now at 5.5.5: 1) offer any benefits, other than getting it out of the way (since I do plan to move to IoP)? 2) have any cost? I did see there were problems using PG3 when 5.5.5 came out but appears those were fixed a week ago now. @johnnyt Hi there! I was also in your EXACT situation in the fall with my Polisy (being very out of date, needing chip shipped to Canada, etc.), so I understand your hesitation. As of today, I am also in your (today's) exact situation - still using my ISY and have a Polisy w ZMatter with a couple node servers. The only difference is that I HAVE been keeping my Polisy up to date and am currently at 5.5.5. I can tell you that in your situation I don't expect you would have any issues updating your Polisy to 5.5.5 at this point based on my experience. I've been reading the forums a lot the last few months and it seems that most of the issues are with migrating from ISY994 to IoX on either Polisy or EISY. I have a 'bunch' of Zwave devices and so I've been biding my time and waiting to migrate. I've decided that when I do the migration I will do a partial migration - any of my ZWave devices that have S2 and or are not functioning in the way that i think they should, those devices will be un-installed fully before I migrate, then will re-add them to the new system when migration is complete. That's about half of my ZWave devices. I also did as you suggested and after installing ZMatter I installed a couple Insteon and ZWave devices to it from scratch to make sure the new ZMatter board was working well - seems like a very smart test to me. There's only been a couple people on the forum mention that the board didn't work for them, but I would still do this test if I were you (can't hurt). Do this after getting your Polisy fully up to date to 5.5.5 first. The only other advice I'd give is make sure you use the 'upgrade packages' from within your Polisy's IoP and give it a LOT of time - ie, given how long it's been for you, I would start it in the evening and just let it run overnight (or at least several HOURS untouched), but it should get there eventually on its own. ALWAYS backup first!! Good luck sir! And let us know how it went. Shawn 1
johnnyt Posted February 10, 2023 Author Posted February 10, 2023 Thanks @Geddy, @ShawnW for your replies. Yes, the idea of not falling too far behind is definitely part of my motivation. When I asked about cost, I didn't mean monetary cost. I meant time cost due to instability, bugs, or loss of functionality. And for sure I will use the Upgrade Packages button provided in IoP AC after doing a backup. Plus, I've noted the warning about how really long it could take. Thanks again. As my next baby step after upgrading IoP/Polisy to 5.5.5 and confirming everything works fine following that baby step, yes I was planning to install zwave board and a couple of zwave devices that are not currently connected to anything just to test things. My question there is related to the ISY migration instructions (for later) that said "do not install zmatter board until told to do so". Just to confirm - does that mean when I'm ready to migrate 994i to IoP I'll have to uninstall the zmatter board then reinstall it when told to do so, or was that step (or should I say delayed step) just to get through the addition of some core 5.5.x new stuff and not applicable anymore? And second, would the devices I had linked to IoP/Zmatter show up after the migration, or will everything on the zmatter board get overwritten (or the board get factory reset) by the ISY migration process? It would be nice if they remained connected as it would offer the possibility of setting up a bunch of things before I migrate that I could actually use after I migrate without having to uninstall (exclude) and reinstall (re-include) those devices and lose the device IDs I had used in programs. I know (or at least think) any programs would be overwritten so I would just export those then import them after the migration.
TRI0N Posted February 10, 2023 Posted February 10, 2023 (edited) 6 hours ago, johnnyt said: Let me ask my question differently. Given I'm not yet using IoP but I am using PG3 for 6 node servers (on a Polisy) and those need to keep working, does upgrading to the latest IoX version - now at 5.5.5: 1) offer any benefits, other than getting it out of the way (since I do plan to move to IoP)? 2) have any cost? I did see there were problems using PG3 when 5.5.5 came out but appears those were fixed a week ago now. I would hold off on do anything right now. 5.5.5 is the Spawn of Satan and it is performing horribly at this time. I would wait a more stable release is put out before doing anything and since you are running 6 Node Servers, that's apparently where the problem is right now in 5.5.5 is that it does not like multiple node servers. TRI0N Edited February 10, 2023 by TRI0N 1
Ross Posted February 10, 2023 Posted February 10, 2023 5 hours ago, Geddy said: @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. @Geddy To recap, the latest versions are: 994 - 5.3.4 for those using 500 series Z-Wave 994 - 5.0.16c for those using 300 series Z-Wave 5.5.5 for Polisy and EISY. You then asked what version of PG3 he was using. Is that different from the Polisy version (5.5.5)? If so, what version of PG3 is the latest? Thank you, Ross
TRI0N Posted February 10, 2023 Posted February 10, 2023 (edited) 4 hours ago, Ross said: @Geddy To recap, the latest versions are: 994 - 5.3.4 for those using 500 series Z-Wave 994 - 5.0.16c for those using 300 series Z-Wave 5.5.5 for Polisy and EISY. You then asked what version of PG3 he was using. Is that different from the Polisy version (5.5.5)? If so, what version of PG3 is the latest? Thank you, Ross Polly is PG3x Version 3.1.22 5.5.5 and 3.1.22 are not happy though. Going to the latest version right now might not be the best idea. I can only confirm that 3.1.22 worked flawlessly for 24 hours using eisy 5.5.4. But when I updated packages to 5.5.5 just @ 24hr later, all hell broke lose. It is not happy hosting multiply node servers. I currently have 5 and it really did a number on my daily automations not working and devices not communicating properly. UPDATE: From my understanding you shouldn't be using 3.1.22. It's for eisy only PG3x and Polisy is PG3. So I have no idea what the latest version of PG3 is. I jumped from 944 to eisy and skipped the Polisy. TRI0N Edited February 10, 2023 by TRI0N
Geddy Posted February 10, 2023 Posted February 10, 2023 12 hours ago, Ross said: If so, what version of PG3 is the latest? 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 Posted February 10, 2023 Author Posted February 10, 2023 (edited) 31 minutes ago, Geddy said: Polisy is PG3 and (I think) is currently 3.1.17 and it looks like the only way to get to 3.1.17 is to do IoX upgrade to 5.5.x. Am at 5.4.5 / PG3 3.1.16 and I see there's an upgrade available but no instructions on how to get there. In the past wasn't it done automagically with a Polyglot restart? If so, not working that way now. Edited February 10, 2023 by johnnyt
johnnyt Posted February 10, 2023 Author Posted February 10, 2023 13 hours ago, TRI0N said: I would hold off on do anything right now. 5.5.5 is the Spawn of Satan and it is performing horribly at this time. I would wait a more stable release is put out before doing anything and since you are running 6 Node Servers, that's apparently where the problem is right now in 5.5.5 is that it does not like multiple node servers. From other posts it appears the 5.5.5 issues are related to PG3x 3.1.22 only, i.e. affecting eisy only - not affecting Polisy/PG3 users. This one below confirms there is an issue with eisy, and there are others from folks in that thread who said they are on Polisy/PG3 and everything is fine for them. 2
Bumbershoot Posted February 10, 2023 Posted February 10, 2023 1 minute ago, johnnyt said: From other posts it appears the 5.5.5 issues are related to PG3x 3.1.22 only, i.e. affecting eisy only - not affecting Polisy/PG3 users. This one below confirms there is an issue with eisy, and there are others from folks in that thread who said they are on Polisy/PG3 and everything is fine for them. Until this morning. I just updated my Polisy, and IoX and PG3 aren't playing along (I can't get to the AC and automations aren't working). The portal shows the machine is offline. Below is a snip from the log... All repositories are up to date. Checking for upgrades (21 candidates): .......... done Processing candidates (21 candidates): .......... done The following 4 package(s) will be affected (of 0 checked): Installed packages to be REMOVED: mongo-c-driver: 1.8.1 New packages to be INSTALLED: node19: 19.5.0 [udi] Installed packages to be UPGRADED: libbson: 1.8.1 -> 1.23.2 [FreeBSD] xmlsec1: 1.2.34_1 -> 1.2.37 [FreeBSD] Number of packages to be removed: 1 Number of packages to be installed: 1 Number of packages to be upgraded: 2 The process will require 43 MiB more space. 10 MiB to be downloaded. [1/3] Fetching xmlsec1-1.2.37.pkg: .......... done [2/3] Fetching node19-19.5.0.pkg: .......... done [3/3] Fetching libbson-1.23.2.pkg: .......... done Checking integrity... done (1 conflicting) - node19-19.5.0 [udi] conflicts with node18-18.13.0 [installed] on /usr/local/bin/corepack Checking integrity... done (0 conflicting) Conflicts with the existing packages have been found. One more solver iteration is needed to resolve them. The following 6 package(s) will be affected (of 0 checked): Installed packages to be REMOVED: mongo-c-driver: 1.8.1 New packages to be INSTALLED: node19: 19.5.0 [udi] Installed packages to be UPGRADED: libbson: 1.8.1 -> 1.23.2 [FreeBSD] xmlsec1: 1.2.34_1 -> 1.2.37 [FreeBSD] Number of packages to be removed: 1 Number of packages to be installed: 1 Number of packages to be upgraded: 2 The process will require 43 MiB more space. Fetching node18-18.13.0.pkg: .......... done [1/6] Deinstalling mongo-c-driver-1.8.1... [1/6] Deleting files for mongo-c-driver-1.8.1: .......... done [2/6] Deinstalling node18-18.13.0... [2/6] Deleting files for node18-18.13.0: .......... done [2/6] Installing node18-18.13.0... [2/6] Extracting node18-18.13.0: .......... done [3/6] Upgrading xmlsec1 from 1.2.34_1 to 1.2.37... [3/6] Extracting xmlsec1-1.2.37: .......... done [4/6] Installing node19-19.5.0... pkg: node19-19.5.0 conflicts with node18-18.13.0 (installs files into the same place). Problematic file: /usr/local/bin/corepack Fri Feb 10 05:25:02 PST 2023|/usr/local/etc/udx.d/static/udxops.sh: upgrading packages successful ... Fri Feb 10 05:25:02 PST 2023|/usr/local/etc/udx.d/static/udxops.sh: checking base packages ... Updating FreeBSD repository catalogue... FreeBSD repository is up to date.
Bumbershoot Posted February 10, 2023 Posted February 10, 2023 5 minutes ago, DennisC said: I would suggest rebooting Polisy. It has been rebooted, more than once.
DennisC Posted February 10, 2023 Posted February 10, 2023 Here are some other suggestions in case you haven't tried them: 1. Check your router to make sure IP address hasn't changed. 2. Turn off antivirus or VPN. 3. Push multifunction button 2 times to reboot. 4. Press and hold the multifunction button till the first and second LEDs (from the left) start blinking then release. This action resets all network configuration back to DHCP on the Ethernet jack next to the serial port. All other network interfaces shall be disabled.
Bumbershoot Posted February 10, 2023 Posted February 10, 2023 12 minutes ago, DennisC said: Here are some other suggestions in case you haven't tried them: 1. Check your router to make sure IP address hasn't changed. 2. Turn off antivirus or VPN. 3. Push multifunction button 2 times to reboot. 4. Press and hold the multifunction button till the first and second LEDs (from the left) start blinking then release. This action resets all network configuration back to DHCP on the Ethernet jack next to the serial port. All other network interfaces shall be disabled. I'm pretty sure this is PG3 related, and not due to changes in the network stack (I'm currently logged into both boxes from the command line). There are no PG3 instances on either machine at the moment. For the cause of this issue, my money is on either the mongo driver getting uninstalled, or a conflict with node19 and PG3.
johnnyt Posted February 10, 2023 Author Posted February 10, 2023 ok things are NOT looking good here and in the IoX 5.5.5 support thread looks like I'll be waiting for a stable 5.5.6 to come before I take my first baby step. 2
Ross Posted February 10, 2023 Posted February 10, 2023 I'm just memorializing the current versions based on what I've gleaned above: 994 - 5.3.4 for those using 500 series Z-Wave 994 - 5.0.16c for those using 300 series Z-Wave Polisy IoP - 5.5.5 Polisy PG3 - 3.1.17 Eisy IoX - 5.5.5 Eisy PG3x - 3.1.22 1 1
oskrypuch Posted February 10, 2023 Posted February 10, 2023 Isn't IoX == IoP, just the new name for the cross device version? (still sitting on Polisy with an empty slot, with 5.4.x) * Orest
Bumbershoot Posted February 10, 2023 Posted February 10, 2023 3 hours ago, Bumbershoot said: Until this morning. I just updated my Polisy, and IoX and PG3 aren't playing along (I can't get to the AC and automations aren't working). The portal shows the machine is offline. Back up and running on both Polisy and eisy. sudo service udx restart 1
Geddy Posted February 10, 2023 Posted February 10, 2023 11 minutes ago, oskrypuch said: Isn't IoX == IoP, just the new name for the cross device version? 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.
Recommended Posts