Arlo: replacement pyarlo module

Hello,

i am experiencing difficulties with the Arlo component.
The devices are shown as unavailbale and i get the following message in the log:

Platform error sensor.aarlo - cannot import name 'CONF_ATTRIBUTION' from 'custom_components.aarlo' (/config/custom_components/aarlo/__init__.py) Platform error alarm_control_panel.aarlo - cannot import name 'CONF_ATTRIBUTION' from 'custom_components.aarlo' (/config/custom_components/aarlo/__init__.py)

Last changes i did:

  • Upgraded supervisor to V.200
  • Upgraded Ha core to V. 0.105.3
  • Upgraded hassOS to v.3.10

Did i miss any breaking changes?

My config for Aarlo as following:

aarlo:
  username: !secret arlo_user
  password: !secret arlo_password 
  last_format: '%m-%d %H:%M'
  refresh_devices_every: 2
#  reconnect_every: 90

alarm_control_panel:
  - platform: aarlo
    home_mode_name: disarmed
    away_mode_name: armed
 
#camera:
#  - platform: aarlo
#    ffmpeg_arguments: '-pred 1 -q:v 2'

sensor:
  - platform: aarlo
    monitored_conditions:
    - last_capture
    - total_cameras
    - battery_level
    - captured_today
    - signal_strength

Thanks for your help in advance!
/ Ralf

It’s a HACS issue: https://github.com/twrecked/hass-aarlo/issues/165

There was a version of HACS that flattened the component’s directory structure.

Thanks a lot for the info.
Got it fixed again with the newer version of HACS.
The way i did: install latest version of HACS, restart, reinstall aarlo.
Working again like a charm.

/ Ralf

I am running HA inside docker on Ubuntu 18.04 it’s a 2 week old install from fresh says on GitHub streaming now works out of the box on docker but if I click the custom glance card it acts like it’s going to stream but just shows a still image never shows a picture.

What’s wrong?

@Blair_Pollard
It could be a couple of things:

  • do you have the stream component enabled?
  • what kind of cameras are you using? There is an issue with ArloQ cameras I’m trying to track down.

What stream component?

Do I need stream: in my config if so I did try with that no difference.

It is an arloq

It’s looking more and more like the stream component doesn’t support the ArloQ cameras. If you read the bug report removing 1 line in the code fixes the issue. We’re going to try and get a fix put in.

Is there a possible issue with the Alarm Control Panel now not responding with the latest version? Running latest version of Aarlo and also using Beta 0.106b5

@grantc
I added support for parsing out schedules so maybe that has had a weird affect. Can you paste your alarm config and I’ll try it here. Can you look in the logs and see if there are any backtraces?

On my end I will update my HA installation to the latest build and check that.

Thanks will do - nothing showing in the logs however
a

larm_control_panel:
  - platform: aarlo
    home_mode_name: disarmed
    away_mode_name: armed
    night_mode_name: armed
    trigger_time: 60
    alarm_volume: 9

I don’t see how, but this might been related with the latest beta?

Crap. Another change was I reordered the mode so custom modes will appear first. Can you try for a test using this config:

alarm_control_pane:
 - platform: aarlo
    home_mode_name: home
    away_mode_name: away
    night_mode_name: night
    trigger_time: 60
    alarm_volume: 9

And I’ll think of a better solution.

Tried you config suggestion and update also to 0.6.13 as well with no success.
Running in VE.

I have a virtual environment somewhere, I’ll take a look.

edit: reproduced it. I’m seeing an error being thrown, I’ll take a look.

edit: I accessed the virtualenv from another machine and it’s working now… The original issue looked like a null not being handled by Lovelace, can you try refreshing the browser (CTRL+SHIFT+R) a few times? And what version of Python is in your virtualenv?

Python 3.7.5rc1

Not sure why the refresh is not working. If I try to run throught frontend I get;

2020-02-26 23:03:15 ERROR (MainThread) [frontend.js.latest.202002204] https://xxxxxx.duckdns.org:xxxx/frontend_latest/chunk.a7f86c7205b90ff898cc.js:3748:712 Uncaught TypeError: Cannot set property ‘value’ of null

