Welcome to 0.8.1 Alpha Releases

DANGER: This is a very alpha release and intended for experienced Home Assistant users.
DANGER: This is a very alpha release, please try on a test system first if possible.

These releases add proper Integration and config flow support to the Aarlo component.

Many thanks to @NickM-27 for starting this, I can only apologise for the amount of time it's taken me to fix up the other pieces of code.

What Should Happen

The code will upgrade a 0.7 installation to use the standard Home Assistant integration configuration mechanism. What this means is:

• key pieces of the Arlo configuration will be moved into the Home Assistant repositories
• all the extra config that comes along with Arlo will be moved into a file called /config/aarlo.yaml
• entities will now be tied to their owning devices, i.e, a camera motion detection entity will be associated the camera device providing it
• integrations can be reloaded, reconfigured, deleted and added on the fly

If It Goes Wrong

Then revert back to an older install. And for this reason I recommend keeping your old config around, Home Assistant will complain about it but it won't affect anything.

But if you can raise a bug telling me what you were doing, what you expected to happen and what happened that would be great.

What Am I Not Sure About

location and media_player devices should work but I have not real mechanism for testing them.

Naming should work. 0.7 upgrades will include the aarlo_ prefix and 0.8 upgrades won't.

What This Fixes From 0.6

• fix a docs issue
• fix a camera recording issue

What This Fixes From 0.5

• make some variable explicit
• fix service entries
• fix translations

What This Fixes From 0.4

• bumps pyaarlo revision to recognise synced cameras

What This Fixes From 0.3

• Add in entities when creating a brand new integration.
• Fix new integration naming.

What This Fixes From 0.1

• Yahoo IMAP support should be better. (And IMAP in general)
• Better pyaarlo parameter support.

DANGER: These are very alpha and intended for experienced Home Assistant users.

Fix a camera record issue.

Welcome to 0.8.1 Alpha Releases

DANGER: This is a very alpha release and intended for experienced Home Assistant users.
DANGER: This is a very alpha release, please try on a test system first if possible.

These releases add proper Integration and config flow support to the Aarlo component.

Many thanks to @NickM-27 for starting this, I can only apologise for the amount of time it's taken me to fix up the other pieces of code.

What Should Happen

The code will upgrade a 0.7 installation to use the standard Home Assistant integration configuration mechanism. What this means is:

• key pieces of the Arlo configuration will be moved into the Home Assistant repositories
• all the extra config that comes along with Arlo will be moved into a file called /config/aarlo.yaml
• entities will now be tied to their owning devices, i.e, a camera motion detection entity will be associated the camera device providing it
• integrations can be reloaded, reconfigured, deleted and added on the fly

If It Goes Wrong

Then revert back to an older install. And for this reason I recommend keeping your old config around, Home Assistant will complain about it but it won't affect anything.

But if you can raise a bug telling me what you were doing, what you expected to happen and what happened that would be great.

What Am I Not Sure About

location and media_player devices should work but I have not real mechanism for testing them.

Naming should work. 0.7 upgrades will include the aarlo_ prefix and 0.8 upgrades won't.

What This Fixes From 0.4

• bumps pyaarlo revision to recognise synced cameras

What This Fixes From 0.3

• Add in entities when creating a brand new integration.
• Fix new integration naming.

What This Fixes From 0.1

• Yahoo IMAP support should be better. (And IMAP in general)
• Better pyaarlo parameter support.

DANGER: These are very alpha and intended for experienced Home Assistant users.

Welcome to 0.8.1 Alpha Releases

DANGER: This is a very alpha release and intended for experienced Home Assistant users.
DANGER: This is a very alpha release, please try on a test system first if possible.

These releases add proper Integration and config flow support to the Aarlo component.

Many thanks to @NickM-27 for starting this, I can only apologise for the amount of time it's taken me to fix up the other pieces of code.

What Should Happen

The code will upgrade a 0.7 installation to use the standard Home Assistant integration configuration mechanism. What this means is:

• key pieces of the Arlo configuration will be moved into the Home Assistant repositories
• all the extra config that comes along with Arlo will be moved into a file called /config/aarlo.yaml
• entities will now be tied to their owning devices, i.e, a camera motion detection entity will be associated the camera device providing it
• integrations can be reloaded, reconfigured, deleted and added on the fly

If It Goes Wrong

Then revert back to an older install. And for this reason I recommend keeping your old config around, Home Assistant will complain about it but it won't affect anything.

But if you can raise a bug telling me what you were doing, what you expected to happen and what happened that would be great.

What Am I Not Sure About

location and media_player devices should work but I have not real mechanism for testing them.

Naming should work. 0.7 upgrades will include the aarlo_ prefix and 0.8 upgrades won't.

What This Fixes From 0.3

• Add in entities when creating a brand new integration.
• Fix new integration naming.

What This Fixes From 0.1

• Yahoo IMAP support should be better. (And IMAP in general)
• Better pyaarlo parameter support.

DANGER: These are very alpha and intended for experienced Home Assistant users.

Welcome to 0.8.1 Alpha Releases

DANGER: This is a very alpha release and intended for experienced Home Assistant users.
DANGER: This is a very alpha release, please try on a test system first if possible.

These releases add proper Intergration and config flow support to the Aarlo component.

Many thanks to @NickM-27 for starting this, I can only apologise for the amount of time it's taken me to fix up the other pieces of code.

What Should Happen

The code will upgrade a 0.7 installation to use the standard Home Assistant integration configuration mechanism. What this means is:

• key pieces of the Arlo configuration will be moved into the Home Assistant repositories
• all the extra config that comes along with Arlo will be moved into a file called /config/aarlo.yaml
• entities will now be tied to their owning devices, i.e, a camera motion detection entity will be associated the camera device providing it
• integrations can be reloaded, reconfigured, deleted and added on the fly

If It Goes Wrong

Then revert back to an older install. And for this reason I recommend keeping your old config around, Home Assistant will complain about it but it won't affect anything.

But if you can raise a bug telling me what you were doing, what you expected to happen and what happened that would be great.

What Am I Not Sure About

location and media_player devices should work but I have not real mechanism for testing them.

Naming should work. 0.7 upgrades will include the aarlo_ prefix and 0.8 upgrades won't.

What This Fixes From 0.1

• Yahoo IMAP support should be better. (And IMAP in general)
• Better pyaarlo parameter support.

DANGER: These are very alpha and intended for experienced Home Assistant users.

Welcome to 0.8.1 Alpha Releases

DANGER: This is a very alpha release and intended for experienced Home Assistant users.
DANGER: This is a very alpha release, please try on a test system first if possible.

These releases add proper Intergration and config flow support to the Aarlo component.

Many thanks to @NickM-27 for starting this, I can only apologise for the amount of time it's taken me to fix up the other pieces of code.

What Should Happen

The code will upgrade a 0.7 installation to use the standard Home Assistant integration configuration mechanism. What this means is:

• key pieces of the Arlo configuration will be moved into the Home Assistant repositories
• all the extra config that comes along with Arlo will be moved into a file called /config/aarlo.yaml
• entities will now be tied to their owning devices, i.e, a camera motion detection entity will be associated the camera device providing it
• integrations can be reloaded, reconfigured, deleted and added on the fly

If It Goes Wrong

Then revert back to an older install. And for this reason I recommend keeping your old config around, Home Assistant will complain about it but it won't affect anything.

But if you can raise a bug telling me what you were doing, what you expected to happen and what happened that would be great.

What Am I Not Sure About

location and media_player devices should work but I have not real mechanism for testing them.

Naming should work. 0.7 upgrades will include the aarlo_ prefix and 0.8 upgrades won't.

DANGER: These are very alpha and intended for experienced Home Assistant users.

No changes. Just a move away from beta.

Add Pro 5 support.

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.

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.