arlo integration is broken

ssmall commented 4 years ago

The problem

arlo integration fails to initialize with message

ERROR (MainThread) [homeassistant.setup] Setup failed for arlo: Integration failed to initialize.

Environment

Home Assistant Core release with the issue: 0.114.1
Last working Home Assistant Core release (if known): N/A
Operating environment (OS/Container/Supervised/Core): Container
Integration causing this issue: arlo
Link to integration documentation on our website: https://www.home-assistant.io/integrations/arlo/

Problem-relevant `configuration.yaml`

arlo: !include arlo.yaml

arlo.yaml

 username: !secret arlo_username
 password: !secret arlo_password

secrets.yaml

arlo_username: REDACTED
arlo_password: REDACTED

Traceback/Error logs

> grep arlo home-assistant.log
2020-08-31 18:29:28 INFO (MainThread) [homeassistant.bootstrap] Setting up stage 2: {'noonlight', 'met', 'sun', 'mobile_app', 'input_datetime', 'hue', 'ffmpeg', 'default_config', 'map', 'input_text', 'alarm_control_panel', 'notify', 'input_number', 'arlo', 'scene', 'system_health', 'input_boolean', 'zeroconf', 'weather', 'light', 'automation', 'zha', 'updater', 'tts', 'ssdp', 'input_select', 'history', 'zone', 'logbook', 'zwave', 'group', 'script'}
2020-08-31 18:29:29 DEBUG (MainThread) [homeassistant.setup] Dependency arlo will wait for ['ffmpeg']
2020-08-31 18:29:34 INFO (MainThread) [homeassistant.setup] Setting up arlo
2020-08-31 18:29:34 DEBUG (SyncWorker_6) [pyarlo] Creating Arlo session
2020-08-31 18:29:34 DEBUG (SyncWorker_6) [pyarlo] Params: {'email': 'REDACTED', 'password': 'REDACTED'}
2020-08-31 18:29:34 DEBUG (SyncWorker_6) [pyarlo] Headers: {'Content-Type': 'application/json', 'Authorization': None}
2020-08-31 18:29:34 DEBUG (SyncWorker_6) [pyarlo] Querying https://arlo.netgear.com/hmsweb/login/v2 on attempt: 0/3
2020-08-31 18:29:34 DEBUG (SyncWorker_6) [pyarlo] Params: {'email': 'REDACTED', 'password': 'REDACTED'}
2020-08-31 18:29:34 DEBUG (SyncWorker_6) [pyarlo] Headers: {'Content-Type': 'application/json', 'Authorization': None}
2020-08-31 18:29:34 DEBUG (SyncWorker_6) [pyarlo] Querying https://arlo.netgear.com/hmsweb/login/v2 on attempt: 1/3
2020-08-31 18:29:34 DEBUG (SyncWorker_6) [pyarlo] Params: {'email': 'REDACTED', 'password': 'REDACTED'}
2020-08-31 18:29:34 DEBUG (SyncWorker_6) [pyarlo] Headers: {'Content-Type': 'application/json', 'Authorization': None}
2020-08-31 18:29:34 DEBUG (SyncWorker_6) [pyarlo] Querying https://arlo.netgear.com/hmsweb/login/v2 on attempt: 2/3
2020-08-31 18:29:35 DEBUG (SyncWorker_6) [pyarlo] Params: {'email': 'REDACTED', 'password': 'REDACTED'}
2020-08-31 18:29:35 DEBUG (SyncWorker_6) [pyarlo] Headers: {'Content-Type': 'application/json', 'Authorization': None}
2020-08-31 18:29:35 DEBUG (SyncWorker_6) [pyarlo] Querying https://arlo.netgear.com/hmsweb/login/v2 on attempt: 3/3
2020-08-31 18:29:35 INFO (MainThread) [homeassistant.setup] Setup of domain arlo took 0.6 seconds
2020-08-31 18:29:35 ERROR (MainThread) [homeassistant.setup] Setup failed for arlo: Integration failed to initialize.

