object_type attribute of last_capture no update

[mattews90]

hello, lately the object_type attribute of last_capture is no longer being updated properly, making it impossible to detect people.

[twrecked]

It's working for me. Can you collect some debug for me.

What kind of cameras are you using? What plan are you on? I know Arlo is changing things on their back end.

[mattews90]

Excuse me, I have 4 arlo pro 3 with Arlo Secure plan. My configuration is this:

aarlo: host: https://my.arlo.com username: !secret arlo_user password: !secret arlo_pass user_agent: linux db_motion_time: 30 db_ding_time: 10 recent_time: 10 last_format: "%m-%d %H:%M" refresh_devices_every: 2 stream_timeout: 120 reconnect_every: 90 verbose_debug: false backend: sse tfa_source: imap tfa_type: email tfa_host: "imap-mail.outlook.com:993" tfa_username: !secret GV_USER tfa_password: !secret GV_PASS

#Arlo Integration alarm_control_panel:

• platform: aarlo code: "****" away_mode_name: AWAY home_mode_name: HOME trigger_time: 150 alarm_volume: 8

sensor:

• platform: aarlo monitored_conditions:
  • total_cameras
  • last_capture
  • recent_activity
  • captured_today
  • battery_level
  • signal_strength

binary_sensor:

• platform: aarlo monitored_conditions:
  • motion
  • sound
  • ding
  • cry
  • connectivity

camera:

• platform: aarlo ffmpeg_arguments: "-pred 1 -q:v 2"

light:

• platform: aarlo

switch:

• platform: aarlo siren: True all_sirens: True snapshot: True doorbell_silence: True siren_volume: 1 siren_duration: 10

media_player:

• platform: aarlo

[twrecked]

I have a very similar set up so you should be seeing the objects. If you can try to get some debug that would help.

One thing to try might be add this to your aarlo config. This will clear out the authentication cache and log in again.

aarlo:
  ...
  save_session: False

[juju159]

Hello @twrecked ,

I have exactly the same issue on one Camera.

save_session: False doesn't resolve the issue

I will give you logs files soonly

[juju159]

Hello @twrecked,

On the picture, 11:30 sensor.last_exterieur sensor: The object_type attribute is Animal and should be a Person as shown on the Arlo application. I copy also the encrypted log. Restart application & remove cache has no effect.

Encrypted_logs.txt

[mattews90]

Sorry for the delay in responding, I too object_type of the sensor sensor.aarlo_last_camere should have changed at 13:10:36 in person but it is animal. Instead looking in the library of lovelace-hass-arlo (v0.2.6.1) the object is correct and results in person. I am attaching debug related to what has been said. logarlo.txt

[mattews90]

[twrecked]

Thanks for the debug, I'll take a look.

One quick thing to try is this option. I remember the Arlo back end can have issues with February have 28 days.

aarlo:
  ...
  library_days: 27

[mattews90]

I entered the text library_days: 27 and it doesn't work. However, I noticed that the object_type attribute is updated with the previous last_capture's object_type, i.e. everything is shifted by 1.

[twrecked]

I think I found the issue. I'm thinking about the correct fix, I'll push something tomorrow.

[twrecked]

Can you try the latest beta, I reverted a change.

[juju159]

Can you try the latest beta, I reverted a change.

Hello @twrecked , Just tested. it seems work with this version: This one https://github.com/twrecked/hass-aarlo/releases/tag/v0.7.4b9 BR. J.

[rafuz]

I am having the same issue but the latest beta does not fix it. However it would be nice to have a binary sensor for each object category. I am relying on a template sensor based on last_capture to get a "person" alarm in home assistant.

EDIT: I see that last_capture and captured_today only updates when I restart home assistant.

Additional Info:

Seems to update when I restart home assistant or once a day at 00:00

[rafuz]

I have changed the backend to SSE and now it works!

[github-actions[bot]]

This issue is stale because it has been open for 365 days with no activity. This issue will be automatically closed within 28 days if there is no further activity.

[crivchri]

Hi,

I have the same (or similar) issue here with v0.8.1.3, where the sensor 'sensor.aarlo_last_' is not (never) updated on motion detected on any of my cameras. However the sensor 'binary_sensor.aarlo_motion_' is correctly updated on motion detected.

I can provide with additional information, to help resolve this issue. Just let me know what you need.

Kind regards.

[twrecked]

Can you start by pasting in /config/aarlo.yaml.

[crivchri]

Can you start by pasting in /config/aarlo.yaml.

Hi @twrecked,

Thank you for your reply!

My /config/aarlo.yaml file is:

version: 1
aarlo:
  reconnect_every: 90
  backend: sse
  save_updates_to: "/config/media"
  save_media_to: "/config/media/${SN}/${Y}/${m}/${d}/${T}"
  stream_snapshot: true
  stream_snapshot_stop: 10
  snapshot_timeout: 15
  user_agent: linux
  snapshot_checks:
  - 1
  - 5

[twrecked]

One question, can you see the video recordings on the real Arlo app?

Before we get to debug can you try the following:

• Can you add the following to the aarlo: section of aarlo.yaml config:

  media_retry:
   - 5
   - 15
   - 25

• Can you try removing the backend setting?

If that doesn't make any difference then we need to turn on verbose debug.

[crivchri]

One question, can you see the video recordings on the real Arlo app?

Before we get to debug can you try the following:

• Can you add the following to the aarlo: section of aarlo.yaml config:

  media_retry:

   - 5

   - 15

   - 25

• Can you try removing the backend setting?

If that doesn't make any difference then we need to turn on verbose debug.

Hi @twrecked,

Thank you for your answer.

I confirm that I can see the video recordings in the real Arlo app. However, I am not 'hosting' them in the Arlo's cloud (also no subscription), only locally on the SD card in the base station.

I have set the 'media_retry' setting and removed the 'backend' setting, as you recommended. But the same issue remains.

Do you need me to to turn on verbose debug? Or do you have another idea?

Kind regards!