Arlo stop Working!

[dfoti10]

[m505h1]

Mine too

[0bmay]

Notification from HA: "Error: login failed: 403 - possible cloudflare issue If error persists you might need to change config and restart."

I had about 60 Arlo emails for 2fa code too

from the debug logs: 2025-02-05 14:54:50.496 ERROR (SyncWorker_4) [custom_components.aarlo] unable to connect to Arlo: attempt=1,sleep=15,error=login failed: 403 - possible cloudflare issue

I was running HA v 2025.1.x (didn't log this prior to upgrading to 2025.2.0) and still have the issue with HA 2025.2.0

[0bmay]

as a reminder, when there are issues please add as much detail as you can. "It stopped working" doesn't really help the developer(s) out at all..

[haydonz]

I have just had the same error and 2FA requests, running 2025.1.4.

[Plargio]

I am getting the same error, and my mailbox got bombarded with 2fa codes

"Error: login failed: 403 - possible cloudflare issue If error persists you might need to change config and restart."

[athrun]

Ran into this issue as well this morning. I got plenty of Arlo 2FA emails. This is with version 0.8.1.11. Before this, it had been running for months without any hiccups.

Logger: pyaarlo
Source: custom_components/aarlo/__init__.py:408
integration: Arlo Camera Support ([documentation](https://github.com/twrecked/hass-aarlo/blob/master/README.md), [issues](https://github.com/twrecked/hass-aarlo/issues))
First occurred: 9:04:39 AM (21 occurrences)
Last logged: 9:07:11 AM

session start failed
body-error=KeyError
error in new response={'meta': {'code': 400, 'error': 9236, 'message': 'Invalid OTP'}}
login failed: finish failed: 400 - Invalid OTP```

[dfoti10]

Same error here.

[LegacyR]

Also experiencing this exact issue.

[0bmay]

I'm guessing it's an issue with cloudflare, as the log suggests, or Arlo changed something and broke the integration.

[RadDip]

According to Cloudflare's incident website, there was an issue today that they have implemented a fix for. They stated they are continuing to monitor the status.

[JuiceDev82]

This broke and remains broken for me after the HA 2025.2 core update that I just installed and rebooted.

[twrecked]

Both this integration and pyaarlo are working here for me.

If someone can turn on pyaarlo and aarlo debug and post it here can take a look at what is happening.

[Reserton]

Seems I chose worst time to install a new HA on a new PI and flatten my old one. My Aarlo broke and getting same error as everyone else about cloud flare. Tried the user_agent , save_session config and didnt fix.

Debug logs below :

[Reserton]

pyaarlo logs :

[twrecked]

@Reserton try deleting the authentication session. Look for and remove this file .aarlo/session.pickle.

[Reserton]

Didn't work. I am also not even getting the auth emails anymore now.

[wat-doing]

I have deleted .aarlo/session.pickle and then Restarted the integration, but same error persists.

[twrecked]

Can you turn on verbose debug? I need to see what is coming back from Arlo. Add verbose debug to your extra Arlo config in aarlo.yaml.

version: 1
aarlo:
  verbose_debug: true

This can get quite chatty, I just need the stuff after and around [pyaarlo] backend: login attempt .

Can you paste that config as well?

[Reserton]

I have added that but logs are no different.

Also seeing this in my logs :

2025-02-06 02:32:14.135 ERROR (MainThread) [homeassistant.config] Invalid config for 'aarlo' at configuration.yaml, line 57: required key 'password' not provided, please check the docs at https://github.com/twrecked/hass-aarlo/blob/master/README.md Invalid config for 'aarlo' at configuration.yaml, line 57: required key 'username' not provided, please check the docs at https://github.com/twrecked/hass-aarlo/blob/master/README.md 2025-02-06 02:32:14.135 ERROR (MainThread) [homeassistant.setup] Setup failed for custom integration 'aarlo': Invalid config.

It seems whenever I add aarlo: for any settings it expects username and password in configuration.yaml

[twrecked]

@Reserton The config needs to be in a new file called aarlo.yaml.

edit: it's an over flow for all the extra settings.

[Reserton]

I added that new file. Still logs have not changed. Does the new file go in same folder as configuration.yaml as thats where i put it.

[twrecked]

Yes, in the same folder. If you upgraded from an older build you should have had one already.

Double check the name, it has to be lower case and with two aa at front.

With verbose debug you should be seeing the replies you are getting from Arlo.

[Reserton]

I am in situation where i just happened to be setting up new Pi when this issue hit. so this has never worked on this Pi. I had copied my old backup, but that doesn't appear to have brought across an aarlo.yaml file but I did delete the devices when it wasn't working and readded.

name is deff right attaching screenshot.

https://imgur.com/a/4TwkNHJ

[twrecked]

You'll know if the file is being read, you'll see this in you log:

 [custom_components.aarlo.cfg] _async_load_yaml1 file_name for /config/aarlo.yaml

And to make sure. this is the logging:

logger:
  default: info
  logs:
    pyaarlo: debug
    custom_components.aarlo: debug

[Reserton]

Yeah I had removed the logging from configuration.yaml just figured that out :

[0bmay]

@Reserton you are going to want to change your Arlo password now as it's in the logs..

[LordPsycho202]

@Reserton you are going to want to change your Arlo password now as it's in the logs..

I was just logging in to warn him the same thing.

[0bmay]

Even though you edited the post @Reserton,. it got emailed out to people who subscribe to this thread. I'd recommend you still change your Arlo password. :-)

[Reserton]

Yeah reset, didnt see it at first skim then noticed.

[twrecked]

@0bmay @LordPsycho202

Thanks for spotting that!

This is the problem:

2025-02-06 03:00:09.213 DEBUG (SyncWorker_5) [pyaarlo] backend: request-body=
'Unknown error has occurred'

Try setting the user agent. I'm not sure what is causing the error because the packet looks good.

version: 1
aarlo:
  verbose_debug: true
  user_agent: linux