gviliunas

Today, I saw that a new version of Notification NS was available. I see this from the Nodeserver's top page (See Step 0 screen shot). Viewing the "Purchases" page I see two related lines. Do I select to upgrade the Production version or Install the Beta version? Is the Beta version the advertised upgrade or is the Beta version yet another possible upgrade beyond the advertised upgrade??? How do I know which one to choose here (See Step 1 screen shot). If I choose incorrectly, it it easily reversed? Taking a guess, I select to upgrade the Production version. With this, I am presented with 3 choices. (See Step 2 screen shot) Hmmmm Which do I select to upgrade the purchased version that is already running happily on my system? I think I want the middle choice.....but I'm not confident in this. Is this going to cost me another $15? Or, should I select the bottom choice. This is Free and the upgrade should be Free?? I just want to do a simple upgrade of what I already have purchased and installed. Currently, I see too many choices and fear purchasing another copy of what I have already purchased or installing another version that I don't want. Maybe the answer is in a Wiki but I would think that this should be a simple intuitive process. I much preferred the PG-2 scheme which gave me a single "Upgrade" button if an upgrade was available. I'm sure these other choices available here in PG3X are useful to some but it isn't intuitive to me and, I suspect, for others as to how to accomplish a simple in-place upgrade for purchased nodeservers. What should I click?

@TechmanI found more information on the allowable MS6 firmware versions here: https://aeotec.freshdesk.com/support/solutions/articles/6000036562-how-to-update-multisensor-6-z-wave-firmware-

@Geddy Ticket #22333 with log files was submitted. Greg

Upgrade to 3.2.2 went as expected BUT , after reboot, all of my IOX 5.6.4 programs that had been in "disabled" state had now re-enabled themselves. Long ago (back in ISY 994 time) this would happen twice a year when we changed time to/from DST so I began putting a "D" suffix to my program names. I don't know how this happened today. I only upgraded PG3 and it was not the day to change to/from DST. I was however, very happy that my programs were marked to indicate which ones should be disabled.

Upgraded from 5.6.3 to 5.6.4 without any problems or abnormal behavior. Thank you to the UDI team!!

Hi @bob123, I had a similar problem with Z-Wave as I moved from the Zooz 700 stick and then onto Z-Matter on Polisy. This may or may not have the same cause but it is easy to check. The root cause of my problem was several Zooz smart outlets that were sending Z-Wave power reports constantly at sub-second frequencies. As Polisy was trying to boot-up, the Z-stick (and later Z-Matter) was deluged by these power reports and was not listening to Polisy. After awhile, Polisy reports that Z-Wave was not responding. I manually rebuilt my ~40-Z-Wave device several times 😬 before, a with the fantastic assistance of UDI, the solution was discovered 😁. Method to test for this: The problem was discovered by unplugging all of my plug-in Z-Wave modules and then trying to reboot Polisy. If this is successful and Z-Matter is now responding to Polisy, I would suspect a chatty device(s) on the Z-Wave network. This problem seems to only affect start-up of Polisy / Z-Matter (or 700 Z-Stick). If I later plugged-in one of my chatty devices, the system continued to work until next reboot. At this point, in my case, I was able to modify the chatty device's parameters to more reasonable reporting frequencies. Good Luck

Upgraded Polisy from 5.6.0 to 5.6.2. Had to clear Java cache but both Lan and Cloud access worked without issue.

@Jimbo.Automates, @Javi, @tlightne Thanks Guys! I had the correct config parameter but the wrong value. I was trying to insert the Pushover api key but needed the UD Portal api key instead as you suspected. Thanks also for helping me find it. I was incorrectly looking in the UD Mobile, Settings but it is well hidden in the UD Mobile, Notifications, Settings. All fixed now!

I tried upgrading to 3.5.4 on PG3x 3.1.27 but the NS is not accepting my api key. ERROR: 05/24/2023 02:30:22 See log for: Please verify your portal_api_key value I also tried regenerating the api key on the pushover.net site but this new key didn't work either. Any ideas? Notification_5-24-2023_23740-AM.zip

@macjeffTHANK YOU! You were exactly correct. I tried access via Edge and I now have PG3x running. Thanks for saving me from myself!

Hmmmm. My PG3X conversion seems to be stuck. I've been looking at this page for a long time and nothing changes. Tried entering an IoX per the eisy wiki (IoP, localhost, port 8080, credentials) but no change.

