Jump to content

PGC Ring updated?


TomL

Recommended Posts

I noticed in PGC Store that the Ring NS is now version 1.1.3 vs the 1.1.0 that I have installed  How do I upgrade to the newest version?  Do I delete current and install newest or just install newest?  I tried just stopping and restarting NS but that did not show any version upgrade happened.

Link to comment

On start:

  logBucket: 'pgc-prod-logbucket-[REDACTED_DATA]',
  url: 'https://github.com/UniversalDevicesInc/ring-nodeserver.git',
  isyPassword: '[REDACTED_DATA]',
  development: false,
  language: 'node',
  userId: '[REDACTED_DATA]',
   'https://[REDACTED_DATA].execute-api.us-east-1.amazonaws.com/prod/api/sys/nsgetioturl?params=[REDACTED_DATA]',
  timeAdded: 1561760405240,
  oauth: '<oAuth config>',
  isyVersion: '5.0.15',
  longPoll: 120,
  name: 'Ring',
  pgUrl:
  shortPoll: 60,
  timeStarted: 0,
  version: '1.1.0',
  id: '00:21:b9:00:f0:9c',
  netInfo:
  nodes: '<nodes>',
     publicIp: '3.89.244.35' },
   { publicPort: 30492,
   { oauth:
  customData:
     httpsIngress: 'https://pgc-ns-ingress.isy.io/ns/[REDACTED_DATA]/',
         '[REDACTED_DATA]',
        created_at: 1579398192,
      { access_token:
        token_type: 'Bearer',
         '[REDACTED_DATA]',
        refresh_token:

This was after receiving the code from Git.

Clearly - it's identifying as version 1.1.0.

And:

image.thumb.png.07dcc2f5108afa3f970929ff8f299524.png

After restarting it and it came back up - still 1.1.0:

image.png.22b4468cd5e01d65c7c150d778fec06e.png

Michael.

Link to comment
On 1/18/2020 at 9:37 PM, MWareman said:

Interesting - package.json lists version 1.1.3:

https://github.com/UniversalDevicesInc/ring-nodeserver/blob/master/package.json

image.png.7be63f7a28dd41b6c6c537ed4211377d.png

server.json (https://github.com/UniversalDevicesInc/ring-nodeserver/blob/master/server.json) contains version 1.,1.3 and profile_version 1.1.0:

image.png.394b71990a97dc667ce503a526236e23.png

Is this just a display bug in PGC?

Michael.

Looks like a PGC bug where the version number is not updated.

But clearly, the nodeserver is indeed updated to 1.1.3.

Benoit

 

Link to comment
10 minutes ago, MWareman said:

Just to be clear, the images are taken from the git repository.

How can I check the actual version installed as it reports in the UI as 1.1.0?

Michael.

1. Search for the postback url in the log:

2020-01-20 03:41:12 info: NS: Starting Subscription with postback URL https://pgc-ns-ingress.isy.io/ns/ring-<uuid>-1/event

2. Try the url in a browser, but replace "event" by "test". You should get a message saying the test is successful. This simply tests the communication to the nodeserver.

3. Now try the url in a browser once again, but remove "event", let the url finish with the forward slash. You should get a message saying "Node server is healthy". If so, this confirms you are running 1.1.3.

Benoit

Link to comment
14 minutes ago, MWareman said:

Just to be clear, the images are taken from the git repository.

How can I check the actual version installed as it reports in the UI as 1.1.0?

Michael.

With PGC currently you can't.  This is a bug where a nodeserver version does NOT get updated in Polyglot dashboard.  The actual code running does get updated anytime the nodeserver is  stopped and started as each time it pulls the code from git.  The only way for the Polyglot dashboard to show the proper version is to REMOVE/DELETE the Nodeserver and then re-install.  Then the version will update to the current/correct version. 

Link to comment
9 minutes ago, bmercier said:

1. Search for the postback url in the log:

2020-01-20 03:41:12 info: NS: Starting Subscription with postback URL https://pgc-ns-ingress.isy.io/ns/ring-<uuid>-1/event

2. Try the url in a browser, but replace "event" by "test". You should get a message saying the test is successful. This simply tests the communication to the nodeserver.

3. Now try the url in a browser once again, but remove "event", let the url finish with the forward slash. You should get a message saying "Node server is healthy". If so, this confirms you are running 1.1.3.

Benoit

All tests matched your steps - so if this confirms 1.1.3 then I'm good. 

Hopefully the PGC version display bug can be fixed soon.

Michael.

Link to comment
  • 4 months later...
On 1/19/2020 at 10:40 PM, bmercier said:


You are definitely using 1.1.3.


Sent from my iPhone using Tapatalk

I'm still running 1.1.0 based on everything in the gui and in the log.  Might explain why its not worked in weeks.  How do I get the Ring  PGC node server fixed?

 

Thanks.

Link to comment
11 hours ago, hart2hart said:

I'm still running 1.1.0 based on everything in the gui and in the log.  Might explain why its not worked in weeks.  How do I get the Ring  PGC node server fixed?

 

Thanks.

Delete and reinstall the nodeserver.

Link to comment
Delete and reinstall the nodeserver.

I added 2nd Ring Outdoor Cam with existing cam and doorbell. The cam motion node is not showing in PGC or obviously ISY. I’ve stopped and started node several times. If delete and add back is required will I need to redo folders ring associated programs?
Link to comment
23 minutes ago, hart2hart said:
On 6/3/2020 at 8:53 AM, bmercier said:
Delete and reinstall the nodeserver.

 

I added 2nd Ring Outdoor Cam with existing cam and doorbell. The cam motion node is not showing in PGC or obviously ISY. I’ve stopped and started node several times. If delete and add back is required will I need to redo folders ring associated programs?

They may have to be edited and re-saved.

Link to comment
  • 2 weeks later...

Hello,

I recently update the Ring PGC to version 1.3.0 via a delete and re-install. The stop and start did not not seem to update the version as expected. However, i am now not able to authenticate with my Ring account. I get the blue message and follow it to my Ring account and grant permission. After i do this, PGC goes into an infinite loop that never returns, and I have to kill the session and log back in to get access again. A single node appears in the ISY994 - for the controller only. I have changed slots with no change to results. I have also deleted and installed again with no effect. The previous version was working fine. What's next to get this working again?

Thanks

image.png.13d0b0cff7e0ed918333eaefd9030344.png

 

image.thumb.png.4df414a296a58ba09bb79620e7ee77a3.png

Link to comment
On 6/17/2020 at 9:51 PM, kcrimson said:

Hello,

I recently update the Ring PGC to version 1.3.0 via a delete and re-install. The stop and start did not not seem to update the version as expected. However, i am now not able to authenticate with my Ring account. I get the blue message and follow it to my Ring account and grant permission. After i do this, PGC goes into an infinite loop that never returns, and I have to kill the session and log back in to get access again. A single node appears in the ISY994 - for the controller only. I have changed slots with no change to results. I have also deleted and installed again with no effect. The previous version was working fine. What's next to get this working again?

Thanks

I would suggest to try again, I think there have been issues recently with PGC itself that are now resolved.

If you still have a problem after, we need to see what the Ring nodeserver logs are saying.

Link to comment
9 hours ago, kcrimson said:

Logins are working now - due to certificate update.

Still no luck on initializing the new version of the PGC Ring. I have attached the real time log file from PGC. There are some socket errors that flash by in red that do not appear in the log when the PGC Ring is installed.

Thanks

ring-0021b90202a2-6.txt 10.77 kB · 3 downloads

Do you get the authorization notice with the link?

If so, are you able to login with your Ring credentials when authorizing?

Benoit

Link to comment

Good morning.

Yes - I do get the authorization notice to connect to Ring. I follow that link to Ring, login, and then authorize on the Ring side.

image.png

I then login and receive the following Ring dialog box.

image.png.75dcc2f9231b7148f7b25cf2a4176f3b.png

After I select "authorize" here, that is when it returns to PGC and starts the endless loop above.

Thanks for your attention on this.

 

Link to comment

Archived

This topic is now archived and is closed to further replies.


×
×
  • Create New...