Did Arlo change something? about arlo HOT 9 CLOSED

Hi Len,

I'm not aware of any changes. I'll do a little testing later today.

from arlo.

Hey Len, as far as I can tell, nothing has changed. I logged into their UI and watched the requests. Can you check the system time on your pi?

from arlo.

The system time is correct, and I've rebooted several times.
It looks like the login succeeds, and then it returns a "401 Client Error: Unauthorized" error while trying "basestations = arlo.GetDevices('basestation')"

from arlo.

Odd. It works fine for me. I just tested. Stupid question here, but did you happen to change your password or anything like that?

Edit: Nevermind, I see you said you didn't change your login info.

from arlo.

Or update any python packages?

from arlo.

Can you add some debugging to Arlo.py for me? Maybe dump the r in the line that does the http request.

r = requests.get(url, headers=headers, cookies=cookies, stream=stream)

from arlo.

Well (blush) I did try updating stuff when it starting failing, so I don't want you to spend a lot of time on this. I might have my PI in an inconsistent state. But it started failing (on both my systems, which use different logins) before I changed anything; I've never changed the userids or passwords.

Using the original 2-year-old code, logging in appears to succeed.
Before the line "r = requests.get(url, headers=headers)" in the get function,
the url is 'https://arlo.netgear.com/hmsweb/users/devices'
and headers is { 'Authorization': '2_5ZUbjyTDdO-odN1dYkQIsPeMbWOcrRtLNin0STbxS_ZmIibW32sprYHvcoVToh_HmCLtFY2NhIju7WRdZyPEbjlpeQ2ffllftvJ3b46j8LaTY9weHJ6PBsTfk2U0JyEzGy_Xz0l23M_b1jqnBhLNtzTcieuvdIA75Apj75-PsHhH'}

Then after requests.get the result r is <Response [401]>
and it raises an exception.

from arlo.

Guess what? Several weeks after it started failing, it suddenly starting working again, without me doing anything! This is for two different Raspberry Pis controlling different cameras with different account logons in different houses in different cities. (I had updated the Python version on one of them when the problem started, but the other one hasn't been touched in two years.)

I can only surmise that Arlo temporarily broke something in the way they respond to the commands that your two-year-old code issues, but then fixed it.

Sorry for the false alarm...

from arlo.

Great news! Thanks for the update. I would highly recommend checking out the latest and greatest code. The API hasn't changed all that much (it has changed) and there have been several bug fixes and new APIs added. That being said, if it ain't broke... :)

from arlo.