arlo: Logins Fail since recent my.Arlo.com change.

Please answer these questions before submitting your issue. Thanks!

What version of Python are you using (python -V)?

3.9.2 (but doesn’t seem to matter)

What operating system and processor architecture are you using (python -c 'import platform; print(platform.uname());')?

Both Windows 10 and Mac OS behave the same

Which Python packages do you have installed (run the pip freeze or pip3 freeze command and paste output)?

Paste your ouptut here
arlo==1.2.40
base36==0.1.1
certifi==2020.12.5
cffi==1.14.5
chardet==4.0.0
click==7.1.2
cryptography==3.4.6
curve25519-donna==1.3
Cython==0.29.22
DateTime==4.3
docopt==0.6.2
ed25519==1.5
Flask==1.1.2
future==0.18.2
h11==0.12.0
HAP-python==3.4.0
httpserver==1.1.0
idna==2.10
ifaddr==0.1.7
iso8601==0.1.13
itsdangerous==1.1.0
Jinja2==2.11.2
MarkupSafe==1.1.1
monotonic==1.5
numpy==1.20.0
pandas==1.2.1
patsy==0.5.1
Pillow==8.1.0
psutil==5.8.0
pycparser==2.20
pypap==0.2.dev201201051355
PyQRCode==1.2.1
PySocks==1.7.1
python-dateutil==2.8.1
pytz==2020.5
PyYAML==5.4.1
requests==2.25.1
scipy==1.6.0
serial==0.0.97
simplejson==3.17.2
six==1.15.0
sseclient==0.0.22
statsmodels==0.12.2
urllib3==1.26.3
uWSGI==2.0.19.1
Werkzeug==1.0.1
zeroconf==0.28.8
zope.interface==5.2.0

### Which version of ffmpeg are you using (`ffmpeg -version`)?

Paste your output here not using FFMPEG

Which Arlo hardware do you have (camera types - [Arlo, Pro, Q, etc.], basestation model, etc.)?

What did you do?

If possible, provide the steps you took to reproduce the issue. A complete runnable program is good. (don’t include your user/password or any sensitive info)

Paste your ouptut here


### What did you expect to see?

Paste your ouptut here

### What did you see instead?

Paste your ouptut here A call to connect, which worked a short time ago, now returns “Error 401 Client Error: Unauthorized for url: https://my.arlo.com/hmsweb/login/v2”

Seems to be related to a recent change in the Arlo app which requires prior authentication. I’ve logged in from 3 different machines (2 PC, 1 Mac) which are attempting to issue the connect call. All return the same error.

Does this issue reproduce with the latest release?