bpwwer

I made the change to comment out the pushover import since I do have access to the repository.  A re-install should get a working version now.

I don't see any errors from PG3, just warnings.
I've mentioned this before, PG3 makes 3 attempts to send the information to the ISY.  Above shows that the first attempt failed, but the second attempt succeeded so that's not an error.

It's on my list to add RIO support to the PG3 version, just need to find the time.

Unless it's a Roku TV, no.  the node server only controls Roku devices.

Yup, that helps.  
I just uploaded version 2.0.1 of the Roku node server to the store.   Refresh the store and then restart the node server and see if that adds your Master Bedroom Roku.

I updated the link in the store listing so it should work now.

I think you almost had it right.  Try ${sys.node.n001_141766_11.CPW} 
The address created by the node server has the "n<slot>_" pre-pended to it when added to the ISY

I was wrong about the API change. I can't find anything wrong.  However, the free plan limits are now pretty low and you do need to have the short poll, long poll and number of forecast days set to stay below those limits.
If you try to get more than 7 days of forecast data with the free or hobbyist plans, the node server will fail to start as it will be sit there waiting for more data that it will never receive.   This makes things a bit more difficult since the node server doesn't have any way to know what plan you have so it can't auto-adjust the parameters.
I've updated the documentation and configuration help to reflect the latest limits.

A just releases a new version (2.0.7) that should fix the issue.
The problem was that @jkosharek's  station is reporting battery data that I had not seen before and the data parser ended up generating two battery drivers with the same name in the node.  The ISY doesn't like that and the node was not really valid, hence it wasn't able to display it properly in the admin console.

Done in version 2.0.1

Is it really this message: "Portal Access Token Expired. Refreshing..." ?  If so, that's not an error, it's a warning. 
The token is only good for about 1 hour and then it needs to be refreshed (or you need to re-login to the Portal). PG3 attempts to refresh it automatically when it detects that it expired.  So unless it fails to refresh, it's behaving as intended.

That likely no longer works.
With the initial versions of PG3, it would work in some specific cases where the PG2 node server and the PG3 node server were mostly compatible and you had a license or didn't need a license for the PG3 version.
Over time, the PG2 and PG3 versions have become less compatible and now you need a license to install any node server on PG3.
If none of the node servers showed up in PG3, that means that none of them met the criteria needed to install the PG3 version.

This issues is fixed in version 3.1.12, see the release announcement for the list of fixes in this version.  It is available now.

PG2 node servers will show as unmanaged in PG3
PG3 node servers will show as unmanaged in PG2
That's because they are two different instances of Polyglot and only one instance can manage any given slot on the IoP. 
To remove a node server, you should use the Polyglot instance that created it to do the remove/delete operation.  When you use Polyglot to delete a node server it will remove it both from the IoP and from the Polyglot instance.
If you are no longer running the instance of Polyglot that created the node server, you can delete it from the IoP by using the admin console's Node Servers -> Configure -> slot range -> Node server/slot and click on the delete button

I don't have this node server installed and don't have any Sonos devices, so I may be completely off base here.  
Typically the commands a node server can send to a device are predefined. To use them in a program you go into the program interface and select 'Control' for the 'then' part of the program and select the specific node server as the device.  It should then have a drop down list of the commands you can send to the device.
Following the links to the node server documentation  https://github.com/simplextech/pg3_docs/tree/main/ST-Sonos
says it supports all the functionality of the API which lists the following:
The actions supported as of today:
play pause playpause (toggles playing state) volume (parameter is absolute or relative volume. Prefix +/- indicates relative volume) groupVolume (parameter is absolute or relative volume. Prefix +/- indicates relative volume) mute / unmute groupMute / groupUnmute togglemute (toggles mute state) trackseek (parameter is queue index) timeseek (parameter is in seconds, 60 for 1:00, 120 for 2:00 etc) next previous state (will return a json-representation of the current state of player) favorite favorites (with optional "detailed" parameter) playlist lockvolumes / unlockvolumes (experimental, will enforce the volume that was selected when locking!) repeat (on(=all)/one/off(=none)/toggle) shuffle (on/off/toggle) crossfade (on/off/toggle) pauseall (with optional timeout in minutes) resumeall (will resume the ones that was pause on the pauseall call. Useful for doorbell, phone calls, etc. Optional timeout) say sayall saypreset queue clearqueue sleep (values in seconds) linein (only analog linein, not PLAYBAR yet) clip (announce custom mp3 clip) clipall clippreset join / leave (Grouping actions) sub (on/off/gain/crossover/polarity) See SUB section for more info nightmode (on/off/toggle, PLAYBAR only) speechenhancement (on/off/toggle, PLAYBAR only) bass/treble (use -10 thru 10 as value. 0 is neutral) Is there something beyond that you need help with?

