Core: 0.74 - Continuous Arlo Errors

[edif30]

Home Assistant release with the issue:
0.74

Last working Home Assistant release (if known):
0.73.x

Operating environment (Hass.io/Docker/Windows/etc.):
Docker

Component/platform:
Arlo

Description of problem:
Continuous errors since update to 0.74

Traceback (if applicable):

Traceback (most recent call last):
  File "/usr/local/lib/python3.6/concurrent/futures/thread.py", line 56, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/src/app/homeassistant/components/arlo.py", line 84, in hub_refresh
    update_base_station=True)
  File "/usr/local/lib/python3.6/site-packages/pyarlo/__init__.py", line 270, in update
    base.update()
  File "/usr/local/lib/python3.6/site-packages/pyarlo/base_station.py", line 687, in update
    self.get_ambient_sensor_data()
  File "/usr/local/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'

Additional information:

[grantclem]

Reported the ambient sensor issue earlier #15486 in the week during the beta release and was told it was resolved.

[lukiffer]

This was fixed in #15503 but was not included in the 0.74 release (see #15486 for more details).

Try updating homeassistant/components/arlo.py to reference pyarlo==0.2.0 - this should fix the problem in the interim. Hopefully the updated reference gets included in 0.75.0b0.

Again apologies for the inconvenience - tried to turn around the fix quickly enough to make 0.74 release, but unfortunately it did not.

[grantclem]

Thanks, sorted, no problem - thanks for your effort anyway

On 22 Jul 2018, at 7:45 am, Luke Fritz [e-mail] wrote:

This was fixed in #15503 https://github.com/home-assistant/home-assistant/pull/15503 but was not included in the 0.74 release (see #15486 https://github.com/home-assistant/home-assistant/issues/15486 for more details).

Try updating homeassistant/components/arlo.py to reference pyarlo==0.2.0 - this should fix the problem in the interim. Hopefully the updated reference gets included in 0.75.0b0.

Again apologies for the inconvenience - tried to turn around the fix quickly enough to make 0.74 release, but unfortunately it did not.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/home-assistant/home-assistant/issues/15585#issuecomment-406830411, or mute the thread https://github.com/notifications/unsubscribe-auth/AdLnQlzVR7nH1smDqT7LCm27Mn73n37Pks5uI70ngaJpZM4VZYZe.

[edif30]

@lukiffer I updated the arlo.py to reference that version as well as the requirements_all.txt. I uninstalled 0.1.9 and installed 0.2.0. Still getting these errors.

[arsaboo]

@edif30 You just need to update the arlo.py file with version 0.2.0. It fixed the errors for me.

[lukiffer]

@edif30 requirements.txt isn't observed by homeassistant at runtime. It looks for REQUIREMENTS in each of the modules and installs those every time homeassistant starts up. You'll want to update this to pyarlo==0.2.0: https://github.com/home-assistant/home-assistant/blob/5e9c1098c0d175946d3ef50656ebbdc083b85fc2/homeassistant/components/arlo.py#L19

This should be located at /lib/python3.6/site-packages/homeassistant/components/arlo.py

[edif30]

@lukiffer I have updated that reference and seem to be still getting errors. Not sure if this makes a difference but I rebuilt my docker container with 0.2.0 and updated the arlo.py file to reflect 0.2.0. Still getting those errors. By just changing the reference to 0.2.0 and not installing 0.2.0, the component wouldn't load. So I'm not really sure what is going on here.

# pip3 freeze | grep arlo
pyarlo==0.2.0

:/usr/src/app/homeassistant/components# cat arlo.py | grep pyarlo
REQUIREMENTS = ['pyarlo==0.2.0']

I can also say that after I made this change, it seemed like the errors stopped but I've been making automation changes frequently and after restarting HA a few times, the errors just started popping back up.

[rafuz]

Is it fixed in 0.74.2?

[msubra]

Updated to 0.74.2, still the issue continues. Here are some debug logs I could grab during startup

