Arlo component not working #17427

Nicxe · 2018-10-14T08:31:16Z

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

The text was updated successfully, but these errors were encountered:

fgorbat · 2018-10-14T18:29:55Z

I'm having the same issue, Arlo's Alarm Control Panel state became "unknown" and the platform slowed down dramatically.

Nicxe · 2018-10-14T18:41:20Z

I can’t get any response from the control panel, it’s impossible to arm or disarm the Arlo cameras

grantclem · 2018-10-15T02:09:43Z

Unfortunately Arlo is not functioning again since .80.

pschmitt · 2018-10-15T07:31:38Z

Related to tchellomello/python-arlo#92

frekel · 2018-10-15T18:52:42Z

Same here, no camera stream and a very slow front-end!

aneisch · 2018-10-15T20:22:49Z

The stream works for me, but the entirety of home Assistant seems to hang during update. I have the component disabled for now.

collse · 2018-10-15T20:48:03Z

same here - sluggish but videos can be pulled and are working ... bit worrisome that its open/untouched for this long especially as it now seems to affect the frontend as well

fgorbat · 2018-10-17T01:01:47Z

0.80.1 the problem persists.

schmittx · 2018-10-17T11:34:28Z

Arlo sensors are also affected in 0.80.1

I have an Arlo Baby and the following are NOT working (returning STATE_UNKNOWN):

battery_level
signal_strength
temperature
humidity
air_quality

Somehow, the following are still working:

captured_today
last_capture
total_cameras

matteskonto · 2018-10-17T19:02:08Z

I had issue with Arlo even on 0.79.3 and I think it is related to changes on Arlo side.

lukiffer · 2018-10-18T03:37:59Z

It appears that the underlying Netgear API has changed, so this will affect you regardless of what version of homeassistant or pyarlo you're running. I'm looking into what changed about the API and will post updates in the source repo on tchellomello/python-arlo#100

lukiffer · 2018-10-18T05:45:55Z

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.

arsaboo · 2018-10-18T06:32:08Z

@lukiffer I updated my pyarlo/__init__.py and can confirm that Arlo sensors are working after the fix. I was getting unknown for them before the fix. I will monitor them for some time and update you again. I have Arlo pro cameras and will be happy to test things with you. Let me know if you need anything.

schmittx · 2018-10-18T11:13:12Z

@lukiffer Good results for me too after updating pyarlo/__init__.py.

grantclem · 2018-10-18T11:20:21Z

I have updated the init.py and can confirm that it appears to be working just fine. Thanks

frekel · 2018-10-18T11:30:04Z

Updated the file and errors are gone. Still no images, but I think that’s something else!

collse · 2018-10-18T12:01:00Z

seems to work for me got it up and running for 10 minutes - got Pros and Baby but will keep an eye on it - they still seem to jump around a bit - but I think that happens every time its updating ...

skaker1 · 2018-10-19T12:04:17Z

Sorry for being stupid: How did you update "pyarlo/init.py"? I'm using Hassbian.

grantclem · 2018-10-19T12:49:12Z

Sorry for being stupid: How did you update "pyarlo/init.py"? I'm using Hassbian.

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

carloleocosta · 2018-10-19T16:33:39Z

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 😃

* Bump pyarlo to 0.2.2, fixes #17427 * Increase log level for refresh message to clear up logs

skaker1 · 2018-10-22T06:55:23Z

I now have installed the bump pyarlo=0.2.2:

Successfully installed certifi-2018.10.15 chardet-3.0.4 idna-2.7 pyarlo-0.2.2 requests-2.20.0 sseclient-py-1.7 urllib3-1.24

But I still got:

2018-10-22 08:42:55 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for camera.vardagsrum (<class 'homeassistant.components.camera.arlo.ArloCam'>) took 6.373 seconds. Please report platform to the developers at https://goo.gl/Nvioub
2018-10-22 08:43:02 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for camera.kok (<class 'homeassistant.components.camera.arlo.ArloCam'>) took 7.054 seconds. Please report platform to the developers at https://goo.gl/Nvioub

