bpwwer

The profile files define the mapping between the numbers and the text.  For email variable substitutions, the ISY (or IoP) is what should be replacing the number with the text.  The admin console reads the profile files and does the same number for text replacement.
So if the admin console is able to read and map the number to the text, then the node server files are fine.
I believe the ISY/IoP only reads the mapping when it starts so is it possible you haven't restarted the ISY since installing ClimaCell? 
 

Nothing in that log file indicates there's a problem.  
However, there are restrictions on what characters can be used for node names.  It looks like that's the only node that has an '&' in the name so you might want to try removing that.

No, the restore is kind of an all or nothing.  As part of the restore, it changes the configuration on the ISY to point back to the PG3 version.  If you then delete the PG3 version, it will delete the node server from both PG3 and the ISY.  The PG2 version will no longer work.  
Possibly you could then delete the PG2 version and re-install the PG2 .
If you just want to partially move to PG3, I'd recommend not trying to use the restore from PG2 backup and just delete the node server from PG2, install the PG3 version in the same slot, re-configure and fix anything that broke.  That's the cleanest way and you can concentrate on making sure each one works correctly before moving on to the next.

Sorry, made a error in the code.  Try version 2.0.2.

I was just about to post here that I pushed out a new version, updated to work with node 18.  But I see you noticed.  Thanks for letting me know that it's working.

The "Load Profile" button won't give any visual indication that it's doing anything.  It simply re-sends the profile files to the ISY.  You can view the PG3 and verify that it really did upload them.  If there are errors uploading the profile files, then that's the problem. 
If the admin console isn't showing the same values as what you posted above, it's because the admin console doesn't have the updated node definitions.   It only reads those files from the ISY when it starts.  So you must restart the admin console before it can show the correct values.
If you deleted the node from the ISY, you'll have to restart the node server so it can re-create the node.

Ok,

Refresh the store and restart the node server.  It should install version 2.0.1 and I believe that will fix the problem.

Version 2.0.5 should handle the new version of the Pandora plug-in.  It uses the sort by newest to get the station list.

I guess that makes sense, "not a number" isn't a number so it can't be converted to an integer.  In any case, the latest version shouldn't crash if that happens again.

I just pushed version 3.0.1 to the node server store.  This version should stop it from crashing.
Restarting the node server, should auto update it.  If that doesn't work, let me know.

Maybe this:
 

Version 2.0.3 should fix both shuffle and repeat command.

Most don't support query because the data is being polled at timed intervals, not by a manual query.