homebridge-nest-accfactory 0.2.0 → 0.2.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +24 -9
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -2,9 +2,23 @@
|
|
|
2
2
|
|
|
3
3
|
All notable changes to `homebridge-nest-accfactory` will be documented in this file. This project tries to adhere to [Semantic Versioning](http://semver.org/).
|
|
4
4
|
|
|
5
|
-
##
|
|
5
|
+
## v0.2.1 (2024/10/05)
|
|
6
6
|
|
|
7
|
-
|
|
7
|
+
## Changes
|
|
8
|
+
|
|
9
|
+
- HomeKit support for multiple speeds on thermostat(s)
|
|
10
|
+
- Audio library in docker release went walkabout. Added back in
|
|
11
|
+
|
|
12
|
+
## Known Issues
|
|
13
|
+
|
|
14
|
+
- Audio from newer Nest/Google camera/doorbell devices is still blank
|
|
15
|
+
- npm package [ip](https://github.com/advisories/GHSA-2p57-rm9w-gvfp) has severity issue. This is being used in external library (werift)
|
|
16
|
+
|
|
17
|
+
## v0.2.0 (2024/10/04)
|
|
18
|
+
|
|
19
|
+
## Breaking Change
|
|
20
|
+
|
|
21
|
+
Unfortunately, from version **0.2.0**, I've made some breaking changes in the code to help move forward with the project.
|
|
8
22
|
So, what does this mean for you, the end user.
|
|
9
23
|
1) You'll need to remove all previously discovered devices from HomeKit before adding them back in after upgrading to this version
|
|
10
24
|
2) If using Homebridge version, remove any cached acccesory data associated with this plug-in
|
|
@@ -15,18 +29,19 @@ So, what does this mean for you, the end user.
|
|
|
15
29
|
6) Any automations will need to be re-created in HomeKit
|
|
16
30
|
7) History in EveHome app will be lost
|
|
17
31
|
|
|
18
|
-
|
|
32
|
+
Apologies for this change, as I can understand what an inconvience and frustration it will be :-(
|
|
33
|
+
|
|
34
|
+
## Changes
|
|
35
|
+
|
|
36
|
+
- General code cleanup and bug fixes
|
|
37
|
+
- Common configuration between Homebridge plug-in and docker/standalone versions
|
|
38
|
+
- Seemlessly allow Nest/Google devices to be migrated between Nest <-> Google Home apps
|
|
19
39
|
|
|
20
40
|
## Known Issues
|
|
21
41
|
|
|
22
42
|
- Audio from newer Nest/Google camera/doorbell devices is still blank
|
|
23
43
|
- npm package [ip](https://github.com/advisories/GHSA-2p57-rm9w-gvfp) has severity issue. This is being used in external library (werift)
|
|
24
44
|
|
|
25
|
-
## v0.2.0 (2024/10/04)
|
|
26
|
-
|
|
27
|
-
- General code cleanup and bug fixes
|
|
28
|
-
- Common configuration between Homebridge plug-in and docker/standalone versions
|
|
29
|
-
- Seemlessly allow Nest/Google devices to be migrated between Nest <-> Google Home apps
|
|
30
45
|
|
|
31
46
|
## v0.1.9 (alpha)
|
|
32
47
|
|
|
@@ -69,4 +84,4 @@ Appologies for this change, as I can understand what an inconvience and frustrat
|
|
|
69
84
|
## v0.0.1 (2024-08-27)
|
|
70
85
|
|
|
71
86
|
- Inital re-coding from Nest_accfactory code base. These projects will now share a common code base
|
|
72
|
-
- Camera/Doorbell support currently removed will re-worked
|
|
87
|
+
- Camera/Doorbell support currently removed will re-worked
|
package/package.json
CHANGED
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
"name": "homebridge-nest-accfactory",
|
|
3
3
|
"displayName": "Homebridge Nest Accfactory",
|
|
4
4
|
"type": "module",
|
|
5
|
-
"version": "0.2.
|
|
5
|
+
"version": "0.2.1",
|
|
6
6
|
"description": "Homebridge support for Nest/Google devices including HomeKit Secure Video (HKSV) support for doorbells and cameras",
|
|
7
7
|
"author": "n0rt0nthec4t",
|
|
8
8
|
"license": "Apache-2.0",
|