Release 2.27.0 - #397
Merged
Merged
Release 2.27.0#397
Conversation
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).
Fixes from the 2026-09-29 CCTV expert audit, each checked against an
official manufacturer source and then re-checked by an independent
reviewer (kept 1622, reverted 0 unsupported edits).
Fields: ip_rating ×1, rtsp_url_template ×1, best_substream ×1.
- RTSP, TVT Digital (tvt): The records were wrong and the guide is right. Every official TVT camera manual I found gives /profile1 (main), /profile2 (sub) and /profile3 (third) on port 554. No official TVT document gives /ch01/0. In all 404 records I changed rtsp_url_template to rtsp://{user}:{pass}@{ip}:554/profile1 and best_substream to rtsp://{user}:{pass}@{ip}:554/profile2, and appended the manual URL to sources. strix/verified/tvt.json is Source: https://www.manualslib.com/manual/2558336/Tvt-Digital-Td-5422e1.html?page=58
Changed records get the source appended and last_verified 2026-10-01.
Fixes from the 2026-09-29 CCTV expert audit, each checked against an
official manufacturer source and then re-checked by an independent
reviewer (kept 833, reverted 0 unsupported edits).
Fields: rtsp_url_template ×1, best_substream ×1, notes ×1, resolution.max_width/max_height ×8, ip_rating ×2.
- RTSP, Longse: Records were wrong and the guide is right. Longse's official FAQ says main = /0, sub = /1, third = /2, default port 554. I rewrote all 274 records from rtsp://{user}:{pass}@{ip}:554/ to rtsp://{user}:{pass}@{ip}:554/0 and added best_substream rtsp://{user}:{pass}@{ip}:554/1 right after it. The bare-root notes were replaced with the official format. The 3 records that cited community bare-root reports (lbh30ss500, lbp Source: https://web.archive.org/web/20190911214224/http://www.longse.com/SUPPORT/FAQ/Camera/2017/0822/973.html
Changed records get the source appended and last_verified 2026-10-01.
Fixes from the 2026-09-29 CCTV expert audit, each checked against an official manufacturer source and then re-checked by an independent reviewer (kept 64, reverted 16 unsupported edits). Fields: rtsp_url_template ×73, resolution.max_height ×2, ip_rating ×5. - RTSP, Honeywell: Decided per series; the brand guide (strix/verified/honeywell.json) is correct and was not edited. Records were wrong for these series and were rewritten: (a) 35 Series HC35* and the HC35T/HC60T bi-spectrum thermal models -> /live1s1.sdp (optical channel main stream); (b) 60 Series HC60* -> /live1s1.sdp. The 60UG02, 60UG04 and HC60WM20R1 guides document /live1s1.sdp. The older 60 Series configuration guides (HC60W35R Source: https://prod-edam.honeywell.com/content/dam/honeywell-edam/hbt/en-us/documents/manuals-and-guides/user-manuals/hon-ba-sec-600-60ug04-a-honeywell-60-series-cameras-user-guide-20250822.pdf Changed records get the source appended and last_verified 2026-10-01.
Fixes from the 2026-09-29 CCTV expert audit, each checked against an official manufacturer source and then re-checked by an independent reviewer (kept 70, reverted 0 unsupported edits). Fields: rtsp_url_template ×4, best_substream ×4, templates[+main path "/"] ×1, resolution.max_width/max_height ×46, video.streams[main].resolution ×6, resolution.megapixels ×1, resolution.label ×1, weight_g ×7. - RTSP, ACTi: (1) /rtsp/av0 records (a950, z83, z85, z97) were wrong. No official ACTi doc uses /rtsp/av0, and ACTi's generic VLC KB gives rtsp://IP:RTSPport/stream#. These records are now :554/stream1 with best_substream :554/stream2. Port 554 comes from the A950 firmware manual (download.acti.com/?id=28964). Caveat: the newer Z-series firmware manual (id=28904) is a Chinese-language copy and gives no default access name, so stre Source: https://download.acti.com/?id=29560 Changed records get the source appended and last_verified 2026-10-01.
Fixes from the 2026-09-29 CCTV expert audit, each checked against an official manufacturer source and then re-checked by an independent reviewer (kept 61, reverted 0 unsupported edits). Fields: ip_rating ×61. Changed records get the source appended and last_verified 2026-10-01.
Fixes from the 2026-09-29 CCTV expert audit, each checked against an official manufacturer source and then re-checked by an independent reviewer (kept 2, reverted 0 unsupported edits). Fields: ip_rating ×1. - RTSP, ABUS: No change (unresolved): no official ABUS doc found for the /Streaming/Channels/101 path on IPCA/IPCB/IPCS/TVIP4x510 cameras; the guide's /h264 applies only to the old TVIP platform. Records and strix/verified/abus.json left untouched. Source: https://c1.abus.com/asc-pim-assets-01/medias/docus/23/20200428-IPCB_Fix_TVIP4x510.pdf Changed records get the source appended and last_verified 2026-10-01.
Fixes from the 2026-09-29 CCTV expert audit, each checked against an official manufacturer source and then re-checked by an independent reviewer (kept 6, reverted 0 unsupported edits). Fields: ip_rating ×4, environment ×1, templates[/rtsp_tunnel].stream+source+strix_lead, notes, verified_on ×1. - RTSP, bosch: Records are right; the guide was incomplete. Bosch's own 'RTSP usage with Bosch VIP Devices' note (section 3.2.8) documents /rtsp_tunnel as a path alias on the default RTSP port (example RTSP://160.10.0.1/rtsp_tunnel). It does not change the transport mode and takes the same ?inst= query. The guide's existing /rtsp_tunnel template was labelled stream 'main-tunnel' with an unsourced port-10600 claim. I changed it to s Source: https://download.catalogosicurezza.com/DOWNLOAD/Bosch/Documentazione/TVCC/Manuali/Prodotti_IP/rtsp%20.pdf Changed records get the source appended and last_verified 2026-10-01.
Fixes from the 2026-09-29 CCTV expert audit, each checked against an official manufacturer source and then re-checked by an independent reviewer (kept 81, reverted 0 unsupported edits). Fields: resolution.max_width/max_height ×45, video.streams[main].resolution ×26, resolution.label ×4, resolution.megapixels ×7. Changed records get the source appended and last_verified 2026-10-01.
Fixes from the 2026-09-29 CCTV expert audit, each checked against an official manufacturer source and then re-checked by an independent reviewer (kept 96, reverted 0 unsupported edits). Fields: rtsp_url_template ×41, best_substream ×41, ip_rating ×14. - RTSP, American Dynamics: Both the records (/ufirststream) and the guide's main path (/primarystream) were wrong for these cameras. Every Gen 4 Installation and Configuration Guide (Pro Gen4, Flex Gen4, Essentials Gen4, and the PTZ, fisheye, multisensor and dual-sensor guides) gives rtsp://cameraip:554/videoStreamId=1 for Stream 1. The Essentials Gen4 and Fisheye guides give /videoStreamId=2 for Stream 2. Changed 41 records to main /videoStre Source: https://illustracameras.com/wp-content/uploads/2024/08/UM_PG4-2-4-5-8MP-Series_8200-2007-08_L.en_-1.pdf Changed records get the source appended and last_verified 2026-10-01.
Fixes from the 2026-09-29 CCTV expert audit, each checked against an official manufacturer source and then re-checked by an independent reviewer (kept 9, reverted 0 unsupported edits). Fields: templates[+] main ×1, ip_rating ×8. - RTSP, hanwha: The 36 records are correct and the guide was incomplete. Hanwha's official RTSP article documents a different path for multi-sensor cameras: /<sensor#>/profile2/media.smp, with sensor numbers 0-3 (0 = sensor 1). Its examples include PNM-9081VQ, PNM-9080VQ, PNM-9322VQP, PNM-9002VQ and PNM-7002VD. All 36 flagged files are PNM multi-sensor models using /0/profile2 for the main stream and /0/profile3 for the substream. I Source: https://support.hanwhavision.eu/hc/en-gb/articles/4414178841746-RTSP-URLs Changed records get the source appended and last_verified 2026-10-01.
Fixes from the 2026-09-29 CCTV expert audit, each checked against an official manufacturer source and then re-checked by an independent reviewer (kept 48, reverted 0 unsupported edits). Fields: rtsp_url_template ×42, best_substream ×2, notes ×1, ip_rating ×2, templates[+] /stream0/mobotix.mjpeg (main, MJPEG, strix_lead manual:mobotix) ×1. - RTSP, Mobotix: Records wrong. Neither /cam0/stream nor /mobotix.pro/mxpeg appears in any official MOBOTIX documentation. The fix depends on the platform. (1) Mx6 x16/x26 records (21) and single-sensor MOBOTIX 7 records (c71, c71-nurseassist, d71, p71, q71, v71): main is :554/stream/profile0 and best_substream is :554/stream/profile1. (2) Multi-sensor or thermal MOBOTIX 7 records (m73, m73-en54-v2/v3, m73-fm, s74, s74-dual, s74-en54 Source: https://community.mobotix.com/t/rtsp-streaming-with-mobotix-cameras/4912 Changed records get the source appended and last_verified 2026-10-01.
Fixes from the 2026-09-29 CCTV expert audit, each checked against an
official manufacturer source and then re-checked by an independent
reviewer (kept 39, reverted 2 unsupported edits).
Fields: rtsp_url_template + best_substream ×40, templates (added main /profile1 + sub /profile2, strix_lead manual:panasonic) + notes ×1.
- RTSP, Panasonic (Panasonic Middle East PM-series, TVT-OEM): The records were wrong. I rewrote 40 of the 41 flagged PM-* records from Dahua /cam/realmonitor?channel=1&subtype=0/1 to rtsp://{user}:{pass}@{ip}:554/profile1 (main) and /profile2 (sub), keeping port 554. The existing i-PRO /Src/MediaInput/* guide templates are correct for the WV-* i-PRO line and stay as they are. Because the PM line is a different OEM, I added /profile1 and /profile2 templates to strix/verified/pan Source: Panasonic
Changed records get the source appended and last_verified 2026-10-01.
Fixes from the 2026-09-29 CCTV expert audit, each checked against an official manufacturer source and then re-checked by an independent reviewer (kept 11, reverted 0 unsupported edits). Fields: video.max_fps ×2, video.streams[0].fps (main 3840x2160) ×1, environment ×3, weight_g ×5. Changed records get the source appended and last_verified 2026-10-01.
Fixes from the 2026-09-29 CCTV expert audit, each checked against an official manufacturer source and then re-checked by an independent reviewer (kept 32, reverted 0 unsupported edits). Fields: ip_rating ×32. Changed records get the source appended and last_verified 2026-10-01.
Fixes from the 2026-09-29 CCTV expert audit, each checked against an
official manufacturer source and then re-checked by an independent
reviewer (kept 5, reverted 16 unsupported edits).
Fields: rtsp_url_template ×16, best_substream ×16, ip_rating ×5.
- RTSP, JideTech: The records were wrong; the guide is correct. All 16 records had the bare placeholder path '/', which no JideTech document gives. JideTech's own RTSP section (shown on the BC60-8MP and P22-30X-8MP product pages) says main = /stream0 and sub = /stream1 on port 554. I set rtsp_url_template to rtsp://{user}:{pass}@{ip}:554/stream0 and best_substream to .../stream1 in all 16 files. strix/verified/jidetech.json is unchang Source: https://www.jidetech.com/products/jidetech-8mp-poe-bullet-ip-camera-apply-to-ndaa
Changed records get the source appended and last_verified 2026-10-01.
Fixes from the 2026-09-29 CCTV expert audit, each checked against an official manufacturer source and then re-checked by an independent reviewer (kept 58, reverted 4 unsupported edits). Fields: rtsp_url_template ×10, best_substream ×10, configs.blue_iris.notes ×10, ip_rating ×14, resolution.max_width/max_height ×14, resolution (megapixels/max_width/max_height/label) ×5, resolution.megapixels + label ×3, video.streams[main] resolution/fps ×2, video.streams[main].resolution ×1, strix/verified/flir.json templates ×1. - RTSP, flir: The 10 records were wrong. '/avc' is FLIR's path for its automation/science cameras (KB a_id/1053), not its security cameras. I rewrote them by product family. Saros DH-390 and DM-390 now use /stream1 with sub /stream2 (KB 5428 lists 'DM-Series, DX-Series, DH-390 Dome'). The 3 Quasar CP PTZs now use /stream1 with sub /stream2 (Quasar 4K IR PTZ Installation and User Guide, which says ch0/ch1 are legacy aliases). Elara Source: https://flir.custhelp.com/app/answers/detail/a_id/5428/~/flir-thermal-security-cameras---opening-and-troubleshooting-video-issues Changed records get the source appended and last_verified 2026-10-01.
Fixes from the 2026-09-29 CCTV expert audit, each checked against an official manufacturer source and then re-checked by an independent reviewer (kept 19, reverted 8 unsupported edits). Fields: ip_rating ×19, rtsp_url_template ×8, best_substream ×8. - RTSP, swann: Records were wrong. The Dahua-style /cam/realmonitor path appears in no official Swann document. Swann's official DVR/NVR manuals (DVR-1590 p.51, Platinum Digital HD p.57, DVR-1600 p.51) document rtsp://<ip>:554/ch01/0 for main and /ch01/1 for sub. I rewrote rtsp_url_template and added best_substream on the 8 NVR/recorder-attached cameras, and appended the manual URL to their sources. swwhd-outcam (standalone Wi-Fi) Source: https://www.manualslib.com/manual/1299190/Swann-Dvr-1590-Series.html?page=51 - RTSP, airlive: Unresolved, nothing changed. No official doc gives the RTSP URL for the current AirCam models. The CGI API's stream1/stream2 are encoder-config names, not RTSP paths. The guide's /mpeg4/media.3gp is from legacy-model manuals only. Source: https://www.airlive.com/data/download/file/AirCam_HTTP_CGI_API_v1.0.10-2.pdf Changed records get the source appended and last_verified 2026-10-01.
Fixes from the 2026-09-29 CCTV expert audit, each checked against an
official manufacturer source and then re-checked by an independent
reviewer (kept 50, reverted 0 unsupported edits).
Fields: rtsp_url_template ×13, best_substream ×13, resolution.megapixels ×1, resolution.label ×1, weight_g ×3, ip_rating ×15, resolution.max_width ×2, resolution.max_height ×2.
- RTSP, RVi: The 13 CFG records were wrong. Rewrote the main stream to rtsp://{user}:{pass}@{ip}:554/RVi/1/1 and the substream to /RVi/1/2. Records already had the KB URL added to sources; CFG61/CFG64 also got their quick-start PDFs. Did not change the guide file, which already has /RVi/1/1 and /RVi/1/2. Source: RVi
Changed records get the source appended and last_verified 2026-10-01.
Fixes from the 2026-09-29 CCTV expert audit, each checked against an official manufacturer source and then re-checked by an independent reviewer (kept 31, reverted 0 unsupported edits). Fields: rtsp_url_template ×9, best_substream ×5, templates (added main /ch01/0 + sub /ch01/1 direct-camera templates; notes; verified_on) ×1, resolution.max_width/max_height + video.streams[main].resolution/fps ×5, environment ×3, ip_rating ×4, resolution.megapixels / label ×1, resolution ×1, resolution.megapixels ×1, resolution + features ×1. - RTSP, camius: The records were wrong: they used the Dahua path /cam/realmonitor. The official Camius guide gives the direct IP-camera path as rtsp://CAMERA_IP:554/ch01/0 (main) and /ch01/1 (sub). All 9 records were rewritten to that path on port 554, with best_substream updated where it existed. The guide was also incomplete: it only had the NVR/DVR path /rtsp/streaming. The direct-camera main and sub templates were added to strix Source: https://www.camius.com/add-ip-cameras-on-network/ Changed records get the source appended and last_verified 2026-10-01.
Fixes from the 2026-09-29 CCTV expert audit, each checked against an official manufacturer source and then re-checked by an independent reviewer (kept 20, reverted 2 unsupported edits). Fields: resolution.megapixels ×6, ip_rating ×14, environment ×1, resolution.max_width/max_height ×2. Changed records get the source appended and last_verified 2026-10-01.
… (133 files)
Fixes from the 2026-09-29 CCTV expert audit, each checked against an
official manufacturer source and then re-checked by an independent
reviewer (kept 136, reverted 1 unsupported edits).
Fields: rtsp_url_template / best_substream(added) ×6, rtsp_url_template / best_substream; blue_iris.profile; notes ×1, rtsp_url_template / best_substream; configs.blue_iris.profile (76x); Dahua-claim notes ×1, ip_rating ×14, resolution.megapixels ×1, resolution.max_width ×1, resolution.max_height ×1, resolution.label ×1, video.streams[main].resolution ×1, environment ×1.
- RTSP, Digital Watchdog: The guide and all records were wrong. DW's official KB 323 ('MEGApix IP Camera RTSP Stream List') gives /profile1 (1st stream) and /profile2 (2nd stream) on port 554 for current MEGApix Core Professional and Value Line cameras, and /video1+audio1 and /video1s+audio1 for the DWC-XPZA03Mi/XPZA08Mi PTZs. The old realmonitor guide template cited a product page that has no RTSP or Dahua content. I rewrote the guide templa Source: https://digitalwatchdog.happyfox.com/kb/article/323-megapix-ip-camera-rtsp-stream-list/
Changed records get the source appended and last_verified 2026-10-01.
Fixes from the 2026-09-29 CCTV expert audit, each checked against an official manufacturer source and then re-checked by an independent reviewer (kept 30, reverted 0 unsupported edits). Fields: ip_rating ×28, environment ×1, resolution.megapixels ×1. Changed records get the source appended and last_verified 2026-10-01.
fix(amcrest): Helix RTSP format for the HLX- cameras (#394)
…Helix fix (2.26.1 not released separately)
ch-bas
added
documentation
Fixes from the 2026-09-29 CCTV expert audit, each checked against an official manufacturer source and re-checked by an independent reviewer (kept 20, reverted 1 unsupported edits). Fields: templates (added main /live.sdp + sub /live2.sdp; removed both from unverified_leads; notes + verified_on updated) ×1, brand ×19. - RTSP, vivotek: The records are right and the guide was incomplete. Vivotek documents both naming schemes: /live.sdp and /live2.sdp are the access names on firmware below 0x13, and they stay in place on units upgraded to 0x13+ without a factory reset. /live1s1.sdp and /live1s2.sdp apply only after a factory reset on 0x13+. I added /live.sdp (main) and /live2.sdp (sub) to strix/verified/vivotek.json as verified templates and removed Source: https://download.vivotek.com/downloadfile/downloads/usersmanuals/md8563-dehmanual_en.pdf Brand spelling unified to Vivotek (501 files).
Fixes from the 2026-09-29 CCTV expert audit, each checked against an
official manufacturer source and re-checked by an independent reviewer
(kept 280, reverted 0 unsupported edits).
Fields: rtsp_url_template ×1, notes ×1.
- RTSP, Uniarch: Records were wrong and the guide is correct. The official Uniarch FAQ gives rtsp://<ip>/media/video1 for main, /media/video2 for sub and /media/video3 for third. The old '/' path came from crowd-sourced iSpyConnect data. In all 70 records I rewrote rtsp_url_template to rtsp://{user}:{pass}@{ip}:554/media/video1. None of these records had a best_substream key, so I didn't add one. strix/verified/uniarch.json is unchan Source: https://www.uniarch.cn/Support/FAQ/202209/951565_575360_0.htm
Fixes from the 2026-09-29 CCTV expert audit, each checked against an official manufacturer source and re-checked by an independent reviewer (kept 75, reverted 1 unsupported edits). Fields: rtsp_url_template ×1, best_substream ×1, templates ×1. - RTSP, ClareVision: Split by product line. Current CLR-V100/V200/V300 line: records were wrong, so all 25 were rewritten to /0 (main) and /1 (sub), following Clare's help-center RTSP article, which covers only V100/V200/V300. Legacy CV-* and ClareVision Plus CVP-* line (21 flagged records): the records are right and the guide was incomplete. These are Hikvision-firmware devices, and Clare's ClareVision API Product Bulletin (Doc ID 528) Source: https://www.clarecontrols.com/helpcenter/clarevision-camera-nvr-rtsp-stream-urls CLR-V (/0, /1) cameras: Blue Iris switched from the Hikvision profile to Generic/ONVIF and the Hikvision-protocol notes replaced, so the integration notes match the documented paths.
Fixes from the 2026-09-29 CCTV expert audit, each checked against an official manufacturer source and re-checked by an independent reviewer (kept 1, reverted 3 unsupported edits). Fields: rtsp_url_template ×3, best_substream ×3. - RTSP, EZVIZ: Records wrong. EZVIZ's official support FAQ documents rtsp://admin:<verification code>@<ip>:554/ch1/main. No official EZVIZ source documents /h264/ch1/main/av_stream (that is a Hikvision path). Rewrote rtsp_url_template to /ch1/main and best_substream to /ch1/sub in all 3 affected records (c6n, h8-pro-3k, h8c), added the FAQ to sources and set last_verified to 2026-10-01. Guide unchanged. Source: https://support.ezviz.com/faq/article/How-to-set-up-C6N-TY1-TY2-as-a-webcam
Fixes from the 2026-09-29 CCTV expert audit, each checked against an official manufacturer source and re-checked by an independent reviewer (kept 28, reverted 0 unsupported edits). Fields: resolution.megapixels / max_width / max_height / video.streams[main].resolution ×1, environment ×4, ip_rating ×18, resolution.max_height / resolution.label / video.max_fps / ip_rating ×1, video.max_fps and video.streams[main 3840x2160].fps ×2, resolution.max_width / max_height / video.streams[main].resolution ×2.
…ass (24 files) Fixes from the 2026-09-29 CCTV expert audit, each checked against an official manufacturer source and re-checked by an independent reviewer (kept 24, reverted 2 unsupported edits). Fields: rtsp_url_template ×4, resolution ×1, environment ×2, ip_rating ×17. - RTSP, Canon: Records were wrong and the guide is correct. The official Canon operation guides for VB-H47/VB-M46 (vbneog-e.pdf), VB-R13VE and VB-S805D document only rtsp://IP:port/rtpstream/config1(to 5)=r|u|m. All 4 records were rewritten to /rtpstream/config1=r. They had no best_substream, so none was added. strix/verified/canon.json is unchanged. Source: http://gdlp01.c-wss.com/gds/1/0300044031/05/vbneog-e.pdf
… pass (42 files) Fixes from the 2026-09-29 CCTV expert audit, each checked against an official manufacturer source and re-checked by an independent reviewer (kept 47, reverted 0 unsupported edits). Fields: ip_rating ×13, environment ×1, video.max_fps ×2, video.streams[0].fps (3840x2160) ×2, resolution.megapixels ×1, resolution.label ×1, aliases ×1, release_notes ×1, brand ×1. Brand spelling unified to BEWARD (361 files) so the brand has one page.
Fixes from the 2026-09-29 CCTV expert audit, each checked against an official manufacturer source and re-checked by an independent reviewer (kept 26, reverted 0 unsupported edits). Fields: resolution.max_width/max_height/label ×2, ip_rating ×9, environment ×1, resolution.megapixels ×3, resolution.max_width/max_height ×2. - RTSP, annke: No change to the record or strix/verified/annke.json. Only the WZ520 was flagged, and no official ANNKE source for its RTSP path was found (community sources say port 8554, /Streaming/Channels/101). Reported as unresolved. Source: https://ipcamtalk.com/threads/annke-wz520-ptz.80933/
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.
Release 2.27.0: data-quality fixes from the 2026-09-29 CCTV expert audit, plus the Amcrest Helix RTSP fix (#395). The planned 2.26.1 patch (#396, closed) is folded in here.
Contents
/1/1and/1/0(Correction: Amcrest HLX-IP5M-B102EW-AI #394, fix(amcrest): Helix RTSP format for the HLX- cameras (#394) #395).strix/verified/) corrected or completed for 11 brands, including Vivotek's/live.sdpnaming.ip_ratingadded to 301 cameras, about 140 resolution fixes, 15 weight fixes, 18 environment fixes.About 1,630 records in total. Every edit cites an official manufacturer source and was re-checked by an independent reviewer, which reverted edits its source didn't support. Values a manufacturer doesn't publish were left unchanged, not estimated. No new cameras.
package.jsonis 2.27.0, the CHANGELOG entry is in, and the data lint passes.Merging to
maincuts the public v2.27.0 release. The CHANGELOG date says "Unreleased"; I'll set it when you're ready to merge.Fixes #394