search

home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
73.43k stars 30.66k forks source link

Arlo Q camera not working after update to 0.72.0b2 using the new Arlo Component #15026

Closed MuppetOwl closed 5 years ago

MuppetOwl commented 6 years ago

Home Assistant release with the issue: 0.72.0b2

Last working Home Assistant release (if known): 0.71

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

Component/platform: Arlo Camera

Description of problem:

Unable to prepare setup for platform camera.arlo: Could not setup all dependencies.
20:56 setup.py (ERROR)
Unable to setup dependencies of camera.arlo. Setup failed for dependencies: arlo
20:56 setup.py (ERROR)
Unable to prepare setup for platform sensor.arlo: Could not setup all dependencies.
20:56 setup.py (ERROR)
Unable to setup dependencies of sensor.arlo. Setup failed for dependencies: arlo
20:56 setup.py (ERROR)
Setup failed for arlo: Component failed to initialize.
20:56 setup.py (ERROR)
ryanwinter commented 6 years ago

I'm seeing the same issues in 0.72. I've disabled the integration.

tchellomello commented 6 years ago

If you run pip freeze what's is the pyarlo version installed?

tchellomello commented 6 years ago

Updated to latest 0.72 and worked fine to me. Please let me know if you are still hitting any issues.

MuppetOwl commented 6 years ago

Still same issue for me on 0.72. Was working on 0.71.I have a Arlo Q plus Camera

018-06-24 18:17:48 ERROR (MainThread) [homeassistant.setup] Setup failed for arlo: Component failed to initialize.
2018-06-24 18:17:48 ERROR (MainThread) [homeassistant.setup] Unable to setup dependencies of sensor.arlo. Setup failed for dependencies: arlo
2018-06-24 18:17:48 ERROR (MainThread) [homeassistant.setup] Unable to prepare setup for platform sensor.arlo: Could not setup all dependencies.
2018-06-24 18:17:52 ERROR (MainThread) [homeassistant.setup] Unable to setup dependencies of camera.arlo. Setup failed for dependencies: arlo
2018-06-24 18:17:52 ERROR (MainThread) [homeassistant.setup] Unable to prepare setup for platform camera.arlo: Could not setup all dependencies.
arsaboo commented 6 years ago

Cameras and sensors work fine for me here as well.

tchellomello commented 6 years ago

@CookieMonster87 it seems to be something environmental on your configuration. This pip freeze does not seem to be the environment your HASS is using. If you just create a new environment (for test only) does it work?

MuppetOwl commented 6 years ago

Did reinstall hassbian completely now and did not change/upgrade anything like python to 3.6. So its 3.5 now like on a standard hassbian install. Did only copy my yaml config files. Still same error. If I go back to Home Assistant 0.71 it works.

yaml config is like this. and works without any issues on 0.71. Must I force a pyarlo version update? how do I do that on Hassbian?

arlo:
  username: "myemail"
  password: !secret password

camera:
  - platform: arlo
    ffmpeg_arguments: '-pred 1 -q:v 2'
MuppetOwl commented 6 years ago

