Refresh Token becoming Invalid after only a few minutes about ring HOT 2 CLOSED

One step would be to use something way newer the 9.23.0, latest version is 13.1.0. Nothing that old has been tested in a very long time and there are many updates to token handling due to changes in Ring API. You will not have much success with such an old version.

Changes to the token while the connection is active should not matter, the token is automatically updated in-memory and you don't need to care about this. The consuming code must monitor onNewRefreshToken so that it can save these new tokens for a future new connection.

You didn't share your code, just some random logs that only you can understand (clearly not from ring-client-api). Attempting to interpret your logs in the absence of other information, it appears to show new connections, but it's not at all clear why you keep reconnecting to Ring. This is not required, once the API client is connected, you can just reuse the connection without concerning about the token.

Your example was this:

• Create an API Client <-- Not sure how you are creating an API client without already having a token
• npx -p ring-client-api ring-auth-cli
• Subscribe to ring.onRefreshTokenUpdated and listen for any events
• if event, update persistence with new token, delete old one.
• Use auth token to call getCameras - get success
• Use auth token to call getCameras - get Auth error

But to me the flow is more like this:

• npx -p ring-client-api ring-auth-cli - get a token and store it in the persistent file
• Create an API Client using token from persistent file
• Subscribe to ring.onRefreshTokenUpdated and, on new event, replace the token in the persistent file
• Use API client and getCameras - get success
• Use API client and getCameras - get success

If at any point the connection is closed, create a new API Client using the last token saved in the persistent file, that is all.

A new token will be generated every time you make a new connection, but that should not matter as you should only need to make a new connection if the prior code has existed.

from ring.

@tsightler Thanks for your feedback and insight

You were right, the issue was I was creating a new ring client for each request. I guess this isn't the correct pattern. I'll raise a PR with a note for the Wiki to make this more explicit.

The fix for me was to add a new InitRing function which called the RingAPI class at start up and then a getter for whenever I actually wanted to use it.

Didn't need to upgrade the version (although I will!)

Appreciate the help!

from ring.