Having issues generating refresh token

[happydutch]

I am using a docker installation and updated to latest.

Started new container and got this message:

Node version v16.14.2
2023-09-08T17:34:22.841Z ring-mqtt No refresh token was found in the state file, use the Web UI at http://<host_ip_address>:55123/ to generate a token.
2023-09-08T17:34:22.834Z ring-mqtt State file /data/ring-state.json not found. No saved state data available.

However when I use the UI, it hangs and I see the following in the logs:

Node version v16.14.2
2023-09-08T17:34:22.841Z ring-mqtt No refresh token was found in the state file, use the Web UI at http://<host_ip_address>:55123/ to generate a token.
2023-09-08T17:34:22.834Z ring-mqtt State file /data/ring-state.json not found. No saved state data available.
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at ServerResponse.res.cookie (/app/ring-mqtt/node_modules/express/lib/response.js:884:36)
    at /app/ring-mqtt/lib/tokenapp.js:70:25
    at Object.serialize (/app/ring-mqtt/node_modules/cookie/index.js:126:11)
TypeError: argument val is invalid
2023-09-08T17:40:00.935Z ring-mqtt WARNING - Unhandled Promise Rejection

I was able to generate a refreshtoken manually using

npx -p ring-client-api ring-auth-cli

Where can I save this token manually?

Thanks,

[happydutch]

Never mind, turns out that when I placed ring-state.json in /data it started to work. I had still to authenticate, but UI worked after that.

[tsightler]

Honestly, the UI sometimes gives that weird error and I haven't been able to figure out why. It seems like it happens when there is a null response from the Ring servers, but, theoretically, that shouldn't happen. I've seen it completely randomly, but usually, after a try or two, it works, which makes it very difficult to troubleshoot the root cause.

[tsightler]

BTW, the docker install instructions for ring-mqtt already document how to acquire a token via the CLI, and it's not by using ring-auth-cli but rather with init-ring-mqtt. If you follow those instructions, it will create the token and place it in /data/ring-state.json automatically as well as create a basic config.json there as well.

Glad you got it working, this comment is mostly for future users if Google returns this issue.

[tsightler]

Node version v16.14.2

Also, you state you updated to the latest container version but that Node version hasn't been in use in any container built in the last year, so that's pretty weird. While current versions might still run on v16, they are not tested and v18 or higher are recommended. Admittedly, if using the container, this shouldn't matter.

[happydutch]

That's odd indeed, I pulled a fresh container using :latest...

And thank you for this excellent integration!!!