Auth failure after update to 3.1.1 about ring-mqtt HOT 14 CLOSED

The error seems to indicate that you entered an invalid username and password (access denied from the authentication attempt). Are you sure you used a valid account? You can always just restart the addon and try again.

from ring-mqtt.

I am able to login via the website with the same account / creds.
Copy paste.

Oddly enough I am successful with the addon by using my personal, instead of the shared account I created for Home Assistant. Same password even.

from ring-mqtt.

Weird right?

from ring-mqtt.

Also where is your Buy me a coffee link? I use this addon every single day and cannot thank you enough.

from ring-mqtt.

Even more weird as there were absolutely zero chanhes to the code that gets the token so if it worked before and not now I have no idea why. Also the error is super clear, access denied is pretty basic auth failure, so I can't see how it could be anything else. Really weird.

Also, I use a shared account with no issues. Perhaps you could try an alternative method to get a token, the web page is just a poorlt implement hack so maybe it's something there, although I don't know what.

from ring-mqtt.

from ring-mqtt.

from ring-mqtt.

I thought about the password encoding as well, because I'm definitely doing nothing special there, but the fact that it works with another account using the same password made me think that wasn't it. I also have some pretty weird characters in my service account password with no issues.

The web based tool is just a very quickly implemented wrapper around the existing functions in ring-client-api and I did update to the latest API version in the most recent push, perhaps something changed there, although it seems to work for me. You can always generate the token from the cli of any machine with node installed by doing something like:

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

Or, from HASS.io you can get CLI access and run ring-auth-cli from within the addon container.

from ring-mqtt.

I've tested everything I can think of with this and all auth works just fine got me. I get a successful token each and every time, no issues. I tried with existing shared accounts, main accounts, new accounts, I tried huge, complex passwords. I'm not sure what else could be the issue here.

from ring-mqtt.

I have pushed version 3.2.1 which includes some enhacements to the Web UI including checking for valid user/password and token entry. Also, it's no longer required to manually copy and paste the token as the token is automatically saved into the new ring-state.json file.

I've tested authentication with this quite completely, using 3 different accounts with all types of generated passwords. The only authentication failures I could reproduce were when I had requested too many 2FA tokens too quickly and Ring blocked the account for about 12 hours (interestingly, the error message indicated it would only be blocked for 10 minutes).

If you are still having issues please let me know and we can troubleshoot. Otherwise I will close this issue in a few days.

from ring-mqtt.

I finally got to circle back to this.
Right now I am signed in as my personal account and it works.
I'm trying to change the login, but it keeps grabbing my current refresh token for my personal account.
I tried removing the key from config.

How can I get the add-on to host the web UI again?

from ring-mqtt.

I uninstalled then reinstalled, added my second account and auth works now.
Closing

from ring-mqtt.

Is this you? https://www.paypal.com/paypalme/tsightler/

from ring-mqtt.

Thanks for the feedback and glad to know you got it working. In a future version of the add-on the web UI will simply run all the time so that you can generate a new token with a new account even if it is already running. It will also automatically detect MQTT connection info using the HA API. For now, if the current token is functional the only way to use a new account is to do what you did, uninstall/reinstall, unless you manually connect to the container and delete the existing token. Hopefully when I release 4.0 in a few weeks the entire auth will be handled via the UI and require no config at all (other than token generation) to get it working, at least, that's the plan.

No that isn't me! :)
While I appreciate the gesture I don't really need any donations for this project. I'm fortunate to have a great job that pays the bills quite nicely and I started this project mainly as an excuse to learn Javascript (something I'm still not good at but at least I've learned enough to be dangerous) and it was useful for my own home automation.

If you have money to donate I'd suggest picking a charity you can be passionate about or perhaps even select some person you know that is in need (I know plenty in that state during these times) and send them the money instead. Most likely that's what I would do with it anyway.

from ring-mqtt.