Unable to set modes with the new Arlo user experience

[jtgentry]

Long story short, this was all working perfectly until I added an account for my son which forced me to upgrade to the new user experience. The integration was failing to load until I also upgraded the HomeAssistant Arlo account to the new user experience. I can now see the cameras in hass but I can't set any modes. It appears Arlo eliminated custom modes so there's no way to set "night" mode anymore. You only get Arm Away, Arm Home and Standby. When I try to set a mode I get the following message:

2023-06-18 08:21:40.403 DEBUG (SyncWorker_6) [custom_components.aarlo.alarm_control_panel] Arlo set mode to armed
2023-06-18 08:21:40.404 DEBUG (SyncWorker_6) [pyaarlo] multilocation, deduced v3 api
2023-06-18 08:21:40.404 DEBUG (SyncWorker_6) [pyaarlo] BaseStations don't have modes in v3

Let me know if you need additional logging or snippets from my yaml(s). I've been having this issue for a couple of weeks but didn't want to bother anyone until I've done my due diligence.

[johnnybhuang]

hey, did you point the entity to "user_location_home" / alarm_control_panel.aarlo_user_location_home ?

[jtgentry]

I must be misunderstanding your question b/c "user_location_home" does not appear to be an attribute of "alarm_control_panel". I tried a few combinations in my configuration.yaml but nothing would pass the check prior to allowing a reboot. FWIW, I only have one "Home" so I guess I would expect "location.py" to only come back with one option.

[johnnybhuang]

strange... I have "alarm_control_panel.aarlo_user_location_home" in my HA... I'll paste my config / screenshot bit later on when I'm back on my laptop for you if that helps...

[jtgentry]

Yes please! Thanks!

[johnnybhuang]

here's what I have in my configuration.yaml ...

alarm_control_panel:

• platform: aarlo away_mode_name: armAway disarm_mode_name: Standby home_mode_name: Standby trigger_time: 30 alarm_volume: 8

Here's my alarm_panel config too

[jtgentry]

