btreinders

First error I got was I have over 1024 programs and subsequent tries results in the error in the screenshot. I am on the latest IoX and PG3x on a polisy. Thank you.

Upgrade wasn't straight forward, waited for the beeps and then waiting for the reboot to happen I saw MQTT errors scrolling in the tail of log so fast it could not keep up. I don't have the MQTT node server installed either. ISY was not responsive, could not open PG3x or AC. After an hour of this I rebooted from command line. Everything came up and everything seems ok.

I did submit a ticket but today I tried a few more times after failing at least 5 times and now they are working. If they give any insight I will definitely post it here though.

Will do, thank you!

I am getting a backup fails on a Polisy running the latest 5.6.4. Could not open zip file and then could not retrieve ./FILES/CONF/ZYCGF/zddx/fa7f27fa-DevicesData.xml Can I just delete the files under ZYCGF and try again? If so, where are they located? I don't seem them at ./

Understood on all. I agree that restarting PG3.x often is a bad idea. I just wondered if it was possible to automate restarting just one node server. I will work with the developers to get any issues corrected for sure. Maybe in the future PG3x can start node servers one by one after a restart to relieve the stress on IoX? Thank you for the responses.

Is there a way to automatically restart a certain node server from IoX or another device? Since upgrading to 3x quite often if the Polisy is rebooted certain node servers will show online but will not really be working until I restart them. For instance the Hue node server this morning that it is working but when I use IoX to turn on a Hue light I get an ND_slot error pop up. Restarting the Hue node server fixes it. I also see this with Ecobee and Elk node servers. Possibly Kasa as well. What I'd like to be able to do is run a test program after a reboot that would turn on a light and then check to see if that light came on or not and if it did not then send me a notification but also restart that node server in the meantime. Not sure it's related but the only way I can see the logs for any of the node servers is to download them, the real time just pops up a green window saying starting events log but I never see the logs. I am on 3.2.2 but expect to update to 3.2.3 later today. Thank you!

I gave that a try and had the same result. Thank you for all the help, I will open a ticket.

I think the USB Zmatter dongle is bad. I factory reset it and factory reset a few devices and I can't add those to it after the factory reset. Guess I'll open a ticket. Hope I can get back to the old dongle without too much trouble.

@DennisCAnswers below That is not what I am saying. ZWave addresses use to start with ZW and after migration, they will begin with ZY. Therefore, all programs and/or notifications will require their address to be updated. That is not good news, I was waiting to upgrade to Zmatter once there was an update that would not require all programs to be updated. I thought I read one of the latest IoX updates did that. I guess I was wrong. Some type of intervention might be required, like resaving all programs and updating addresses as mentioned above. I sent you the current link for migration because I wanted you to read through it and make sure you followed all of the directions to the letter. I did follow that guide when I migrated. Did you follow the directions exactly and if so, what specific differences are you seeing? Yes, I followed the directions as written in that guide. Can you explain in more detail? What are you seeing in admin console? Can you query the devices? No, cannot query them, just returns a error which strangely has a node server in the pop up. They all show as placeholders with the red disabled icon. When the migration restore is run the IoX starts syncing and interviewing and they all timeout. If devices are not showing status, go to the top level menu and select ZWave - Synchronize - New & Deleted with Interview. That results in the same as the IoX doing this during the restore. All timeout. Before doing that, if you have battery devices, click the battery icon in the top level menu to turn off battery devices. I will try this one but I cannot see how that would fix the powered devices. (just tried again with battery devices deselected and still have the same results.)

Thank you @DennisC I guess I don't know where the "When migrating from Zooz to UD ZMatter dongle, the Zwave address will change and will require manual intervention. All necessary instructions are here:" came from? Are you saying that for all my devices I will need to remove them and add them? I was under the impression that most devices will migrate just fine without intervention. I did use the migration backup and the migrate button in IoX which created the backup. I then removed the Zooz and installed the Zmatter and restored the migration backup. I have not tried the battery devices yet but can't even get the powered devices to work. I really don't want to try and remove one and then add it because it sounds like once you do that you can't go back to the Zooz Zmatter to work. Thank you in advance! Really appreciate it.

I have done all the steps in the migration from ZOOZ to ZMATTER and now none of my 50 or so devices work. They are all placeholders and running a sync with interview just times out whether I do that individually or all at once. I have the ZMATTER dongle on the same USB extender the ZOOZ was on so I assume that is ok? I do have all the new options for ZWAVE like heal network and sync with interview so I assume the Polisy sees the dongle like it should. Any suggestions?

Guess that is why I missed it. I have a Polisy not an Eisy and the upgrade instructions for PG3x do not mention a pw change for Polisy.

After upgrading to PG3x from PG2 and PG3 I could not login to PG3x on my Polisy. After seeing a post about someone with an Eisy and not being able to login with the A/C credentials I finally tried that and got in. My question is where in the upgrade procedure does it say to it will change to your A/C credentials instead of using admin/admin? Did I miss that?

Reboot did it. I rebooted many times yesterday and nothing would fix it. I guess the multi function button must have done the trick with a reboot after. Thanks again!

Thank you for the quick reply! I am not quite up though, still no zwave. Any suggestions? I will try to reboot after the getting the 4 beeps to see if that will do it.

That makes sense as it never did beep 4 times when I upgraded packages and after about 15 mins I rebooted it with a sudo reboot. I guess it was just stuck in that loop. Zooz 700 USB dongle. From the uname command: FreeBSD polisy 13.1-RELEASE-p4 FreeBSD 13.1-RELEASE-p4 releng/13.1-n250171-95499 c45614c POLISY amd64 Looks like the same entries are not repeating, it shows the upgrade is good. I am guessing now that the USB dongle is still supported? Thank you!

I did not realize the upgrade packages also updated the IoX firmware. I was only trying to update PG3. Now my zwave dongle does not respond which I assume is because 5.6.0 does not support it anymore. Is this correct? I can't find a definitive answer. If so, can I go back to 5.4.5 and if so how can I do that? With the ISY it was easy but with Polisy I don't see how to downgrade. Thank you! (5.4.5 isn't listed in the old software either. Goes from 5.4.3 to 5.5.0 on the previous release page.)

I have not had a chance to look at the logs. The only symptom I have is that communication between HA and the Polisy just stops and I have to reboot to fix it. I will look at the logs the next time it happens. Thank you.

I have this happen about once a month or so and for me the only thing that fixes it is to reboot the home assistant pi I have integrated with the ISY integration for HA. Has anyone else seen this issue? If so, how do you handle it? Thank you!

Thank you, I had missed the re-install option on the pop up.

Thanks for the explanation. Is this the only way to install them? There won't be an option in the future to just force an install and not install all new ones for just restarting PG3?

Thank you for the reply but one of them has auto updated in the past with a restart. It is the ELK node server. The other one is the OpenWeathermap node server. AVRemote had the issue and I uninstalled and reinstalled it and it fixed it. I would rather not do that with these two as they are heavily involved in programs and in the past I have had to redo all of them. AVRemote went smoothly and all programs did stay intact but I really would rather not attempt that with these two.

I have several node servers that will not install the update when I restart them. Have we changed the way this works? I restarted PG3 and nothing changed. I also uninstalled one and reinstalled it and that did the trick. Thank you!

Clean install fixed it and now I am having a very similar issue with another node server. It won't install but does at least run. I am reluctant to reinstall it since it is very involved to install and in a lot of programs if I screw up. So must be a PG3 issue and not just single node server. Thank you!