Joey Berkovitz

You're likely running into the authentication issue mentioned here: https://github.com/davglass/doorbot/issues/52 The main code hasn't been updated to support oauth yet, so you'll need to switch to a version that has...

Not sure about the details, but if you're using my fork, it doesn't have the latest download code, so you should probably download the contents of the example folder from...

The history function in doorbot.js also changed, try copying that too

I updated download-all.js and doorbot.js in my fork. I tested the fix for download-all.js and it did a few loops before I stopped it, so it looks like it's working...

Is this possibly related to the fact that you can't disable 2FA anymore? This module doesn't support 2FA logins, but if you have an auth and refresh token, it'll work...

Yes. Try that script I sent and see if you get an error. At least on my account there's no way to disable 2FA, just switch it to email as...

Maybe try running the ring-auth-cli from somewhere like here: https://github.com/dgreif/ring/wiki/Refresh-Tokens to get a refresh token After that, put your refresh token in your .ringAlarmCache file in the "refreshToken" key: {"oauthToken":"BLANK","refreshToken":"REFRESHTOKEN","hardware_id":"ID"}...

It should be in your home directory - /home/USER on Linux, C:\Users\USER\ on Windows. Also, this functionality is only included in my fork.

Sounds like maybe there's something wrong work your save directory, variable called base. Otherwise will need some more logging to figure out your specific issue

Thanks anyway. Figured out that the correct websocket URL is actually "wss://" + alarmConnection.server + "/?authcode=" + alarmConnection.authCode, which enabled me to establish a connection. Will provide updates as I...