@dbwarner5 I'm using Chrome. Polisy came back as pg3x bit no node servers. I try waiting as see if they appear.

@dbwarner5 I received the same error as you when trying to enable pg3x

Upgraded successfully to 5.6.0. No issues. Everything is working in my system. Thanks UDI Team!

Upgraded easily and successfully to V5.5.9 from v5.5.7. No issues! Thank you to the UDI team for all their hard work.

Upgraded to 5.5.7 from 5.5.6 on Polisy with no problems. PG2 and PG3 started without problem or additional reboot(s) needed after the upgrade. 😀

@geddy Thank you! This 2nd reboot (Per the instructions, I did a power-cycle after receiving the 4+1 beeps after upgrading packages.) finished and everything (IoX, PG2, and PG3 ) are all working.

@Geddy The system has been up ~ 20 minutes. I can get into the Admin Console and everything looks normal. I can get to P2G on Polisy and everything looks normal. I noticed the problem when asking Alexa to turn-on a PG3 LiFX NS controlled lamp and getting no response. I cannot access the PG3 web page Running "Top" from an ssh session doesn't show a polyglot-v3 process running

Upgraded successfully to IoX 5.5.6 BUT now, after the restart, Cannot connect to PG3. When attempting to connect to the PG3 web page, I get: This site can’t be reached xxx.xxx.x.xx refused to connect.

I upgraded to v5.5.5. No issues encountered and everything is working normally.

Hmmm Chris had said that sub-1 second reporting intervals might be a problem. I would have thought that 5 sec would be okay. In any event, once Polisy is up, you can plug that multi sensor back in any your system should run fine.

Hi @EJones01, I was seeing a similar problem at reboot. When polisy boots, it asks the ZMatter board for an ID string. In my case, I had several very chatty z-wave devices that were sending data at < 1 second intervals. These were somehow confusing ZMatter and it wasn't responding to Polisy correctly. I would see errors like the ones I see in your log: Tue 01/31/2023 04:40:16 PM : [ZMATTER-ZWAVE-DETECT|/dev/ttyU1] No serial dataTue 01/31/2023 04:40:16 PM : [ZMATTER-ZWAVE-DETECT|/dev/ttyU1] Is not ZMatter Z-WaveTue 01/31/2023 04:40:16 PM : [USB PORTS][ZMatterZWave] initializePort [/dev/ttyU1] - Not our portTue 01/31/2023 04:40:16 PM : [USB PORTS][ZMatterZWave] initializePort [/dev/ttyU2] seqNo=4 isRemoved=FalseTue 01/31/2023 04:40:16 PM : [ZMATTER-ZWAVE-DETECT|/dev/ttyU2] Start ZMatter Z-Wave port detection Working with UDI, Chris recommended that I unplug some of the chatty devices. I did this and was able to boot. Ths allowed me to boot but the final solution, for me once the system was up, was to change parameters to reduce the frequency that some smart plugs were reporting energy usage. After doing this, I can reboot without problems. Hopefully your problem has a similar cause. Good luck in getting your system working again.

Upgraded to 5.5.4 and no problems experienced. No need for any subsequent reboots. All NS working including LiFX on PG3 (Using .yaml file) Previously, I have seen the condition where previously discovered z-wave devices have blank status in the Admin Console after restarting IoX. When this happens, in my case, if I checked the Z-Wave X-Ray, DH All Devices, there was a failure message instead of usual list of devices with their interview status. To fix this I rebooted, sometimes several times. I suspect that "chatty devices" are preventing the Z-Wave interface from starting properly sometimes. Rebooting has solved my problem. Had this not worked, I would have next unplugged any device that reports energy status and rebooted but I haven't had to do that yet. Edit: After successful 5.5.3 to 5.5.4 upgrade on Polisy.

@jhoulihan I think we need more information... 1. Can you describe your system (i994, Polisy, or Eisy), (Zooz Z-Wave, Matter Z-Wave, Insteon), (Current firmware version)? 2. Besides the Admin Console behavior, it your ISY working? i.e Does it control devices and run programs 3. If you open the event viewer, is the process hanging in one particular place?

@brians Zooz Smart Plug Model ZEN06 / Intertek Model HKZW-SO03. (Identical plugs with slightly different labeling. Both of these have Intertek part number 5005292. These switches Include easily and work well but, as I discovered, they can be very chatty by default. They do have parameters that can be set to reduce the frequency or altogether stop energy reporting.