And the Alarm and all sensors (for Arlo) are unknown. Have I missed something?

collse · 2018-10-22T13:00:37Z

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 ...

joiglifberg · 2018-11-02T18:30:00Z

This issue is not entirely solved.
My Arlo alarm entity still get state "unknown" every 2 minute or so as you can see in the image below.
I'm using 0.81.2 with Hass.io.

collse · 2018-11-03T11:17:59Z

I believe ‘unknown’ is shown as soon as the status update starts - but you are correct the issuse isnt fully solved as the alarm panels still cause issues

michaelhenningersrb · 2018-11-25T17:36:26Z

Hi,

I have the same problem with the unknown status.

Any solutions for this?
Thanks

timdonovanuk · 2018-11-28T08:10:06Z

0.81.1 my alro constantly shows Unknown and never updates:

mbrunton77 · 2018-11-28T13:10:59Z

My arlo status goes back and forth from home and unknown.

htvekov · 2018-11-29T21:07:58Z

I experience the same intermittent unknown status as almost everyone else. For this reason I've made a copy of the sensor that filters out unknown status and leave the copysensor at last known proper state (Armed Home, Armed Away, Unarmed). Otherwise it's impossible to use the Arlo component for something usefull in Home Assistant. Hope that the Arlo component will soon be fixed...

michaelhenningersrb · 2018-11-30T08:33:48Z

@htvekov @mbrunton77 @timdonovanuk who shall we inform to reopen this issue or open another one?

BaQs · 2018-12-01T21:56:44Z

There is another issue opened that looks similar: #15177

BaQs · 2018-12-01T21:58:54Z

There is another issue opened that looks similar: 15177

I experience the same intermittent unknown status as almost everyone else. For this reason I've made a copy of the sensor that filters out unknown status and leave the copysensor at last known proper state (Armed Home, Armed Away, Unarmed). Otherwise it's impossible to use the Arlo component for something usefull in Home Assistant. Hope that the Arlo component will soon be fixed...

Could you please share your config ? Might be usefull for a lot of us 👍

htvekov · 2018-12-05T21:56:51Z

Basically I've just made a sensor that filters out the intermittent unknown status from the control panel:

 - platform: template
    sensors:
      arlomode:
        friendly_name: 'Arlo mode'
        value_template: >-
          {% if is_state("alarm_control_panel.arlo_base" , "disarmed") %}
            OFF
          {% elif is_state("alarm_control_panel.arlo_base" , "armed_home") %}
            HOME
          {% elif is_state("alarm_control_panel.arlo_base" , "armed_away") %}
            AWAY
          {% else %}
            {{ states ("sensor.arlomode") }}
          {% endif %}

But this doesn't help at all regarding the underlying problems setting mode from HA. Quite often the mode simply doesn't shift due to time out problems with the Arlo API calls. I've changes my HA settings so i only load the control panel and camera sensors. This seems to help a lot and apparently affects the ability to change mode from HA effectively (but still not allways working 100% as time out problems still occationally occur). I really hope that the Arlo component will eventually be fixed. At least I hope that focus would be making the core components such as the control panel and camera sensors 100% reliable. Fingers crossed...

teqnet · 2018-12-08T06:11:03Z

My arlo is still toggeling to unknown on version 83.3.
I get delay messages in the log:
Update of alarm_control_panel.arlo_t is taking over 10 seconds

I guess I also have to create a filter for automation...

Is this affecting the overall performance in hass?

htvekov · 2018-12-11T10:51:51Z

No, I don't experience any performance issues due to an extra sensor.

But the main problem still exist:
Unreliable Arlo control panel which after x hours suddenly can't relay changes to Arlo API.
Sometimes with heavy Async.py log errors. Sometimes without log errors ? It simply gives up and no changes to Arlo state are made when requested from HA.

