core: Arlo component not working

Home Assistant release with the issue: 0.80.0

Last working Home Assistant release (if known): 0.79.3

Operating environment (Hass.io/Docker/Windows/etc.): Hass.io

Component/platform: Arlo

Description of problem: Arlo component work, not possible to arm or disarm. alarm_control_panel.arlo is unknown

When I put homeassistant.components.arlo: debug I get only this in the logg. Nothing els in any log regarding Arlo

2018-10-14 10:18:32 INFO (SyncWorker_10) [homeassistant.components.arlo] Updating Arlo Hub component
2018-10-14 10:19:33 INFO (SyncWorker_15) [homeassistant.components.arlo] Updating Arlo Hub component
2018-10-14 10:20:34 INFO (SyncWorker_0) [homeassistant.components.arlo] Updating Arlo Hub component
2018-10-14 10:21:35 INFO (SyncWorker_12) [homeassistant.components.arlo] Updating Arlo Hub component
2018-10-14 10:22:36 INFO (SyncWorker_0) [homeassistant.components.arlo] Updating Arlo Hub component
2018-10-14 10:23:37 INFO (SyncWorker_16) [homeassistant.components.arlo] Updating Arlo Hub component
2018-10-14 10:24:38 INFO (SyncWorker_1) [homeassistant.components.arlo] Updating Arlo Hub component
2018-10-14 10:25:39 INFO (SyncWorker_14) [homeassistant.components.arlo] Updating Arlo Hub component

About this issue

Original URL
State: closed
Created 6 years ago
Reactions: 3
Comments: 50 (12 by maintainers)

Commits related to this issue

Bump pyarlo to 0.2.2, fixes #17427 — committed to lukiffer/home-assistant by lukiffer 6 years ago
Bump pyarlo==0.2.2 (#17673) * Bump pyarlo to 0.2.2, fixes #17427 * Increase log level for refresh message to clear up logs — committed to home-assistant/core by lukiffer 6 years ago

Most upvoted comments

Wanted to close the loop as I know this issue is affecting quite a few folks – the root cause was a change in model validation in the Arlo API. This was causing the server-side-event stream to close and subsequent SyncWorker threads to hang. Eventually this would saturate the thread pool and cause Home Assistant (including the websockets handlers) to slow down significantly.

The PR is referenced on the above-linked issue. If you’d like to help test with your Arlo devices (I personally only have the Arlo Baby camera), you can grab the pyarlo/__init__.py and replace it in your site-packages/pyarlo folder in your Home Assistant instance. If you run into any issues please comment on the above-linked issue.

I’ll continue to update this issue as we progress towards pushing to PyPi.

lukiffer on Oct 18, 2018

@arsaboo they dont - I did add another camera the other day and its not being resolved/integrated into HASS - I assume due to the underlying issues - so for me Arlo is not working - the old ones just keep working but the component is defunct for sure

EDIT: well, seemed to be a permissions issue why the other cam didnt show up - it is now but the sensors and alarm panel issue still exists …

collse on Jan 28, 2019

Still no plans of fixing this or should we just go with IFTTT? The Control panel is spamming the log with unknown, disarm and so on every single, maybe every two minute.

YoinkZed on Jan 25, 2019

There is another issue opened that looks similar: #15177

BaQs on Dec 1, 2018

maybe the update was incorrect?

I did:

cd /srv/homeassistant/lib/python3.6/site-packages/pyarlo

wget https://raw.githubusercontent.com/tchellomello/python-arlo/8c4cebcd1a9c35b36d894e3b63519a521abe64b5/pyarlo/__init__.py

restart of hass …

collse on Oct 22, 2018

Sorry for being stupid: How did you update “pyarlo/init.py”? I’m using Hassbian.

srv/homeassistant/lib64/python3.6/site-packages/pyarlo

Same embarassimg question: where find pyarlo/… in Hassos? Thanks a lot 😃

carloleocosta on Oct 19, 2018