fix(amcrest): Helix RTSP format for the HLX- cameras (#394) - #395
Merged
Merged
Conversation
ch-bas
force-pushed
the
fix/amcrest-helix-rtsp
branch
from
October 1, 2026 10:11
3da0b3e to
5b5c177
Compare
ch-bas
force-pushed
the
fix/amcrest-helix-rtsp
branch
from
October 1, 2026 10:12
5b5c177 to
34d01d6
Compare
Closed
Amcrest's Helix line doesn't use the Dahua /cam/realmonitor path the rest
of the brand uses. Amcrest's KB article "Accessing Legacy Helix Devices
Using RTSP" (filed under all three HLX cameras) gives
rtsp://{user}:{pass}@{ip}:554/<channel>/<stream>, stream 1 = main, 0 = sub.
- HLX-IP5M-B102EW-AI, HLX-IP5M-T103EW-AI, HLX-IP8M-T303EW-AI:
main /1/1, substream /1/0, with a note (fallback /1/main, /1/sub)
- Home Assistant: onvif instead of the Dahua-API amcrest integration
- Blue Iris: Generic/ONVIF instead of the Dahua profile
- KB article added as a source; last_verified bumped
- strix/verified/amcrest.json: Helix templates + note, so the Amcrest
RTSP guide no longer implies realmonitor for every model
Reported via the website by SrDri and Michael M. (Amcrest support).
ch-bas
force-pushed
the
fix/amcrest-helix-rtsp
branch
from
October 1, 2026 10:14
34d01d6 to
9820145
Compare
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #394. Targets
release/2.27.0(the planned 2.26.1 patch was folded into 2.27.0).What was wrong
All three Amcrest Helix cameras used the Dahua-style path
/cam/realmonitor?channel=1&subtype=0, like the rest of the brand. Amcrest's KB article Accessing Legacy Helix Devices Using RTSP gives a different format for Helix:rtsp://user:pass@ip:554/<channel ID>/<stream ID>, with stream 1 for main and 0 for sub. Amcrest files that article under exactly these three models.Changes
/1/1/1/0/1/1/1/0/1/1/1/0/1/mainand/1/subas a fallback. The article's wording ("main" (1), "sub" (0)) can also be read that way.onvifinstead ofamcrest. The native integration targets the Dahua-based API of Amcrest's other cameras.Generic/ONVIFinstead ofDahua.last_verifiedis bumped.strix/verified/amcrest.json: adds the Helix main/sub templates, marked "Helix (HLX-) line only", and a note.verifiedstays false, because the article is documentation, not a device test.Checks
npm run lintpasses.schema/camera.schema.json.Reported via the website by SrDri and Michael M. (Amcrest support).