Can't arm/disarm #687
Comments
|
I was going to point you at the other bug raised about this but you already found it. I haven't upgraded to v4 yet, I even bought a bunch of Pro 4 cameras but that didn't seem to help. I'm getting my new set up going and then I'll give the v4 interface a try. |
|
Thank you! I am anxious to hear what you find. As far as I can tell, any new user that wants to use this integration moving forward will need to use v4. I spoke with Arlo and they said there is now no way to share your arlo account with a new arlo user without first upgrading to v4. |
|
I can't turn on v4 yet, it's only available in certain places and where I am doesn't look like it's turned on yet. |
|
To turn it on go to the Arlo app or web dashboard and add a new Pro 5 camera. From there you will be promoted to update. That is the only way from my understanding. Maybe that’s what you already tried.
|
|
Thank you for the 7.3 update! What values do I need to enter for armed home, armed away, and disarmed? I seem to be having the same issues. |
|
I also cannot figure out the proper config for armed home, armed away, and disarmed. |
|
I still don't have a fully working V4 interface going. I'll try and play around with what I have later. I'm assuming you have the location support running? If so you can try: mode_api: v3In your |
|
I have it working here but I want to test it a little more. Then I'll add the config changes needed here. |
|
Can you give 0.7.4b1 a go? You'll need to specify the new api in your config: aarlo:
mode_api: v3That should be all you need to do. If you find you're missing events then set the backend to sse. aarlo:
mode_api: v3
backend: sse |
|
And you have to use the location device not the individual bases. The name will be similar to the old alarm name but with your location name tagged on the end; eg |
|
Thanks for this great integration… have made the addition of the api mode in my configuration, already running SSE, but no change in arm/disarm modes or functions. Not certain what you meant by ‘location device’ in your last comment… can you elaborate? TIA! |
|
You will now have an extra |
|
Hmmm…. I only see my original alarm panel… |
|
First error in log: body-error=JSONDecodeError |
|
I've got somebody else seeing that message. Was there a line with This is a new feature and - of course - it's working for me but seems to be failing for some people. |
|
Did not see a request-text entry anywhere… here is full syntax from three successive entries in the log: 2023-02-03 08:22:40.108 WARNING (SyncWorker_6) [pyaarlo] No locations returned from /hmsdevicemanagement/users/CJ7KJ3-336-59340728/locations |
|
What version are you running? edit: you just found another issue which I'll fix... but I still need the version |
|
I believe 7.4.1B3? It just became available in the update server within the last hour or so. |
|
I just realised you need to enable debug for the component. Can use set you logger up with this and try again. You'll still see the crash - which I will fix - but that logger:
default: info
logs:
custom_components.aarlo: debug
custom_components.aarlo.alarm_control_panel: debug
custom_components.aarlo.binary_sensor: debug
custom_components.aarlo.camera: debug
custom_components.aarlo.light: debug
custom_components.aarlo.media_player: debug
custom_components.aarlo.sensor: debug
custom_components.aarlo.switch: debug
pyaarlo: debug |
|
One other thing to try, delete the session file from |
|
ok - there is this entry: 2023-02-03 09:59:30.297 DEBUG (SyncWorker_2) [pyaarlo] request-text=<!doctype html><title>HTTP Status 404 – Not Found</title><style type="text/css">body {font-family:Tahoma,Arial,sans-serif;} h1, h2, h3, b {color:white;background-color:#525D76;} h1 {font-size:22px;} h2 {font-size:16px;} h3 {font-size:14px;} p {font-size:12px;} a {color:black;} .line {height:1px;background-color:#525D76;border:none;}</style> HTTP Status 404 – Not Found<script>(function(){var js = "window['__CF$cv$params']={r:'793c07e15b950325',m:'DN9.bKQeIEjmcpTgT8XTPTr8cncAlRLszPTKbQYeq0Y-1675436370-0-Aec3cOmGf7Ymq1hAsI6xeA2lh8Ar5L0atvSuDT/JktLN4f9swtGTIelI9sPEOVDOthfQRsnBATE6TGJRgDd8Qfo4ITzPalOK0DnLjPuie1m5UsjjDT/LXcaCybj/bJkP0Nj673agiBYDao+4TPpptTOiIctsNN/VHzEhauFW1xL8g4aoj/Q/K1ImLWwbQBKDkPjKuhibIJw/tSW7U0LXRKO1YpkNhVI8LCWmr5s5rTTXr7h7NHw56AIkhKREtVEqwy0v8Iv22f8pjx4zk2ZQsoE=',s:[0x594e58478b,0x264c7b7138],u:'/cdn-cgi/challenge-platform/h/b'};var now=Date.now()/1000,offset=14400,ts=''+(Math.floor(now)-Math.floor(now%offset)),_cpo=document.createElement('script');_cpo.nonce='',_cpo.src='/cdn-cgi/challenge-platform/h/b/scripts/alpha/invisible.js?ts='+ts,document.getElementsByTagName('head')[0].appendChild(_cpo);";var _0xh = document.createElement('iframe');_0xh.height = 1;_0xh.width = 1;_0xh.style.position = 'absolute';_0xh.style.top = 0;_0xh.style.left = 0;_0xh.style.border = 'none';_0xh.style.visibility = 'hidden';document.body.appendChild(_0xh);function handler() {var _0xi = _0xh.contentDocument || _0xh.contentWindow.document;if (_0xi) {var _0xj = _0xi.createElement('script');_0xj.nonce = '';_0xj.innerHTML = js;_0xi.getElementsByTagName('head')[0].appendChild(_0xj);}}if (document.readyState !== 'loading') {handler();} else if (window.addEventListener) {document.addEventListener('DOMContentLoaded', handler);} else {var prev = document.onreadystatechange || function () {};document.onreadystatechange = function (e) {prev(e);if (document.readyState !== 'loading') {document.onreadystatechange = prev;handler();}};}})();</script> |
|
Did you delete the pickle file? |
|
Not yet, working on it, not on my normal setup. |
|
OK, session.pickle deleted, restart, and same: 2023-02-03 10:44:38.521 WARNING (SyncWorker_8) [pyaarlo] body-error=JSONDecodeError HTTP Status 404 – Not Found<script>(function(){var js = "window['__CF$cv$params']={r:'793c49ffc9d2daed',m:'xvuiaqMi3s2pWwI1z9hYZsBwQ14HJ1jAhQnqVHvP3ik-1675439078-0-AV2MgWIgLNjM9F/HkBI0nC5VU/uS1lF0OfWcWERrJDzwD69rw4VAnLp9QA8H2l2VdXXIz+Te4FQ66ZPLAPZcZ6ZgWGZ8ovGJmdZ+oT2oTtzdUEIK4tOmu7DxywZWSLXbrTYd23uaHXE4OwmrwgHvlmgajkohsqnfMTn+eJE/OPvgXgHnTmKaftriC4oLap19HUuhqwQ+TWMu4p1VdwHqXhle4FviJ+wkAucO6SMwjePo8YYq0095wfjX0baCCJ47lyAuveRUKhqud1h+UziMaWU=',s:[0x116388a35b,0x8c8a533c39],u:'/cdn-cgi/challenge-platform/h/b'};var now=Date.now()/1000,offset=14400,ts=''+(Math.floor(now)-Math.floor(now%offset)),_cpo=document.createElement('script');_cpo.nonce='',_cpo.src='/cdn-cgi/challenge-platform/h/b/scripts/alpha/invisible.js?ts='+ts,document.getElementsByTagName('head')[0].appendChild(_cpo);";var _0xh = document.createElement('iframe');_0xh.height = 1;_0xh.width = 1;_0xh.style.position = 'absolute';_0xh.style.top = 0;_0xh.style.left = 0;_0xh.style.border = 'none';_0xh.style.visibility = 'hidden';document.body.appendChild(_0xh);function handler() {var _0xi = _0xh.contentDocument || _0xh.contentWindow.document;if (_0xi) {var _0xj = _0xi.createElement('script');_0xj.nonce = '';_0xj.innerHTML = js;_0xi.getElementsByTagName('head')[0].appendChild(_0xj);}}if (document.readyState !== 'loading') {handler();} else if (window.addEventListener) {document.addEventListener('DOMContentLoaded', handler);} else {var prev = document.onreadystatechange || function () {};document.onreadystatechange = function (e) {prev(e);if (document.readyState !== 'loading') {document.onreadystatechange = prev;handler();}};}})();</script>2023-02-03 10:44:38.565 WARNING (SyncWorker_8) [pyaarlo] No locations returned from /hmsdevicemanagement/users/CJ7KJ3-336-59340728/locations |
|
Same here. Added API, deleted pickle, added debugger. I am only seeing my original alarm control panel devices.
…________________________________
From: ibaeic ***@***.***>
Sent: Friday, February 3, 2023 9:48 AM
To: twrecked/hass-aarlo ***@***.***>
Cc: kneeboy03 ***@***.***>; Author ***@***.***>
Subject: Re: [twrecked/hass-aarlo] Can't arm/disarm (Issue #687)
OK, session.pickle deleted, restart, and same:
2023-02-03 10:44:38.521 WARNING (SyncWorker_8) [pyaarlo] body-error=JSONDecodeError
2023-02-03 10:44:38.562 INFO (MainThread) [homeassistant.setup] Setup of domain zone took 0.8 seconds
2023-02-03 10:44:38.564 DEBUG (SyncWorker_8) [pyaarlo] request-text=<!doctype html><title>HTTP Status 404 – Not Found</title><style type="text/css">body {font-family:Tahoma,Arial,sans-serif;} h1, h2, h3, b {color:white;background-color:#525D76;} h1 {font-size:22px;} h2 {font-size:16px;} h3 {font-size:14px;} p {font-size:12px;} a {color:black;} .line {height:1px;background-color:#525D76;border:none;}</style>
HTTP Status 404 – Not Found
<script>(function(){var js = "window['__CF$cv$params']={r:'793c49ffc9d2daed',m:'xvuiaqMi3s2pWwI1z9hYZsBwQ14HJ1jAhQnqVHvP3ik-1675439078-0-AV2MgWIgLNjM9F/HkBI0nC5VU/uS1lF0OfWcWERrJDzwD69rw4VAnLp9QA8H2l2VdXXIz+Te4FQ66ZPLAPZcZ6ZgWGZ8ovGJmdZ+oT2oTtzdUEIK4tOmu7DxywZWSLXbrTYd23uaHXE4OwmrwgHvlmgajkohsqnfMTn+eJE/OPvgXgHnTmKaftriC4oLap19HUuhqwQ+TWMu4p1VdwHqXhle4FviJ+wkAucO6SMwjePo8YYq0095wfjX0baCCJ47lyAuveRUKhqud1h+UziMaWU=',s:[0x116388a35b,0x8c8a533c39],u:'/cdn-cgi/challenge-platform/h/b'};var now=Date.now()/1000,offset=14400,ts=''+(Math.floor(now)-Math.floor(now%offset)),_cpo=document.createElement('script');_cpo.nonce='',_cpo.src='/cdn-cgi/challenge-platform/h/b/scripts/alpha/invisible.js?ts='+ts,document.getElementsByTagName('head')[0].appendChild(_cpo);";var _0xh = document.createElement('iframe');_0xh.height = 1;_0xh.width = 1;_0xh.style.position = 'absolute';_0xh.style.top = 0;_0xh.style.left = 0;_0xh.style.border = 'none';_0xh.style.visibility = 'hidden';document.body.appendChild(_0xh);function handler() {var _0xi = _0xh.contentDocument || _0xh.contentWindow.document;if (_0xi) {var _0xj = _0xi.createElement('script');_0xj.nonce = '';_0xj.innerHTML = js;_0xi.getElementsByTagName('head')[0].appendChild(_0xj);}}if (document.readyState !== 'loading') {handler();} else if (window.addEventListener) {document.addEventListener('DOMContentLoaded', handler);} else {var prev = document.onreadystatechange || function () {};document.onreadystatechange = function (e) {prev(e);if (document.readyState !== 'loading') {document.onreadystatechange = prev;handler();}};}})();</script>
2023-02-03 10:44:38.565 WARNING (SyncWorker_8) [pyaarlo] No locations returned from /hmsdevicemanagement/users/CJ7KJ3-336-59340728/locations
—
Reply to this email directly, view it on GitHub<#687 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AOD733GY5B55UYRLKVU2OY3WVUSGBANCNFSM6AAAAAAT6MVA24>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
I've just pushed another beta that includes some URL changes - to bring it more into line with the Arlo web page. If this doesn't work are either of you comfortable looking at packets in a browser (Via the debug tools, I'm in Canada so the servers I'm getting may be working differently than yours. |
|
Results notwithstanding, happy to try to help in any way I can! |
|
Sad to report no change for me. Same errors. |
|
Hostname change did it for me - no longer do I get a JSON decode error in
the response. Another alarm_control_panel.location_Name entity has
appeared and is working properly.
Thanks once again good sir!
…-Joe
On Sun, Nov 19, 2023 at 1:04 PM Steve Herrell ***@***.***> wrote:
That's perfect. I could load that file into Chrome and check the packet
ordering.
A few things:
-
There is a small difference in packet ordering, *pyaarlo* sends a
*devices* request then a *location* request. The official website
seems to reverse that. I'll try altering this in *pyaarlo*.
-
My test location login has a different value in the result of the v3
session request. I don't know what this means. Yours shows:
canUserMigrate: true
Mine shows:
canUserMigrate: false
I'll keep looking to see if I spot any other differences.
In the meantime, some random things to try:
- Try a different user agent:
aarlo:
...
user_agent: linux
- Try changing the authentication headers a little:
aarlo:
...
send_source: true
-
Try caching the auth session - remove the save_session: false piece.
-
Poke around on the official website with the HA login? Maybe there is
a setting you can alter or change the name of the location that comes with
the login. (This is clutching at straws...)
—
Reply to this email directly, view it on GitHub
<#687 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ANUCNHBLKNKR5HINWIX3AFTYFJC3XAVCNFSM6AAAAAAT6MVA26VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJXHEZTGMRVGU>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
Joe Rainey
***@***.***
(407)491-8234
"Experience is something you usually get just after you need it..." -
Steven Wright
|
|
Ok, so I've tried a few tests (each by updating config, rebooting, then calling the change modes service to each of the 3 modes):
The logs can be found here: I initially tried moving all of my aarlo: configuration.yaml config to aarlo.yaml but it wouldn't load the integration so I reverted back. In each of the log files there are some notes, but I didn't see anything obviously different from previous runs (I'm not sure what to be looking for - mainly was trying to search for errors around instances of the mode name (armHome/armAway/standby). EDIT: Thanks a million @twrecked !
|
|
That's great news! And as you've noticed you end up with 2 locations, there is the one you share and the one Arlo gives you for free with the account. The second one you kind of have to ignore... |
|
Following along but still having this issue. Cameras all work fine, I can update the alarm status via automations and can update the status via the alarm_set_mode service, but the location still shows unavailable. I also have two physical locations and both show here, but both unavailable.
|
|
@dugancom |
|
Ok, here's the errors from the log. Working on sanitizing and posting the whole thing 2023-11-23 09:50:07.400 ERROR (MainThread) [homeassistant.components.alarm_control_panel] Platform aarlo does not generate unique IDs. ID left_side is already used by alarm_control_panel.aarlo_left_side - ignoring alarm_control_panel.aarlo_left_side |
|
Encrypted logs. |
|
Thanks. I got it. One thing, you have 2 cameras with the same name "Left Side", can you log in with the Home Assistant account on the main Arlo page and check that. The code can't handle that at the moment. I've had this happen, I upgraded some cameras and the name changes never made it to the second account, they don't always follow the main account. |
|
If you turn on very verbose debug and send me those logs I can take a look. You aren't getting any locations returned so the verbose log would help with that. |
|
I think I see the other camera now, I keep getting logged out because of being logged into two locations so I'll shut down ha and work on it. It'll take me a bit but I'll upload the new logs. |
|
OK, fixed the double Left and turned on very verbose. |
|
I'm not seeing the verbose debug and I realise this is my fault, I should have realised this, you're on the new alpha so you need to add the debug stuff into # aarlo.yaml
aarlo:
... current config
verbose_debug: True
packet_dump: TrueBut from what I can see you aren't getting any locations returned. |
|
Ok, try these. I didn't look at them yet but the file is bigger. And I get a location for each of the physical places in Entities
|
|
This one is great, thanks. I'll take a look. |
|
@dugancom pr #841 should fix it, can you try the latest alpha? I was calling a method that didn't exist... And you are going to get |
|
Ok, downloaded and restarted but everything looks the same. Anything ese I should do to flush it? Logs attached just in case. |
|
You did great, give me a few minutes, there was another missing call. Apologies, I don't have any setup using Locations so I do rely on other people for this. |
|
Can you try again - alpha 9. And we'll see where it dies this time... |
|
Got it! Everything is working, I can change alarm mode manually now. As you said I have a location for each location and the controls work as expected. Thanks so much, appreciate all of the help! If ever you need to test something again I'm happy to help, Here's a last set of logs if it's useful. Thanks again! |
|
@dugancom That's great it's working and the logs look good. Thanks for trying the alpha and I really appreciate the offer of help because, like I said, I'm flying a bit blind on the location stuff. |
|
You bet, just let me know. |
|
Hi Steve…Question: I’ve just added a second hub to improve the Arlo WiFi networking coverage. I moved one camera to the new hub, and now the HA integration does not seem to detect that camera.Do you support multiple hubs? If so, is there something I can do to get this working?Thanks in advance as always for your amazing integration, and your very gracious assistance to all of us out here in open-source land.Cheers,JoeJoe Rainey(407)491-8234On Nov 19, 2023, at 2:41 PM, Steve Herrell ***@***.***> wrote:
That's great news!
And as you've noticed you end up with 2 locations, there is the one you share and the one Arlo gives you for free with the account. The second one you kind of have to ignore...
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
|
|
We support multiple hubs. You might need to re-share the camera. |
|
Aah, of course! One might think I’d been bitten enough by that to remember it!Thank you once again,JoeJoe Rainey(407)491-8234On Dec 17, 2023, at 7:29 AM, Steve Herrell ***@***.***> wrote:
We support multiple hubs. You might need to re-share the camera.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
|
|
I'm guessing the arm disarm is still TBD for non-basestation cameras? |
|
Same question from my side. I have an old Arlo Q standalone camera without base station and can not set the mode (armed/disarmed) from the alarm_control_panel. I can change modes in the control panel in HA but it does not have an effect on Arlo as reported in the app and vice versa. Running HA on a Raspberry 4 |
|
@twrecked, User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/121.0.0.0 Safari/537.36 {"mode":"standby"} For Armed home and away, the general put was the same but the json was {"mode":"armAway"} {"mode":"armHome"} {"mode":"standby"} If I have time sometime soon, I'll try to read over the code and see if this is just a matter of identifying a non-base camera setup and a different way to send the arm commands, which it likely is. Not going to promise I can delve into your whole code and figure it all out in a weekend and I spend all day messing with piece-meal code from others or stuff I wrote in a rush. So, I'm usually burnt by the time I get home. If anyone else feels froggy, look at the github repo and find the commands currently in use and how the logic plays out to see if you can help. It's only one person doing this and I'm sure hey have a life and bills. :-) |
|
@cswinney22 If you turn on verbose debugging you can capture exactly what Aarlo is trying to send to the backend. But you are probably right, they might have changed something. But can you continue this in #887 somebody else is seeing your issue. |
Will do. Thanks! |
I have older Pro2 cameras (hub based), a light, and a doorbell. In order for me to create a new user (to integrate with HA), I had to upgrade to the new Arlo interface. This is done by adding a new hypothetical Pro5 camera in Arlo. By doing this, some things are no longer supported, such as custom modes and scheduled modes on older cameras.
Anyway, I am now able to connect Home Assistant but I cannot switch modes. I used to have separate modes for the light, doorbell, and the hub. Now it is combined into one mode for all devices with the options:
When I setup my yaml configuration home and away modes as "armed" and "home", I am able to toggle it in HA but it does not pass to Arlo
When looking in my chrome developer log, it is sending "armAway", "armHome", and "standby" when I switch modes in Arlo. When I change by yaml configuration to those values, I am no longer able to toggle modes in HA and they also do not change the Arlo mode. I have also tried "Arm Away", and "arm away".
Any help would be appreciated!
The text was updated successfully, but these errors were encountered: