Open bslefevre opened 3 years ago
Sorry to be a nuisance but can you turn on verbose_debug
and re-run the test? This will print out the packets that Arlo is sending us.
aarlo:
verbose_debug: True
I've quickly scanned the logging and I'm completely missing the "ding" events passing by
It only goes: INFO (MainThread) [custom_components.aarlo.binary_sensor] ArloBinarySensor: Ding Deurbel created
and that's it
You should change the password on your HA account, it was in the logs.
You can paste the logs here and it will encrypt them so only I can see them. It doesn't forward the logs to me automatically so you need to upload the output here.
I'll take a look at the output and get back to you.
edit: I just downloaded the logs and deleted the message.
Thanks! I wasn't aware of the encrypted method of sending the logging!
Some more information, maybe it's usefull! My HASS died so I've re-installed everything. I also re-added the Doorbell to Arlo. The "ding"-event is being created but not being hit when you press the doorbell. So even with an (almost) clean install the problem's there
Can you upload logs after the fresh install. The problem, at least from the previous install, was Arlo isn't sending me the ding notification. I'm seeing a media upload notification, ie, a new video, just not the button press notification.
Here is a new test with a complete reinstall of HASS and Arlo Doorbel reinstalled into Arlo (still no joy with the ding on my end) 20210423 - logging - encrypted.txt
Those logs don't even mention the doorbell at all. I don't think Arlo is send you the notification.
You mention 2FA, I'm assuming this account doesn't have it enabled?
As you can see the 2FA is enabled
So I've disabled the 2FA and commented the settings for 2FA in configuration.yaml. It still doesn't trigger the "ding"-event though Any more thoughts/idea?
@twrecked do you know there's a setting within Arlo Webapp to enable/disable the "ding"-event per user?
So, I've been looking into this again and forcing the API mode to V2 and the error I'm getting is:
[pyaarlo] error in response={'data': {'error': '2217', 'message': 'The device does not exist.', 'reason': 'Invalid uniqueId recieved.'}, 'success': False}
I've got no idea what's going on but maybe this is where the problem lays? Do you know what to do to fix this?
By the way I've added an Nest Hub 2 to my collection and the Arlo integration made it possible to get the "ding-event" working natively on the Nest Hub 2. So I'm thinking something is wrong with my installation of hass-aarlo?
-- EDIT -- I've fixed this error by removing and readding it to my HASS purposed Arlo account
Also the event binary_sensor.aarlo_motion_deurbel
doesn't appear to be working any more.
Do you've got any suggestions what to do?
I've done a factory reset, removed the other camera's from the account for HASS
Is there something to see withing the versioning between what HASS thinks my device is and what de Arlo server is thinking it is?
It appears to not update any of the status. With the arm/disarm it stay's the same But streaming can be activated though
Since a few days (I think from 09-04-2021 in the evening) the ding event from the Arlo Doorbell isn't working anymore. I haven't changed anything and spontaniously it doesn't work any more. The Arlo App still does the calls to our phones but the event doesn't appear to reach HASS or be computed from it. I've now updated to the latest version of HASS (2021.4.3) and to hass-aarlo v0.7.1.beta.11 but that also didn't do the trick! Is there something changed with the API or is 2FA necessary for this? I've added logging from when I've pressed the doorbell ("Deurbel") logging.txt