Arlo Q camera not working after update to 0.72.0b2 using the new Arlo Component #15026
Comments
|
I'm seeing the same issues in 0.72. I've disabled the integration. |
|
If you run pip freeze what's is the pyarlo version installed? |
|
Updated to latest 0.72 and worked fine to me. Please let me know if you are still hitting any issues. |
|
Still same issue for me on 0.72. Was working on 0.71.I have a Arlo Q plus Camera |
|
Cameras and sensors work fine for me here as well. |
|
@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? |
|
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. 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? |
|
|
I find my Baby Arlo fails now as well saying the configuration is broken. |
|
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. |
|
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. |
|
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 |
|
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. |
|
No News on this one? I have the same issue on 0.74 |
|
@tchellomello |
|
@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 root@my:/usr/src/app# python -m homeassistant --version
0.74.0
root@my:/usr/src/app# pip freeze | grep pyarlo
pyarlo==0.1.9All 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 |
|
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. |
|
@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: So mine looks like it logs in successfully gets an authorization token then bombs out. |
|
Still not working for me. How can I provide better logs for troubleshooting? |
|
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. |
|
I Give up. Sold the Arlo and bought a Nest instead so I get a component that is working without issues for Home Assistant. |
|
I have to warn you, the Nest Cam streaming is not available on HA. Only snapshot. |
|
I debugged the arlo component today with 0.78.0.dev0. I had a created a user homeassistant to share the Arlo access with minimal rights, but that apparently does not work. |
|
@tdiekmann Do you have Arlo with base station or Arlo Q (standalone camera)? Thanks |
|
@foxys0, I have the Arlo Pro cameras with base station. |
|
@tdiekmann This issue is about Arlo Q, rights management unfortunately will not help. |
Same here :( |
|
@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. |
|
I've sent a pull request #16529 to fix it, it works on my side. |
|
@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 Not sure about |
|
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 👍 |
|
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! |
|
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. |
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:
The text was updated successfully, but these errors were encountered: