homebridge-texecom-full 4.3.0 → 4.3.1-beta.0
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 +93 -71
- package/README.md +12 -0
- package/config.schema.json +29 -0
- package/index.js +652 -489
- package/package.json +57 -58
package/CHANGELOG.md
CHANGED
|
@@ -1,71 +1,93 @@
|
|
|
1
|
-
# Change log
|
|
2
|
-
|
|
3
|
-
This change log documents all release versions of homebridge-texecom
|
|
4
|
-
|
|
5
|
-
### 4.
|
|
6
|
-
|
|
7
|
-
- **
|
|
8
|
-
- **
|
|
9
|
-
|
|
10
|
-
|
|
11
|
-
|
|
12
|
-
- **FIX** -
|
|
13
|
-
- **
|
|
14
|
-
|
|
15
|
-
|
|
16
|
-
|
|
17
|
-
|
|
18
|
-
|
|
19
|
-
|
|
20
|
-
|
|
21
|
-
- **FIX** -
|
|
22
|
-
|
|
23
|
-
|
|
24
|
-
|
|
25
|
-
- **
|
|
26
|
-
|
|
27
|
-
|
|
28
|
-
|
|
29
|
-
|
|
30
|
-
- **
|
|
31
|
-
|
|
32
|
-
### 4.2.
|
|
33
|
-
|
|
34
|
-
- **
|
|
35
|
-
|
|
36
|
-
|
|
37
|
-
|
|
38
|
-
|
|
39
|
-
|
|
40
|
-
|
|
41
|
-
|
|
42
|
-
|
|
43
|
-
- **
|
|
44
|
-
|
|
45
|
-
### 4.2.
|
|
46
|
-
|
|
47
|
-
- **TWEAK** -
|
|
48
|
-
|
|
49
|
-
|
|
50
|
-
### 4.2.
|
|
51
|
-
|
|
52
|
-
- **
|
|
53
|
-
|
|
54
|
-
|
|
55
|
-
|
|
56
|
-
|
|
57
|
-
|
|
58
|
-
|
|
59
|
-
|
|
60
|
-
|
|
61
|
-
|
|
62
|
-
|
|
63
|
-
|
|
64
|
-
|
|
65
|
-
|
|
66
|
-
|
|
67
|
-
-
|
|
68
|
-
|
|
69
|
-
|
|
70
|
-
|
|
71
|
-
|
|
1
|
+
# Change log
|
|
2
|
+
|
|
3
|
+
This change log documents all release versions of homebridge-texecom
|
|
4
|
+
|
|
5
|
+
### 4.3.1-beta.0 (2026-08-18)
|
|
6
|
+
|
|
7
|
+
- **FIX** - Accessories are bridged again instead of being published as external accessories. 4.3.0 required every zone and area to be added to the Home app by hand, this restores the behaviour of 4.2.8 and earlier.
|
|
8
|
+
- **FIX** - Accessory UUIDs now match the scheme used up to 4.2.8, so upgrading from 4.2.8 keeps existing accessories along with their rooms, names and automations.
|
|
9
|
+
- **FIX** - Accessories are held in the Homebridge accessory cache and reused across restarts, and accessories removed from the config are unregistered.
|
|
10
|
+
- **FIX** - The first arm or disarm from a HomeKit button is no longer ignored (#26). The flag used to suppress echoes from the panel was never being cleared once alarm driven updates moved to `updateValue`.
|
|
11
|
+
- **FIX** - A full arm no longer changes to Night in the Home app a minute later (#25). The user numbers that decide how an arm is reported are configurable via `remote_users`, `app_users` and `default_arm_state` instead of being fixed in code, and an arm started from HomeKit now reports the state that was actually asked for.
|
|
12
|
+
- **FIX** - User numbers over 99 are no longer truncated when reading area messages from the panel.
|
|
13
|
+
- **FIX** - Areas are matched by area number rather than by their position in the config.
|
|
14
|
+
- **FIX** - The retry timer was never cleared once a command succeeded, so every arm or disarm sent a second UDL login to the panel two seconds later.
|
|
15
|
+
- **TWEAK** - `engines.homebridge` widened back to `^1.6.0 || ^2.0.0`, 4.3.0 refused to run on Homebridge 1.x.
|
|
16
|
+
- **TWEAK** - Removed the unused `crypto-js` dependency.
|
|
17
|
+
|
|
18
|
+
### 4.3.0 (2026-05-23)
|
|
19
|
+
|
|
20
|
+
- **FIX** - Homebridge v2 compatibility: updated to new platform API with `didFinishLaunching` and `configureAccessory`
|
|
21
|
+
- **FIX** - Replaced deprecated `on('set', callback)` characteristic handler with `onSet` returning a Promise
|
|
22
|
+
- **FIX** - UUID collision between zones and areas sharing the same zone number
|
|
23
|
+
- **FIX** - All alarm-driven state updates now use `updateValue` instead of `setValue` to prevent feedback loops
|
|
24
|
+
- **FIX** - SerialPort v12 compatibility: `baudRate` (camelCase) and `@serialport/parser-readline` pipe parser
|
|
25
|
+
- **FIX** - Removed erroneous `registerAccessory` call alongside `registerPlatform`
|
|
26
|
+
|
|
27
|
+
### 4.2.8 (2025-7-28)
|
|
28
|
+
|
|
29
|
+
- **TWEAK** - Data conversion issue (Typo)
|
|
30
|
+
- **NEWS** - We are verified!!
|
|
31
|
+
|
|
32
|
+
### 4.2.7 (2025-7-28)
|
|
33
|
+
|
|
34
|
+
- **FIX** - Connection issue
|
|
35
|
+
- **NEWS** - We are verified!!
|
|
36
|
+
|
|
37
|
+
### 4.2.6 (2025-07-25)
|
|
38
|
+
|
|
39
|
+
- **FIX** - Fixed issues for Verification.
|
|
40
|
+
|
|
41
|
+
### 4.2.6-beta.2 (2025-01-22)
|
|
42
|
+
|
|
43
|
+
- **FIX** - Removed carbondioxide
|
|
44
|
+
|
|
45
|
+
### 4.2.6-beta.0 (2025-01-21)
|
|
46
|
+
|
|
47
|
+
- **TWEAK** - House keeping.
|
|
48
|
+
- **FIX** - Added carbonmonoxide and dioxide to config.schema.
|
|
49
|
+
|
|
50
|
+
### 4.2.5 (2025-01-03)
|
|
51
|
+
|
|
52
|
+
- **TWEAK** - Added the version for serial port to work on new node.js
|
|
53
|
+
|
|
54
|
+
### 4.2.5-beta.1 (2024-12-17)
|
|
55
|
+
|
|
56
|
+
- **TWEAK** - Added the version for serial port to work on new node.js
|
|
57
|
+
|
|
58
|
+
### 4.2.3 (2024-10-09)
|
|
59
|
+
|
|
60
|
+
- **TWEAK** - Trying to get verified by homebridge
|
|
61
|
+
|
|
62
|
+
### 4.2.2-beta2 (2024-10-09)
|
|
63
|
+
|
|
64
|
+
- **TWEAK** - Can not install in certain cases. Added post script to check if python is installed.
|
|
65
|
+
- **TEST** - Tested on Homebridge V2
|
|
66
|
+
|
|
67
|
+
### 4.2.2-beta1 (2024-09-14)
|
|
68
|
+
|
|
69
|
+
- **TWEAK** - Area triggering reduced to Away Arm only
|
|
70
|
+
- Not triggering when in Home and evening arm
|
|
71
|
+
|
|
72
|
+
### 4.2.1 (2024-09-14)
|
|
73
|
+
|
|
74
|
+
- **FEATURE** - Added arm and disarm for each area
|
|
75
|
+
- Added zones to each area to be able to trigger an alarm.
|
|
76
|
+
|
|
77
|
+
### 1.0.3 (2017-01-28)
|
|
78
|
+
|
|
79
|
+
- **FIX** - Zone matching did not work at all in previous release.
|
|
80
|
+
- **FEATURE** - A dwell time is now configureable for each zone before activation is cleared.
|
|
81
|
+
- **FIX** - Breaks added to zone searching for added performance.
|
|
82
|
+
|
|
83
|
+
### 1.0.2 (2017-01-24)
|
|
84
|
+
|
|
85
|
+
- **TWEAK** - Zone matching made much more efficient for added improvement.
|
|
86
|
+
|
|
87
|
+
### 1.0.1 (2017-01-21)
|
|
88
|
+
|
|
89
|
+
- **FIX** - Dependencies for serialport were incorrect which prevented NPM installation.
|
|
90
|
+
|
|
91
|
+
### 1.0.0 (2017-01-21)
|
|
92
|
+
|
|
93
|
+
- **FEATURE** - Initial release.
|
package/README.md
CHANGED
|
@@ -96,6 +96,18 @@ For UDL
|
|
|
96
96
|
| --- | --- | --- |
|
|
97
97
|
| `udl` | 1234 | The UDL code on the panel to be able to arm and disarm alarm |
|
|
98
98
|
|
|
99
|
+
For arm state reporting
|
|
100
|
+
|
|
101
|
+
When an area is armed the panel reports the area and the user number, but not whether it was a full arm or a part arm. These settings say how to read that.
|
|
102
|
+
|
|
103
|
+
| Key | Default | Description |
|
|
104
|
+
| --- | --- | --- |
|
|
105
|
+
| `remote_users` | `[]` | User numbers that arm using a remote or keyfob, e.g. `[17]`. An arm by one of these users is always reported to HomeKit as Away. |
|
|
106
|
+
| `app_users` | `[]` | User numbers the panel reports when an area is armed from this plugin, e.g. `[25, 254]`. |
|
|
107
|
+
| `default_arm_state` | `"away"` | What to report for an arm by any other user, at a keypad for example. One of `away`, `night` or `stay`. |
|
|
108
|
+
|
|
109
|
+
When the arm was started from HomeKit the plugin already knows what was asked for and reports that, whatever the user number. These settings only come into play for an arm that started somewhere else.
|
|
110
|
+
|
|
99
111
|
### Per-zone Configuration
|
|
100
112
|
|
|
101
113
|
This plugin is a platform plugin so you must configure each zone from your Texecom intruder alarm into your config individually.
|
package/config.schema.json
CHANGED
|
@@ -46,6 +46,35 @@
|
|
|
46
46
|
"maxLength": 6,
|
|
47
47
|
"title": "UDL"
|
|
48
48
|
},
|
|
49
|
+
"remote_users": {
|
|
50
|
+
"type": "array",
|
|
51
|
+
"title": "Remote / Keyfob Users",
|
|
52
|
+
"description": "Panel user numbers that arm using a remote or keyfob. An arm by one of these users is always shown as Away in HomeKit.",
|
|
53
|
+
"items": {
|
|
54
|
+
"type": "integer",
|
|
55
|
+
"title": "User Number"
|
|
56
|
+
}
|
|
57
|
+
},
|
|
58
|
+
"app_users": {
|
|
59
|
+
"type": "array",
|
|
60
|
+
"title": "App Users",
|
|
61
|
+
"description": "Panel user numbers the panel reports when an area is armed from this plugin. An arm by one of these users is shown as whatever was asked for in HomeKit.",
|
|
62
|
+
"items": {
|
|
63
|
+
"type": "integer",
|
|
64
|
+
"title": "User Number"
|
|
65
|
+
}
|
|
66
|
+
},
|
|
67
|
+
"default_arm_state": {
|
|
68
|
+
"type": "string",
|
|
69
|
+
"title": "Default Arm State",
|
|
70
|
+
"default": "away",
|
|
71
|
+
"description": "What to show in HomeKit when an area is armed by any other user, at a keypad for example. The panel does not report whether an arm was full or part, so this is a best guess.",
|
|
72
|
+
"enum": [
|
|
73
|
+
"away",
|
|
74
|
+
"night",
|
|
75
|
+
"stay"
|
|
76
|
+
]
|
|
77
|
+
},
|
|
49
78
|
"zones": {
|
|
50
79
|
"type": "array",
|
|
51
80
|
"title": "Zones",
|