body-error=JSONDecodeError

[akjaouen]

Hi,
I am receiving this new error :
body-error=JSONDecodeError
on the account connection of my Arlo Go. This has been working for months without any issue, and I haven't changed anything recently. Do you know where this might come from ?

It seems related to a <Response [403]> on the
r = self._session.post(
url, json=params, headers=headers, timeout=timeout
)

Here is the params :
{'email': 'a........', 'password': 'Q..........', 'language': 'en', 'EnvSource': 'prod'}

And headers I am using :
{'Accept': 'application/json, text/plain, /', 'Accept-Language': 'en-US,en;q=0.9', 'Origin': 'https://my.arlo.com', 'Referer': 'https://my.arlo.com/', 'Source': 'arloCamWeb', 'User-Agent': 'Mozilla/5.0 (iPhone; CPU iPhone OS 11_1_2 like Mac OS X) AppleWebKit/604.3.5 (KHTML, like Gecko) Mobile/15B202 NETGEAR/v1 (iOS Vuezone)'}

Thanks in advance.

[akjaouen]

I am still working on it.

I have noticed twrecked changes on the mqtt calls notably in the headers keys. But even adapting text on this side, made no difference on the 403 error.

[twrecked]

If you can capture some logs I can take a look.

But if this is really early on try upgrading cloudscraper. he requirement are showing 1.2.58 but they are up to release 1.2.71.

[akjaouen]

Thank you for getting back to me.
I have just upgraded cloudscraper to 1.2.71 as mentioned, but it doesn't seem to make a difference.

Here are some logs :
log.txt

The 403 message appears with the following input :

URL:
https://ocapi-app.arlo.com/api/auth?eventId=FE!b741eca4-b333-4c75-9144-7316e0898871&time=1684005230685

HEADERS:
{'Accept': 'application/json, text/plain, */*', 'Accept-Encoding': 'gzip, deflate, br', 'Accept-Language': 'en-GB,en;q=0.9,en-US;q=0.8', 'Origin': 'https://my.arlo.com', 'Referer': 'https://my.arlo.com/', 'Source': 'arloCamWeb', 'User-Agent': 'Mozilla/5.0 (iPhone; CPU iPhone OS 11_1_2 like Mac OS X) AppleWebKit/604.3.5 (KHTML, like Gecko) Mobile/15B202 NETGEAR/v1 (iOS Vuezone)', 'x-user-device-id': '6HN72F8R-176-59088669', 'x-user-device-automation-name': 'QlJPV1NFUg==', 'x-user-device-type': 'BROWSER', 'x-transaction-id': 'FE!b741eca4-b333-4c75-9144-7316e0898871'}

[twrecked]

And you're on the latest version of pyaarlo? Because those were the errors I was seeing before I updated the headers.

[akjaouen]

Yes lastest version :

(base) jaouen@jaouens-MBP pyaarlo % git log                                                         
commit 3eead47bc4d2d6ddb5e8e1386b0a05b9ffae938d (HEAD -> master, origin/master, origin/HEAD)
Author: Steve Herrell <[email protected]>
Date:   Wed May 10 07:30:17 2023 -0400

    Mqtt config (#119)
    
    * MQTT Config.
    
    Allow these items to be configured:
    - mqtt hostname
    - check hostname in SSL certificate
    - mqtt transport type.
    
    Fix changed header.

[akjaouen]

If that helps, when I connect with the my.arlo.com web interface, I get the following.
I guessed that it is on the "auth" call that it seems to block when I use Pyaarlo. But even trying to add other missing headers fields did not make a change.

[twrecked]

They changed the name of one of the headers to ...automation-name, you can see it in the trace you sent, and you have that fix in the code.

2 things to try

Delete the season pickle files, one of them is named 'aarlo.pickle' and I can't remember the other but they are next to each other and try starting it again

Can you change your external IP address? It maybe thinks you made too many bad attempts and it has blocked you.

[njaouen]

Hi Steve,
I have tried all proposed solutions :

• deleting both the session.pickle and aarlo.pickle files in .aarlo,
• switching to a different IP address (even on a different computer and network),
• mqtt_hostname_check=False (as you proposed in authentication error #121, since it seems to be exactly the same issue).

But I am still getting the same error, as mentionned in #121.