Core: Arlo errors occurring after 0.74.0b0 update

[grantclem]

2018-07-16 17:43:45 ERROR (MainThread) [homeassistant.core] Error doing job: Future exception was never retrieved
Traceback (most recent call last):
  File "/usr/lib/python3.6/concurrent/futures/thread.py", line 56, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/arlo.py", line 84, in hub_refresh
    update_base_station=True)
  File "/srv/homeassistant/lib/python3.6/site-packages/pyarlo/__init__.py", line 270, in update
    base.update()
  File "/srv/homeassistant/lib/python3.6/site-packages/pyarlo/base_station.py", line 687, in update
    self.get_ambient_sensor_data()
  File "/srv/homeassistant/lib/python3.6/site-packages/pyarlo/base_station.py", line 481, in get_ambient_sensor_data
    properties = history_event.get('properties')
AttributeError: 'NoneType' object has no attribute 'get'

[grantclem]

Change #15074? Add additional sensors for Arlo Baby camera (@lukiffer - #15074) (sensor.arlo docs).

Don't have a Baby Arlo device (just Arlo Pro). No Ambient Sensor for Pro devices.

[lukiffer]

I'm looking into it. Looks to be a relatively easy fix. What's the appropriate way to get the fix merged (should the PR go to dev or to rc or somewhere else)?

[lukiffer]

The fix for this was in the underlying library. It's been addressed - waiting for a version bump and I'll send in a PR when it's pushed to pypi.

[tchellomello]

@lukiffer pyArlo 0.2.0 pushed to PyPi. Thanks for for contribution :+1:

[lukiffer]

@grantclem sorry for the inconvenience and thanks for reporting the issue. It was an oversight in testing on my part -- each dev of pyarlo seems to have some subset of devices, but not all. @tchellomello has put together a support matrix of which contributors have which devices so we can get a better handle on testing.

[grantclem]

Thanks for the quick resolution - glad we got it early

On 17 Jul 2018, at 2:25 pm, Luke Fritz [e-mail] wrote:

@grantclem https://github.com/grantclem sorry for the inconvenience and thanks for reporting the issue. It was an oversight in testing on my part -- each dev of pyarlo seems to have some subset of devices, but not all. @tchellomello https://github.com/tchellomello has put together a support matrix of which contributors have which devices so we can get a better handle on testing.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/home-assistant/home-assistant/issues/15486#issuecomment-405473380, or mute the thread https://github.com/notifications/unsubscribe-auth/AdLnQi5-YUw20Kc_p7XBhuBHEWW5ii6Yks5uHYNDgaJpZM4VQ4jd.

[grantclem]

Hi Luke,

Not sure this fix is working after the 74.0 release. Just a heads up...

On 17 Jul 2018, at 2:25 pm, Luke Fritz [e-mail] wrote:

@grantclem https://github.com/grantclem sorry for the inconvenience and thanks for reporting the issue. It was an oversight in testing on my part -- each dev of pyarlo seems to have some subset of devices, but not all. @tchellomello https://github.com/tchellomello has put together a support matrix of which contributors have which devices so we can get a better handle on testing.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/home-assistant/home-assistant/issues/15486#issuecomment-405473380, or mute the thread https://github.com/notifications/unsubscribe-auth/AdLnQi5-YUw20Kc_p7XBhuBHEWW5ii6Yks5uHYNDgaJpZM4VQ4jd.

[edif30]

It's definitely not. I just posted a new issue under https://github.com/home-assistant/home-assistant/issues/15585

[lukiffer]

@grantclem @edif30 It looks like the fix for this wasn't included in the 0.74.0 release (rc branch is still referencing 0.1.9). Hopefully this will referenced commit will ship soon. In the interim, you can update homeassistant/components/arlo.py to reference pyarlo==0.2.0 manually to avoid filling up the HA logs.

[edif30]

@lukiffer TY!

[GrandNewbien]

@lukiffer, is there anyway to access those files while using hassOS?

[lukiffer]

@GrandNewbien I'm not sure about hassOS, but it appears it was included in 0.75.0 - it should be fixed by simply upgrading to the latest version.