version 0.7.4.beta.19

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.

version 0.7.4.beta.18

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 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.

version 0.7.4.beta.17

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 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.

version 0.7.4.beta.16

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

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.

This update limits the number of login attempts.
This update fixes a header merge mix up.

version 0.7.4.beta.15

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

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.

This update limits the number of login attempts.

version 0.7.4.beta.14

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

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.

version 0.7.4.beta.12

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

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.

version 0.7.4.beta.13

This release builds on the the Arlo v4 APIs support.
[thanks @JeffSteinbok]

This pre-release adds initial support for Arlo's new 8-in-1 sensor.
[thanks @xirtamoen for lending the sensors]

I don't own a sensor so this code is still in testing, some binary sensor states maybe reversed or not work at all... Send debug if you find an issue. Revert back to the previous release if you have to.

Also fixed:

• better status update handing, Arlo has changed some of its APIs
• added configurable IMAP timeout
• revert a premature optimisation
• better location naming

version 0.7.4.beta.11

This release builds on the the Arlo v4 APIs support.
[thanks @JeffSteinbok]

This pre-release adds initial support for Arlo's new 8-in-1 sensor.
[thanks @xirtamoen for lending the sensors]

I don't own a sensor so this code is still in testing, some binary sensor states maybe reversed or not work at all... Send debug if you find an issue. Revert back to the previous release if you have to.

Also fixed:

• better status update handing, Arlo has changed some of its APIs
• added configurable IMAP timeout
• revert a premature optimisation
• better location naming

version 0.7.4.beta.9

This release builds on the the Arlo v4 APIs support.
[thanks @JeffSteinbok]

This pre-release adds initial support for Arlo's new 8-in-1 sensor.
[thanks @xirtamoen for lending the sensors]

I don't own a sensor so this code is still in testing, some binary sensor states maybe reversed or not work at all... Send debug if you find an issue. Revert back to the previous release if you have to.

Also fixed:

• better status update handing, Arlo has changed some of its APIs
• added configurable IMAP timeout
• revert a premature optimisation