homebridge-texecom-full 4.3.1-beta.0 → 4.3.1-beta.3
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 +107 -92
- package/README.md +18 -0
- package/config.schema.json +6 -0
- package/index.js +726 -652
- package/package.json +57 -57
package/CHANGELOG.md
CHANGED
|
@@ -1,93 +1,108 @@
|
|
|
1
|
-
# Change log
|
|
2
|
-
|
|
3
|
-
This change log documents all release versions of homebridge-texecom
|
|
4
|
-
|
|
5
|
-
### 4.3.1-beta.
|
|
6
|
-
|
|
7
|
-
- **
|
|
8
|
-
- **
|
|
9
|
-
|
|
10
|
-
|
|
11
|
-
|
|
12
|
-
- **FIX** -
|
|
13
|
-
- **FIX** -
|
|
14
|
-
|
|
15
|
-
|
|
16
|
-
|
|
17
|
-
|
|
18
|
-
|
|
19
|
-
|
|
20
|
-
-
|
|
21
|
-
|
|
22
|
-
- **FIX** -
|
|
23
|
-
- **FIX** -
|
|
24
|
-
- **FIX** -
|
|
25
|
-
- **FIX** -
|
|
26
|
-
|
|
27
|
-
|
|
28
|
-
|
|
29
|
-
- **
|
|
30
|
-
- **
|
|
31
|
-
|
|
32
|
-
|
|
33
|
-
|
|
34
|
-
|
|
35
|
-
- **
|
|
36
|
-
|
|
37
|
-
|
|
38
|
-
|
|
39
|
-
- **FIX** -
|
|
40
|
-
|
|
41
|
-
|
|
42
|
-
|
|
43
|
-
|
|
44
|
-
|
|
45
|
-
|
|
46
|
-
|
|
47
|
-
|
|
48
|
-
|
|
49
|
-
|
|
50
|
-
|
|
51
|
-
|
|
52
|
-
|
|
53
|
-
|
|
54
|
-
|
|
55
|
-
|
|
56
|
-
-
|
|
57
|
-
|
|
58
|
-
|
|
59
|
-
|
|
60
|
-
-
|
|
61
|
-
|
|
62
|
-
|
|
63
|
-
|
|
64
|
-
|
|
65
|
-
|
|
66
|
-
|
|
67
|
-
|
|
68
|
-
|
|
69
|
-
-
|
|
70
|
-
|
|
71
|
-
|
|
72
|
-
|
|
73
|
-
|
|
74
|
-
|
|
75
|
-
|
|
76
|
-
|
|
77
|
-
###
|
|
78
|
-
|
|
79
|
-
- **
|
|
80
|
-
- **
|
|
81
|
-
|
|
82
|
-
|
|
83
|
-
|
|
84
|
-
|
|
85
|
-
-
|
|
86
|
-
|
|
87
|
-
###
|
|
88
|
-
|
|
89
|
-
- **
|
|
90
|
-
|
|
91
|
-
|
|
92
|
-
|
|
1
|
+
# Change log
|
|
2
|
+
|
|
3
|
+
This change log documents all release versions of homebridge-texecom
|
|
4
|
+
|
|
5
|
+
### 4.3.1-beta.3 (2026-08-19)
|
|
6
|
+
|
|
7
|
+
- **FEATURE** - `external_accessories` for installs that ran 4.3.0. That release published accessories outside the bridge, and HomeKit gives no way to move a standalone accessory onto a bridge without it counting as a new accessory, so the scenes, buttons and automations built on them would all have to be set up again. Turning this on republishes them the way 4.3.0 did, with the same identities, and they carry on working. Off by default, so a fresh install or one coming from 4.2.8 gets bridged accessories.
|
|
8
|
+
- **TWEAK** - Switching between the two modes tidies up after itself: turning the option on removes the bridged accessories that are no longer served.
|
|
9
|
+
|
|
10
|
+
### 4.3.1-beta.2 (2026-08-19)
|
|
11
|
+
|
|
12
|
+
- **FIX** - Arming or disarming areas 5 to 8 addressed the wrong areas. The area bitmask was being run through `parseInt(..., 16)` a second time, so area 5 asked the panel for areas 2, 3 and 5, area 6 for 2, 5 and 6, area 7 for 3, 6 and 7, and area 8 sent a value too large to fit the byte. Areas 1 to 4 were unaffected, their masks survive the round trip. Present since 4.2.8.
|
|
13
|
+
- **FIX** - An area number outside the 1 to 8 the panel can address is now reported rather than quietly sending a null byte.
|
|
14
|
+
|
|
15
|
+
### 4.3.1-beta.1 (2026-08-19)
|
|
16
|
+
|
|
17
|
+
- **FIX** - The arm/disarm command is retried once, as the login already was. Panels have been seen to ignore the first write and answer only the resend, which silently lost the command.
|
|
18
|
+
- **FIX** - An area and a zone carrying the same number were given the same serial number, so a panel with, say, zone 1 and area 1 published several accessories that were identical as far as HomeKit was concerned. Area serial numbers are now namespaced, zone serial numbers are unchanged. Present since 4.2.8.
|
|
19
|
+
|
|
20
|
+
### 4.3.1-beta.0 (2026-08-18)
|
|
21
|
+
|
|
22
|
+
- **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.
|
|
23
|
+
- **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.
|
|
24
|
+
- **FIX** - Accessories are held in the Homebridge accessory cache and reused across restarts, and accessories removed from the config are unregistered.
|
|
25
|
+
- **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`.
|
|
26
|
+
- **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.
|
|
27
|
+
- **FIX** - User numbers over 99 are no longer truncated when reading area messages from the panel.
|
|
28
|
+
- **FIX** - Areas are matched by area number rather than by their position in the config.
|
|
29
|
+
- **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.
|
|
30
|
+
- **TWEAK** - `engines.homebridge` widened back to `^1.6.0 || ^2.0.0`, 4.3.0 refused to run on Homebridge 1.x.
|
|
31
|
+
- **TWEAK** - Removed the unused `crypto-js` dependency.
|
|
32
|
+
|
|
33
|
+
### 4.3.0 (2026-05-23)
|
|
34
|
+
|
|
35
|
+
- **FIX** - Homebridge v2 compatibility: updated to new platform API with `didFinishLaunching` and `configureAccessory`
|
|
36
|
+
- **FIX** - Replaced deprecated `on('set', callback)` characteristic handler with `onSet` returning a Promise
|
|
37
|
+
- **FIX** - UUID collision between zones and areas sharing the same zone number
|
|
38
|
+
- **FIX** - All alarm-driven state updates now use `updateValue` instead of `setValue` to prevent feedback loops
|
|
39
|
+
- **FIX** - SerialPort v12 compatibility: `baudRate` (camelCase) and `@serialport/parser-readline` pipe parser
|
|
40
|
+
- **FIX** - Removed erroneous `registerAccessory` call alongside `registerPlatform`
|
|
41
|
+
|
|
42
|
+
### 4.2.8 (2025-7-28)
|
|
43
|
+
|
|
44
|
+
- **TWEAK** - Data conversion issue (Typo)
|
|
45
|
+
- **NEWS** - We are verified!!
|
|
46
|
+
|
|
47
|
+
### 4.2.7 (2025-7-28)
|
|
48
|
+
|
|
49
|
+
- **FIX** - Connection issue
|
|
50
|
+
- **NEWS** - We are verified!!
|
|
51
|
+
|
|
52
|
+
### 4.2.6 (2025-07-25)
|
|
53
|
+
|
|
54
|
+
- **FIX** - Fixed issues for Verification.
|
|
55
|
+
|
|
56
|
+
### 4.2.6-beta.2 (2025-01-22)
|
|
57
|
+
|
|
58
|
+
- **FIX** - Removed carbondioxide
|
|
59
|
+
|
|
60
|
+
### 4.2.6-beta.0 (2025-01-21)
|
|
61
|
+
|
|
62
|
+
- **TWEAK** - House keeping.
|
|
63
|
+
- **FIX** - Added carbonmonoxide and dioxide to config.schema.
|
|
64
|
+
|
|
65
|
+
### 4.2.5 (2025-01-03)
|
|
66
|
+
|
|
67
|
+
- **TWEAK** - Added the version for serial port to work on new node.js
|
|
68
|
+
|
|
69
|
+
### 4.2.5-beta.1 (2024-12-17)
|
|
70
|
+
|
|
71
|
+
- **TWEAK** - Added the version for serial port to work on new node.js
|
|
72
|
+
|
|
73
|
+
### 4.2.3 (2024-10-09)
|
|
74
|
+
|
|
75
|
+
- **TWEAK** - Trying to get verified by homebridge
|
|
76
|
+
|
|
77
|
+
### 4.2.2-beta2 (2024-10-09)
|
|
78
|
+
|
|
79
|
+
- **TWEAK** - Can not install in certain cases. Added post script to check if python is installed.
|
|
80
|
+
- **TEST** - Tested on Homebridge V2
|
|
81
|
+
|
|
82
|
+
### 4.2.2-beta1 (2024-09-14)
|
|
83
|
+
|
|
84
|
+
- **TWEAK** - Area triggering reduced to Away Arm only
|
|
85
|
+
- Not triggering when in Home and evening arm
|
|
86
|
+
|
|
87
|
+
### 4.2.1 (2024-09-14)
|
|
88
|
+
|
|
89
|
+
- **FEATURE** - Added arm and disarm for each area
|
|
90
|
+
- Added zones to each area to be able to trigger an alarm.
|
|
91
|
+
|
|
92
|
+
### 1.0.3 (2017-01-28)
|
|
93
|
+
|
|
94
|
+
- **FIX** - Zone matching did not work at all in previous release.
|
|
95
|
+
- **FEATURE** - A dwell time is now configureable for each zone before activation is cleared.
|
|
96
|
+
- **FIX** - Breaks added to zone searching for added performance.
|
|
97
|
+
|
|
98
|
+
### 1.0.2 (2017-01-24)
|
|
99
|
+
|
|
100
|
+
- **TWEAK** - Zone matching made much more efficient for added improvement.
|
|
101
|
+
|
|
102
|
+
### 1.0.1 (2017-01-21)
|
|
103
|
+
|
|
104
|
+
- **FIX** - Dependencies for serialport were incorrect which prevented NPM installation.
|
|
105
|
+
|
|
106
|
+
### 1.0.0 (2017-01-21)
|
|
107
|
+
|
|
93
108
|
- **FEATURE** - Initial release.
|
package/README.md
CHANGED
|
@@ -108,6 +108,24 @@ When an area is armed the panel reports the area and the user number, but not wh
|
|
|
108
108
|
|
|
109
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
110
|
|
|
111
|
+
### Upgrading from 4.3.0
|
|
112
|
+
|
|
113
|
+
**Only relevant if you ran 4.3.0.** Skip this if you came from 4.2.8 or earlier, or are installing fresh.
|
|
114
|
+
|
|
115
|
+
4.3.0 published every zone and area as a standalone accessory that had to be added to the Home app by hand. From 4.3.1 they are bridged again, which is how it worked up to 4.2.8 and means they appear on their own.
|
|
116
|
+
|
|
117
|
+
The catch is that HomeKit treats a standalone accessory and a bridged one as different accessories, so any scene, button or automation built on the ones 4.3.0 published stops working when they move back onto the bridge. Nothing the plugin does can carry that across.
|
|
118
|
+
|
|
119
|
+
If you set all that up under 4.3.0 and would rather keep it:
|
|
120
|
+
|
|
121
|
+
```json
|
|
122
|
+
"external_accessories": true
|
|
123
|
+
```
|
|
124
|
+
|
|
125
|
+
That republishes them exactly as 4.3.0 did, with the same identities, so everything keeps working untouched. The trade-off is that they stay outside the bridge, so a zone added later still has to be paired by hand.
|
|
126
|
+
|
|
127
|
+
Leaving it off, or leaving it out entirely, gives bridged accessories.
|
|
128
|
+
|
|
111
129
|
### Per-zone Configuration
|
|
112
130
|
|
|
113
131
|
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
|
@@ -155,6 +155,12 @@
|
|
|
155
155
|
]
|
|
156
156
|
}
|
|
157
157
|
},
|
|
158
|
+
"external_accessories": {
|
|
159
|
+
"type": "boolean",
|
|
160
|
+
"title": "Keep 4.3.0 External Accessories",
|
|
161
|
+
"default": false,
|
|
162
|
+
"description": "Only for installs that ran 4.3.0. That release published every zone and area outside the bridge, so they had to be added to the Home app by hand. Turn this on to keep publishing them that way, with the same identities, so the scenes, buttons and automations built on them keep working. Leave it off otherwise."
|
|
163
|
+
},
|
|
158
164
|
"debug":{
|
|
159
165
|
"type":"boolean",
|
|
160
166
|
"title":"Debug",
|