version 0.8.1.18

Warning!

This release tries a new authentication mechanism that should cut down on the number of 2fa requests the component makes. I've tested it as well as I can for me but it might break your setup. If it does return to 0.8.1.14.1 and that should restore previous version of pyaarlo. If you do run into problems please raise an issue. Include debug logs if possible.

What Changed

Arlo recently changed their back end and a part of those changes was to reduce the authorization token timeout from 2 weeks to 2 hours. This resulted in a lot a 2fa request being made. This update uses the latest pyaarlo that implements the "trusted browser" mechanism the browser uses when connecting to my.arlo.com.

You should not need to make any changes to your system but if you do run into problems try deleting the following and restarting:

.aarlo/cookies.txt
.aarlo/session.pickle

Fixes

This releases quietens down a warning about notification use.

version 0.8.1.17

Sorry for this release, I scored an own-goal with a pypi update in 1.16, that this fixes.

Warning!

This release tries a new authentication mechanism that should cut down on the number of 2fa requests the component makes. I've tested it as well as I can for me but it might break your setup. If it does return to 0.8.1.14.1 and that should restore previous version of pyaarlo. If you do run into problems please raise an issue. Include debug logs if possible.

What Changed

Arlo recently changed their back end and a part of those changes was to reduce the authorization token timeout from 2 weeks to 2 hours. This resulted in a lot a 2fa request being made. This update uses the latest pyaarlo that implements the "trusted browser" mechanism the browser uses when connecting to my.arlo.com.

You should not need to make any changes to your system but if you do run into problems try deleting the following and restarting:

.aarlo/cookies.txt
.aarlo/session.pickle

version 0.8.1.16

Warning!

This release tries a new authentication mechanism that should cut down on the number of 2fa requests the component makes. I've tested it as well as I can for me but it might break your setup. If it does return to 0.8.1.14.1 and that should restore previous version of pyaarlo. If you do run into problems please raise an issue. Include debug logs if possible.

What Changed

Arlo recently changed their back end and a part of those changes was to reduce the authorization token timeout from 2 weeks to 2 hours. This resulted in a lot a 2fa request being made. This update uses the latest pyaarlo that implements the "trusted browser" mechanism the browser uses when connecting to my.arlo.com.

You do not need to make any changes to your setup, everything is handled automatically.

version 0.8.1.15

Warning!

This release tries a new authentication mechanism that should cut down on the number of 2fa requests the component makes. I've tested it as well as I can for me but it might break you setup. If it does return to 0.8.1.14.1 and that should restore previous version of pyaarlo. If you do run into problems please raise an issue. Include debug logs if possible.

What Changed

Arlo recently changed their back end and a part of those changes was to reduce the authorization token timeout from 2 weeks to 2 hours. This resulted in a lot a 2fa request being made. This update uses the latest pyaarlo that implements the "trusted browser" mechanism the browser uses when connecting to my.arlo.com.

You do not need to make any changes to your setup, everything is handled automatically.

version 0.8.1.14

This release does nothing but fix the pyaarlo version to 0.8.0.14.

I'm going to release a modified version of pyaarlo to deal with Arlo server changes and in case it breaks I want people to get back to a sane version.

version 0.8.1.13

Possible streaming fix.

Thanks to @yongfg for this.

This uses a new user agent that returns an rtsp stream we can feed into Home Assistant.

I say possible fix because the fix finder reported issues with the streaming not always starting. I didn't see that on my limited set of tests but I figured getting more data on this might help.

I'm still looking at improving the stream component to get the mpeg-dash streams working.

version 0.8.1.12

This is a quick fix to change the default user_agent to linux from arlo. People were reporting problems with Arlo rejecting their connections using the original user_agent.

version 0.8.1.11

What This Fixes From 0.8.1.10

• Temp fix for camera API
• Add aiofiles requirement

What This Fixes From 0.8.1.9 and earlier

• Added French translations; thanks to @SocrateMobile
• Remove deprecated constants
• Possible location/alarm mode fix
• Squash erroneous 'browser not trusted' error
• Fix battery drain on new cameras
• 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
• 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

Also...

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.

version 0.8.1.10

What This Fixes From 0.8.1.9

• Added French translations; thanks to @SocrateMobile

What This Fixes From 0.8.1.8 and earlier

• Remove deprecated constants
• Possible location/alarm mode fix
• Squash erroneous 'browser not trusted' error
• Fix battery drain on new cameras
• 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
• 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

Also...

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.

version 0.8.1.9

What This Fixes From 0.8.1.8

• Remove deprecated constants
• Possible location/alarm mode fix

What This Fixes From 0.8.1.7 and earlier

• Squash erroneous 'browser not trusted' error
• Fix battery drain on new cameras
• 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
• 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

Also...

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.