Additional information

I have tested the exact same configuration using https://github.com/twrecked/hass-aarlo instead (by renaming config references from arlo to aarlo) and the integration initializes without issue. My Arlo account does not have 2FA enabled.

springstan commented 4 years ago

Please fill out the issue template, you can find it by clicking on New Issue and then selecting Report a bug with Home Assistant. Copy and paste the provided template into this already created issue, click preview to take a look at the empty template and then fill out as much as you can. Any additional information can be helpful!

Thanks for understanding :)

tylerszabo commented 4 years ago

@springstan can we just use #33095?

frenck commented 4 years ago

No, we cannot, that issue has been closed stale after there was no confirmation the issue was still present. A new issue, like this one, can be created. Although it does need to follow the issue template as requested by @springstan.

Thanks 👍

ssmall commented 4 years ago

@springstan @frenck PTAL, I have updated the issue description with the information you requested. It would be great to figure out a fix for this since it appears it has been broken since at least March of this year.

frenck commented 4 years ago

Glad to see that the maintainers of HomeAssistant are committed to bureaucracy over fixing broken functionality.

Not sure if that was called for. I think it was a fairly nicely asked for the extra data (that the template takes care of) just to prevent missing info over and over again. If you want to call that bureaucracy, sure... I would like to call it efficiency in a large project that currently deals with a lot of things.

The information you're requesting is also present in https://github.com/home-assistant/core/issues/33818, which you resolved as a duplicated of the now-closed issue that you're refusing to re-open.

Please note that that issue was automatically closed because nobody cared to confirm the issue was still present.

PTAL, I have updated the issue description with the information you requested. It would be great to figure out a fix for this since it appears it has been broken since at least March of this year.

Nevertheless, thanks for updating the description. I'm going to categorize the issue now. 👍

probot-home-assistant[bot] commented 4 years ago

arlo documentation arlo source _{^{(message by IssueLinks)}}

fermulator commented 4 years ago

(this is in fact a dup of #33095)

github-actions[bot] commented 4 years ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

MakkaKaplar commented 4 years ago

I have no new information, commenting to confirm the problem still exists.

seanmurphy1661 commented 4 years ago

New to this issue and Home Assistant. My Arlo integration is not working as well. Is there anything that I can do to help resolve this?

TakesTheBiscuit commented 3 years ago

Hi - have you guys tried logging in at https://my.arlo.com/ ? if so does it present you with MFA?

TakesTheBiscuit commented 3 years ago

Arlo integration will need to be changed to use new repo, i suspect: https://github.com/twrecked/pyaarlo

Who is doing this work? Or should i take a look?

TakesTheBiscuit commented 3 years ago

@tchellomello has merged https://github.com/tchellomello/python-arlo/pull/115 and pypi is updated : https://libraries.io/pypi/pyarlo 0.2.4 is now up - it would be good to test a new version of the HA arlo component with : "requirements": ["pyarlo==0.2.4"],

I am afraid i do not have the current setup in order to test/dev against HA - is anyone else able to try? :)

TakesTheBiscuit commented 3 years ago

https://github.com/home-assistant/core/pull/44034

MSJocke commented 3 years ago

I cant see if this is mentioned or not, but I still have this issue with my Arlo's I get the following error - I have only the "arlo: username/password component lines in yaml, not even the sensors

Error during setup of component arlo Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/setup.py", line 213, in _async_setup_component result = await task File "/usr/local/lib/python3.8/concurrent/futures/thread.py", line 57, in run result = self.fn(*self.args, **self.kwargs) File "/usr/src/homeassistant/homeassistant/components/arlo/init.py", line 57, in setup arlo_base_station = next((station for station in arlo.base_stations), None) File "/usr/local/lib/python3.8/site-packages/pyarlo/init.py", line 172, in base_stations return self.devices.get('base_station') File "/usr/local/lib/python3.8/site-packages/pyarlo/init.py", line 187, in devices for device in data.get('data'): AttributeError: 'NoneType' object has no attribute 'get'

