DennisC

I believe if you are using eisy, then you are referring to PG3x, which uses the eisy password for credentials. Have you tried entering admin/admin, or if you have already changed the eisy credentials after resetting, than you new credentials?

I received that same message along with repeated notices that there was an update available. After several attempts to upgrade and several reboots, I got the message you received to stop coming up. I'm still getting the notice about an upgrade being available, but UD told me to ignore it for now.

FYI, if you are referring to eisy, be aware that it does not have a speaker.

To close the loop on this, Michel spent over two hours in my system yesterday trying to figure out why I am getting the upgrade packages notice. He confirmed I had all of the latest upgrades. For now, he told me to ignore the message. As for Weatherflow node server not starting, that required a patch from Bob which he issued last night (upgrade 3.0.28).

You are only allowed 1 user in the admin console. While space for more are there, it never worked.

There is a new firmware out, v5.5.6 that might help you.

I am comfortable with ssh and I already opened a support ticket. I'm on PG3x v3.1.22. Thanks

It's been several hours since I did the upgrade to v5.5.6. I have been alternating trying to restart PG3x, rebooting eisy, and/or upgrading packages. While my firmware and UI is at v5.5.6, I can not get Weatherflow Node Server to update the admin console with Tempest Data. The forecast data shows up, as does wind and pressure. All other values for my Tempest read 0. I have confirmed the station number has not changed. After every reboot (waiting about 15 minutes) I have to query all the node servers. Every so often, after rebooting, I receive a message when logging in to admin console per the below screenshot: I try to update, the admin console closes, but there is no pending update. Still no luck getting Weatherflow data to populate. One other thing, in the admin console, Weatherflow is shown as on line and last seen 1676317868 seconds ago.

Thank you. Yes, I did the update and all node servers are running. I am having trouble getting Weatherflow node server to populate the admin console. I see it is running and in the node server log I see data being sent, but no luck so far.

Re-read my messages, that is the only way to query the Tempest. I am showing 0 except for wind and pressure.

The Tempest is included via a node server. I have tried querying it numerous times. I see data is sent in the node server log, but the fields in the admin console remain at 0 except for wind and pressure.

After completing the upgrade to v5.5.6, I can confirm all of the node servers in PG3x are running. I had to clear Java cache and reload start.jnlp. I had to reboot multiple times (after waiting 30 minutes after the first upgrade packages) and trigger upgrade packages twice. I kept getting a message when signing in to admin console that some packages were ready for upgrade. I also kept getting an error that said "Event Received for a Different Subscription Restart". I received this multiple times but finally went away. All node servers required running a query to populate the admin console. I did this about 15 minutes after the last reboot. @bpwwerSo far, now about 30 minutes after the last restart, I can not get Weatherflow Tempest readings in the admin console. I have queried it several times and I see the query data in the Weatherflow node server log, but the admin console has all 0's for readings except for pressure & wind. I have tried closing and relogging in to admin console several times and I tried restarting the Weatherflow node server. Edit: Forecast data is populating in the admin console.

The original problem that led to the minor update with the bigger problem, was some node servers would not restart on PG3x. I am trying to understand if an upgrade packages will fix that issue and should we be updating now. Are all of your node servers on PG3x running after the upgrade?

Do you have multiple node servers and are they all running now on PG3x?

Maybe, but I can think of several things that could go wrong........ For some people, it might have been a safer bet to use file backup rather than moving the SD card. I guess we will never know.

What firmware and UI are you running? Was this a migration or a new fresh install with Zwave devices added manually? Do you have any devices other than Zwave and if so, how are they running?

Thanks. How about the issue with PG3x and node servers not starting, are you close to a fix?

That doesn't necessarily mean UD is supporting the port.

If you are talking about the eisy, I don't believe it has a SD card slot. These are the eisy specs from UD sales page: Specs HARDWARE: Intel Celeron Quad Core @2.9GHz | 8GB RAM | 60GB Storage | TPM 2.0 WiFi 6 | Bluetooth 5.2 | 1 x Gigabit Ethernet | 4 x USB Ports | 2 x 4K HDMI Ports Internal NVMe slot can extend storage to 1TB No additional storage is needed.

I suggest you do nothing until the current issue is resolved. You can monitor the support post to know when everything is safe to continue. The current migration firmware for eisy is v5.5.5 and until now, it has performed the best when migrating. Therefore, you will want to be on at least v5.5.5 before migrating to eisy. Since most of the time, each firmware release is better than the previous, especially for migrating, you want to be on the latest release before migrating. Following the directions, you should upgrade packages and then take a backup. So, I suggest you wait until the current issue is taken care of before migrating and start by upgrading packages.

First, Don't upgrade right now. Since this weekend, there has been an issue with the upgrade packages button, just hold off until that is resolved. When you are ready, make sure to upgrade packages first, to the latest version of firmware, then follow this guide: https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Migration

All of your questions are answered in the wiki Migration document located here: https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Migration This document is upgraded regularly, so make sure you are looking at the latest. 1. Since you are going from ISY to Polisy, if you read the specific instructions for that upgrade, you are not doing anything until you are ready to install the migration backup from your ISY, other than upgrading and backing up Polisy. Just leave the Zwave support box unchecked unt you are told to make sure it is checked. You can certainly factory reset your current ZMatter board on the Polisy to be safe. 2. According to the instructions, yes, you will loose what was already added to Polisy when you restore your ISY migration backup to Polisy. You are migrating one system to another, not "adding to". As an aside, I would wait until the current upgrade packages issue is resolved before migrating. You want to make sure you are on the current version for both systems when you migrate and right now there is an issue with upgrade packages.

ISY is at end of life and will no longer receive updates, unless a major security flaw is detected. Polisy was to be the replacement, but supply issues for parts required to build it killed that. UD has committed to developing Polisy for several more years. Eisy is the future and while there are currently some growing pains, it is what is currently available. Eisy also runs PG3x which is required for node servers. No Pi unit is required. A USB PLM is required for eisy. If you already have a serial PLM, UD has a cable kit that can connect it to eisy.

I'm hopeful that Bob can provide more information about what's currently happening.

@bpwwer, Does that mean we should be doing an update now and node servers that won't start should all work after the update? Edit: After reading the board, it appears many more users are experiencing problems after attempting an upgrade.