Arlo stop Working!

[dfoti10]

No description provided.

[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

[jxbrown]

@twrecked Im on Home Assistant 2024.2.5

[twrecked]

That might be too old. If you want to keep that you need to drop back to the previous version of aarlo you were using and set the user_agent in your config. You were probably on 0.8.1.8 before.

[jxbrown]

With 0.8.1.8, i'm getting this error: login failed: 403 - possible cloudflare issue
If error persists you might need to change config and restart.

Where do I set the user_agent ? I don't have a aarlo.yaml file.

[twrecked]

You need to create the file - next to your configuration.yaml. Put this in it.

version: 1
aarlo:
  user_agent: linux

[jxbrown]

downgrading to v0.8.1.8 worked. Thanks!

The only issue i have now is getting battery level info. When I go into the device settings, all of the sensors are disabled. I get the following message: This entity is disabled.

[n1976jmk]

my aarlo.yaml:

version: 1
aarlo:
  #verbose_debug: true
  backend: sse
  cipher_list: HIGH:!DH:!aNULL
  last_format: '%d.%m.%y %H:%M'
  reconnect_every: 90
  request_timeout: 120
  stream_timeout: 180
  refresh_devices_every: 3
  send_source: true
  mqtt_hostname_check: False
  mqtt_host: mqtt-cluster-z1.arloxcld.com
  mode_api: v2
  user_agent: Mozilla/5.0 (iPhone; CPU iPhone OS 18_3 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/18.3 Mobile/15E148 Safari/604.1

The lovelace card settings code:

type: custom:aarlo-glance
entity: camera.aarlo_some_camera
name: Some Camera
image_view: direct
image_top: name,status
image_bottom: motion,library,stream,snapshot
image_click: recordings
library_sizes: 3,4,2

Thanks, 0bmay, but can I please have a little more help? I have the Carlo version .18 (newest installed) and working, yay :).

My question is since I am only 4 months new to HA, using a HA Green. I did install the Lovelace HASS Aarlo sucessfully as well. I am still using (and enjoying) the default overview dashboard. How can I add this Lovelace to it showing my one Arlo camera?

thanks for your extra patience with me!

r/
Jonathan

[jxbrown]

downgrading to v0.8.1.8 worked. Thanks!

The only issue i have now is getting battery level info. When I go into the device settings, all of the sensors are disabled. I get the following message: This entity is disabled.

Update: I was able to fix the problem by disabling and enabling the integration again. Thanks @twrecked for all your help!

[martin0675]

Same here.

2025-02-10 11:10:23.252 ERROR (SyncWorker_4) [pyaarlo] session start failed
2025-02-10 11:10:32.567 ERROR (SyncWorker_4) [pyaarlo] login failed: 403 - possible cloudflare issue
2025-02-10 11:10:41.871 ERROR (SyncWorker_4) [pyaarlo] login failed: 403 - possible cloudflare issue
2025-02-10 11:10:41.878 ERROR (SyncWorker_4) [custom_components.aarlo] unable to connect to Arlo: attempt=4,sleep=120,error=login failed: 403 - possible cloudflare issue
2025-02-10 11:10:41.879 ERROR (SyncWorker_4) [custom_components.aarlo] unable to connect to Arlo: stopping retries, too may failures

In addition I have no access from Scrypted to Arlo. Therefore maybe a problem at Arlo / Cloudflare...?

[Reserton]

Same here.

2025-02-10 11:10:23.252 ERROR (SyncWorker_4) [pyaarlo] session start failed 2025-02-10 11:10:32.567 ERROR (SyncWorker_4) [pyaarlo] login failed: 403 - possible cloudflare issue 2025-02-10 11:10:41.871 ERROR (SyncWorker_4) [pyaarlo] login failed: 403 - possible cloudflare issue 2025-02-10 11:10:41.878 ERROR (SyncWorker_4) [custom_components.aarlo] unable to connect to Arlo: attempt=4,sleep=120,error=login failed: 403 - possible cloudflare issue 2025-02-10 11:10:41.879 ERROR (SyncWorker_4) [custom_components.aarlo] unable to connect to Arlo: stopping retries, too may failures

In addition I have no access from Scrypted to Arlo. Therefore maybe a problem at Arlo / Cloudflare...?

Please can you read the thread. This has already been fixed.

[stanb200]

Only really use aarlo for Battery Levels, but noticed - at the same time as all the other problems reported - that my automations had stopped working. Done all the fixes and updates suggested here and elsewhere and I am now seeing that of 7 cameras, 4 that connect directly to Arlo e.g. WiFi Connection are reporting battery fine here, whereas the 3 that connect via the Arlo Basestation initially did not update their battery levels, and since reinstalling/updating show battery level as "unknown" in HA. Previously, all were showing battery levels.

I can see mention of battery levels missing above, but its not clear if this is meant to be working again yet, any idea if its expected at this stage. not really sure what to provide to assist troubleshooting here as the logs don't seem to mention battery for anything.

[Reserton]

Only really use aarlo for Battery Levels, but noticed - at the same time as all the other problems reported - that my automations had stopped working. Done all the fixes and updates suggested here and elsewhere and I am now seeing that of 7 cameras, 4 that connect directly to Arlo e.g. WiFi Connection are reporting battery fine here, whereas the 3 that connect via the Arlo Basestation initially did not update their battery levels, and since reinstalling/updating show battery level as "unknown" in HA. Previously, all were showing battery levels.

I can see mention of battery levels missing above, but its not clear if this is meant to be working again yet, any idea if its expected at this stage. not really sure what to provide to assist troubleshooting here as the logs don't seem to mention battery for anything.

All my cameras connect via a Arlo Basestation and are all reporting their battery levels without issues.

I can see the person you referenced above said the below

"Update: I was able to fix the problem by disabling and enabling the integration again. Thanks @twrecked for all your help!"

[jeanpatrick19]

🔹 Problem:
I am unable to stream live video from my Arlo VMC4030 camera in Home Assistant using the aarlo integration. Snapshots work fine, but when I try to start live streaming, nothing happens in the interface.

🔹 Environment:
Home Assistant Core: 2025.2.2
Supervisor: 2025.02.0
Operating System: 14.2
Front-end: 20250210.0
Aarlo Integration Version: 0.8.1.12

🔹 What I've Tried So Far:
✅ Snapshots work fine (camera.snapshot), and I can view images.
✅ Enabled stream: in configuration.yaml and restarted HA.
✅ Camera entity appears as "recently active" with frontend_stream_type: hls.
✅ Added the camera to Lovelace (picture-glance), but clicking does not start the stream.
✅ Tried camera.play_stream via Developer Tools, but I get a media_player required error.
✅ Modified aarlo settings in configuration.yaml, trying backend: sse and stream_timeout: 120, but no success.

🔹 Question:
How can I fix this issue and enable live streaming in Home Assistant?
Does aarlo still support live streaming for Arlo cameras?
Is there any additional configuration required to force HLS or another streaming method?
Any help is appreciated! 🚀

[twrecked]

@jeanpatrick19 we already have an open issue for this: #1034

[fightinbeavs]

Can someone dumb it down for some of us to get this fixed? I am getting the same error message everyone else is, but above aarlo.yaml is mentioned, but I dont have that folder. Can someone please dumb it down, where to put that, what to put in it? additionally any other fixes that people have found to resolve this issue that we all seemed to face after the update. thank you to anyone who is able to assist!

[Reserton]

Can someone dumb it down for some of us to get this fixed? I am getting the same error message everyone else is, but above aarlo.yaml is mentioned, but I dont have that folder. Can someone please dumb it down, where to put that, what to put in it? additionally any other fixes that people have found to resolve this issue that we all seemed to face after the update. thank you to anyone who is able to assist!

You don't need to do any of that now. Just update the Aarlo addon in HACS.

You need to be on the latest version v0.8.1.12 and that will automatically fix the issue this was raised for.

[nohimx]

I already updated Aarlo in HACS, it latest version, but it still doesn't work. Already tried to disable remove reinstall... Here is debug output.

2025-02-12 11:10:26.584 DEBUG (SyncWorker_2) [pyaarlo] backend: request-params=
{'EnvSource': 'prod',
'email': 'xxx@xxx.com',
'language': 'en',
'password': 'xxx'}
2025-02-12 11:10:26.584 DEBUG (SyncWorker_2) [pyaarlo] backend: request-headers=
{'Accept': 'application/json, text/plain, /',
'Accept-Encoding': 'gzip, deflate, br',
'Accept-Language': 'en-GB,en;q=0.9,en-US;q=0.8',
'Cache-Control': 'no-cache',
'Content-Type': 'application/json',
'Dnt': '1',
'Origin': 'https://my.arlo.com',
'Pragma': 'no-cache',
'Referer': 'https://my.arlo.com/',
'User-Agent': 'Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, '
'like Gecko) Chrome/133.0.0.0 Safari/537.36',
'X-User-Device-Automation-Name': 'QlJPV1NFUg==',
'X-User-Device-Id': '34de0fc9-497c-4b53-87f3-88c49399832b',
'X-User-Device-Type': 'BROWSER'}

Response is standard cloudflare page of blocking.

<title>Attention Required! | Cloudflare</title>\n' Sorry, you have been blocked You are unable to access ocapi-app.arlo.com

[jeanpatrick19]

Good morning guys!

Problem apparently solved, everyone! Updated to version V0.8.1.13.

First, I deleted the entire integration and all related files. Then, I updated to version 0.8.1.13, reconnected everything, and now it's working perfectly. Cameras are streaming in real-time again. I'm using Picture Glance for visualization.

`camera_view: live
type: picture-glance
title: Camera
entities:

• entity: binary_sensor.aarlo_sound_camera
• entity: binary_sensor.aarlo_motion_camera
• entity: sensor.aarlo_recent_activity_camera
• entity: switch.aarlo_all_sirens
  camera_image: camera.aarlo_camera`

The streaming is even better than before! Huge thanks for the update and for fixing the issue!
@twrecked , you’re amazing! 🎉🚀

[bslefevre]

Does v0.8.1.13 also solve the 403 - possible cloudflare issue issue?

[nohimx]

Does v0.8.1.13 also solve the 403 - possible cloudflare issue issue?

for me still same, error exist

[jeanpatrick19]

I believe you should uninstall the integration, delete all Aarlo integration files, reboot HASS, reinstall the integration, and then reconnect your account.

[jeanpatrick19]

A versão v0.8.1.13 também resolve o 403 - possible cloudflare issueproblema?

Yes, it worked for me. In fact, version 0.8.1.12 had already fixed it, but it caused the livestreaming error.

[bslefevre]

I believe you should uninstall the integration, delete all Aarlo integration files, reboot HASS, reinstall the integration, and then reconnect your account.

I've deleted the integration, restarted HASS, upgraded to v0.8.1.13, restarted HASS and installed Arlo again.
No cloudflare error any more!
Only now I've got this one:

`
Logger: homeassistant.config_entries
Source: config_entries.py:586
First occurred: 4:46:58 PM (1 occurrences)
Last logged: 4:46:58 PM

Error setting up entry Aarlo for @.nl for aarlo
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 586, in async_setup
result = await component.async_setup_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/aarlo/init.py", line 276, in async_setup_entry
await hass.config_entries.async_forward_entry_setups(entry, ARLO_PLATFORMS)
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2046, in async_forward_entry_setups
await integration.async_get_platforms(platforms)
File "/usr/src/homeassistant/homeassistant/loader.py", line 1177, in async_get_platforms
import_future.result()
File "/usr/src/homeassistant/homeassistant/loader.py", line 1177, in async_get_platforms
import_future.result()
File "/usr/src/homeassistant/homeassistant/loader.py", line 1177, in async_get_platforms
import_future.result()
[Previous line repeated 5 more times]
File "/usr/src/homeassistant/homeassistant/loader.py", line 1165, in async_get_platforms
platforms.update(self._load_platforms(platform_names))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/loader.py", line 1090, in _load_platforms
platform_name: self._load_platform(platform_name)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/loader.py", line 1264, in _load_platform
cache[full_name] = self._import_platform(platform_name)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/loader.py", line 1296, in _import_platform
return importlib.import_module(f"{self.pkg_path}.{platform_name}")
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/util/loop.py", line 200, in protected_loop_func
return func(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/importlib/init.py", line 90, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "", line 1387, in _gcd_import
File "", line 1360, in _find_and_load
File "", line 1331, in _find_and_load_unlocked
File "", line 935, in _load_unlocked
File "", line 995, in exec_module
File "", line 488, in _call_with_frames_removed
File "/config/custom_components/aarlo/alarm_control_panel.py", line 24, in
from homeassistant.components.alarm_control_panel.const import (
ImportError: cannot import name 'AlarmControlPanelState' from 'homeassistant.components.alarm_control_panel.const' (/usr/src/homeassistant/homeassistant/components/alarm_control_panel/const.py)
`

I've restarted my HASS a couple of times but apparently it still cannot import the AlarmControlPanelState

What can I do about this?

Running HASS at 2024.7.3 btw

[twrecked]

Sorry; but I think you need to upgrade to a newer HASS. AlarmControlPanelState was added sometime in October 2024.

[bslefevre]

I can do you one better!

AlarmControlPanelState has been added in 2024.11 according to this page

I'm now upgrading to 2024.12.5

It now works as expected with HASS@2024.12.5 and hass-aarlo@v0.8.1.12

[nohimx]

I have hass lates version 2025.2.2, deleted reinstalled upgraded aarlo, still cloudflare issue to login. I have a core installation on ubuntu. By some reason version aarlo showed is 0.8.1.14.

2025-02-13 10:17:52.405 INFO (SyncWorker_4) [pyaarlo] pyarlo 0.8.0.13 starting...
2025-02-13 10:17:52.405 DEBUG (SyncWorker_4) [pyaarlo] config: loaded
2025-02-13 10:17:52.413 DEBUG (SyncWorker_4) [pyaarlo] background: starting
2025-02-13 10:17:52.417 DEBUG (SyncWorker_4) [pyaarlo] backend: session file not read
2025-02-13 10:17:52.417 DEBUG (SyncWorker_4) [pyaarlo] backend: looking for user_agent linux
2025-02-13 10:17:52.417 DEBUG (SyncWorker_4) [pyaarlo] backend: oldish session, getting a new one
2025-02-13 10:17:52.417 DEBUG (SyncWorker_4) [pyaarlo] backend: CloudFlare curve set to: secp384r1
2025-02-13 10:17:52.463 DEBUG (SyncWorker_4) [pyaarlo] backend: login attempt #1
2025-02-13 10:17:55.522 DEBUG (SyncWorker_4) [pyaarlo] backend: login attempt #2
2025-02-13 10:17:58.634 DEBUG (SyncWorker_4) [pyaarlo] backend: login attempt #3
2025-02-13 10:18:01.677 ERROR (SyncWorker_4) [pyaarlo] login failed: 403 - possible cloudflare issue
2025-02-13 10:18:01.677 DEBUG (SyncWorker_4) [pyaarlo] backend: login failed, trying another ecdh_curve
2025-02-13 10:18:01.677 DEBUG (SyncWorker_4) [pyaarlo] backend: CloudFlare curve set to: prime256v1
2025-02-13 10:18:01.738 DEBUG (SyncWorker_4) [pyaarlo] backend: login attempt #1
2025-02-13 10:18:04.811 DEBUG (SyncWorker_4) [pyaarlo] backend: login attempt #2
2025-02-13 10:18:07.841 DEBUG (SyncWorker_4) [pyaarlo] backend: login attempt #3
2025-02-13 10:18:10.868 ERROR (SyncWorker_4) [pyaarlo] login failed: 403 - possible cloudflare issue
2025-02-13 10:18:10.869 DEBUG (SyncWorker_4) [pyaarlo] backend: login failed, trying another ecdh_curve
2025-02-13 10:18:10.869 DEBUG (SyncWorker_4) [pyaarlo] backend: failed to log in
2025-02-13 10:18:10.870 DEBUG (ArloMediaDownloader) [pyaarlo] media-downloader: not starting downloader
2025-02-13 10:18:10.872 ERROR (SyncWorker_4) [custom_components.aarlo] unable to connect to Arlo: attempt=4,sleep=120,error=login failed: 403 - possible cloudflare issue
2025-02-13 10:18:10.872 ERROR (SyncWorker_4) [custom_components.aarlo] unable to connect to Arlo: stopping retries, too may failures

[Thireus]

These 403 - possible cloudflare issue errors started to happen for me as well just a few days ago... all way working fine for months until now.

Reloading the integration only worked for me once (pure luck I guess), now I've had to reboot HA and the Aarlo integration fails again with this 403 😩.