Releases: twrecked/hass-aarlo
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.
Contributors
Assets 2
version 0.8.1.8
What This Fixes From 0.8.1.7
- Squash erroneous 'browser not trusted' error
What This Fixes From 0.8.1.5 and earlier
- 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.
Contributors
Assets 2
version 0.8.1.7
What This Fixes From 0.8.1.6
- Fix battery drain on new cameras
What This Fixes From 0.8.1.5 and earlier
- 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.
Contributors
Assets 2
version 0.8.1.6
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
Contributors
Assets 2
version 0.8.1.5
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
Contributors
Assets 2
version 0.8.1.4
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
Contributors
Assets 2
version 0.8.1.3
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
Contributors
Assets 2
version 0.8.1.2
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
Contributors
Assets 2
version 0.8.1.1
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
Contributors
Assets 2
version 0.7.4.3
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.