arlo integration fails to initialize in 0.107.2

[NotSteveAtGithub]

The problem

I have been using the arlo integration for my Arlo hub and Arlo2 cameras successfully for a number of months now. However, starting in 0.107.2, startup reports that the integration failed to initialize and that it is unable to set up the arlo.sensor and arlo.camera components.

Environment

arch	aarch64
dev	false
docker	true
hassio	true
os_name	Linux
os_version	4.19.106-v8
python_version	3.7.6
timezone	America/Chicago
version	0.107.3
virtualenv	false

• Home Assistant release with the issue: 0.107.2
• Last working Home Assistant release (if known): 0.107.1
• Operating environment (Hass.io/Docker/Windows/etc.): Hass.io
• Integration causing this issue: arlo
• Link to integration documentation on our website: https://www.home-assistant.io/integrations/arlo/

Problem-relevant configuration.yaml

arlo: 
  username: !secret arlo_username 
  password: !secret arlo_password

camera: 
  - platform: arlo
    ffmpeg_arguments: '-pred 1 -q:v 2'

sensor:
  - platform: arlo
    monitored_conditions:
      - captured_today
      - last_capture
      - total_cameras
      - battery_level
      - signal_strength

Traceback/Error logs

2020-03-21 08:22:06 ERROR (MainThread) [homeassistant.setup] Setup failed for arlo: Integration failed to initialize.
2020-03-21 08:22:10 ERROR (MainThread) [homeassistant.setup] Unable to prepare setup for platform arlo.sensor: Unable to set up component.
2020-03-21 08:22:14 ERROR (MainThread) [homeassistant.setup] Unable to prepare setup for platform arlo.camera: Unable to set up component.

Additional information

[jpreiditsch]

I see this in 107.4 as well.
From the home assistant log file it seems to try to authenticate 3 times then fails. Maybe arlo changed the response format slightly. I did authenticate using postman to the arlo api

[ocalvo]

I am also seeing this as well, perhaps is because Arlo requires Two Factor Authentication?

[lizeroy]

I am now seeing the same error as well, MFA would make sense. Is there some sort of work around?

[NotSteveAtGithub]

The account I use for home assistant has 2FA turned off, and I have verified that I can log into the Arlo website with that account. I'm guessing that @jpreiditsch 's theory about arlo possibly changing the response format could be the culprit, but sadly I'm not set up to debug this.

[lizeroy]

Same here the account I am using has MFA turned off.

[lillfredrik]

+1 hopefully Arlo will run with API keys after they force us on MFA at the end of the year, otherwise IFTT or Homekit maybe is the alternative?

[wanti00]

same for me. now version 107.5 and still problem continues

[jurgenweber]

yeah, I just got this when upgrade from 0.107.1 to 0.107.5

2020-03-23 12:31:23 ERROR (MainThread) [homeassistant.setup] Setup failed for arlo: Integration failed to initialize.
2020-03-23 12:31:24 ERROR (MainThread) [homeassistant.setup] Unable to prepare setup for platform arlo.sensor: Unable to set up component.

[jurgenweber]

looks like it has been reported in the project also; tchellomello/python-arlo#114

[jurgenweber]

there is also a new integration in the works; https://github.com/twrecked/hass-aarlo

[Quellweg22]

same for me. now version 107.5 and still problem continues

[LaskaBozzolo]

Same problem here

[madhatter007]

Same here. Has anyone tried to restore to a previous version to see if problem clears?

[wanti00]

i didnt try it but 107.7 and still continue to fail

[amoyzc]

Any plan for fixing this?

[jurgenweber]

yea, so py-arlo isn't really maintained, so its a problem. My recommendation is to move to the new integration that has an active community. https://github.com/twrecked/hass-aarlo

[madhatter007]

Being non-technical, I followed the below getting setup. So the above link to github usurps this?

https://www.home-assistant.io/integrations/arlo/

[ocalvo]

There is a PR with the fix but the mainterner is unresponsive.
What should you do in those cases?

[ocalvo]

It seems someone needs to request a name transfer for pyarlo by filing a new issue here

[madhatter007]

FYI got mine fixed following this:
https://github.com/twrecked/hass-aarlo/
Key is to first install HACS if don't have it, then find/install aarlo.
Then just change all refs of 'arlo' to 'aarlo' in your configuration.

[rv-kip]

+1 on https://github.com/twrecked/hass-aarlo/. I used

Copy the aarlo directory into your /config/custom_components directory.

And changed arlo --> aarlo in my configs and it seems to be working fine.

[stale]

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 now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[ReX1983]

Is there an official resolution for this integration?

[fermulator]

bah please re-open; (stale bot is annoying)
we need to either:

1. kill old integration and replace w/ new
2. fix and push PR into pyarlo and pull in updates

[tylerszabo]

I think this issue should be reopened or it'll be doomed to be duped. See #39472

[fermulator]

@frenck I understand that this was closed as stale, but the community has clearly shown that the issue is still present. IMO it is more important to retain this core ticket (which has all the duplications to it), rather than the fact it got closed due to stale bot and re-opened? The context, history, and age of an issue is important too.

AND, we have a PR in the upstream package that resolves the issue (just pending acceptance)

[fermulator]

@dshokouhi are you able to re-open?

[fklasen]

Won't this and any other integration fail completely when they move to mandatory two factor authentication in 5 days?

[danielgoepp]

Subscribing to this thread. Anyone have any updates on support for MFA with Arlo?

[hoopermathew80]

I am having the same issue, waiting with anticipation to see what those who are much more skilled than I am can come up with. Hopefully a relatively user friendly solution.

[MakkaKaplar]

Please comment on the Open issue #39472 instead!