Open roygbiv856 opened 5 years ago
This really doesn't have anything to do with the addon but rather support would have to be coded into the script (this addon is just a wrapper for my ring-alarm-mqtt script) and, by turn, my script is dependent on ring-client-api. The latter did recently add support for 2FA, so it might be possible to support it in my script, but I'm skeptical of the practical use. Do you really want to have to enter a single use PIN every time you restart HASSIO? The implementation also requires saving a token on the filesystem. I'm just afraid it would open a world of support requests because it is not straightforward to use.
My suggestion at this time is to just create a separate account that is used by the addon and share the devices you want the addon to use. You can create a very strong random password on this account and leave 2FA off, while enabling 2FA on your primary account. This also has the nice advantage that automation options performed by the addon actually show being performed by the addon specific account (I call mine Home Assistant so I get events like "Alarm armed home by Home Assistant").
I'm willing to entertain ideas on implementing 2FA in a practical way, but I'm not sure I want to get into the hassle of supporting it.
Is there currently anyway to use this add on along with Ring's new 2FA? I can't get the add on to work with 2FA activated on my Ring account. If not, maybe sometime in the future?