gviliunas

I agree with @brians, The last time I tried this was with Polisy and a Zooz 700 dongle. The only way I was able to maintain the zwave node numbers was to factory reset the dongle and then re-add the devices in the same order as previously added. With ~45 devices, it was a giant PIA. One mistake and start over. Probably better to re-add the device, accepting the new z-wave node and then fix any program issues.

Kaz: Maybe you can use temp-dependent on/off thermal switches with a magnetic base like this to trigger your automation: https://www.amazon.com/BBQ-Element-Magnetic-Thermostat-Fireplace-Temperature/dp/B07WC8M3MM/ref=sr_1_2_sspa?crid=2X6ZC9VLURVOQ&keywords=fireplace+thermal+switch&qid=1698372489&sprefix=fireplace+thermal+switch%2Caps%2C167&sr=8-2-spons&sp_csd=d2lkZ2V0TmFtZT1zcF9hdGY&psc=1

@bmercier @Jimbo.Automates Thanks for the update. Actually, I found another solution. I looked back at the details page of the Notification NS and discovered an "Update" button adjacent to the Start, Stop, Restart, and Load Profile buttons. (Sorry, no screen shot) I clicked this button and now I was presented with the "Available purchase/install options" page BUT, this time the NS slot number was populated. (Sorry, the screen shot was the original that I took when navigating directly from the Purchases page. In this case, "N24" was shown on one of the option lines) I clicked "Update" on the line containing my "N24" installed designation and the NS upgraded properly. To sum it up, it appears that "Installed" column of the "Available purchase/install options" page is populated or not based on how you arrived at this page.

Upgraded from PG3x 3.2.2 to 3.2.3 with NO Problems. Everything working well. None of my "Disabled" programs were re-enabled this time during the upgrade. Yeah! Thanks for your hard work UDI Development Team!!!

Hi @Jimbo.AutomatesThanks for your reply. This NS is installed in Slot 24 as in this screen shot. It would be nice if the "New Message" advertising the update would contain a live link directly to the update.

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!

Yes @carealtor, I fear that widespread adoption of AI will only serve to homogenize many of our choices in products available. I fear that many future "developments" will devolve into lazy "me-too" safe development and acquisition choices. The times they are a-changing but I'm not sure it's all for the best... To this, Chat gpt responds (Better than most politicians): "Change is an inevitable part of life and society, and it can often be difficult to predict the long-term consequences of these changes. While some changes may bring positive benefits, others may have negative consequences. It is important to approach change with a critical and open mind, considering the potential impacts on different groups of people and the broader societal implications. It is also important to recognize that some changes may be necessary in order to address social, economic, and environmental challenges facing us today. However, if you have concerns about specific changes that are taking place, it may be helpful to engage in constructive dialogue with others and work towards finding solutions that benefit everyone involved. It is important to remember that change can be challenging, but it can also be an opportunity for growth and progress if approached thoughtfully and with an open mind."

@Geddy ChatGPT has the following answer: (See the last paragraph): There is no one "optimum" home automation system that suits everyone, as the ideal system will depend on the individual's needs, preferences, and budget. However, here are some factors to consider when choosing a home automation system: Compatibility: Ensure that the automation system is compatible with the devices and appliances you have or plan to buy. User Interface: The user interface should be easy to use and intuitive, whether it is a smartphone app, a wall-mounted control panel, or voice commands. Expandability: The system should be expandable, so you can add new devices or features as your needs change. Security: A home automation system should provide robust security features to protect your privacy and data. Cost: The cost of the system should be within your budget, including installation and ongoing maintenance costs. Customer Support: Choose a system from a company that offers good customer support, including warranty, technical support, and repair services. Some popular home automation systems include Amazon Alexa, Google Home, Apple HomeKit, Samsung SmartThings, and Philips Hue. It is important to research and compare the features, compatibility, and customer reviews before making a purchase.

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