2018-07-26 12:29:54 INFO (MainThread) [homeassistant.setup] Setting up arlo
2018-07-26 12:29:54 DEBUG (SyncWorker_3) [pyarlo] Creating Arlo session
2018-07-26 12:29:54 DEBUG (SyncWorker_3) [pyarlo] Params: {'email': '<redacted>', 'password': '<redacted>'}
2018-07-26 12:29:54 DEBUG (SyncWorker_3) [pyarlo] Headers: {'Content-Type': 'application/json', 'Authorization': None}
2018-07-26 12:29:54 DEBUG (SyncWorker_3) [pyarlo] Querying https://arlo.netgear.com/hmsweb/login/v2 on attempt: 0/3
2018-07-26 12:29:56 DEBUG (SyncWorker_3) [pyarlo] Params: {'email': '<redacted>', 'password': '<redacted>'}
2018-07-26 12:29:56 DEBUG (SyncWorker_3) [pyarlo] Headers: {'Content-Type': 'application/json', 'Authorization': '<redacted>'}
2018-07-26 12:29:56 DEBUG (SyncWorker_3) [pyarlo] Querying https://arlo.netgear.com/hmsweb/users/devices on attempt: 0/3

2018-07-26 12:29:56 INFO (MainThread) [homeassistant.core] Bus:Handling <Event call_service[L]: domain=persistent_notification, serv
ice=create, service_data=title=Invalid config, message=The following components and platforms could not be set up:

 - [arlo](https://home-assistant.io/components/arlo/)

Please check your config., notification_id=invalid_config, service_call_id=140347929274688-2>
2018-07-26 12:29:56 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=persistent_notification.i
nvalid_config, old_state=None, new_state=<state persistent_notification.invalid_config=notifying; title=Invalid config, message=The
following components and platforms could not be set up:

 - [arlo](https://home-assistant.io/components/arlo/)

Please check your config. @ 2018-07-26T12:29:56.802221-05:00>>

[lukiffer]

@rafuz The fix was not included in 0.74.2 - I expect the first appearance will be in 0.75.0b0

@msubra that looks like a different issue that wouldn't have been caused by the ambient sensors update. Happy to help debug - could you open a separate issue and paste the relevant parts of your config?

[edif30]

@lukiffer

2018-07-31 16:24:28 ERROR (MainThread) [homeassistant.core] Error doing job: Future exception was never retrieved
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/concurrent/futures/thread.py", line 56, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/src/app/homeassistant/components/arlo.py", line 84, in hub_refresh
    update_base_station=True)
  File "/config/deps/lib/python3.6/site-packages/pyarlo/__init__.py", line 270, in update
    base.update()
  File "/config/deps/lib/python3.6/site-packages/pyarlo/base_station.py", line 687, in update
    self.get_ambient_sensor_data()
  File "/config/deps/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'

```$ sudo docker exec -it home-assistant bash

cat homeassistant/components/arlo.py | grep REQ

REQUIREMENTS = ['pyarlo==0.2.0']

date

Tue Jul 31 16:25:16 EDT 2018
$ cat .HA_VERSION
0.75.0b0
```

[MartinHjelmare]

@edif30 check that your deps dir is cleared. Your latest log suggests that home assistant is picking up the pyarlo package from the deps dir instead of from /usr/local as your first log in the OP. Docker will install all requirements in the system path before home assistant is started. So there shouldn't be any libs in the deps dir.

[edif30]

@MartinHjelmare WOW, I didn't even notice that. Also, I have no idea how or why the 1.9 was even in the deps. When I build the HA image and HA container, I wipe everything except config yamls. Very odd. I wiped the deps dir and just rebuilt using the 0.75.0b0. So far so good. TY for pointing that out!

@lukiffer my bad, I feel like an idiot not noticing the /deps in the logs.

Going to just monitor for about 10-15 min and I will close this out.

[rpitera]

Where is the location of the arlo.py file for hass.io users? I'm migrating - slowly - from an old AIO install on another pi and I can't seem to find the location of this file anywhere. I know the issue was closed but I thought this would be the best place to ask.