From 14a808d964bec17f1992b97c7efc875311497b76 Mon Sep 17 00:00:00 2001 From: bassem chagra Date: Thu, 1 Oct 2026 12:12:34 +0200 Subject: [PATCH 1/3] chore: open 2.26.1 development --- package.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/package.json b/package.json index 5acff192b6..e1398aebcb 100644 --- a/package.json +++ b/package.json @@ -41,5 +41,5 @@ "ajv": "^8.20.0", "ajv-formats": "^3.0.1" }, - "version": "2.26.0" + "version": "2.26.1" } From 30e53f01b635d34279890be51142a092d35134eb Mon Sep 17 00:00:00 2001 From: bassem chagra Date: Thu, 1 Oct 2026 12:13:45 +0200 Subject: [PATCH 2/3] =?UTF-8?q?docs(changelog):=202.26.1=20=E2=80=94=20Amc?= =?UTF-8?q?rest=20Helix=20RTSP=20fix=20(#394)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- CHANGELOG.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index 737dda5d39..7f0ea6c40d 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -6,6 +6,13 @@ Format: [Keep a Changelog](https://keepachangelog.com/en/1.0.0/) --- +## [2.26.1] — 2026-10-01 + +### Fixed +- **Amcrest Helix RTSP (#394)** — the three Helix (`HLX-`) cameras (`HLX-IP5M-B102EW-AI`, `HLX-IP5M-T103EW-AI`, `HLX-IP8M-T303EW-AI`) carried the Dahua-style `/cam/realmonitor?channel=1&subtype=0` path used by other Amcrest models. Amcrest's KB article [Accessing Legacy Helix Devices Using RTSP](https://support.amcrest.com/hc/en-us/articles/49119561879437-Accessing-Legacy-Helix-Devices-Using-RTSP) documents a different format for this line: `rtsp://user:pass@ip:554//`, with stream 1 = main and 0 = sub. Main is now `/1/1` and the substream `/1/0`, with `/1/main` / `/1/sub` noted as a fallback. Home Assistant now points at the ONVIF integration and Blue Iris at Generic/ONVIF instead of the Dahua-based options. The Amcrest RTSP guide (`strix/verified/amcrest.json`) gains the Helix templates, marked Helix-only. Reported via the website by SrDri and Michael M. (Amcrest support). + +No new cameras. + ## [2.26.0] — 2026-09-30 Dataset reaches **28,400 cameras / 230 brands** (+1,038). A deep gap-fill across already-covered brands from **official manufacturer sources** — every field is transcribed from a manufacturer specification (or its archived copy), and fields a manufacturer does not publish are omitted rather than estimated. No Provision-ISR models are included. Four new brands (Vivint, Defender, Geeni, Merkury); the rest fill genuine catalogue gaps found via manufacturer datasheet APIs/PDFs, China-domestic mirrors, and Internet-Archive captures of discontinued lines. From 9e310a25242091a2ce1176273f1965c71ed15fe9 Mon Sep 17 00:00:00 2001 From: bassem chagra Date: Thu, 1 Oct 2026 12:13:56 +0200 Subject: [PATCH 3/3] docs(changelog): avoid a GitHub @-mention in the 2.26.1 entry --- CHANGELOG.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 7f0ea6c40d..6598c6a9f4 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -9,7 +9,7 @@ Format: [Keep a Changelog](https://keepachangelog.com/en/1.0.0/) ## [2.26.1] — 2026-10-01 ### Fixed -- **Amcrest Helix RTSP (#394)** — the three Helix (`HLX-`) cameras (`HLX-IP5M-B102EW-AI`, `HLX-IP5M-T103EW-AI`, `HLX-IP8M-T303EW-AI`) carried the Dahua-style `/cam/realmonitor?channel=1&subtype=0` path used by other Amcrest models. Amcrest's KB article [Accessing Legacy Helix Devices Using RTSP](https://support.amcrest.com/hc/en-us/articles/49119561879437-Accessing-Legacy-Helix-Devices-Using-RTSP) documents a different format for this line: `rtsp://user:pass@ip:554//`, with stream 1 = main and 0 = sub. Main is now `/1/1` and the substream `/1/0`, with `/1/main` / `/1/sub` noted as a fallback. Home Assistant now points at the ONVIF integration and Blue Iris at Generic/ONVIF instead of the Dahua-based options. The Amcrest RTSP guide (`strix/verified/amcrest.json`) gains the Helix templates, marked Helix-only. Reported via the website by SrDri and Michael M. (Amcrest support). +- **Amcrest Helix RTSP (#394)** — the three Helix (`HLX-`) cameras (`HLX-IP5M-B102EW-AI`, `HLX-IP5M-T103EW-AI`, `HLX-IP8M-T303EW-AI`) carried the Dahua-style `/cam/realmonitor?channel=1&subtype=0` path used by other Amcrest models. Amcrest's KB article [Accessing Legacy Helix Devices Using RTSP](https://support.amcrest.com/hc/en-us/articles/49119561879437-Accessing-Legacy-Helix-Devices-Using-RTSP) documents a different format for this line: `rtsp://{user}:{pass}@{ip}:554//`, with stream 1 = main and 0 = sub. Main is now `/1/1` and the substream `/1/0`, with `/1/main` / `/1/sub` noted as a fallback. Home Assistant now points at the ONVIF integration and Blue Iris at Generic/ONVIF instead of the Dahua-based options. The Amcrest RTSP guide (`strix/verified/amcrest.json`) gains the Helix templates, marked Helix-only. Reported via the website by SrDri and Michael M. (Amcrest support). No new cameras.