Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot arm or disarm location_home #843

Closed
brenmcg57 opened this issue Nov 26, 2023 · 21 comments
Closed

Cannot arm or disarm location_home #843

brenmcg57 opened this issue Nov 26, 2023 · 21 comments

Comments

@brenmcg57
Copy link

brenmcg57 commented Nov 26, 2023

I had a working installation with an automation to arm and disarm the Home location. This stopped working a few days ago. When I try clicking the Arm Home or Arm Away buttons of the location_home card, I get the following popup at the bottom of the screen:

Failed to call service alarm_control_panel/alarm_arm_home. 'NoneType' object has no attribute 'get'

I only have the default Aarlo recommended config sections.

I tried a clean HA install and got the same result. I also tried allowing upgrades to the .8 beta versions. No change in behavior.
Keep in mind that my 2FA is working fine. I can see the camera and interact with their cards.

Maybe not interesting, but now the user_location_home (not to be confused with location_home) card has both arm and disarm buttons and they are interactive, but my Arlo app shows no effect of clicking them. Only the location_home buttons did anything before.

@twrecked
Copy link
Owner

Anything in here help: #687

Other than that I will need

  • the version you are using
  • your config (minus the sensitive pieces)
  • and some debug logs, see here and here on how to encrypt the logs.

@anachronox99
Copy link

anachronox99 commented Nov 27, 2023

Hi I have the same problem.

the Alarm panel that got setup once i installed aarlo does not change its status when I change it in the Arlo mobile app or website. So if I change Alarm status from Armed_away to Disabled in the app, the HA entity status does not change.

Likewise changing it in HA does not reflect the change to Arlo app.

HA info:
Core
2023.11.3
Supervisor
2023.11.3
Operating System
11.1
Frontend
20231030.2

my config:

aarlo:
  host: https://my.arlo.com
  username: XXX
  password: XXX
  db_motion_time: 30
  db_ding_time: 10
  recent_time: 10
  last_format: '%d-%m %H:%M'
  refresh_devices_every: 2
  tfa_host: 'imap.gmail.com'
  tfa_username: XXX
  tfa_password: XXX
  backend: sse

alarm_control_panel:
  - platform: manual  
    code: XXX
    code_arm_required: true
    name: Home alarm
    #pending_time: 3
    arming_time: 3
  - platform: aarlo
    away_mode_name: Armed
    disarmed_mode_name: Disarmed
    trigger_time: 30
    alarm_volume: 8

@brenmcg57
Copy link
Author

brenmcg57 commented Nov 27, 2023

Update: I don't think its the aarlo plugin right now. I think I might have run afoul of some Arlo WAF. I cannot login to my dashboard in the browser from my home network. The instant I click login I get a banner on their site that I have No Internet. (lol ok,) or an instant "Request Timed Out."

If I get behind another public IP using a vpn, I can authenticate. I came across this thread and I am trying to confirm I'm having a similar issue: https://community.arlo.com/t5/Arlo-Pro/You-are-unable-to-access-ocapi-app-arlo-com/m-p/1920672

@brenmcg57
Copy link
Author

brenmcg57 commented Nov 28, 2023

I was able to confirm that I am having the issue linked in my post just above this. Chrome devtools shows me:

Access to XMLHttpRequest at 'https://ocapi-app.arlo.com/api/auth' from origin 'https://my.arlo.com' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.

I believe I am dealing with two issues. I originally posted when I could still interact with my cameras but I could not change the alarm panel mode. Now I have a new issue, where I am blocked from authenticating to my arlo cloud instance from my public IP. I am trying to get Arlo support to unblock my IP. Maybe that'll magically fix my first issue.

@twrecked
Copy link
Owner

Good luck with the blocking issue. Is there any way you can get a new IP?

@anachronox99 (and @brenmcg57 when you're unblocked) try removing the host: config, getting locations from my.arlo.com fails.

@anachronox99
Copy link

HI @twrecked -> so remove the host line altogether, not replace it with some other values?

@twrecked
Copy link
Owner

Yes, remove it, the default (https://myapi.arlo.com) is correct.

@anachronox99
Copy link

OK did that and restarted. My Arlo app shows my status as "Arm Home" and home assistant shows status as armed_away. I then tried to disarm in HA from the Alarm panel lovelace element by clicking 'Disarm' and nothing happened. I then went to the Arlo app and changed status to 'Standby' and waited a minute - HA did not refresh it's status.

@twrecked
Copy link
Owner

@anachronox99 I'm going to need some logs.

Turn on verbose debug.

And encrypt it with the link in that section.

@anachronox99
Copy link

Here you go

homeassistant.log
homeassistant-1.log

@twrecked
Copy link
Owner

There was no arlo related debug in the logs. You need to update your config and reboot. There will be a lot of stuff from aarlo and pyaarlo.

@anachronox99
Copy link

homeassistant.log
ok pls try this. I did a grep and there was some aarlo content not much though.

@twrecked
Copy link
Owner

My bad, I missed a step. You need to add this to you configuration.yaml to turn on the logging. You'll know when it's working - there is a lot of debug.

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

@anachronox99
Copy link

My bad, I missed a step. You need to add this to you configuration.yaml to turn on the logging. You'll know when it's working - there is a lot of debug.

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

New logs:
homeassistant.log

@brenmcg57
Copy link
Author

Looks like my public IP finally got unblocked by Arlo.com security. Who knows, maybe there was a cooldown period. I didn't try to authenticate for 24 hours then was able to login to my Arlo dashboard from a browser.

Since I had butchered my Aarlo instance I started clean with a new install on the latest stable. No problems now! I can interact with all cameras and arm/disarm location_home.

I kind of wish I'd discovered something that could have helped @anachronox99. I'm happy to provide anything from my setup that might be useful for comparison.

@twrecked
Copy link
Owner

twrecked commented Nov 29, 2023

@brenmcg57 That's great. Sometimes you just need to give them time to forget you!

@anachronox99 Logs look good, I'll take a good look at them.

edit:
@anachronox99 Which alarm are you trying to arm? I can see 3 being created.

@anachronox99
Copy link

I made 3 attempts to arm the alarm.

  1. From the UI, I hit Disarm in the lovelace element.
image
  1. From the dev panel, I called a service - first trying to arm it, then trying to disarm it.
image

@twrecked
Copy link
Owner

You've been moved over to locations so that one doesn't work anymore. This is an Arlo thing.

Look for an entity called alarm_control_panel.location_Home.

@anachronox99
Copy link

yup that fixed it! Thanks. so I now appear to have 3 alarm_control_panel entities created - the second one works. I'll disable the others.

image

@twrecked
Copy link
Owner

It's a pain for sure. I'll look to tidy this up later. Disabling for now is the way to go.

@brenmcg57
Copy link
Author

Looks like we're both operational.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants