PG3 not updating version

[apostolakisl]

I put his here, because this is the current node server having this issue, but I have had this happen many times.  I am running 2.0.6 and it says there is an update.  I restart, it briefly shows the new version (2.0.8) and then switches back to 2.0.6 and tells me to restart for the update.  I even tried restarting PG3, same thing.  I also have several other nodes that tell me to restart for a new, even though the current running version is the same as listed in the store.  For example, the itach node currently tells me to restart for a new version even though it is running the current version.

[Panda88]

Sorry - it is an issue with having to update the version number multiple places (and remember to do it everywhere) when releasing the node.   There are at least 3 places that needs to be in sync. 

BTW - you are correct - I did not update the run-time display of the node number to latest version 

I think PG3 compare that to the number in the node store to determine if an update is needed

I did update the node number now - but I'll be looking to add a sleep parameter to the status node to update the car state so a new version will be required 

[Geddy]

@apostolakisl what version of PG3 are you running? Are you on 3.1.x? If on an older version (like 3.0.x) then there's apparently something not allowing it to show the actual version of node server you're running. It's only going to show the last version that is supported by your version of PG3. I saw @bpwwer mention this somewhere. It was a change in the PG3 3.1.x update and would break the older versions if handled differently. 

So make sure PG3 is updated and it might fix your issues with other node servers you say you're having the issue with.  If you're current then it could be the other developers have not updated where the version numbers are since the 3.1.x update in PG3 purchasing process. 

 

[Goose66]

@Panda88, if you are running the Python interface for your node servers, you can drop the server.json file and just pass a version string on the poly.start() call. That way, there are only two places (Node Server Store purchase option(s) and version string passed to poly.start()) that have to be kept in sync.

[Panda88]

Thanks - What about the node version besides purchase options in the developer page?  I try to update both - My impression is it actually uses the node version for checking - you can show different version under purchase options as I understand  - I may be wrong

[apostolakisl]

25 minutes ago, Geddy said:

@apostolakisl what version of PG3 are you running? Are you on 3.1.x? If on an older version (like 3.0.x) then there's apparently something not allowing it to show the actual version of node server you're running. It's only going to show the last version that is supported by your version of PG3. I saw @bpwwer mention this somewhere. It was a change in the PG3 3.1.x update and would break the older versions if handled differently. 

So make sure PG3 is updated and it might fix your issues with other node servers you say you're having the issue with.  If you're current then it could be the other developers have not updated where the version numbers are since the 3.1.x update in PG3 purchasing process. 

 

I'm running 3.0.63.  It is not offering me a newer version.  I checked the "use beta versions" box to see if it offers me a newer version.  So far, it hasn't done anything.  But, now I would be using a beta which may have other issues.

Itach for example is one that is telling me there is a new version, even though it appears I am running the latest.

I also don't know why "i" is coming at the end of the alphabet instead of up where you would expect "i" to be.

[Goose66]

Update PG3 using the Admin Console in IoP - specifically "Configuration"->"System"->"Upgrade Packages."

[apostolakisl]

48 minutes ago, Goose66 said:

Update PG3 using the Admin Console in IoP - specifically "Configuration"->"System"->"Upgrade Packages."

I did the update and nothing changed.

 

Still have 3 nodes saying they need to be restarted to have latest version even though they already have the latest version.  iTach, Push, and Backup are all reporting they need restarting for update but all have the latest.  I restarted them individually and the entire PG3.

 

EDIT: And also now the Tesla ap does to.  It updated to 0.2.9 which is the latest and it wants a restart also.

Edited October 27, 2022 by apostolakisl

[Geddy]

15 minutes ago, apostolakisl said:

I also don't know why "i" is coming at the end of the alphabet instead of up where you would expect "i" to be.

Apparently "computer people" alphabetize capitalizations different than normal humans. Same reason some of the other node servers that are in all caps get put before others. That's "computers" for you.

 

Are you running ISY994 or IoP? Your screen shot above is showing the ISY is at 5.3.3. 

ISY994 current version is 5.3.4

IoP current version is 5.4.4

I don't think that makes a difference for what you're experiencing, but is just another update needed somewhere. 

 

[Goose66]

So the initially reported version in the Dashboard on startup comes from the local database entry in PG3 database. But a few moments after startup, the Dashboard shows the version indicated by the running node server code itself. I had one that was doing what you described, and it was because the code package specified with the new version either wasn't being found or failing on unzip/install, and what ended up being started was the older version, despite the fact that PG3 thought the new version was installed (in my case it wasn't finding the specified zip file on the Node Server Store servers).

Choose one of them and work with the node server developer to go through the log package and see if you can troubleshoot what is (may be) failing on the installation of the update.

WRK

Edited October 27, 2022 by Goose66

[apostolakisl]

1 hour ago, apostolakisl said:

I did the update and nothing changed.

 

 

Still have 3 nodes saying they need to be restarted to have latest version even though they already have the latest version.  iTach, Push, and Backup are all reporting they need restarting for update but all have the latest.  I restarted them individually and the entire PG3.

 

EDIT: And also now the Tesla ap does to.  It updated to 0.2.9 which is the latest and it wants a restart also.

Well, there is another problem then.  I am running 5.4.4 (IoP), not 5.3.3

 

Edited October 27, 2022 by apostolakisl

[bpwwer]

If the version shown on the dashboard/details for the node server matches the version shown in the store listing, you can delete the update notice and it should go away.

[apostolakisl]

3 hours ago, bpwwer said:

If the version shown on the dashboard/details for the node server matches the version shown in the store listing, you can delete the update notice and it should go away.

good enough, but, doesn't the fact that it is showing at all mean there is a bug?

Also something goofy about polisy thinking I am on a different ISY firmware than correct.  

[Panda88]

Sorry - it is an issue with having to update the version number multiple places (and remember to do it everywhere) when releasing the node.   There are at least 3 places that needs to be in sync. 

BTW - you are correct - I did not update the run-time display of the node number to latest version 

I think PG3 compare that to the number in the node store to determine if an update is needed

I did update the node number now - but I'll be looking to add a sleep parameter to the status node to update the car state so a new version will be required 

[Panda88]

Did you try to run an update modules from the AC - if not try to contact Michel - he helped a similar issue I had 

[apostolakisl]

@Panda88  I have updated Polisy using the AC update packages menu to no avail.  And I just updated Tesla node and it successfully installed your new version, but still tells me to restart for a new(er) version that doesn't exist.