twrecked / hass-aarlo

Asynchronous Arlo Component for Home Assistant
GNU Lesser General Public License v3.0
394 stars 78 forks source link

Error: session start failed - No changes in HA anymore #942

Open Phoenix-DH opened 6 months ago

Phoenix-DH commented 6 months ago

Hello together,

I just recognized that after some time, 2-3 days, my aarlo integration is not reflecting anymore the correct information related to what I see in the app. This morning I found that:

Logger: pyaarlo
Source: custom_components/aarlo/__init__.py:406
integration: Arlo Camera Support ([documentation](https://github.com/twrecked/hass-aarlo/blob/master/README.md), [issues](https://github.com/twrecked/hass-aarlo/issues))
First occurred: 7:30:29 AM (2 occurrences)
Last logged: 7:30:29 AM

session start failed
error in new response={'meta': {'code': 400, 'error': 9204, 'message': 'Browser is not trusted'}}

Is this already known? Is that related?

twrecked commented 6 months ago

This is a new one. Is this every 2-3 days or is this the first time this happens?

You can try this:

delete .aarlo/session.pickle and restart, this will force Aarlo to log in again.

If that doesn't fix it can you capture some debug logs.

Phoenix-DH commented 6 months ago

I did, that is the result of the log:

Logger: pyaarlo
Source: custom_components/aarlo/__init__.py:406
integration: Arlo Camera Support ([documentation](https://github.com/twrecked/hass-aarlo/blob/master/README.md), [issues](https://github.com/twrecked/hass-aarlo/issues))
First occurred: 6:49:13 PM (1 occurrences)
Last logged: 6:49:13 PM

error in new response={'meta': {'code': 400, 'error': 9204, 'message': 'Browser is not trusted'}}

Not exactly the same, but I can imagine it is the same. I deleted the file and then did a restart of the aarlo via UI. I have the latest beta installed.

To be honest, I do not pretty know when it started, but I think with one of the latest 2 releases. I did onyl recognize it by accicdent. State in HA was different than in the app.

And what I also recognized today is that my cams won't record anymore. But within the app and the webpage all is fine, I can do a live preview... turn it on and off and switch the modes.

Don't know what happens here.

In germany there will be a public holiday tomorrow, I think on friday I am able to do it.

twrecked commented 6 months ago

Can you paste aarlo.yaml there may be something there we can change.

And try deleting .aarlo/cookies.txt as well.

Phoenix-DH commented 6 months ago

I deleted the file too, still the same.

aarlo.yaml? I was wondering if that file is still needed after config flow implementation? Not much in:

version: 1
aarlo:
  mqtt_host: mqtt-cluster-z1.arloxcld.com

Everything is managed with recording in the native app. Only state changed via HA.

twrecked commented 6 months ago

It's the new overflow config file: https://github.com/twrecked/hass-aarlo#coming-from-earlier-versions

Does the account still have admin access?

I need some debug to see what is happening. There might be some part of the login procedure I need to change.

Phoenix-DH commented 6 months ago

Ah ok 👌🏻

Yes, everything as normal. Will have an eye on and keep trying to get debug logs on friday.

Good thing is that suddenly recording is working again. Maybe really something on Arlo backend.

adfleshner commented 5 months ago

I am also recieving this error when first trying to login to a gmail account using tfa. Im not sure where in the code it is trying to do the login so I am unsure where to add any code to try and fix the issue. I would be willing to help if I could get a run down on how the code does the login. I really want these cameras as apart of my HA but I cant get past the login set at the moment. Thanks in advance.

twrecked commented 5 months ago

@adfleshner Try playing with some of the setting in this section. You might need to change the user agent to Linux to get it to work. But, it could be any one of the other things that affects this piece.

adfleshner commented 5 months ago

Ill give it a try thanks

Phoenix-DH commented 5 months ago

So, no issues anymore from my side 🤷🏼‍♂️ Dont know what was rhe root cause for it.

aglasson commented 4 months ago

I was having this same 'Browser is not trusted' issue from my first attempt to get Aarlo setup. I too had to add the user_agent: linux.

Being that I am relatively new to Home Assistant it took me a bit to work out how to add the config file that didn't already exist. The confusion was the File Editor showing homeassistant/ rather than /config/ as per the Aarlo doco github readme. So for others having the same problem: In the Home Assitant File Editor - add a new file aarlo.yaml at the root if not already present. Add the text;

aarlo:  
  user_agent: linux

Then go back to the Aarlo integration page and if you're already configured, next to the entity where it says your email press reload in the dot menu on the right.