DennisC

I have been using Tasker for several years for both myself and my wife and it has been very reliable. May I ask, have you followed the outline in the wiki and are you using 2 geofences per location, a small and a large?

Having the board installed was the initial issue with the migration in early January. The latter upgrades corrected the problem of the board already being installed. If it makes you feel better, take it out and then reinstall it when told. Just make sure you use the latest directions, as they are constantly being updated. If you are still unsure about how to proceed, why not send the same question to UD support and ask if you can leave the board in with the check box unchecked?

Other than my suggestion to attempt logging directly in to portal via a web page, then PG3x, I'm out of ideas.

Can you login to admin console and if so, with what credentials - admin/admin or have you changed credentials. To enter PG3x, you need to use the same credentials as for admin console. When you say you login in to UDI, are you speaking of the portal? One other thought, I sometimes have an issue if I sign in to Polisy PG3, then try to enter eisy PG3x. I have to open a web page directly to portal, then close that and try logging in to eisy PG3x again, then it seems to work.

I'm not sure I understand, what happens when you go to https:xxx.xxx.x.xxx:3000?

This is a bug UD is aware of, I reported it on Monday. Michel spent over 2 hours in my system checking on it. Use the multifunction button on the front to insure you have the latest upgrade. I believe you press the multifunction button 1 time. Once you are sure you are on the latest upgrade, you should ignore the notice about upgrades being available (as per UD).

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.

I'm sorry, but I need to disagree with you. On pg3x last night, the reinstall button would not work. The node servers needed to be deleted before being able to install the new version

As I stated in my original post, Bob confirmed a bug in latest PG3 which prevents some node servers from upgrading.

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.

That didn't work for me last night with Weather flow node server. That's why I reached out to Bob.

I confirmed last night with Bob that there is a bug in PG3 that is preventing upgrading of node servers. Look for a new version around the end of the week. If you don't want to wait, you would need to delete it, reinstall, and configure.

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.