Closed jannegpriv closed 2 years ago
Verisure has also changed the authentication process so the binding needs to be adapted to that awell. Also some endpoints used for smartlock and battery status has been removed.
I will work on 2 solutions:
Since Verisure offers the possibility to configure per user if MFA shall be activated or not, it seems more reasonable to only support non MFA activated users for the binding, since this specific user then only can be used for automation and the primary user can then have MFA activated if that is desired.
I will therefore rename this issue to support for non MFA activated users.
Fixed by #11265
Verisure has enforced MFA authentication that the binding needs to adapt to.