Arlo: replacement pyarlo module

Third party integrations
404

Thanks again, some progress.

The Q now retrieves the modes on startup but still cannot set them…

2019-05-27 19:43:25 DEBUG (EventStream) [pyaarlo] Lounge BASE got modes
2019-05-27 19:43:25 DEBUG (EventStream) [pyaarlo] ambient: starting mode parse
2019-05-27 19:43:25 DEBUG (EventStream) [pyaarlo] mode0<==>disarmed
2019-05-27 19:43:25 DEBUG (EventStream) [pyaarlo] set:4N527AS150B53/modeIdToName/mode0=disarmed
2019-05-27 19:43:25 DEBUG (EventStream) [pyaarlo] set:4N527AS150B53/modeNameToId/disarmed=mode0
2019-05-27 19:43:25 DEBUG (EventStream) [pyaarlo] mode1<==>armed
2019-05-27 19:43:25 DEBUG (EventStream) [pyaarlo] set:4N527AS150B53/modeIdToName/mode1=armed
2019-05-27 19:43:25 DEBUG (EventStream) [pyaarlo] set:4N527AS150B53/modeNameToId/armed=mode1
2019-05-27 19:43:25 DEBUG (EventStream) [pyaarlo] mode2<==>Dogs home alone
2019-05-27 19:43:25 DEBUG (EventStream) [pyaarlo] set:4N527AS150B53/modeIdToName/mode2=Dogs home alone
2019-05-27 19:43:25 DEBUG (EventStream) [pyaarlo] set:4N527AS150B53/modeNameToId/dogs home alone=mode2
2019-05-27 19:43:25 DEBUG (EventStream) [pyaarlo] mode3<==>Night
2019-05-27 19:43:25 DEBUG (EventStream) [pyaarlo] set:4N527AS150B53/modeIdToName/mode3=Night
2019-05-27 19:43:25 DEBUG (EventStream) [pyaarlo] set:4N527AS150B53/modeNameToId/night=mode3
2019-05-27 19:43:25 DEBUG (EventStream) [pyaarlo] ambient: ending mode parse
2019-05-27 19:43:25 DEBUG (EventStream) [pyaarlo] set:4N527AS150B53/activeMode=disarmed
2019-05-27 19:43:25 DEBUG (EventStream) [pyaarlo] Lounge CAMERA got one modes
2019-05-27 19:43:25 DEBUG (EventStream) [pyaarlo] Lounge got modes

When I try and set mode I just get this…
2019-05-27 19:45:27 DEBUG (SyncWorker_15) [pyaarlo] Lounge:new-mode=dogs home alone,id=mode2
2019-05-27 19:45:27 DEBUG (ArloBackgroundWorker) [pyaarlo] starting request=https://arlo.netgear.com/hmsweb/users/devices/automation/active

405

Can you update and try now? The set should work.

406

That did it, Sherrell you absolute legend, I owe you a beer.

407

Glad that works but I broke it in the first place. Arlo introduced a new way to change modes and I - foolishly - thought it applied to all devices, turns out it’s only the “real” base stations. And I need the new way else some modes don’t appear when I ask for a list of supported ones.

I’ll check that fix into the main branch later tonight (GMT-5) and I’ll let you know when it’s in.

408

@nrd2001 It’s all merged into the master branch.

409

Hey Steve, great to see this is getting updated! Is there a guide on how to pull the latest version down?

410

@richatha
The component supports the custom_updater it works well but I don’t have any real experience using it.

411

Hi,
even though the component is still working great, it regularly crashes on my system so that I have to restart Home Assistant to get it going again. I can’t find any apparent reason why the component stops working. But it occurs at least once or twice a day. Any ideas or does anyone have similar problems?

412

this happens to me too from time to time i find the snap shot boxes on my dashboard are broken and require a reboot which then kicks in. I was hoping upgrading versions might help with this. Not the end of the world for me as i’m currently still using the Arlo app as a back up

413

@ffm777 @richatha

Which version are you on?

Any logs at all? Even if there is no crash can you see the last activity from the pyaarlo component. If you haven’t already can you turn on debugging and keep an eye on it. Use the following:

logger:
  default: info
  logs:
    pyaarlo: debug
414

I‘m on the latest version 0.0.11.

I will turn on debugging and see what I can find out.

415

I’ve just wiped my HA and started again so pulled the latest version down and turned logger on so will keep you posted!

416

I had to go back to an old version as the current version constantly fails to switch modes after a couple of hours. Unfortunately, I only have a copy of 0.0.2 but this one is at least working so far. Hopefully, Steve can figure out what the problem with the mode switching is.

417

@ffm777 @richatha

(Kind of ) Good news - I got mine to lock up too. I’ve added some debug to my setup and I’ll try and reproduce it again.

edit: I saw the lock up again after 5 days. One thing I did notice is I keep sending the same time stamp to the mode change request. I’ve checked in a fix for that in this branch - https://github.com/twrecked/hass-aarlo/tree/mode-api - and I’m testing that branch now.

1 Like
418

Getting this error when I try to stream from lovelace in aarlo custom glance. running in virtual env

2019-06-07 21:58:59 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection.1628511984] Error handling message: Unknown error
Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/components/websocket_api/decorators.py", line 17, in _handle_async_response
    await func(hass, connection, msg)
  File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/components/camera/__init__.py", line 562, in ws_camera_stream
    source = await camera.stream_source()
TypeError: 'str' object is not callable
419

@stogs

I’ll test it out here. What version of home assistant are you on?

edit: no problems, I got the issue here

1 Like
420

@stogs
If you update the Aarlo repository it should be fixed.

I guess they changed the stream API interface and I hadn’t noticed…

421

That fixed the issue I was having. It now seems to be constantly trying to start the stream, I am on 0.94.0. Had to restart to stop it.

2019-06-08 08:26:11 INFO (MainThread) [homeassistant.components.stream] Started stream: rtsps://vzwow653-z2-prod.ar.arlo.com:443/vzmodulelive/.......
422

That could be the preload feature of the stream module. It starts streaming from all the cameras on start up. It should stop after a minute or two.

I think the default should be off. And you can disable it from the standard picture card (I believe).

423

Thanks for the help!!!