Your configuration.yaml looks very similar to mine (shouldn't your disarm_mode_name actually be disarmed_mode_name per the documentation?):

...and here are the entity ids under alarm_control_panel:

I'm up-to-date on aarlo releases so I have no idea why ours would differ or if this even matters in the first place.

[jtgentry]

Given the debug message about "BaseStations don't have modes in v3" maybe this is a known issue and perhaps difficult to fix? Once everyone is forced to the new user experience, perhaps it will get some attention. I'm kind of annoyed that I was forced into the new UI since everything was working so well.

FWIW, I was able to get the Arlo app's geofencing and scheduling features to work which is all I was using Aarlo for in the first place. Although this does limit what I can do I'm at least back to where I was before this.

[twrecked]

Sorry, I was busy at work, I have an account with the new modes enabled but it doesn't have anything "real" on it so it's not much use for testing.

But I was under the impression with the new interface you couldn't change individual base stations.

I you want to capture and encrypt some debug I can take a look.

[jtgentry]

No worries! I appreciate all the effort you've put in to get this working. I know it can't be easy since Arlo doesn't provide an official API and keeps changing stuff on us!

Unfortunately the aarlo integration isn't currently loading due to the authentication issue that you're already working on. Once that is resolved I can upload some logs.

[gones01]

hey there, thanks for looking at this today, I really appreciate your work! I am now able to authenticate

However, I am curious if this is a different issue or related to the changes you had just made? When I attempt to change the modes it fails.

2023-07-04 17:04:01.793 WARNING (SyncWorker_0) [pyaarlo] attempt 1: error in response when setting mode= {'data': {'error': 'AUTO-5050', 'message': 'Failed to update Automation Definitions', 'reason': 'Unable to upload active automation. Please try again'}, 'success': False} 2023-07-04 17:04:02.195 WARNING (ArloBackgroundWorker) [pyaarlo] attempt 2: error in response when setting mode= {'data': {'error': 'AUTO-5050', 'message': 'Failed to update Automation Definitions', 'reason': 'Unable to upload active automation. Please try again'}, 'success': False} 2023-07-04 17:04:02.609 WARNING (ArloBackgroundWorker) [pyaarlo] attempt 3: error in response when setting mode= {'data': {'error': 'AUTO-5050', 'message': 'Failed to update Automation Definitions', 'reason': 'Unable to upload active automation. Please try again'}, 'success': False} 2023-07-04 17:04:02.855 ERROR (ArloBackgroundWorker) [pyaarlo] Failed to set mode.

[ninjazx06]

I am also getting the above errors trying to set mode:

2023-07-04 22:51:28.232 WARNING (SyncWorker_8) [pyaarlo] attempt 1: error in response when setting mode= {'data': {'error': 'AUTO-5050', 'message': 'Failed to update Automation Definitions', 'reason': 'Unable to upload active automation. Please try again'}, 'success': False} 2023-07-04 22:51:28.489 WARNING (ArloBackgroundWorker) [pyaarlo] attempt 2: error in response when setting mode= {'data': {'error': 'AUTO-5050', 'message': 'Failed to update Automation Definitions', 'reason': 'Unable to upload active automation. Please try again'}, 'success': False} 2023-07-04 22:51:28.787 WARNING (ArloBackgroundWorker) [pyaarlo] attempt 3: error in response when setting mode= {'data': {'error': 'AUTO-5050', 'message': 'Failed to update Automation Definitions', 'reason': 'Unable to upload active automation. Please try again'}, 'success': False} 2023-07-04 22:51:28.917 ERROR (ArloBackgroundWorker) [pyaarlo] Failed to set mode.

and also seeing this too:

2023-07-04 23:01:26.659 WARNING (ArloBackgroundWorker) [pyaarlo] error in response={'data': {'error': '500', 'message': 'INTERNAL_SERVER_ERROR', 'reason': 'INTERNAL_SERVER_ERROR'}, 'success': False}

[bjorrwahman]

Im having the same problem, after the authentication fix (version b17)I can now see cameras and status but I get the same error as above when trying to set the alarm status.

[bjornwahman]

Having this issue: From my log:

Logger: pyaarlo Source: custom_components/aarlo/pyaarlo/init.py:720 Integration: Arlo Camera Support (documentation, issues) First occurred: 10:05:33 (3 occurrences) Last logged: 10:05:34

attempt 1: error in response when setting mode= {'data': {'error': 'AUTO-5050', 'message': 'Failed to update Automation Definitions', 'reason': 'Unable to upload active automation. Please try again'}, 'success': False} attempt 2: error in response when setting mode= {'data': {'error': 'AUTO-5050', 'message': 'Failed to update Automation Definitions', 'reason': 'Unable to upload active automation. Please try again'}, 'success': False} attempt 3: error in response when setting mode= {'data': {'error': 'AUTO-5050', 'message': 'Failed to update Automation Definitions', 'reason': 'Unable to upload active automation. Please try again'}, 'success': False}

[shissam]

i believe I am still on the "old" user experience. having the same errors as @bjornwahman, @ninjazx06 (but not the INTERNAL_SERVER_ERROR), @gones01

[ninjazx06]

Just to clarify, I believe I am also on the "old" user experience (because I don't know what the new Arlo experience is and my experience hadn't change).

[pluusla]

Same here, old ui but the same AUTO-5050 error

[jtgentry]

Here is what the new user experience app looks like:

[shissam]

i believe I am still on the "old" user experience. having the same errors as @bjornwahman, @ninjazx06 (but not the INTERNAL_SERVER_ERROR), @gones01

@twrecked @jtgentry two things - (1) yes, I am definitely on the "old" user experience,

and

(2) I can now confirm that the AUTO-5050 error is independent of HA... that is I have a pyaarlo "0.8.0b9" custom app which was able to set the base station mode directly using the pyaarlo object base (e.g., base.mode = 'disarmed') when I tried that just now using pyaarlo I got:

base: name=(redacted),state=available,mode=Armed Day Home,sched=True,schednam=schedule.1
['disarmed', 'armed', 'armed day home', 'armed home with driveway alert', 'armed night home', 'schedule.1']
disarming...
2023-07-05 16:03:41,217 - pyaarlo - WARNING - attempt 1: error in response when setting mode=
{'data': {'error': 'AUTO-5050',
          'message': 'Failed to update Automation Definitions',
          'reason': 'Unable to upload active automation. Please try again'},
 'success': False}
base: name=(redacted),state=available,mode=Armed Day Home,sched=False,schednam=None
arlo: lasterr=None,conn=True
NOW leaving USR1 snippet
10
USR1: DONE exec someting ...
done on do snippet
2023-07-05 16:03:41,684 - pyaarlo - WARNING - attempt 2: error in response when setting mode=
{'data': {'error': 'AUTO-5050',
          'message': 'Failed to update Automation Definitions',
          'reason': 'Unable to upload active automation. Please try again'},
 'success': False}
2023-07-05 16:03:42,106 - pyaarlo - WARNING - attempt 3: error in response when setting mode=
{'data': {'error': 'AUTO-5050',
          'message': 'Failed to update Automation Definitions',
          'reason': 'Unable to upload active automation. Please try again'},
 'success': False}
2023-07-05 16:03:42,358 - pyaarlo - ERROR - Failed to set mode.
<RequestsCookieJar[Cookie(version=0, ...(redacted)>

[bjorrwahman]

With the latest update I can confirm that I can set states again. Thank you

[Minski87]

Hi is there any news for setting the modes (armed, home,standby) from the new user interface? I can't get the modes to run. Cameras and the rest everything runs.

[SebaGaillard74]

Hello everyone!

I've finally found a solution to get my cameras armed by an automation with new interface

The problem is a change in the way to get the activation mode in the arlo app. Before, the cameras can be activated individually. Or, now, you have to enable all of them or nothing.

The solution is simple: instead off calling Arlo Camera Support "Alarm Set Mode" in your automation, you have to create a new action who use the entity "alarm_control_panel.aarlo_location_XXXXXX" where XXXXX is the name of your location set up in your arlo app.

And if you have doorbells, and you doesn't want to enable them in the armed away mode, it's simple: either you use a armed home mode with only your cameras, or just go on the app arlo > routines > armed away> click on the device that you doesn't want to be enabled> delete device

hope that's help someone. Sorry for the approximate English.

PS: if you want the new app on the arlo, you can force by trying to add a new device> camera> Pro series> Pro 5. At this time, your app should ask you to switch to the new app

[pesce]

I have "alarm_control_panel.aarlo_location_home" in my entity list, when I click on it, it shows the various modes and I can interact with these modes... But when I try to set up an automation using "call service" I cannot locate "alarm_control_panel.aarlo_location_home" in the list. What am I doing wrong? Thank you!

[pesce]

Figured it out: