@bpwwer,

I had a notice for the Ambient Weather NS to update to 2.0.7.  I'm on 2.0.6.  After restarting the NS, the version remains 2.0.6(at least according to the NS info).  I've tried this several times with the same results.  The PG3 log for that event is attached.  I'm running PG3 3.1.15.

Can't say if this is limited to this NS.

 

Ambient Weather Update(25Nov22).rtf

I have the same issue but since everything was running ok it was low priority...

same issue...

I don't see anything wrong (other than it not updating). 

I did just re-upload the package file since it's possible I made the package but forgot to upload it.

@bpwwer Just tried the restart and still shows version as 2.06 but like I said low priority for me...

@bpwwer,

I finally had another NS ready for update and it updated normally.  Whatever is going on, it must be unique to the Ambient Weather NS.

Once I restart the Ambient Weather NS, the "new version" message goes away.  But when I return the next day to PG3, it's there again.  Just an observation.  Maybe there's a clue there.

 

Until we're able to update the Ambient Weather NS with a restart, there is another method you can use to update the NS.  I had to do this with the ELK node server and just completed it with this node server and it worked fine.

1) Go to the Node Server store and select the AmbientWeather button.

2) The next screen with show the latest version.  On the Perpetual line, select the Install button.

3) On the form displayed, look for "AmbientWeather is already installed in slot (your slot number)" and select the "Reinstall here?" button.

4) The latest version will be installed and the NS restarted.  Configuration info is preserved.

Worked for me.  All the data looks good.