homebridge-texecom-full 4.3.0 → 4.3.1-beta.1

package/CHANGELOG.md

@@ -2,6 +2,33 @@
 
 This change log documents all release versions of homebridge-texecom
 
+### 4.3.1-beta.1 (2026-08-19)
+
+- **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.
+- **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.
+
+### 4.3.1-beta.0 (2026-08-18)
+
+- **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.
+- **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.
+- **FIX** - Accessories are held in the Homebridge accessory cache and reused across restarts, and accessories removed from the config are unregistered.
+- **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`.
+- **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.
+- **FIX** - User numbers over 99 are no longer truncated when reading area messages from the panel.
+- **FIX** - Areas are matched by area number rather than by their position in the config.
+- **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.
+- **TWEAK** - `engines.homebridge` widened back to `^1.6.0 || ^2.0.0`, 4.3.0 refused to run on Homebridge 1.x.
+- **TWEAK** - Removed the unused `crypto-js` dependency.
+
+### 4.3.0 (2026-05-23)
+
+- **FIX** - Homebridge v2 compatibility: updated to new platform API with `didFinishLaunching` and `configureAccessory`
+- **FIX** - Replaced deprecated `on('set', callback)` characteristic handler with `onSet` returning a Promise
+- **FIX** - UUID collision between zones and areas sharing the same zone number
+- **FIX** - All alarm-driven state updates now use `updateValue` instead of `setValue` to prevent feedback loops
+- **FIX** - SerialPort v12 compatibility: `baudRate` (camelCase) and `@serialport/parser-readline` pipe parser
+- **FIX** - Removed erroneous `registerAccessory` call alongside `registerPlatform`
+
 ### 4.2.8 (2025-7-28)
 
 - **TWEAK** - Data conversion issue (Typo)
@@ -57,7 +84,7 @@ This change log documents all release versions of homebridge-texecom
 - **FIX** - Zone matching did not work at all in previous release.
 - **FEATURE** - A dwell time is now configureable for each zone before activation is cleared.
 - **FIX** - Breaks added to zone searching for added performance.
- 
+
 ### 1.0.2 (2017-01-24)
 
 - **TWEAK** - Zone matching made much more efficient for added improvement.
@@ -68,4 +95,4 @@ This change log documents all release versions of homebridge-texecom
 
 ### 1.0.0 (2017-01-21)
 
-- **FEATURE** - Initial release.
+- **FEATURE** - Initial release.

package/README.md

@@ -96,6 +96,18 @@ For UDL
 | --- | --- | --- |
 | `udl` | 1234 | The UDL code on the panel to be able to arm and disarm alarm |
 
+For arm state reporting
+
+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.
+
+| Key | Default | Description |
+| --- | --- | --- |
+| `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. |
+| `app_users` | `[]` | User numbers the panel reports when an area is armed from this plugin, e.g. `[25, 254]`. |
+| `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`. |
+
+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.
+
 ### Per-zone Configuration
 
 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

@@ -46,6 +46,35 @@
                 "maxLength": 6,
                 "title": "UDL"
             },
+            "remote_users": {
+                "type": "array",
+                "title": "Remote / Keyfob Users",
+                "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.",
+                "items": {
+                    "type": "integer",
+                    "title": "User Number"
+                }
+            },
+            "app_users": {
+                "type": "array",
+                "title": "App Users",
+                "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.",
+                "items": {
+                    "type": "integer",
+                    "title": "User Number"
+                }
+            },
+            "default_arm_state": {
+                "type": "string",
+                "title": "Default Arm State",
+                "default": "away",
+                "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.",
+                "enum": [
+                    "away",
+                    "night",
+                    "stay"
+                ]
+            },
             "zones": {
                 "type": "array",
                 "title": "Zones",