Core: Arlo: Connection pool is full, discarding connection: arlo.netgear.com / Takes long time to start/update and total_cameras do not work

[Nicxe]

Make sure you are running the latest version of Home Assistant before reporting an issue.

You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:

**Home Assistant release (hass --version): 0.58

**Python release (python3 --version): Python 3.5.3

**Component/platform: Arlo

I get error Connection pool is full, discarding connection: arlo.netgear.com from Arlo component.

Every 5 to 10 minute I get this warning

Update of alarm_control_panel.arlo is taking over 10 seconds
Update of camera.vardagsrummet is taking over 10 seconds
Update of camera.baksidan is taking over 10 seconds
Update of sensor.signal_strength_vardagsrummet is taking over 10 seconds
Update of sensor.battery_level_vardagsrummet is taking over 10 seconds
Update of sensor.signal_strength_baksidan is taking over 10 seconds
Update of sensor.battery_level_baksidan is taking over 10 seconds

The sensor total_cameras states unknown

[Nicxe]

And I have the same problem as in 0.57 that I can't arm any mode on arlo if I have the sensor evadible. If I only have Arlo control panel it works great.

[djmcp]

Same here - updated to 0.58.1 and still seeing noneType on startup and devices taking over 10 seconds

NoneType

Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/homeassistant/helpers/entity_component.py", line 217, in async_add_entity
    yield from entity.async_device_update(warning=False)
  File "/usr/lib/python3.6/site-packages/homeassistant/helpers/entity.py", line 306, in async_device_update
    yield from self.hass.async_add_job(self.update)
  File "/usr/lib/python3.6/asyncio/futures.py", line 331, in __iter__
    yield self  # This tells Task to wait for completion.
  File "/usr/lib/python3.6/asyncio/tasks.py", line 244, in _wakeup
    future.result()
  File "/usr/lib/python3.6/asyncio/futures.py", line 244, in result
    raise self._exception
  File "/usr/lib/python3.6/concurrent/futures/thread.py", line 55, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/lib/python3.6/site-packages/homeassistant/components/camera/arlo.py", line 169, in update
    self._camera.update()
  File "/config/deps/lib/python3.6/site-packages/pyarlo/camera.py", line 286, in update
    self.base_station.update()
AttributeError: 'NoneType' object has no attribute 'update'

Updates taking over 10 seconds

Update of camera.back_deck is taking over 10 seconds
Update of camera.front_porch is taking over 10 seconds
Setup of alarm_control_panel is taking over 10 seconds.

[arsaboo]

I am also seeing lot of those warnings.

Update of sensor.battery_level_arlolivingroom is taking over 10 seconds
Update of sensor.battery_level_arlolivingroom is taking over 10 seconds
Update of camera.arlolivingroom is taking over 10 seconds

[djmcp]

Any word if someone is actively investigating this?

[tlyakhov]

Also experiencing this. Tried all sorts of config changes, same thing.

[karlkar]

Hello.
The fix is simple, but needs to be in a library pyarlo. I did it in my commit:
https://github.com/karlkar/python-arlo/commit/feaca2e9b14678baf586343c5adb1e6b13c12224
There's also one more problem with the base_stations that can be fixed like here:
https://github.com/karlkar/home-assistant/commit/9aa41c2ecea40ef828f816cbaac4417edc0ed080

With this two fixes Arlo Q camera is detected, displays still picture and plays last video.
If anyone could tell me how to properly apply this changes to home assistant I could do it.
I have never before updated the library dependencies, so help with that would be needed. Should I create merge request to the python-arlo repository or give my fork address as home assistant's requirement?

[MartinHjelmare]

First create a PR to python-arlo github. When that is merged and pyarlo has released a new version to pypi, create a PR to home assistant with the requirements updated.

[Nicxe]

@karlkar So If I do this changes to this files it would work better?

[karlkar]

Much better. Now Arlo Q setup fails because of exception.

I've already created a pull request to pyarlo repo, so we need to wait for acceptance.

[Nicxe]

Ok, I tried to change the files but the got a Arlo error in HASS. Maby I did something wrong...

Good with the PR, hope they accept it soon :-)

[karlkar]

PR is accepted. Should I wait for a release now?
https://github.com/tchellomello/python-arlo/commit/0e1dddc1907b7aa5992a8b4108153efa58fe0a71

[tchellomello]

@karlkar I'll publish a new pyarlo package tomorrow including your patch so then you can submit your fix to HA. I will let you know once this is ready to go.

[tchellomello]

@karlkar pyarlo 0.1.2 has been published and it's now available at PyPi. Thanks!

[sacha81]

I'm now on 061.1 with pyarlo 0.1.2 but my arlo is still not working in HomeAssistant.

[karlkar]

@sacha81
If you're having Arlo Q, you also need to have https://github.com/home-assistant/home-assistant/pull/11748

[Nicxe]

The component is more stable now but still get a lot of error regarding long time, I get this every 3-4 minutes.

Updating arlo alarm_control_panel took longer than the scheduled update interval 0:00:30
Update of camera.vardagsrummet is taking over 10 seconds
Update of camera.baksidan is taking over 10 seconds
Update of alarm_control_panel.arlo is taking over 10 seconds