Just bought myself a Arlo Q (model VMC3040). While setting up the device in Home Assistant (i’m running 0.56.2 in a Synology Docker) The sensors are coming up, but the camera itself is not recognised.
2017-10-29 21:34:38 ERROR (MainThread) [homeassistant.components.camera] Error on device update!
Traceback (most recent call last):
File "/usr/src/app/homeassistant/helpers/entity_component.py", line 216, in async_add_entity
yield from entity.async_device_update(warning=False)
File "/usr/src/app/homeassistant/helpers/entity.py", line 309, in async_device_update
yield from self.hass.async_add_job(self.update)
File "/usr/local/lib/python3.6/asyncio/futures.py", line 332, in __iter__
yield self # This tells Task to wait for completion.
File "/usr/local/lib/python3.6/asyncio/tasks.py", line 250, in _wakeup
future.result()
File "/usr/local/lib/python3.6/asyncio/futures.py", line 245, in result
raise self._exception
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/camera/arlo.py", line 163, in update
self.attrs[ATTR_BATTERY_LEVEL] = self._camera.get_battery_level
File "/usr/local/lib/python3.6/site-packages/pyarlo/camera.py", line 134, in get_battery_level
base = self._session.base_stations[0]
IndexError: list index out of range
It seems to be a recurring issue regarding the fact the Arlo Q does not need a Base Station. For now I have reverted back to 0.54.0. I Also can confirm the camera is working in this version.
Guys @Dennis87@M4tthijs, are you still on version 0.54 or is this problem with Arlo Q fixed already? I am new to HA so I am not sure if it is a bug or just my configuration. Thanks a lot
Traceback (most recent call last):
File "/usr/lib/python3.6/site-packages/homeassistant/helpers/entity_component.py", line 171, in _async_setup_platform
SLOW_SETUP_MAX_WAIT, loop=self.hass.loop)
File "/usr/lib/python3.6/asyncio/tasks.py", line 352, in wait_for
return fut.result()
File "/usr/lib/python3.6/asyncio/futures.py", line 244, in result
raise self._exception
File "/usr/lib/python3.6/asyncio/tasks.py", line 179, in _step
result = coro.send(None)
File "/usr/lib/python3.6/asyncio/coroutines.py", line 210, in coro
res = func(*args, **kw)
File "/usr/lib/python3.6/site-packages/homeassistant/components/camera/arlo.py", line 61, in async_setup_platform
cameras.append(ArloCam(hass, camera, config))
File "/usr/lib/python3.6/site-packages/homeassistant/components/camera/arlo.py", line 78, in __init__
self._camera.base_station.refresh_rate = SCAN_INTERVAL.total_seconds()
AttributeError: 'NoneType' object has no attribute 'refresh_rate'
You’ll need to make sure you have the latest version of the PyArlo library installed. Something like pip3 install pyarlo==0.1.0. I’ve noticed that sometimes HASS upgrades may fail to install an updated dependency.
Ok @jwillaz, I deleted hassio, installed hassbian and tried to install the latest PyArlo library as you suggested, but the error is still there. I also tried to comment problematic line with base station (Arlo Q has no base station) just to see what happen and now I can see (at least) last fetched image
Hi @foxys, sorry, my response was specifically related to your above error. Refresh_rate is an attribute introduced in a more recent version of PyArlo. I wasn’t thinking that this was Q-related error, but it is. Since you are using an Arlo Q, you are correct - there is no base station. This is what is returning ‘NoneType’ and stating it has no refresh_rate attribute. Hoping that any devs with the device would consider contributing to a library update. It should be rather straightforward to make BaseStations optional, but without a device, I don’t know how the Q communicates. Perhaps it simply makes BaseStation calls AND Camera calls itself, but that’s just guessing.
I ran into the same issue with an Account I set up on Arlo specifically for HomeAssistant.
Needed to go into the Arlo app settings -> Grant Access
Select the account you setup and ensure that you have a tick in the bottom box: Allow Access Rights
No update yet. I ended up with crazy workaroud - input boolean (ARM / DISARM) integrated via IFTTT and Stringify (IFTTT + Arlo does not work either http://status.ifttt.com/incidents/2wpfb9t09n8v).
@karlkar Can you please help me/us with configuration of Arlo? New pyarlo is now part of HASSIO 0.61.0, I also create custom component from your commit, but last video and sensors (battery, signal, motion…) are still not accessible. The only thing which works is “still picture”. Thanks a lot!
I’ve been experiencing this issue since 0.54 also. Which sucked because I had just bought the Arlo Q about a month before this issue occurred. I can’t really offer much help since I don’t have much coding experience but I’d be more than happy to test anything needed. I’m really hoping for a fix for this soon
My arlo q plus camera is working without any issue/error msg and see the picture from it with latest hass.io.
Only issue now its that is does not get info like signal strength, last capture etc. It just states unknown.
Can confirm that the Arlo Q is working as well since the new update! Feels so nice to have my camera on my Home Assistant security page again!! I’m not getting any info either but instead of showing unknown it just doesn’t show those attributes at all anymore on mine