Only a reboot of HA, restores the ability to change state again.
But again, will only work for x hours again then...

Can someone please share examples of their IFTTT settings, as I need to migrate this vital core thing in my HA setup from Arlo control panel to IFTTT.

Thank you in advance

joch · 2018-12-11T11:46:00Z

Can someone please share examples of their IFTTT settings, as I need to migrate this vital core thing in my HA setup from Arlo control panel to IFTTT.

I did exactly that, and it has been solid since. Some key things:

Input boolean: https://github.com/joch/home-assistant-config/blob/master/input_boolean.yaml#L61
Reset booleans when triggered: https://github.com/joch/home-assistant-config/blob/master/automation/internal/arlo.yaml
alarm automation: https://github.com/joch/home-assistant-config/blob/master/automation/home/alarm.yaml#L14

Add an IFTTT recipe like "If Arlo Detects Motion in 'camera name', then make a web request" for each camera, and point the web request to https://[yourhomeassistant]/api/services/input_boolean/turn_on?api_password=yourapipassword.

htvekov · 2018-12-11T19:23:55Z

Thanks joch.

I'll try and set IFTTT up ASAP.

Reference to my own bug issue here #19201

YoinkZed · 2019-01-25T07:22:02Z

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.

collse · 2019-01-25T13:25:17Z

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.

I think the issue is that the original maintainer doesnt have the time and others potentially dont have the skill/visibility to fix it

michaelhenningersrb · 2019-01-25T14:29:44Z

There are to options for me:

Get the skills :)
or
Get rid of the arlo stuff

frekel · 2019-01-25T14:39:02Z

I have chosen the third option: I stopped using HomeAssistant... 😢

michaelhenningersrb · 2019-01-25T14:47:02Z

I have chosen the third option: I stopped using HomeAssistant... 😢

Not really? Only because of the cameras? What is you alternative homeautomation hub?

YoinkZed · 2019-01-25T14:50:13Z

openhab?

What other Surveillance systems do you have?
That seems to work?

Bjsulla · 2019-01-25T15:07:01Z

One option is to remove the Arlo Control Panel from Home Assistant and to use Node-RED to arm/disarm/change mode. This actually works great with the Node-red-contrib-home-assistant-websocket that is available.

Found this that describes how to control Arlo from Node-RED
https://siege36.github.io/2rs2ns/setting-custom-arlo-mode-with-node-red/

arsaboo · 2019-01-25T15:42:31Z

Use the IFTTT Alarm component for Arlo. Arlo cameras work fine with HA.

Given that there is no official API for Arlo, the support was always going to be iffy

YoinkZed · 2019-01-25T16:49:12Z

I tried searching for home Assistant on the IFTTT page but I wasn't able to locate it.

Might just be me :/

zemerick1 · 2019-01-26T19:01:54Z

Weird that this is closed. I still cannot change mode with this component. I believe pyArlo is still using the old API. See issue here: 108 I find this alternative module is a lot better maintained. For now I'm going to have to use that module to Arm/Disarm. Until pyArlo resolves this issue.

collse · 2019-01-28T12:51:47Z

@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 ...

zemerick1 · 2019-02-06T03:10:18Z

Is this on the radar to be fixed ?

collse · 2019-02-06T12:42:16Z

@zemerick1 I dont think it is - seems like its being a non open API integration this would to be expected ... as I have seen this twice now that I chose to purchase something based on the supported components list on the HA website which then lost its capabilities I am thinking of raising it on the forums ...

Hucksleyy91 · 2019-03-11T13:33:06Z

Im loged in as root and when I run cd /srv/ ect I get “no such file or directory”
I’m running hassio on a raspberry pi 3 by itself

I’m having no issues with the arm/disarm it works on both HomeKit buttons also

Make sure your not loged into the same account on another device as It only allows 1 active login per account

My camera is not working just shows as idle and grey also