Can’t seem to arm/disram via dev tools either
image

Thanks! That was the error I was getting too. I’ll try and get it again.

edit: And is there a link on how I get the beta version going?

Can you make sure debug is on and get some traces from pyaarlo when the issue occurs? Thanks!

logger:
  default: info
  logs:
    pyaarlo: debug
    custom_components.aarlo.alarm_control_panel: debug

Beta release has finished - run with the official release of 0.106

Below is when I try to set to" Arm Night" using this config;

Note: default appears to be set to “dis-armed”

alarm_control_panel:

  • platform: aarlo
    home_mode_name: home
    away_mode_name: away
    night_mode_name: night
    trigger_time: 60
    alarm_volume: 9

2020-02-27 08:17:27 DEBUG (MainThread) [custom_components.aarlo.alarm_control_panel] supported: 15
2020-02-27 08:17:42 DEBUG (MainThread) [custom_components.aarlo.alarm_control_panel] supported: 15
2020-02-27 08:17:42 DEBUG (SyncWorker_12) [custom_components.aarlo.alarm_control_panel] Base Station set mode to night
2020-02-27 08:17:42 WARNING (SyncWorker_12) [pyaarlo] Base Station: mode night is unrecognised
2020-02-27 08:17:42 ERROR (MainThread) [frontend.js.latest.202002204] :0:0 Script error.
2020-02-27 08:17:42 DEBUG (MainThread) [custom_components.aarlo.alarm_control_panel] supported: 15

Using my original config

Trying to set to “dis-armed”

Note: default appears to be set to “armed”

alarm_control_panel:

  • platform: aarlo
    home_mode_name: disarmed
    away_mode_name: armed
    night_mode_name: armed
    trigger_time: 60
    alarm_volume: 9

2020-02-27 08:31:56 ERROR (MainThread) [frontend.js.latest.202002204] :0:0 Script error.
2020-02-27 08:31:56 DEBUG (SyncWorker_5) [custom_components.aarlo.alarm_control_panel] Base Station set mode to disarmed
2020-02-27 08:31:56 DEBUG (SyncWorker_5) [pyaarlo] set:4RE1727PA02CA/activeSchedule=None
2020-02-27 08:31:56 DEBUG (SyncWorker_5) [pyaarlo] Base Station:new-mode=disarmed,id=mode0
2020-02-27 08:31:56 DEBUG (MainThread) [custom_components.aarlo.alarm_control_panel] supported: 15

Extra Info

Disarming/Arming through the Arlo app itself seems to just change the modes of being armed, either “Armed_Home” or “Armed_Away” in HA.

Disarmed (through Arlo) = “Armed Home” (status in HA)
Armed (through Arlo) = “Armed Away” (status in HA)

Hope this makes sense? :slight_smile:

Thanks for all that. I’ve got my virtualenv running and an hour or two free so I’ll track down the issue!

One thing I did find, the error you reported - Cannot set property ‘value’ of null is coming from the Alarm Panel Card. I don’t see it happening when I use an alarm inside a Glance Card.

Arlo Q Streaming Not Working - posting here for extra coverage.

It looks like the issue is inside the streaming component - Q streaming bug. It looks like a simple solution is to comment out the line that raises the error:

                """ comment out this! """
                raise StopIteration("No dts in packet")

The bug reports also contains a patch that ignores up to 10 dts errors before before stopping the stream because I’m not sure of the consequences of ignoring all dts errors.

If anybody struggling with their Q cameras has the editing skills to try these changes and report back that would be great.

Hi, I have Aarlo-glance card and when I press the card the last movie is played.
I would like to start playing by using using a script instead, is that possible and if
so, how?

Thank you in advance.

It’s possible. I guess you could add an attribute to the camera - or a new variable entity - telling it which video to play and watch that from lovelace card. After that’s it’s just a matter of telling it which video to play and the card will do the rest.