Arlo component not working

Nicxe commented 6 years ago

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

fgorbat commented 6 years ago

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

Nicxe commented 6 years ago

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

grantclem commented 6 years ago

Unfortunately Arlo is not functioning again since .80.

pschmitt commented 6 years ago

frekel commented 6 years ago

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

aneisch commented 6 years ago

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

collse commented 6 years ago

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 commented 6 years ago

0.80.1 the problem persists.

schmittx commented 6 years ago

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 commented 6 years ago

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

lukiffer commented 6 years ago

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 https://github.com/tchellomello/python-arlo/issues/100

lukiffer commented 6 years ago

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 commented 6 years ago

@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 commented 6 years ago

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

grantclem commented 6 years ago

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

frekel commented 6 years ago

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

collse commented 6 years ago

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 commented 6 years ago

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

grantclem commented 6 years ago

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

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

carloleocosta commented 6 years ago

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 😃

skaker1 commented 6 years ago

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 commented 6 years ago

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 commented 6 years ago

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 commented 6 years ago

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 commented 5 years ago

Hi,

I have the same problem with the unknown status.

Any solutions for this? Thanks

timdonovanuk commented 5 years ago

0.81.1 my alro constantly shows Unknown and never updates:

mbrunton77 commented 5 years ago

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

htvekov commented 5 years ago

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 commented 5 years ago

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

BaQs commented 5 years ago

There is another issue opened that looks similar: #15177

BaQs commented 5 years ago

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 commented 5 years ago

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 commented 5 years ago

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 commented 5 years ago

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 commented 5 years ago

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 commented 5 years ago

Thanks joch.

I'll try and set IFTTT up ASAP.

Reference to my own bug issue here #19201

YoinkZed commented 5 years ago

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 commented 5 years ago

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 commented 5 years ago

There are to options for me:

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

frekel commented 5 years ago

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

michaelhenningersrb commented 5 years ago

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

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

YoinkZed commented 5 years ago

openhab?

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

Bjsulla commented 5 years ago

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 commented 5 years ago

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 commented 5 years ago

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

Might just be me :/

zemerick1 commented 5 years ago

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 commented 5 years ago

@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 commented 5 years ago

Is this on the radar to be fixed ?

collse commented 5 years ago

@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 commented 5 years ago

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

home-assistant / core

Arlo component not working #17427