Skip to content

version 0.7.4.beta.19
Compare
Choose a tag to compare
@twrecked twrecked released this 03 Aug 00:30
· 6 commits to version-0.7.x since this release
v0.7.4b19
0c396fc
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

THIS INCLUDES A POSSIBLE FIX FOR LOGIN AND CERTIFICATE ERRORS

Arlo changed their back end and it broke the integration. They:

  • changed the header requirements
  • changed the MQTT server settings

This update includes the fix that has gotten most people back up and running [thanks jurgenweber]
This update includes a fix for an error introduced by the next update.
This update removes caching and forces SSE over a non cloudscraper connection.
This update limits the number of login attempts.
This update fixes a header merge mix up.

If you still see login issue try removing the <home-assistant-dir>/.aarlo/session.pickle file to regenerate an authentication token.

If you use the mqtt back end and see certificate issues you can try adding one of these to your Aarlo configuration:

  • add mqtt_hostname_check: False, this stops certificate validation. The downside here is any one can potentially now pretend to be Arlo.
  • add mqtt_host: mqtt-cluster-z1.arloxcld.com, this changes the MQTT host we use to a fixed one, the certificate on this host is correct. The downside here is they could remove this host at any time

I've added a third option, mqtt_transport this defaults to tcp and you shouldn't need to change it. The only other value it can be is websockets.

Assets 2
Loading