Issue with trying to upgrade solaredge NS

[Mecheng70]

Trying to upgrade the beta solaredge_poly.  @photogeek54 mentioned to copy @bpwwer.

Been having 2 issues.

1. Solaredge NS not sending child nodes to AC. Was on with Michel and he thinks that the issue is the space or something in the site name that comes from Solaredge.  I think that is it the "/" messing it up.
2. Can't update to the 1.1.01 solaredge_poly non production nodeserver.

Focusing on number 2 as number 1 may go away when upgrading.

I have installed, uninstalled, deleted, restarted the node and PG3X and still the version indicates that the newer version is loaded, however, on refresh it reverts back to the previous revision.  The update doesn't update as it reverts back.

Here is a video showing it reverting back.  https://photos.app.goo.gl/MpHj22nM7a3HagLJ9

 

Here are the PG3 debug log.  pg3_6-20-2023_14724_PM.zip

@photogeek54 identified this being strange.

6/20/2023, 13:44:30 [pg3] error: unhandledRejection REPORT THIS!: [object Promise], reason: TypeError: Cannot read properties of undefined (reading 'status')
6/20/2023, 13:44:30 [pg3] error: IoX Response: [Try: 1] [00:21:b9:02:62:25] :: [404 - OK] :: 0.947786ms - http://127.0.0.1:8080/rest/ns/1/nodes/n001_dy1352992/report/status/ST/16.0/33

 

For backstory:

In order to get the nodes added to AC, I copied and pasted them into a browser with the name without the "/" in the URL.  The "/" gets translated to %2F

FROM

/rest/ns/1/nodes/n001_1352992/add/SESITE?primary=n001_1352992&name=NAME%20-%20NEC6518%2FNBTC6804

TO

http://172.16.5.251:8080/rest/ns/1/nodes/n001_1352992/add/SESITE?primary=n001_1352992&name=3036Street

Edited June 20, 2023 by Mecheng70
added information for number 1.

[photogeek54]

v1.1.01 of Solaredge should take care of the "/" problem but that version won't load for @Mecheng70.

Also attached is the log from the node server.

debug.log

[bpwwer]

When the version reverts like that, it means the node server code is sending that version after it starts.

PG3 access the node server store record for the node server and that record has version as 1.1.01 so PG3 assigns that version to it's internal record of the node server.  Then with the node server starts it passes version 1.1.0 to PG3 and PG3 updates it's internal record to reflect what is actually running.

There were versions of PG3x that had issues with permissions of node server files such that once installed, it wasn't able to update them.  I believe that was fixed in 3.1.26 so make sure you are running a recent version.

You could try installing in a different slot, doing that would guarantee that you have the most recent node server code installed.  If you still see the issue, then the node server package that is out on the server isn't matching the version listed in the node server store. 

[Mecheng70]

9 hours ago, bpwwer said:

 

You could try installing in a different slot, doing that would guarantee that you have the most recent node server code installed.  If you still see the issue, then the node server package that is out on the server isn't matching the version listed in the node server store. 

Installed the solaredge_poly in slot 10:

Notice that the current version is 1.1.0

Updated it using the Update button and the same thing happened where after the update, the current version changed from 1.1.01 to 1.1.0.

Only one node shows up in AC for each of the NS.:

[Mecheng70]

Also deleted all NS and rebooted.  Reinstalled into slot 6.  Updated to 1.1.01 and then it reverted to 1.1.0.

Here are the log files.solaredge_poly_6-21-2023_83403_PM.zip

[photogeek54]

So I've reproduced @Mecheng70 issue of not being able to load the current version of solaredge from the non-production store. I deleted my own v1.1.01 NS and tried to reinstall it and now I can only get v1.1.0 even after restarting PG3X and the admin console. There are some errors showing in the PG3X log if that has anything to do with it.

error: IoX Response: [Try: 1] [00:21:b9:02:60:68] :: [404 - OK] :: 43.417083ms - http://127.0.0.1:8080/rest/nodes/n005_controller 6/21/2023, 23:11:20 [pg3] warn: node controller on profile 00:21:b9:02:60:68/5 not in the database. Adding...

I also see in @Mecheng70's log that he has 2 controllers showing up. Deleting a NS should make those go away. Assuming that his issue not adding the nodes has to do with the "/" in his controller name, then getting him (and me now) to the current version should help.

Seems like some kind of PG3X issue and I have the latest IOX and PG3X. I'm hoping @bpwwer has an idea.

 

[bpwwer]

@photogeek54 You have version 1.1.02  as the version specified in the node server store entry but the node server is sending it's version as 1.1.0

You probably want them to match.

[photogeek54]

Just figured it out. it's my problem. Fix coming soon.

 

[photogeek54]

v1.1.02 is now correctly published in the non-production store, fixed problem syncing to github.

@Mecheng70's problem adding nodes due to an illegal character in the site name appears to also be fixed.

[Mecheng70]

Up and running.  Can see them in UD Mobile.  THANK YOU!