1.0.3 is the latest version.  You can always compare the version listed in the store with the version you are running.   If they are the same, you can delete the notification.

The node server is already running.  If you try to start a second copy, it fails because only one node server can be running in a slot.
Since node servers are independent processes on the OS, under rare conditions they will continue to run when PG3 attempts to stop them.  When that happens, PG3 gets confuses because it doesn't know the node server is still running and lets you try and start it again, which then fails.
Possibly, restarting PG3 will clear.  If not, then the only way is to either manually kill it via the console or restart Polisy

@tmorse305If you refresh the store and try re-installing it should work now.   

Try upgrading packages again and get version 3.1.8.  I think this will resolve the issue.  It it still says the node server has expired, try restarting the node server and see if that fixes it.

Try updates packages again and restart with version 3.1.8.   If it still says it's expired, restart the node server and pm me the PG3 log

Fixed in version 3.0.24 of the node server

I'm running on my Fedora system using icedTea.   Over the years I've had to fiddle with it a bit to keep it working but I don't have any specific recommendations.  I'm currently using java-11-openjdk-11.0.13.0.8-2.fc33.x86_64 if that helps at all.
My launcher icon on the desktop is configured like this:
[Desktop Entry] Version=1.0 Name=ISY Launcher GenericName=Java Web Start Application Comment=This utility finds ISY and launches the correct version of the UI-Admin Console-Dashboard Categories=Network;ISY Launcher;Java;Javaws; Type=Application Icon=/home/bpaauwe/.config/icedtea-web/icons/udlogo.png X-Vendor=Universal Devices- Inc. Exec=/usr/libexec/icedtea-web/javaws --verbose --nosecurity "https://isy.universal-devices.com/launcher/isy.jnlp" > /tmp/isy.log 2>&1 That launches the ISY finder and then I do have to manually add (or load a saved listing) of my ISY/IoP devices as it only seems to ever automatically find one ISY. 

You seem to be asking a couple of different things here so I'll try to answer as best I can.
On your local network, there shouldn't be any problem accessing PG3 from an iPad.  I just connected to mine using my iPhone and other than the small screen, it worked fine.
That being said, you may have to use an unsecured connection (http vs. https) as the iPad probably won't allow you to use the self-signed certificate since it it can't verify it.   Using the ISY Finder to connect may always try to use a secure connection.  If so, you simply have to type the Polisy's IP address manually into the browser address field (http://<ip address:3000/).
Then you mention trying to do it remotely.  Right now, PG3 does not provide any method to access it remotely.  That's not to say you can't, but you have to know how to configure your network to allow this.  You can open port 3000 through your router, however, for security reasons it is never a good idea to open ports.  Or you can access your home network via a VPN.  Using a VPN is much more secure and once the VPN is configured and connected, you'd access PG3 remotely the same way as if you were on your home network.

Yes, it is the same issue.
Version 3.0.23 should fix it.

This is the problem:
24:00:46 [pg3] error: ISY Response: [Try: 1] [00:0d:b9:53:d8:14] :: [404 - OK] :: 18.856618ms - http://192.168.2.117:8080/rest/ns/7/nodes/n007_controller/report/status/ETO/2.903759505852784/106
The ISY is rejecting it. A 404 error means "not found".  I did some experiments and it seems the ISY rejects it if there are too many digits of precision in the value.
I just pushed out version 3.0.22 that rounds the value so this should be fixed.  If you refresh the node server store, and then restart the WeatherFlow node server, it should auto-install the update.