Releases: n0rt0nthec4t/homebridge-nest-accfactory
Releases · n0rt0nthec4t/homebridge-nest-accfactory
0.3.1
0.3.0
Changes
- General code cleanup and stability improvements
- Introduced plugin-style architecture for Nest/Google devices
- Updated README.md to reflect changes to the devices section in configuration
- Prevent excluded devices from being restored from Homebridge cache
- Added internal support for selecting active temperature sensor (not yet exposed to HomeKit)
- Fixed loss of custom devices section when using the plugin config UI
- Fixed motion services being recreated when restored from Homebridge cache
- Fixed missing devices for Nest FieldTest accounts
- Added hot water heating boost (on/off) support for compatible EU/UK Thermostats
- Added support for Nest Heat Link devices as room temperature sensors
Deprecation Notice
- Support for the standalone Docker version of this plugin is planned to be deprecated in an upcoming release. While it currently remains functional, future updates may no longer include Docker-specific build support. Users are encouraged to transition to standard Homebridge installations where possible.
Known Issues
- Audio from newer Nest/Google cameras and doorbells is currently silent (blank audio output)
- The ip npm package has a known security advisory GHSA-2p57-rm9w-gvfp; this is used indirectly via the werift library
Thanks
Special thanks to @Daniel and @Brad for testing and feedback on this release!
0.2.11
0.2.9
Changes
- General code cleanup and bug fixes
- Support for Nest Protect(s) in Google Home app
- Default location to check for ffmpeg binary is now /usr/local/bin
- Logs Nest Protect(s) self testing status
Known Issues
- Audio from newer Nest/Google camera/doorbell devices is still blank
- npm package ip has severity issue. This is being used in external library (werift)
0.2.5
0.2.5 version bump
0.2.4
0.2.3
0.2.2
Changes
- Improved handling of configuration file with docker/standalone version
- Warning about the use of legacy configuration options with docker/standalone version
Known Issues
- Audio from newer Nest/Google camera/doorbell devices is still blank
- npm package ip has severity issue. This is being used in external library (werift)
0.2.1
Minor updated to just released 0.2.0, with fix to include missing library in docker/standalone ffmpeg binary.
Changes
- HomeKit support for multiple speeds on thermostat(s)
- Audio library in docker release went walkabout. Added back in
Known Issues
- Audio from newer Nest/Google camera/doorbell devices is still blank
- npm package ip has severity issue. This is being used in external library (werift)
0.2.0
Breaking changes v0.2.0
Unfortunately, from version 0.2.0, I've made some breaking changes in the code to help move forward with the project.
So, what does this mean for you, the end user.
- You'll need to remove all previously discovered devices from HomeKit before adding them back in after upgrading to this version
- If using Homebridge version, remove any cached acccesory data associated with this plug-in
- If using docker/standalone version, remove the 'persist' folder
- Re-add devices to HomeKit once version upgraded
- Any HomeKit Secure Video recordings will be lost
- Will need to re-configure camera streaming and notification options
- Any automations will need to be re-created in HomeKit
- History in EveHome app will be lost
Apologies for this change, as I can understand what an inconvience and frustration it will be :-(
Changes
- General code cleanup and bug fixes
- Common configuration between Homebridge plug-in and docker/standalone versions
- Seemlessly allow Nest/Google devices to be migrated between Nest <-> Google Home apps
Known Issues
- Audio from newer Nest/Google camera/doorbell devices is still blank
- npm package ip has severity issue. This is being used in external library (werift)