-
Notifications
You must be signed in to change notification settings - Fork 79
Description
I previously had a working version of aarlo, but it broke earlier this year.
I had been trying to get it to work, but decided to start again from scratch..
I removed the HACS aarlo package, renamed aarlo.yaml and deleted .aarlo from the config folder.
I then restarted the Homeassistant server, added the HACS integration back and tried to setup from scratch.
Following the advice in this group, I created a brand new gmail account, and invited it to my Arlo account. I created an app password for my gmail account and tested that everything worked.
So I can login to the gmail account and I can login to Arlo with the new account. But when aarlo tries to configure the compnent I get this error.
2025-06-22 18:54:31.849 INFO (SyncWorker_35) [pyaarlo] pyarlo 0.8.0.17 starting...
2025-06-22 18:56:11.843 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry Aarlo for ******@gmail.com for aarlo
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 749, in __async_setup_with_context
result = await component.async_setup_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/aarlo/init.py", line 247, in async_setup_entry
arlo = await hass.async_add_executor_job(login, hass, domain_config)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
asyncio.exceptions.CancelledError
I was getting 2025-06-21 19:29:16.714 ERROR (SyncWorker_23) [custom_components.aarlo] unable to connect to Arlo: attempt=4,sleep=120,error=login failed: 429 - possible cloudflare issue but this new error has replaced it.
It looks like 2FA codes re being sent to my gmail account now, so I dont't know what is going on.
My arlo.yaml file:
aarlo:
backend: sse
user_agent: random - hashed out
All help gratefully received
Paul