Skip to content

Releases: twrecked/hass-aarlo

version 0.8.1.alpha.9

24 Nov 04:20
be64c5a
Compare
Choose a tag to compare
version 0.8.1.alpha.9 Pre-release
Pre-release

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.

version 0.8.1.alpha.8

24 Nov 01:49
1a22987
Compare
Choose a tag to compare
version 0.8.1.alpha.8 Pre-release
Pre-release

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.

version 0.8.1.alpha.7

23 Nov 02:26
17401f6
Compare
Choose a tag to compare
version 0.8.1.alpha.7 Pre-release
Pre-release

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.

version 0.7.4.1

23 Nov 03:12
830f319
Compare
Choose a tag to compare

Fix a camera record issue.

version 0.8.1.alpha.5

04 Nov 18:27
2a93fec
Compare
Choose a tag to compare
version 0.8.1.alpha.5 Pre-release
Pre-release

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.

version 0.8.1.alpha.4

02 Nov 13:36
8b96b8a
Compare
Choose a tag to compare
version 0.8.1.alpha.4 Pre-release
Pre-release

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.

version 0.8.1.alpha.3

01 Nov 00:57
40b7d77
Compare
Choose a tag to compare
version 0.8.1.alpha.3 Pre-release
Pre-release

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.

version 0.8.1.alpha.1

31 Oct 03:27
cfd3314
Compare
Choose a tag to compare
version 0.8.1.alpha.1 Pre-release
Pre-release

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.

version 0.7.4.0

30 Oct 19:36
612a228
Compare
Choose a tag to compare

No changes. Just a move away from beta.

version 0.7.4.beta.20

15 Oct 21:26
0cb7eb5
Compare
Choose a tag to compare

Add Pro 5 support.