pip freeze MarkupSafe==1.0 multidict==4.3.1 promise==2.1 psutil==5.4.6 py-vapid==1.4.0 pyarlo==0.1.7 PyBluez==0.22 pycparser==2.18 PyDispatcher==2.0.5 pyharmony==1.0.20 PyJWT==1.6.0 python-dateutil==2.7.3 python-nest==4.0.2 python-openzwave==0.4.3 python-pushover==0.3 pyTibber==0.4.1 pytz==2018.4 pywebpush==1.6.0 PyYAML==3.12 requests==2.18.4 Rx==1.6.1 six==1.11.0 sleekxmpp==1.3.3 SQLAlchemy==1.2.8 sseclient-py==1.7 teslajsonpy==0.0.23 typing==3.6.4 ua-parser==0.8.0 urllib3==1.22 user-agents==1.1.0 voluptuous==0.11.1 voluptuous-serialize==1.0.0 xmltodict==0.11.0 yarl==1.2.6 aiohttp==3.3.2 aiohttp-cors==0.7.0 asn1crypto==0.24.0 astral==1.6.1 async-timeout==3.0.0 attrs==18.1.0 bt-proximity==0.1.2 certifi==2018.4.16 cffi==1.11.5 chardet==3.0.4 cryptography==2.2.2 distro==1.3.0 googlemaps==2.5.1 gql==0.1.0 graphql-core==2.0 ha-ffmpeg==1.9 home-assistant-frontend==20180622.1 homeassistant==0.72.0 http-ece==1.0.5 idna==2.6 idna-ssl==1.0.1 Jinja2==2.10 MarkupSafe==1.0 multidict==4.3.1 promise==2.1 psutil==5.4.6 py-vapid==1.4.0 pyarlo==0.1.7 PyBluez==0.22 pycparser==2.18 PyDispatcher==2.0.5 pyharmony==1.0.20 PyJWT==1.6.0 python-dateutil==2.7.3 python-nest==4.0.2 python-openzwave==0.4.3 python-pushover==0.3 pyTibber==0.4.1 pytz==2018.4 pywebpush==1.6.0 PyYAML==3.12 requests==2.18.4 Rx==1.6.1 six==1.11.0 sleekxmpp==1.3.3 SQLAlchemy==1.2.8 sseclient-py==1.7 teslajsonpy==0.0.23 typing==3.6.4 ua-parser==0.8.0 urllib3==1.22 user-agents==1.1.0 voluptuous==0.11.1 voluptuous-serialize==1.0.0 xmltodict==0.11.0 yarl==1.2.6

jurgenweber commented 6 years ago

I find my Baby Arlo fails now as well saying the configuration is broken.

2018-06-25 11:00:39 ERROR (MainThread) [homeassistant.setup] Setup failed for arlo: Component failed to initialize.
2018-06-25 11:00:39 ERROR (MainThread) [homeassistant.setup] Setup failed for arlo: Component failed to initialize.
2018-06-25 11:00:46 ERROR (MainThread) [homeassistant.setup] Unable to setup dependencies of sensor.arlo. Setup failed for dependencies: arlo
2018-06-25 11:00:54 ERROR (MainThread) [homeassistant.setup] Unable to prepare setup for platform sensor.arlo: Could not setup all dependencies.
2018-06-25 11:00:54 ERROR (MainThread) [homeassistant.setup] Unable to setup dependencies of camera.arlo. Setup failed for dependencies: arlo
2018-06-25 11:00:54 ERROR (MainThread) [homeassistant.setup] Unable to prepare setup for platform camera.arlo: Could not setup all dependencies.
# pip freeze
aiohttp==3.3.2
aiohttp-cors==0.7.0
asn1crypto==0.24.0
astral==1.6.1
async-timeout==3.0.0
attrs==18.1.0
boto3==1.7.40
botocore==1.10.40
bt-proximity==0.1.2
certifi==2018.4.16
cffi==1.11.5
chardet==3.0.4
colorlog==3.1.4
cookies==2.2.1
cryptography==2.2.2
distro==1.3.0
docutils==0.14
ecdsa==0.13
enum-compat==0.0.2
envs==1.2.6
fastdotcom==0.0.3
future==0.16.0
gTTS-token==1.1.1
ha-ffmpeg==1.9
holidays==0.9.5
home-assistant-frontend==20180622.1
homeassistant==0.72.0
http-ece==1.0.5
idna==2.6
idna-ssl==1.0.1
Jinja2==2.10
jmespath==0.9.3
jsonrpc-async==0.6
jsonrpc-base==1.0
jsonrpc-websocket==0.6
libnacl==1.6.1
libsoundtouch==0.7.2
MarkupSafe==1.0
multidict==4.3.1
mutagen==1.40.0
mysqlclient==1.3.12
netdisco==1.4.1
netifaces==0.10.7
numpy==1.14.3
paho-mqtt==1.3.1
Pillow==5.1.0
pkg-resources==0.0.0
protobuf==3.6.0
pushbullet.py==0.11.0
py-vapid==1.4.0
pyarlo==0.1.7
PyBluez==0.22
PyChromecast==2.1.0
pycparser==2.18
pycryptodome==3.3.1
PyDispatcher==2.0.5
pyHik==0.1.8
PyJWT==1.6.0
PyMySQL==0.8.1
python-dateutil==2.7.3
python-forecastio==1.4.0
python-jose-cryptodome==1.3.2
python-magic==0.4.15
python-openzwave==0.4.3
pytz==2018.4
pywebpush==1.6.0
PyYAML==3.12
requests==2.18.4
responses==0.9.0
roombapy==1.3.1
s3transfer==0.1.13
samsungctl==0.7.1
six==1.11.0
SQLAlchemy==1.2.8
sseclient-py==1.7
transmissionrpc==0.11
typing==3.6.4
ua-parser==0.8.0
urllib3==1.22
user-agents==1.1.0
voluptuous==0.11.1
voluptuous-serialize==1.0.0
wakeonlan==1.0.0
warrant==0.6.1
websocket-client==0.48.0
xmltodict==0.11.0
yarl==1.2.6
zeroconf==0.20.0
jurgenweber commented 6 years ago