actuallymentor commented 3 years ago

44034

Hmm I see this is merged but the issue is still present on my system. Does the MFA system require extra setup?

actuallymentor commented 3 years ago

When using the Arlo plugin I still get an init error:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/setup.py", line 213, in _async_setup_component
    result = await task
  File "/usr/local/lib/python3.8/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/src/homeassistant/homeassistant/components/arlo/__init__.py", line 57, in setup
    arlo_base_station = next((station for station in arlo.base_stations), None)
  File "/usr/local/lib/python3.8/site-packages/pyarlo/__init__.py", line 172, in base_stations
    return self.devices.get('base_station')
  File "/usr/local/lib/python3.8/site-packages/pyarlo/__init__.py", line 187, in devices
    for device in data.get('data'):
AttributeError: 'NoneType' object has no attribute 'get'

A lot of community members seem to have switched to twrecked/hass-aarlo since arlo made 2FA mandatory.

Should I conclude this HA module is no longer maintained and switch to that one?

tchellomello commented 3 years ago

@actuallymentor I think we should officially migrate to hass-aarlo. I've not being able to maintain it anymore. If anyone wants to maintain it I can grant the privileges or maybe we should migrate to twrecked/hass-aarlo. @twrecked, have you considered replacing officially the module? If you want, I can help to make your implementation the default one.

actuallymentor commented 3 years ago

@tchellomello thanks for your quick response, that's very good to know.

@twrecked let me know if I can do anything to support!

twrecked commented 3 years ago

@tchellomello I've thought about replacing the official module, and I've made code changes that will make that easier in the future, but there is still work that needs to be done, these are 2 I can think of:

add config flow support
remove pyaarlo from aarlo (this one is ongoing)

One remaining issue is Arlo themselves, there isn't an official interface and they have a habit of just changing the back end and breaking installs. For example, once they just rehashed the whole authentication mechanism and new logins failed and last month they turned on CloudFlare's anti-bot pages. When that happens I like to get changes out in a day and I'm not sure how quick I could manage that as an official module.

tchellomello commented 3 years ago

@twrecked I hear you since they don't offer an API, it's not much fun to see all your work being deprecated in the blink of an eye.

Please you have my total support to replace the official module, as I don't own any Arlo devices anymore, it's close to impossible to maintain a good library especially when we are in dark.

Thanks for your hard work on it!

github-actions[bot] commented 3 years ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

actuallymentor commented 3 years ago

@tchellomello I've thought about replacing the official module, and I've made code changes that will make that easier in the future, but there is still work that needs to be done, these are 2 I can think of:

add config flow support

remove pyaarlo from aarlo (this one is ongoing)

One remaining issue is Arlo themselves, there isn't an official interface and they have a habit of just changing the back end and breaking installs. For example, once they just rehashed the whole authentication mechanism and new logins failed and last month they turned on CloudFlare's anti-bot pages. When that happens I like to get changes out in a day and I'm not sure how quick I could manage that as an official module.

A module that works most of the time beats a module that works none of the time :)

shupershuff commented 3 years ago

So is there a way to get this integration working?

tchellomello commented 3 years ago

Yes please let's deprecate pyarlo and replace it by aarlo. The pyarlo repository has been deprecated.

Thayios commented 3 years ago

Is there anything we can do to get the replacement going? 2FA is now required on Arlo so the official integration is broken as far as I can tell.

awilliams84 commented 3 years ago

I was trying to setup aarlo today and am getting "2fa startup failed" has this been resolved?

Thayios commented 3 years ago

No, it has not unfortunately.

awilliams84 commented 3 years ago

I just setup aarlo, so all good now!

github-actions[bot] commented 2 years ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

awilliams84 commented 2 years ago

Resolved using aarlo instead

thecode commented 2 years ago

This integration is removed from core on next release, closing

home-assistant / core