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

Many thanks to @NickM-27 for starting this.

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 a 0.7 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 This Fixes From 0.8.1.5

• bump pyaarlo revision to add the following cameras
  • Essential Indoor Gen2 HD
  • Essential Outdoor Gen2 HD
  • Essential Outdoor Gen2 2K
  • Essential XL Outdoor Gen2 HD
  • Essential XL Spotlight

What This Fixes From 0.8.1.3 and earlier

• bump pyaarlo revision to add better error code reporting
• fix an IO in event loop message
• fix a light warning
• handle motion events from all-on-one sensor
• bumped pyaarlo to bring in Essential Indoor 2 support
• fixed an alarm upgrade issue where you couldn't arm a base station
• removed some code creating deprecated warning

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

Many thanks to @NickM-27 for starting this.

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 a 0.7 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 This Fixes From 0.8.1.4

• bump pyaarlo revision to add better error code reporting

What This Fixes From 0.8.1.3 and earlier

• fix an IO in event loop message
• fix a light warning
• handle motion events from all-on-one sensor
• bumped pyaarlo to bring in Essential Indoor 2 support
• fixed an alarm upgrade issue where you couldn't arm a base station
• removed some code creating deprecated warning

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

Many thanks to @NickM-27 for starting this.

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 a 0.7 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 This Fixes From 0.8.1.3

• fix an IO in event loop message
• fix a light warning

What This Fixes From 0.8.1.2 and earlier

• handle motion events from all-on-one sensor
• bumped pyaarlo to bring in Essential Indoor 2 support
• fixed an alarm upgrade issue where you couldn't arm a base station
• removed some code creating deprecated warning

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 a 0.7 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 This Fixes From 0.8.2

• handle motion events from all-on-one sensor

What This Fixes From 0.8.1

• bumped pyaarlo to bring in Essential Indoor 2 support
• fixed an alarm upgrade issue where you couldn't arm a base station
• removed some code creating deprecated warning

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 a 0.7 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 This Fixes From 0.8.1

• bumped pyaarlo to bring in Essential Indoor 2 support
• fixed an alarm upgrade issue where you couldn't arm a base station
• removed some code creating deprecated warning

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

What This Fixes From 0.8.1

• removed some code creating deprecated warning

Fixed some deprecated warnings.

Fixed a runtime error caused by a callback.

0.7 has now been deprecated by 0.8... there will be less and less fixes being made to this.

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

What This Fixes From 0.15

• nothing.. just a version change

What This Fixes From 0.14

• better back end detection

What This Fixes From 0.13

• fix a callback threading issue (thank @bdraco)

What This Fixes From 0.12

• tweaks doorbell support

What This Fixes From 0.11

• adds more camera and doorbell support

What This Fixes From 0.10

• fixed several upgrade issues

What This Fixes From 0.9

• added siren support
• added an import notice

What This Fixes From 0.8

• fix another location issue

What This Fixes From 0.7

• fix a location issue

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.

Welcome to 0.8.1 Beta Releases

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

• better back end detection

What This Fixes From 0.13

• fix a callback threading issue (thank @bdraco)

What This Fixes From 0.12

• tweaks doorbell support

What This Fixes From 0.11

• adds more camera and doorbell support

What This Fixes From 0.10

• fixed several upgrade issues

What This Fixes From 0.9

• added siren support
• added an import notice

What This Fixes From 0.8

• fix another location issue

What This Fixes From 0.7

• fix a location issue

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.

Welcome to 0.8.1 Beta Releases

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

• fix a callback threading issue (thank @bdraco)

What This Fixes From 0.12

• tweaks doorbell support

What This Fixes From 0.11

• adds more camera and doorbell support

What This Fixes From 0.10

• fixed several upgrade issues

What This Fixes From 0.9

• added siren support
• added an import notice

What This Fixes From 0.8

• fix another location issue

What This Fixes From 0.7

• fix a location issue

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.

Welcome to 0.8.1 Beta Releases

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

• tweaks doorbell support

What This Fixes From 0.11

• adds more camera and doorbell support

What This Fixes From 0.10

• fixed several upgrade issues

What This Fixes From 0.9

• added siren support
• added an import notice

What This Fixes From 0.8

• fix another location issue

What This Fixes From 0.7

• fix a location issue

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.

Welcome to 0.8.1 Alpha Releases

DANGER: This is an alpha release and intended for experienced Home Assistant users.

This will be the final alpha release.

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

• adds more camera and doorbell support

What This Fixes From 0.10

• fixed several upgrade issues

What This Fixes From 0.9

• added siren support
• added an import notice

What This Fixes From 0.8

• fix another location issue

What This Fixes From 0.7

• fix a location issue

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.

Welcome to 0.8.1 Alpha Releases

DANGER: This is an alpha release and intended for experienced Home Assistant users.

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

• fixed several upgrade issues

What This Fixes From 0.9

• added siren support
• added an import notice

What This Fixes From 0.8

• fix another location issue

What This Fixes From 0.7

• fix a location issue

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.

Welcome to 0.8.1 Alpha Releases

DANGER: This is an alpha release and intended for experienced Home Assistant users.

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

• added siren support
• added an import notice

What This Fixes From 0.8

• fix another location issue

What This Fixes From 0.7

• fix a location issue

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.

Fix a synced state 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.8

• fix another location issue

What This Fixes From 0.7

• fix a location issue

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.

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

• fix a location issue

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

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.