Also all my sensors are working perfectly

frekel mentioned this issue Oct 15, 2018

Updating Arlo Hub component causes HASS to hang #17490

Closed

lukiffer mentioned this issue Oct 18, 2018

Remove extraneous params from subsequent query requests tchellomello/python-arlo#101

Merged

lukiffer added a commit to lukiffer/home-assistant that referenced this issue Oct 21, 2018

Bump pyarlo to 0.2.2, fixes home-assistant#17427

4ae8b25

lukiffer mentioned this issue Oct 21, 2018

Bump pyarlo==0.2.2 #17673

Merged

5 tasks

ghost added the in progress label Oct 21, 2018

Danielhiversen closed this as completed in #17673 Oct 21, 2018

ghost removed the in progress label Oct 21, 2018

Danielhiversen pushed a commit that referenced this issue Oct 21, 2018

Bump pyarlo==0.2.2 (#17673)

95371fe

* Bump pyarlo to 0.2.2, fixes #17427 * Increase log level for refresh message to clear up logs

Nicxe mentioned this issue Oct 28, 2018

Arlo alarm_control_panel entity does not show up #17893

Closed

Arlo component not working #17427

Arlo component not working #17427

Comments

Nicxe commented Oct 14, 2018 • edited

fgorbat commented Oct 14, 2018

Nicxe commented Oct 14, 2018

grantclem commented Oct 15, 2018

pschmitt commented Oct 15, 2018

frekel commented Oct 15, 2018

aneisch commented Oct 15, 2018

collse commented Oct 15, 2018 • edited

fgorbat commented Oct 17, 2018

schmittx commented Oct 17, 2018 • edited

matteskonto commented Oct 17, 2018

lukiffer commented Oct 18, 2018

lukiffer commented Oct 18, 2018

arsaboo commented Oct 18, 2018 • edited

schmittx commented Oct 18, 2018

grantclem commented Oct 18, 2018

frekel commented Oct 18, 2018

collse commented Oct 18, 2018 • edited

skaker1 commented Oct 19, 2018

grantclem commented Oct 19, 2018

carloleocosta commented Oct 19, 2018

skaker1 commented Oct 22, 2018

collse commented Oct 22, 2018

joiglifberg commented Nov 2, 2018

collse commented Nov 3, 2018

michaelhenningersrb commented Nov 25, 2018

timdonovanuk commented Nov 28, 2018

mbrunton77 commented Nov 28, 2018

htvekov commented Nov 29, 2018

michaelhenningersrb commented Nov 30, 2018

BaQs commented Dec 1, 2018 • edited

BaQs commented Dec 1, 2018

htvekov commented Dec 5, 2018 • edited by MartinHjelmare

teqnet commented Dec 8, 2018

htvekov commented Dec 11, 2018

joch commented Dec 11, 2018

htvekov commented Dec 11, 2018

YoinkZed commented Jan 25, 2019

collse commented Jan 25, 2019

michaelhenningersrb commented Jan 25, 2019

frekel commented Jan 25, 2019

michaelhenningersrb commented Jan 25, 2019

YoinkZed commented Jan 25, 2019

Bjsulla commented Jan 25, 2019

arsaboo commented Jan 25, 2019

YoinkZed commented Jan 25, 2019

zemerick1 commented Jan 26, 2019

collse commented Jan 28, 2019 • edited

zemerick1 commented Feb 6, 2019

collse commented Feb 6, 2019

Hucksleyy91 commented Mar 11, 2019

Nicxe commented Oct 14, 2018 •

edited

collse commented Oct 15, 2018 •

edited

schmittx commented Oct 17, 2018 •

edited

arsaboo commented Oct 18, 2018 •

edited

collse commented Oct 18, 2018 •

edited

BaQs commented Dec 1, 2018 •

edited

htvekov commented Dec 5, 2018 •

edited by MartinHjelmare

collse commented Jan 28, 2019 •

edited