doing some investigation for me, hass is install 0.1.7...... writing some basic python it returns nothing but if I upgrade to the new version... https://github.com/tchellomello/python-arlo/releases/tag/0.1.8. it works.

Lets bump the version in hass?

I manually made the change with some success. I do not have images for the camera but the sensors are updating. Maybe we can turn on some Arlo.baby sepcific ones.. anyway, another topic.

MuppetOwl commented 6 years ago

Is this maybe an issue for the "stand alone" Arlo Q, Q plus and baby etc that does not use a a base station?

I had to go back to 0.71 where this was working (sensors did not) but the camera and picture from it was and without all the errors in the log.

fosselius commented 6 years ago

I was trying to use the component for the first time together with Arlo that has the base station and I received the same errror message. I’m also on 0.72

MuppetOwl commented 6 years ago

Still same issue on 0.73. Any plans to fix this mess soon? Or is it possible to force this component back to like it was on 0.71 before the "Upgrade" where is was actually working for Arlo Q etc.

fosselius commented 6 years ago

No News on this one? I have the same issue on 0.74

MuppetOwl commented 6 years ago

@tchellomello Is a fix being worked on? Can also still confirm same issue on 0.74

tchellomello commented 6 years ago

@CookieMonster87 I'm unable to reproduce the same issue on 0.74. It is working fine for me.

On 0.74, you should see the pyarlo==0.1.9. Is that the one you are seeing? 

 root@my:/usr/src/app# python -m homeassistant --version
0.74.0
root@my:/usr/src/app# pip freeze | grep pyarlo
pyarlo==0.1.9

All Arlo integrations are being loaded fine in my environment. Can you enable the debug version so then we can see why dependencies are broken?

mmello

MuppetOwl commented 6 years ago

Yes pyarlo is 0.1.9

How do I activate debug version? I have tried to reinstall hassbian and also the latest versions of hass.io three times on a new sd card. Still same error so dont think this is an installation issue.

shimmyt commented 6 years ago

@CookieMonster87 I'm having the same issue as you except with the Arlo base station. To enable debug mode edit your configuration.yaml file and throw logger: https://www.home-assistant.io/components/logger/ in there. Here are the results of mine wonder if you're seeing the same thing:

2018-08-02 21:57:59 INFO (MainThread) [homeassistant.loader] Loaded camera.arlo from homeassistant.components.camera.arlo
2018-08-02 21:57:59 INFO (MainThread) [homeassistant.loader] Loaded arlo from homeassistant.components.arlo
2018-08-02 21:57:59 INFO (MainThread) [homeassistant.loader] Loaded alarm_control_panel.arlo from homeassistant.components.alarm_control_panel.arlo
2018-08-02 21:58:01 INFO (MainThread) [homeassistant.setup] Setting up arlo
2018-08-02 21:58:01 DEBUG (SyncWorker_1) [pyarlo] Creating Arlo session
2018-08-02 21:58:01 DEBUG (SyncWorker_1) [pyarlo] Params: {'email': 'email', 'password': 'password'}
2018-08-02 21:58:01 DEBUG (SyncWorker_1) [pyarlo] Headers: {'Content-Type': 'application/json', 'Authorization': None}
2018-08-02 21:58:01 DEBUG (SyncWorker_1) [pyarlo] Querying https://arlo.netgear.com/hmsweb/login/v2 on attempt: 0/3
2018-08-02 21:58:02 DEBUG (SyncWorker_1) [pyarlo] Params: {'email': 'myemail@email.com', 'password': 'mypassword'}
2018-08-02 21:58:02 DEBUG (SyncWorker_1) [pyarlo] Headers: {'Content-Type': 'application/json', 'Authorization': 'longauthorizationcode'}
2018-08-02 21:58:02 DEBUG (SyncWorker_1) [pyarlo] Querying https://arlo.netgear.com/hmsweb/users/devices on attempt: 0/3
2018-08-02 21:58:02 INFO (MainThread) [homeassistant.setup] Setup of domain arlo took 1.2 seconds.
2018-08-02 21:58:02 ERROR (MainThread) [homeassistant.setup] Setup failed for arlo: Component failed to initialize.
 - [arlo](https://home-assistant.io/components/arlo/)
 - [arlo](https://home-assistant.io/components/arlo/)

So mine looks like it logs in successfully gets an authorization token then bombs out.

fosselius commented 6 years ago

Still not working for me. How can I provide better logs for troubleshooting?

MuppetOwl commented 6 years ago

Possible to revert this component to the old version like it was on 0.71 that was working?

We are many with the same error so this is not just a environment issue. the component was broken for many of us after 0.71. https://community.home-assistant.io/t/error-while-setting-up-arlo-q/31019/14

MuppetOwl commented 6 years ago

I Give up. Sold the Arlo and bought a Nest instead so I get a component that is working without issues for Home Assistant.

awarecan commented 6 years ago

I have to warn you, the Nest Cam streaming is not available on HA. Only snapshot.

tdiekmann commented 6 years ago

I debugged the arlo component today with 0.78.0.dev0. In order for the arlo components to show up, you need to ensure that the user id you use to authenticate with Arlo has a base station shared and the 'Allow Access Rights' feature enabled. Without it, the pyarlo lib does not return a base station and the component returns False during setup.

I had a created a user homeassistant to share the Arlo access with minimal rights, but that apparently does not work.

matejcerny commented 6 years ago

@tdiekmann Do you have Arlo with base station or Arlo Q (standalone camera)? Thanks

tdiekmann commented 6 years ago

@foxys0, I have the Arlo Pro cameras with base station.

matejcerny commented 6 years ago

@tdiekmann This issue is about Arlo Q, rights management unfortunately will not help.

Megachip commented 6 years ago

So mine looks like it logs in successfully gets an authorization token then bombs out.

Same here :(

2018-09-08 19:26:16 DEBUG (SyncWorker_12) [pyarlo] Querying https://arlo.netgear.com/hmsweb/users/devices on attempt: 0/3
2018-09-08 19:26:16 INFO (MainThread) [homeassistant.setup] Setup of domain arlo took 2.0 seconds.
2018-09-08 19:26:16 ERROR (MainThread) [homeassistant.setup] Setup failed for arlo: Component failed to initialize.
tdiekmann commented 6 years ago

@foxys0 that may very well be the case. I don't have a Arlo Q to test this with. When I debugged the code, I found that it makes the assumption that there is a base station returned in the PyArlo object. That assumption did not hold true unless the base station information was shared with the user accessing the API, i.e. the returned structure was empty. Hope this helps you in debugging the Arlo Q case.

zellux commented 6 years ago

I've sent a pull request #16529 to fix it, it works on my side.

zellux commented 6 years ago

@Megachip @fosselius can you upgrade to 0.78 and see if it is working for you?

Megachip commented 6 years ago

@Megachip @fosselius can you upgrade to 0.78 and see if it is working for you?

Working fine, including last video.

But would it possible to remove Battery Level on VMC3040S? The device didn't have a battery so it didn't provide a value for that parameter.

Not sure about Signal Strength ... the q models supports wifi, but mine are all connected via ethernet. "connectivity": { "type": "ethernet", "connected": true, "mepStatus": "unknown" }

balloobbot commented 5 years ago

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 :+1:

asjmcguire commented 5 years ago

Is this still an issue you are experiencing? Can you please try upgrading to the latest version of Home Assistant (0.90) and report back if this is still a problem? Thanks!

stale[bot] commented 5 years ago

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.