Release 2.27.1 - #400
Merged
Merged
Release 2.27.1#400
Conversation
DATA_MIRROR_DIR copied cameras.json and data-meta.json but not the RTSP guide layer, so the downstream site kept rendering old guides after a guide correction (in 2.27.0, 23 brand guides were stale there, and Digital Watchdog's guide page contradicted its 115 camera pages). Copy data/rtsp-patterns.json too when it exists.
…roper brand names 29 guides were still in the old shape (no brand display name, port instead of default_port, label/url templates), so downstream sites printed names like "I Pro", "Idis", "Lts". Same paths and sources; brand names now match the camera records (i-PRO, IDIS, LTS, ZKTeco, HOLOWITS ...).
…s consistent
Mechanical consistency fixes from the 2026-10-01 CCTV expert audit; no
spec values are changed.
- protocols: add "rtsp" on 653 cameras that have an RTSP URL but didn't
list the protocol (the RTSP filter missed them).
- connectivity: add "ethernet" on 333 PoE cameras that didn't list it
(330 had no connectivity field at all).
- storage.onboard: true on 181 cameras that state a microSD capacity.
- Sonoff (4): RTSP templates use {user}:{pass}@{ip} like every other record.
- Home Assistant integration: generic_camera -> generic, motionEye ->
motioneye (41).
- Blue Iris profile: 8,229 values collapsed to the names Blue Iris uses.
ONVIF, Generic ONVIF/RTSP, ONVIF/RTSP, ONVIF/Generic, Generic/RTSP,
Generic, RTSP, TVT/Generic ONVIF -> Generic/ONVIF; VIVOTEK -> Vivotek;
Hikvision (generic) -> Hikvision; unsupported / None variants ->
Not supported.
From the 2026-10-01 CCTV expert audit: RTSP paths for cameras that listed RTSP but had none, ONVIF missing from protocols, PoE class vs power draw, and max resolution vs main stream. Every change cites the manufacturer's own documentation and was re-checked by an independent reviewer (kept 13, reverted 0 unsupported edits). 1 item(s) left unresolved where no official source exists; third-party RTSP lists were not used. - Mapesen (rtsp_no_url): No brand guide: strix/verified/mapesen.json was NOT created. The only official RTSP path Mapesen publishes is in the Sentrust 4MP/5MP Face Recognition Camera manuals (main /stream_0, auxiliary /stream_1, port 554). A brand guide would show that path on all ~340 other Mapesen cameras, which run different firmware (the road-surveillance manual shows RTSP port 8554, for example). Source: https://www.mapesen.com/web/userfiles/download/manual/20260415/MAPESEN%20Sentrust%204MP%20Face%20Recognition%20Camera%20User%20Manual%20V.H11.pdf - Mapesen (onvif_missing): Both affected lines support ONVIF, so "onvif" was added to protocols and onvif_port kept. B702 PTZ series: all five datasheets print 'ONVIF: Support'. Road-monitoring 80BFG403LM7A2-PTBA-RD: datasheet prints 'Interface(API): ONVIF,GB28181,Public Cloud'. All six datasheets were checked, not a sample. Source: https://www.mapesen.com/easy-ip-ptz/b702-ptz-series.html - Mapesen (max_res_vs_main_stream): Real error on LPR-H3KP500M4-T, fixed. The datasheet's maximum video resolution is 1920x1080@25fps; 3200x1800 is the still 'Imaging / Capture Image Resolution'. max_width/max_height set to 1920x1080 to agree with the main stream; megapixels 5 and label 5MP kept, because the maker states '5.0MP' and a '5MP starlight CMOS' sensor. Source: https://www.mapesen.com/web/userfiles/productfile/gengxin/LPR-H3KP500M4-Tspecification-mapesenV.H06-1.pdf
From the 2026-10-01 CCTV expert audit: RTSP paths for cameras that listed RTSP but had none, ONVIF missing from protocols, PoE class vs power draw, and max resolution vs main stream. Every change cites the manufacturer's own documentation and was re-checked by an independent reviewer (kept 229, reverted 0 unsupported edits). 6 item(s) left unresolved where no official source exists; third-party RTSP lists were not used. - ACTi (max_res_vs_main_stream): The old max_width/max_height were the spec tab's sensor 'Effective Pixels'. Set them to the top row (by pixel count) of 'Maximum Frame Rate vs. Resolution', which already equalled the main stream on 143 of 147 records. 144 fixed. Exceptions: B59A/B74/B74A use the 4096x2160 dewarped mode because ACTi rates them 8MP on it (B74/B74A main stream changed from 3072x2048@24 to 4096x21 Source: https://www.acti.com/product/<MODEL>?tab=specifications - ACTi (poe_class_vs_draw): Every flagged datasheet prints a class, so poe_class is unchanged everywhere. Where a separate PoE wattage is printed below the DC/AC figure, consumption_w now uses it (A412, A426 -> 12.95; A955, A957, A959 -> 51). The other 6 already equal what ACTi prints and stay flagged as maker contradictions. Source: ACTi - ACTi (onvif_missing): Decided per model on ACTi's own statement. 6 ACM models whose 2012+ datasheet revision prints 'ONVIF Compliant' got 'onvif' added to protocols (ACM-1231, 3401, 3701, 3701E, 7411, 8511). The other 92 (CAM-5xxx/6xxx/7xxx, ACM models with only pre-2012 datasheets, and A376/A377 thermal, A429-P1, A961, I98-K1, K71-P1, K72-P1, PCAM-1602, Z813-P1) have no ONVIF statement anywhere and Source: https://www.acti.com/products/onvif-conformant-products - ACTi (rtsp_no_url): No ACTi record was flagged for this; strix/verified/acti.json already exists in the required shape and was not touched. Source: strix/verified/acti.json
From the 2026-10-01 CCTV expert audit: RTSP paths for cameras that listed RTSP but had none, ONVIF missing from protocols, PoE class vs power draw, and max resolution vs main stream. Every change cites the manufacturer's own documentation and was re-checked by an independent reviewer (kept 17, reverted 0 unsupported edits). 3 item(s) left unresolved where no official source exists; third-party RTSP lists were not used. - Trassir (rtsp_no_url): Official RTSP documentation found, so I created strix/verified/trassir.json with the most common line: /live/main, /live/sub, /live/mobile (third stream, 4.x firmware), default port 554. TRASSIR publishes three manuals with three different paths. The main manual (/live/*) names 141 of the 205 flagged records at their exact revision. The 8 MP line (QTR manual, 12 records) uses / Source: https://www.dssl.ru/support/tech/documentation/ip-kameryi-trassir/
From the 2026-10-01 CCTV expert audit: RTSP paths for cameras that listed RTSP but had none, ONVIF missing from protocols, PoE class vs power draw, and max resolution vs main stream. Every change cites the manufacturer's own documentation and was re-checked by an independent reviewer (kept 36, reverted 0 unsupported edits). 5 item(s) left unresolved where no official source exists; third-party RTSP lists were not used. - Comelit (rtsp_no_url): Created strix/verified/comelit.json with /profile1 (main), /profile2 (sub), /profile3 (third) on port 554. This is the path for the Advance, Next and current Comelit CCTV lines, 153 of the 198 flagged records, each of which links one of Comelit's manuals documenting it on its product page; those records were not edited. The Smart series uses a different path (/0 main, /1 sub), Source: https://staticpro.comelitgroup.com/storage/2025/09/51030/mt-ipcam-comelit-cctv-en-6ed.pdf - Comelit (poe_class_vs_draw): Recorded what each datasheet prints. IPBCAMS08ZA: consumption_w 13.8 to 14.5 (the PoE figure), class 0 kept as printed. IPPTZA04Z30A (class 4, 30 W) and MIPPTZA04Z25A (class 3, 23 W) already match their datasheets and were left unchanged. All three flags will keep firing because the contradiction is in Comelit's own datasheets. Source: https://staticpro.comelitgroup.com/en-001/datasheets/14753-ipbcams08za.pdf - Comelit (max_res_vs_main_stream): IPDCAMS02ZA: resolution.max 2048x1536 was correct (datasheet lists 3MP output at 15 fps). The main stream entry was wrong and is now 2048x1536 at 15 fps; video.max_fps stays 30, which the datasheet gives for 1080p. Source: https://staticpro.comelitgroup.com/en-001/datasheets/14756-ipdcams02za.pdf
From the 2026-10-01 CCTV expert audit: RTSP paths for cameras that listed RTSP but had none, ONVIF missing from protocols, PoE class vs power draw, and max resolution vs main stream. Every change cites the manufacturer's own documentation and was re-checked by an independent reviewer (kept 166, reverted 0 unsupported edits). 9 item(s) left unresolved where no official source exists; third-party RTSP lists were not used. - Hikvision (onvif_missing): Decided per record from its own datasheet. Hikvision datasheets call ONVIF "Open Network Video Interface"; where the API row lists it (or a localized equivalent), "onvif" was added: 85 records. Where the API row lists only ISAPI/SDK variants (DS-2CD1021G0-I, -IVIE, DS-2CD1121G0-I, DS-2CD1131G0-I, DS-2CD1321G0-I, DS-2CD1331G0-I, DS-2DF2F200SCG-DY, DS-2XS2T41G1-ID), onvif_port wa Source: Per-record - Hikvision (poe_class_vs_draw): Hikvision PTZ datasheets print two figures, e.g. "PoE 802.3bt, type3, class6, max. 60W (Max. 50 W, including max. 10 W for IR and max. 8 W for heater)". I read the first as the supply/class budget and the bracketed one as the camera's maximum draw, and set consumption_w to the bracketed PoE figure (matches existing class-6/50 W and class-8/62-65 W records in the brand). This is Source: Per-record - Hikvision (max_res_vs_main_stream): resolution.max set to the largest main-stream resolution the datasheet lists: DS-2CD2367G2-L to 3200x1800; DS-2DE3A400BW-DE and DS-2DE4425IWG-E to 2560x1440; DS-2XC3646G0H-LIZSU and DS-2XV6445G0-Y to 2688x1520 (their "Max. Resolution" row says 2560x1440 but the main stream lists 2688x1520); DS-2XS6F85G1-ILC1 to 2688x1520 / 4 MP (8 MP is stills only). Where the stream entry was Source: Per-record
From the 2026-10-01 CCTV expert audit: RTSP paths for cameras that listed RTSP but had none, ONVIF missing from protocols, PoE class vs power draw, and max resolution vs main stream. Every change cites the manufacturer's own documentation and was re-checked by an independent reviewer (kept 13, reverted 0 unsupported edits). 3 item(s) left unresolved where no official source exists; third-party RTSP lists were not used. - AVYCON (rtsp_no_url): AVYCON documents three RTSP syntaxes on its own support portal, one per camera platform. The brand guide carries the Diversity (NDAA) Series, the largest line: /rtsp/streaming?channel=01&subtype=0, 1 and 2 for firmware v8.2.4+, with the older /ch01/0, /ch01/1, /ch01/2 form (also printed in the AVC-NS Series manual, section 8.7) recorded in the notes. Twelve records on the other Source: https://avycon.freshdesk.com/support/solutions/articles/36000299011-rtsp-syntax-for-ndaa-diversity-series-ip-cameras
From the 2026-10-01 CCTV expert audit: RTSP paths for cameras that listed RTSP but had none, ONVIF missing from protocols, PoE class vs power draw, and max resolution vs main stream. Every change cites the manufacturer's own documentation and was re-checked by an independent reviewer (kept 149, reverted 0 unsupported edits). 1 item(s) left unresolved where no official source exists; third-party RTSP lists were not used. - Longse (max_res_vs_main_stream): Brand-wide cause: resolution.max_width/max_height had been filled from the datasheet's sensor 'Effective Pixels' row (e.g. 3864x2192) instead of the main-stream output. Every Longse datasheet prints a 'Main Stream 1/2/3' table; the largest resolution listed under Main Stream 1 is now the record's max and its main-stream resolution. 119 records had max corrected; 17 had the main Source: Per-model - Longse (onvif_missing): All 11 flagged records support ONVIF per their own datasheets (10 PT-series PTZ: 'ONVIF Support (PROFILE S, PROFILE T)'; BMSCHFG200W: 'Support ONVIF 19.12(Profile S/T)'). Added "onvif" to protocols on all 11 and kept configs.frigate.onvif_port. All 11 datasheets were read, not a sample. Source: Per-model
From the 2026-10-01 CCTV expert audit: RTSP paths for cameras that listed RTSP but had none, ONVIF missing from protocols, PoE class vs power draw, and max resolution vs main stream. Every change cites the manufacturer's own documentation and was re-checked by an independent reviewer (kept 115, reverted 0 unsupported edits). 6 item(s) left unresolved where no official source exists; third-party RTSP lists were not used. - Dahua (onvif_missing): 110 flagged: 105 got 'onvif' added, 1 had onvif_port removed, 4 unresolved. The 101 CN-market records cite abbreviated dahuatech.com pages that have no 接入标准 row, so the decision was made per product line from full-spec official pages or Dahua-issued ONVIF Declarations of Conformance for the same line. 12 of them have a base-model document (source appended, last_verified bumped) Source: https://www.dahuatech.com/product/info/14065.html - Dahua (max_res_vs_main_stream): 15 flagged: 7 fixed, 3 left as not-an-error or ambiguous, 5 unresolved. Dahua 4MP datasheets often print Max. Resolution 2688×1520 as a 20 fps main-stream mode alongside 2560×1440@25/30. Where the datasheet states the 2688×1520 main-stream mode with its frame rate, the main stream entry was set to 2688x1520@20 (matches 35 existing Dahua records). Where the datasheet's Max. Reso Source: Per-model - Dahua (poe_class_vs_draw): IPC-PDBW5831-B360: datasheet prints Class 4, so poe_class stays 4 and consumption_w is now the PoE maximum 23.8 W (31.2 W was the AC 24V figure). DH-IPC-HFW8843K2-ZRL-IL4: poe_class 3 deleted because no class number is printed; 25.4 W (PoE max) kept. That deletion rests on the record's existing reseller-hosted transcription, since no official page was found. Source: https://materialfile.dahuasecurity.com/uploads/cpq/14937/datasheet/IPC-PDBW5831-B360_S0_datasheet_20221208.pdf
From the 2026-10-01 CCTV expert audit: RTSP paths for cameras that listed RTSP but had none, ONVIF missing from protocols, PoE class vs power draw, and max resolution vs main stream. Every change cites the manufacturer's own documentation and was re-checked by an independent reviewer (kept 121, reverted 0 unsupported edits). 2 item(s) left unresolved where no official source exists; third-party RTSP lists were not used. - i-PRO (onvif_missing): Decided per model, not per line: all 96 flagged records were checked against their own datasheet or product page. 90 state ONVIF conformance and got 'onvif' added to protocols. 5 had onvif_port removed because no official document claims ONVIF: M-24-FW-T and M-26-FW (budget advidia models) and the pre-ONVIF WV-NS202A, WV-NS954, WV-NW964. 1 (M-46-FW-V2-INDIA) is unresolved. Source: Per-model - i-PRO (poe_class_vs_draw): All 24 were wrong in the record, not in the datasheet. WV-X67 PTZ (15): consumption_w held the AC/DC mains figure, now the PoE++ figure of 70.2 W, Class 8 kept. WV-U31x01/U35x01-F2L(G) (8): current datasheets print 5.3 W Class 2, so 7.8/8.6 W became 5.3. WV-SFV531: datasheet PDF prints Class 0 (the web page's 'Class 2' is a typo), so poe_class is now 0 and 10.1 W is kept. Source: Per-model - i-PRO (max_res_vs_main_stream): WV-U11550-V3 and WV-U22550-F3L: the 2592x1944 maximum is a real H.265/H.264 output in 4:3 30 fps mode, so the main stream was raised from 2560x1440 to 2592x1944. WV-SW158: not an error (3MP is MJPEG-only, H.264 tops out at 1080p), left unchanged. Source: Per-model
From the 2026-10-01 CCTV expert audit: RTSP paths for cameras that listed
RTSP but had none, ONVIF missing from protocols, PoE class vs power draw,
and max resolution vs main stream. Every change cites the manufacturer's
own documentation and was re-checked by an independent reviewer (kept
5, reverted 0 unsupported edits). 4 item(s) left unresolved
where no official source exists; third-party RTSP lists were not used.
- LILIN (rtsp_no_url): Created strix/verified/lilin.json as a brand-level guide: main /stream0, sub /stream1, third /stream2, port 554. No path was copied into the 110 camera records. LILIN's manuals or HTTP API document confirm the scheme for the P2/Z2, P3/Z3, P5/Z5, P6/Z6, P7/Z7, V1 and S7/S8 lines. The fisheye F2R3682IM rests on LILIN's generic IP-camera SDK ('use rtsp://<ServerIP>/stream0 ~ strea Source: https://lilin.zendesk.com/hc/en-gb/articles/360045653451-LILIN-IP-Camera-RTSP-Information
- LILIN (poe_class_vs_draw): Deleted power.poe_class on all 4 flagged records: LILIN datasheets print 'PoE (IEEE 802.3af compliant)' and no class number, so the class 2 was not maker-stated. consumption_w was already the datasheet's PoE figure on 3 records and was left as is. On Z6R8952X3 it stays at the product page's 10 W because the datasheet PDF's 10.7 W sits in a column that appears mislabelled (see u Source: https://meritlilin.com/downloads/Catalogue-Z6R6552X3-EN.pdf
From the 2026-10-01 CCTV expert audit: RTSP paths for cameras that listed RTSP but had none, ONVIF missing from protocols, PoE class vs power draw, and max resolution vs main stream. Every change cites the manufacturer's own documentation and was re-checked by an independent reviewer (kept 89, reverted 0 unsupported edits). 5 item(s) left unresolved where no official source exists; third-party RTSP lists were not used. - Ganz (rtsp_no_url): Ganz sells several firmware families, and an official RTSP URL exists for only one of them. The Genstar Web Operation Guide V3.6 (Protocol Info page) gives the rule rtsp://ip:port/snl/live/cameraid/streamid for the GENSTAR line (ZN8-* and ZNT8-*). The thermal ZNT8-B1Fxx-1 is included because Ganz's own /series/genstar page and the GenStar Series brochure list it; the guide itse Source: https://computarganz.s3.amazonaws.com/Ganz+Active+Resources/Genstar+Web+Operation+Guide+Manual+V3.6_02.09.2024.pdf - Ganz (poe_class_vs_draw): No data change. The single flagged record (ZN-D5M212-DLP) reproduces the datasheet exactly: it prints PoE Class-2 and 13.08W. The dataset records what the maker prints, so both values stay; this is a datasheet inconsistency, not a transcription error. Source: https://computarganz.s3.amazonaws.com/Ganz+Active+Resources/ZN-D5M212-DLP_08.20.21_V3+spec.pdf
From the 2026-10-01 CCTV expert audit: RTSP paths for cameras that listed RTSP but had none, ONVIF missing from protocols, PoE class vs power draw, and max resolution vs main stream. Every change cites the manufacturer's own documentation and was re-checked by an independent reviewer (kept 16, reverted 7 unsupported edits). 9 item(s) left unresolved where no official source exists; third-party RTSP lists were not used. - Zavio (rtsp_no_url): Created strix/verified/zavio.json: port 554, main /video.pro1, sub /video.pro2, third /video.pro3. The path follows the stream-profile number and profiles are user-defined. It is printed in 18 archived manuals covering 22 dataset records (D4210, D4211, P6210, F3210, D7320/D7510, B7320/B7510, B8210, D8210, B8220, D8220, D8520, D4320/D4520, P4320, P4520, CB3210/CB3211, CB5220/CB6 Source: https://web.archive.org/web/20140719185557/http://www.zavio.com/downloads/product/83/Zavio%20User%20Manual_D4210_20140626.pdf - Zavio (onvif_missing): All 10 flagged models (B5110, D3100, F1100, F210A, F3000, F3110, F312A, F531E, F731E, M511E) have no ONVIF statement in their datasheet or user manual, while every ONVIF-capable Zavio datasheet prints it. Removed configs.frigate.onvif_port and did not add 'onvif' to protocols. Also corrected the notes that claimed ONVIF autodiscovery and switched home_assistant.integration from Source: Per-model - Zavio (poe_class_vs_draw): Every flagged datasheet prints the class the record carries (class 1 for D4210, D4211, D4320, D4520, P4320, P4520, P6210; class 0 for D8210, D8220, D8520), so poe_class was kept everywhere. consumption_w was changed only where the datasheet gives a separate PoE maximum: D4210 4.19, D4211 5.14, P6210 5.14. The other seven already match the datasheet. All ten still exceed their c Source: Each
From the 2026-10-01 CCTV expert audit: RTSP paths for cameras that listed RTSP but had none, ONVIF missing from protocols, PoE class vs power draw, and max resolution vs main stream. Every change cites the manufacturer's own documentation and was re-checked by an independent reviewer (kept 1, reverted 0 unsupported edits). 0 item(s) left unresolved where no official source exists; third-party RTSP lists were not used. - Dallmeier (rtsp_no_url): Resolved at brand level with a new guide, strix/verified/dallmeier.json: port 554, main /encoder1, sub /encoder2, third /encoder3. Dallmeier's own configuration manuals print these URLs for all three firmware families behind the 78 records, so no record needed its own rtsp_url_template and no camera file was edited. Domera OS (DDF6050DN, RDF5xxx/RDF6xxx, SDF6800/6900, DDZ5230/5 Source: https://www.dallmeier.com/api/1617455215/cloud?action=show&path=/Download_Centre_2.0/Product_Documents/02_Camera/RDF6100DN_Series/02_Documentation/Configuration/conf_DOMERA_OS_en.pdf
From the 2026-10-01 CCTV expert audit: RTSP paths for cameras that listed RTSP but had none, ONVIF missing from protocols, PoE class vs power draw, and max resolution vs main stream. Every change cites the manufacturer's own documentation and was re-checked by an independent reviewer (kept 1, reverted 0 unsupported edits). 1 item(s) left unresolved where no official source exists; third-party RTSP lists were not used. - Bolide (rtsp_no_url): No verified brand guide and no per-record rtsp_url_template. I created strix/verified/bolide.json with status "unverified" and empty templates, recording the legacy official paths (/ch00/0, /ch00/1, /0) under unverified_leads with their scope, plus default_port 554 from that manual. An unverified file is not shown as a guide on the site (src/lib/rtsp.ts requires status "verifie Source: https://cdn.shopify.com/s/files/1/0538/4264/1085/files/HD_NETWORK_CAMERA_USER_MANUAL.pdf
From the 2026-10-01 CCTV expert audit: RTSP paths for cameras that listed RTSP but had none, ONVIF missing from protocols, PoE class vs power draw, and max resolution vs main stream. Every change cites the manufacturer's own documentation and was re-checked by an independent reviewer (kept 67, reverted 0 unsupported edits). 0 item(s) left unresolved where no official source exists; third-party RTSP lists were not used. - Hyundai (onvif_missing): Decided per record, not per line: all 67 flagged By Demes product pages were fetched. 63 state ONVIF explicitly, so "onvif" was added to protocols and onvif_port kept. 4 (HYU-1088, HYU-1089, HYU-1091, HYU-942) list only 'ISAPI and SDK' with no ONVIF in any language version, so onvif_port was removed and the ONVIF wording in their frigate/home_assistant/blue_iris config notes wa Source: https://bydemes.com/en/products/cctv/network-cameras/
From the 2026-10-01 CCTV expert audit: RTSP paths for cameras that listed RTSP but had none, ONVIF missing from protocols, PoE class vs power draw, and max resolution vs main stream. Every change cites the manufacturer's own documentation and was re-checked by an independent reviewer (kept 59, reverted 0 unsupported edits). 7 item(s) left unresolved where no official source exists; third-party RTSP lists were not used. - Vivotek (poe_class_vs_draw): Every one of the 34 flagged datasheets was read. Root cause: consumption_w held the AC 24V / DC 12V / heater figure instead of the PoE figure. Set consumption_w to the printed PoE maximum on 28 records; kept poe_class where the datasheet prints a class (Class 0/3/4), deleted it on 9 records whose datasheets print only '802.3af PoE' / '802.3at PoE plus' with no class number (ip8 Source: Per-record - Vivotek (max_res_vs_main_stream): AF5127 / AF5127V: real error. Sensor is 2560x1920 but the maximum stream the datasheet states is 1920x1920; resolution.max_width/max_height set to 1920x1920 to agree with video.streams[main]. Source: https://download.vivotek.com/downloadfile/downloads/datasheets/af5127datasheet_en.pdf - Vivotek (onvif_missing): Decided per product line. (1) Legacy 7000-series / IP3137 MPEG-4 generation (17 records): no ONVIF in datasheets or user manuals -> onvif_port removed, integration notes and HA integration corrected. (2) VORTEX cloud line (8 records): datasheet/product-page protocol lists include RTSP/RTP/RTCP and WebRTC but no ONVIF -> onvif_port removed. (3) SC8131 stereo counting camera: no Source: Datasheets
From the 2026-10-01 CCTV expert audit: RTSP paths for cameras that listed RTSP but had none, ONVIF missing from protocols, PoE class vs power draw, and max resolution vs main stream. Every change cites the manufacturer's own documentation and was re-checked by an independent reviewer (kept 13, reverted 4 unsupported edits). 6 item(s) left unresolved where no official source exists; third-party RTSP lists were not used. - Vicon (rtsp_no_url): Created strix/verified/vicon.json with the most common line (Roughneck AI V2000 / Roughneck V2100, plus the V2000D-PTZ and V2008PTZ-IR): port 554, /stream1, /stream2, /stream3. This covers 22 flagged records through the guide with no per-record copy. Lines with a different documented path got their own template: the 10 V940-series records use /ch1/stream1 and /ch1/stream2, and Source: https://vicon-security.com/hubfs/Product%20Resources/Roughneck_V2000-V2100_UserGuide-02.pdf - Vicon (poe_class_vs_draw): All 4 flagged records left unchanged. Each datasheet prints '802.3af class 3' together with the recorded maximum draw (14.4 W for V2005D, 16.5 W for the Anavio dome) and gives no separate PoE wattage, so the records already match the source. Only last_verified was bumped to 2026-10-01. Source: https://info.vicon-security.com/hubfs/Product%20Resources/V2000D-Dome-Series_Datasheet1.pdf
From the 2026-10-01 CCTV expert audit: RTSP paths for cameras that listed RTSP but had none, ONVIF missing from protocols, PoE class vs power draw, and max resolution vs main stream. Every change cites the manufacturer's own documentation and was re-checked by an independent reviewer (kept 58, reverted 0 unsupported edits). 0 item(s) left unresolved where no official source exists; third-party RTSP lists were not used. - LTS (onvif_missing): All 55 flagged records get "onvif" added to protocols; onvif_port is kept. Every one was checked against its own LTS spec or data sheet (33 Platinum CMIP/LTCMIP current and legacy, 1 Platinum via an archived copy, 13 Pro-X LXIP, 8 Pro-VS VSIP); no model lacked ONVIF. Platinum sheets often write it as "Open Network Video Interface", which is why the token was missed. Source: pic.ltsmall.com - LTS (poe_class_vs_draw): lts-cmip5353-z: poe_class deleted because the data sheet prints only "PoE (802.3af)" with no class number. consumption_w stays 14, the data sheet's stated maximum. Source: https://pic.ltsmall.com/pdf/LTCMIP5353-Z_data%20sheet.pdf - LTS (max_res_vs_main_stream): A real error in both records, on the stream side: resolution.max 3840x2160 was right, and the main stream entry had recorded the 30 fps mode (2688x1520). Main stream set to 3840x2160 with fps 20 on lts-lxip3582we-28mda and lts-lxip3582web-28mda. Source: https://pic.ltsmall.com/software/6af16383e469a4dd9caa5c0d683170c2/LXIP3582WE-28MDA_Spec%20Sheet.pdf
From the 2026-10-01 CCTV expert audit: RTSP paths for cameras that listed
RTSP but had none, ONVIF missing from protocols, PoE class vs power draw,
and max resolution vs main stream. Every change cites the manufacturer's
own documentation and was re-checked by an independent reviewer (kept
1, reverted 0 unsupported edits). 0 item(s) left unresolved
where no official source exists; third-party RTSP lists were not used.
- Luminys (rtsp_no_url): Official RTSP documentation found, so I created the brand guide strix/verified/luminys.json and changed no camera records. Format: rtsp://{user}:{pass}@{ip}:554/video/livemedia?Ch=<channel>&Streamtype=<0 main | 1 sub>. The Luminys Wiki states it for Luminys devices in general; the Network Camera User Manual Rev. 1 (linked from 47 of the 58 product pages, across N3/N4/N5/N9) and Source: https://wiki.luminyscorp.com/NVR/RTSP_URL_Formatting
From the 2026-10-01 CCTV expert audit: RTSP paths for cameras that listed RTSP but had none, ONVIF missing from protocols, PoE class vs power draw, and max resolution vs main stream. Every change cites the manufacturer's own documentation and was re-checked by an independent reviewer (kept 51, reverted 0 unsupported edits). 3 item(s) left unresolved where no official source exists; third-party RTSP lists were not used. - Vikylin (rtsp_no_url): Vikylin is a multi-OEM brand, so the path is per series. Created strix/verified/vikylin.json with the path its own PG and YC manuals print: /stream0 (main), /stream1 (sub), port 554 (the manuals print the URL with no port, i.e. the RTSP default). That is the largest officially documented line (31 PG + 17 YC of 126 records). YC records (17) and PG2046IRCS-P rely on the guide; on Source: https://vikylin.com/download-center/
From the 2026-10-01 CCTV expert audit: RTSP paths for cameras that listed RTSP but had none, ONVIF missing from protocols, PoE class vs power draw, and max resolution vs main stream. Every change cites the manufacturer's own documentation and was re-checked by an independent reviewer (kept 8, reverted 0 unsupported edits). 7 item(s) left unresolved where no official source exists; third-party RTSP lists were not used. - Urmet (rtsp_no_url): Found official Urmet user manuals through the urmet.com Libretti download API. I created strix/verified/urmet.json with the most common line's paths: main /ch01/0, sub /ch01/1, third /ch01/2, port 554. This covers 23 flagged records: 1099/200-203 and 300-304, 1099/600/601/700/701, the 1093 M4I/M4ZI 4MP I-series, 1093/185FE/186BN/187C, and VK 1099/553. A different line (the Wi-F Source: https://www.urmet.com/it-it/Professionista/Strumenti/Libretti-e-Certificazioni
From the 2026-10-01 CCTV expert audit: RTSP paths for cameras that listed RTSP but had none, ONVIF missing from protocols, PoE class vs power draw, and max resolution vs main stream. Every change cites the manufacturer's own documentation and was re-checked by an independent reviewer (kept 48, reverted 0 unsupported edits). 2 item(s) left unresolved where no official source exists; third-party RTSP lists were not used. - BEWARD (onvif_missing): Old B-series (B10xx, B2920, B54, B85-5, B87L) and BD3070/BD4070/BD4370 pages list no ONVIF, and the 2010 BD3070/4070 manual has none either. On these, onvif_port was removed and the HA integration set to generic. B85-2-IP2 is the exception: the B85-x-IP2 manual (covering B85-2/B85-7) documents ONVIF on port 2000, so onvif was added to protocols and the port set to 2000. B85-5-I Source: https://www.beward.ru/files/a39f63536f3ef43bcf40946dc90469b4 - BEWARD (poe_class_vs_draw): Kept the poe_class each datasheet prints (Class 0 or Class 3). consumption_w is the printed PoE maximum where one is given (8 / 9.5 / 12 / 13 W). Where none is given, it is the overall datasheet maximum (19.2 / 51 W). Source: beward.ru
From the 2026-10-01 CCTV expert audit: RTSP paths for cameras that listed RTSP but had none, ONVIF missing from protocols, PoE class vs power draw, and max resolution vs main stream. Every change cites the manufacturer's own documentation and was re-checked by an independent reviewer (kept 43, reverted 3 unsupported edits). 1 item(s) left unresolved where no official source exists; third-party RTSP lists were not used. - Avigilon (poe_class_vs_draw): H3 PTZ and H4 PTZ pendant: consumption_w set to the printed PoE+ Class 4 figure of 25.5 W, poe_class 4 kept. H5A IR PTZ: 90 W PoE and Class 8 kept as printed; this is a false positive because 90 W is the switch budget. H6A/H6X domes: poe_class 3 changed to 4, since the datasheet prints PoE+ Class 4 for the full 25 W / 18 W modes (Class 3 is only a reduced 13 W mode). Source: Avigilon - Avigilon (onvif_missing): H4 ETD thermal and H4 Pro 6K/7K: onvif_port removed. Their datasheets leave ONVIF out of the protocol lists and never mention it, while the other Avigilon line datasheets do print ONVIF profiles. 'onvif' was not added to protocols. Source: avigilon-h4-etd-datasheet-en-rev5.pdf,
From the 2026-10-01 CCTV expert audit: RTSP paths for cameras that listed RTSP but had none, ONVIF missing from protocols, PoE class vs power draw, and max resolution vs main stream. Every change cites the manufacturer's own documentation and was re-checked by an independent reviewer (kept 11, reverted 0 unsupported edits). 3 item(s) left unresolved where no official source exists; third-party RTSP lists were not used. - Bolin Technology (rtsp_no_url): Created strix/verified/bolin.json (verified, port 554, main /media/video1, sub /media/video2) for the current firmware lines. The legacy lines that use different paths got per-record rtsp_url_template and best_substream: PSIA channels/0 and channels/1 for B9-418, BC-7, BC-9, EX1030SHD and SD530SHD (5 records), and /stream/main and /stream/sub for D412 and VCC-M2 (2 records). Source: https://knowledge.bolintechnology.com/ex1030huserguide - Bolin Technology (poe_class_vs_draw): No change. Class 8 and 85 W / 78 W are the values the datasheets print. The higher draw is the heater-on maximum, and Bolin advises against PoE for that load. Source: https://bolintechnology.com/wp-content/uploads/2023/08/EXU230H-Outdoor-PTZ-Camera-Datasheet-02052025.pdf - GW Security (rtsp_no_url): Unresolved. The guide stays status unverified because no official RTSP path is documented. Third-party paths were not used. Source: strix/verified/gw-security.json - GW Security (max_res_vs_main_stream): In all 3 records the main-stream entry was wrong (the sub-stream or a lower resolution had been recorded). Corrected it to the maximum main-stream resolution from the archived product spec tables. resolution.max_* was already correct. Source: web.archive.org
From the 2026-10-01 CCTV expert audit: RTSP paths for cameras that listed
RTSP but had none, ONVIF missing from protocols, PoE class vs power draw,
and max resolution vs main stream. Every change cites the manufacturer's
own documentation and was re-checked by an independent reviewer (kept
7, reverted 0 unsupported edits). 1 item(s) left unresolved
where no official source exists; third-party RTSP lists were not used.
- Verkada (rtsp_no_url): Resolved by the verified brand guide strix/verified/verkada.json: port 8554, /high for main and /standard for sub. These changes were already in the worktree from an earlier pass, and I re-checked them against both Verkada help pages today. Single-sensor cameras (35 flagged) use the guide. The multisensor CH/CY line (6 records) has per-record templates with the {camera_id} pref Source: https://help.verkada.com/command/organization-settings/integrations/set-up-the-verkada-fusus-camera-integration
- CNB (rtsp_no_url): Unresolved: no official RTSP path found, so nothing changed. Third-party paths were not used. Source: https://cnbtec.com/en/support/download
From the 2026-10-01 CCTV expert audit: RTSP paths for cameras that listed RTSP but had none, ONVIF missing from protocols, PoE class vs power draw, and max resolution vs main stream. Every change cites the manufacturer's own documentation and was re-checked by an independent reviewer (kept 10, reverted 0 unsupported edits). 4 item(s) left unresolved where no official source exists; third-party RTSP lists were not used. - Illustra (rtsp_no_url): Created a brand guide using /videoStreamId=1 and /videoStreamId=2 on port 554. Older lines with a different documented path carry it on their own records: the Pro mini-domes, Pro 30x PTZ and 5MP LT fisheye use /StreamId=N, and the Essentials Gen1 indoor mini-dome uses Dahua /cam/realmonitor. The Gen4 records' iSpy-derived /primarystream was replaced with the documented /videoSt Source: Illustra - Illustra (poe_class_vs_draw): LPR dome: consumption set to the PoE 12.95 W figure (class 3 printed). Indoor PTZ Gen4: poe_class deleted because only 'PoE+ Type 2 (30W)' is printed. The Flex 3MP/8MP bullets were left unchanged because the datasheet prints both class 3 and 15 W. Source: Illustra - Ajax (rtsp_no_url): Unresolved: Ajax publishes no RTSP path (the app shows the per-device links). No guide was created. Source: https://ajax.systems/support/manuals/onvif/
From the 2026-10-01 CCTV expert audit: RTSP paths for cameras that listed RTSP but had none, ONVIF missing from protocols, PoE class vs power draw, and max resolution vs main stream. Every change cites the manufacturer's own documentation and was re-checked by an independent reviewer (kept 91, reverted 0 unsupported edits). 5 item(s) left unresolved where no official source exists; third-party RTSP lists were not used. - Tenda (rtsp_no_url): Official Tenda RTSP FAQ found. Created strix/verified/tenda.json: port 8554, /profile0 (main) and /profile1 (sub) for most models, as status verified. Lines that differ carry their own URL: CP6 V2.0 and CT6 use port 554 /tenda and /tenda_sub; CP3 v3 and CH3 v2 use port 554 /ch=1?subtype=0|1. The other 30 flagged records use the brand guide. I removed the unsourced '/1, /2 typic Source: https://www.tendacn.com/us/material/show/844937962672197 - Tenda (onvif_missing): The datasheets for IC7-LRS and IT7-LRS list RTSP/HTTP/DHCP/DDNS only, CS6G is app/cloud-only and the CP6 V2.0 datasheet does not list ONVIF. So configs.frigate.onvif_port was removed from all four records, not 'onvif' added. CP6 got protocols [rtsp] and the generic HA integration. Source: https://static.tenda.com.cn/tdeweb/download/IC7-LRS/IC7-LRS%20EN-Datasheet.pdf - Anpviz (onvif_missing): All 35 records had no protocols array at all. Anpviz's official manuals for every camera line document ONVIF: the H Series 'All Model' manual (Integration Protocol, Open Network Video Interface), the U/Uprime 'All Model' manual ('Built in standard ONVIF protocol') and the U(M) manual ('supports standard ONVIF protocol'). Added protocols ["onvif"] to all 35, inserted in schema k Source: https://anpvizsupport.com/u_file/file/2503/25/d2f527a589.pdf - Bosch (poe_class_vs_draw): The flags came from storing the VDC/VAC maximum in consumption_w. Bosch datasheets print the class and a separate PoE maximum. I set consumption_w to the PoE maximum: 12.95 W for 15 Class 3 models, 12.9 W for 8 thermal models, 25.5 W for nde-8702-rxl and autodome-ip-5000-ir (Class 4). FLEXIDOME multi 7000i: poe_class set to 5 (PoE++), the class printed for its 42.3 W maximum. S Source: Bosch - Bosch (max_res_vs_main_stream): ndp-5533-z30l: max_width/max_height were the sensor's effective pixels (2688x1520). Changed to the datasheet's maximum streaming resolution, 2560x1440, which matches the main stream. Source: https://resources.keenfinity.tech/public/documents/NDP_5533_Z30L_Data_sheet_enUS_125941039499.pdf
From the 2026-10-01 CCTV expert audit: RTSP paths for cameras that listed RTSP but had none, ONVIF missing from protocols, PoE class vs power draw, and max resolution vs main stream. Every change cites the manufacturer's own documentation and was re-checked by an independent reviewer (kept 74, reverted 0 unsupported edits). 5 item(s) left unresolved where no official source exists; third-party RTSP lists were not used. - Axis (poe_class_vs_draw): From each datasheet: consumption_w = camera max on PoE, not midspan ratings (37/74 W) or DC figures. poe_class is kept only when that class covers the max draw (q1805/q1806 Class 6; p5414/p5415/p5654/q6052/q6054*/q6055 Class 4 at 16-19 W). It is deleted when the printed class only applies to a lower-power fallback mode and the max needs Axis High PoE with no class (P1354-E, P13 Source: Axis - Axis (max_res_vs_main_stream): Set max resolution to the datasheet's max main-stream output (M4216-V 2304x1728, the 5 MP sensor is downscaled; Q3527-LVE 3072x1728; Q3536-LVE 2688x1512). Corrected the main stream to match on P1357, P1487-LE and Q1755-E. Source: Axis - InVid Tech (rtsp_no_url): No brand guide. The Milesight-line records (INVID-MS-*, INVID-TS*; InVid datasheets call them Milesight Network Cameras) get per-record templates from Milesight's official RTSP KB: /main and /sub, with /sensor1/* for the multi-directional C5321 and /channel1/* for the dual-sensor C8477. Paramont, Secure and Vision lines are unresolved (no official camera RTSP doc). Source: https://support.milesight.com/support/solutions/articles/69000859092-rtsp-stream-of-milesight-network-camera-nvr-vms - ESCAM (rtsp_no_url): escam.cn product pages publish the RTSP URL per model in a second tab (the earlier 'not found' note was wrong). Guide set to the most common line, /live/0/main and /live/0/sub on port 554 (11 records). Per-record overrides: Xiongmai .sdp? form (9), /11 and /12 (3), port-80 /ch0_0.264 (QP180). 7 models' pages publish no RTSP URL. Source: http://www.escam.cn/product/60-en.html,
From the 2026-10-01 CCTV expert audit: RTSP paths for cameras that listed RTSP but had none, ONVIF missing from protocols, PoE class vs power draw, and max resolution vs main stream. Every change cites the manufacturer's own documentation and was re-checked by an independent reviewer (kept 58, reverted 0 unsupported edits). 3 item(s) left unresolved where no official source exists; third-party RTSP lists were not used. - Amcrest (onvif_missing): IP/ProHD/UltraHD line (IP2M/IP3M/IP4M/IP5M/IP8M): add 'onvif'. Every model's user manual documents the ONVIF settings tab, and the IP2M-850E, IP4M-1041 and IP5M-B1276 datasheets list ONVIF. ASH Smart Home line: remove onvif_port. Neither the datasheets nor the manuals mention ONVIF; they cover RTSP only. Source: support.amcrest.com - Amcrest (max_res_vs_main_stream): All 8 fixed from the datasheets. The main stream was raised to the stated max (2960x1668@20 for AL5M and B1276EB/EW, 3840x2160@20 for AL8M). Max resolution was corrected from sensor or wrong values to the main-stream max (IP2M-850E 1920x1080, IP4M-1041 2560x1440, IP5M-B1186EB-AI-V3 2960x1668). last_verified was set to 2026-10-01 on these. Source: Amcrest - Reolink (onvif_missing): Followed Reolink's official protocol-support KB by product type. Battery WiFi cameras (Argus, Solar Floodlight Cam) and NVR-kit cameras (B/D 400/500/800/1200) have no standalone ONVIF, so onvif_port was removed. PoE and plug-in cameras (RLC, Duo, CX820, Elite Pro Floodlight, OMVI) support ONVIF, so 'onvif' was added. Source: https://support.reolink.com/articles/900000617826-Which-Reolink-Products-Support-CGI-RTSP-ONVIF/ - Reolink (max_res_vs_main_stream): On both Video Doorbells (PoE/WiFi), main stream changed from 1920x2560 to 2560x1920, matching the official spec PDF; max resolution was already right. Source: cdn.reolink.com - Yudor (rtsp_no_url): Not found. Yudor's only official manual leaves the RTSP path user-set and blank by default, so no strix/verified/yudor.json was created and no records were changed. Source: https://www.yudor.com.tw/download.php?lang=en&tb=1&cid=21
…files) From the 2026-10-01 CCTV expert audit: RTSP paths for cameras that listed RTSP but had none, ONVIF missing from protocols, PoE class vs power draw, and max resolution vs main stream. Every change cites the manufacturer's own documentation and was re-checked by an independent reviewer (kept 23, reverted 1 unsupported edits). 4 item(s) left unresolved where no official source exists; third-party RTSP lists were not used. - Ernitec (rtsp_no_url): Created the brand guide from Ernitec's own Web Operation Guide (Sunell-style rule rtsp://ip:port/snl/live/<cameraid>/<streamid>): main /snl/live/1/1, sub /snl/live/1/2, port 554. Status changed from unverified to verified, and the crowd-sourced leads are kept as unverified_leads. No per-record changes. Source: https://ernitec.com/wp-content/uploads/Ernitec_Weboperation_Guide_IPcameras_Base_Pro.pdf - Oncam (rtsp_no_url): Created strix/verified/oncam.json for the EVO-05 line (13 of 26 records): main ?camera=13, sub ?camera=12, third ?camera=26. Lines with different paths got their own configs.frigate: EVO-12 uses /h264/video.sdp?name=FE1, EVO-180 uses /video.sdp?name=FE1 (no sub-stream documented for either, so no best_substream), and the C-08/C-12 records use /h264/video.sdp?name=MP1 with MP2 a Source: https://support.oncamgrandeye.com/hc/en-gb/articles/360017723940-Evolution-05-05-Mini-Connecting-to-the-camera-RTSP-stream - Eagle Eye Networks (rtsp_no_url): Created strix/verified/eagle-eye-networks.json with main /snl/live/1/1 only, taken from EEN's own KB, which gives it as the path for 'Eagle Eye Networks cameras'. EEN publishes no sub-stream path, so none was added. No per-record changes. Source: https://support.een.com/portal/en/kb/articles/adding-cameras-via-rtsp - Hanwha (poe_class_vs_draw): Five records had a 24VAC/heater or wrong figure in consumption_w; I replaced it with the datasheet's PoE maximum, which brings them within their class (qnp-6230rh 51, sno-7084r 12.5, snp-5321h 25, xno-6085r 12.95, xnp-a6374rh 51). poe_class was left as printed. xnd-8081rev and xno-6324rhp were left as is because their datasheets print a class that cannot carry the printed maxim Source: Hanwha - Hanwha (max_res_vs_main_stream): In QND-7080R and QNV-7080R, max_width changed from 2688 to 2592, matching the brochure's maximum resolution of 2592x1520 and the main stream. The 16 TNO thermal records are thermal false positives and were left unchanged. Source: https://hvsgmpprdstorage.blob.core.windows.net/pim/QNP-6230H/10/Brochures_Wisenet-Q-series_180202_EN.pdf
From the 2026-10-01 CCTV expert audit: RTSP paths for cameras that listed RTSP but had none, ONVIF missing from protocols, PoE class vs power draw, and max resolution vs main stream. Every change cites the manufacturer's own documentation and was re-checked by an independent reviewer (kept 45, reverted 3 unsupported edits). 4 item(s) left unresolved where no official source exists; third-party RTSP lists were not used. - Pelco (poe_class_vs_draw): Esprit Compact PTZ/Bispectral: kept poe_class 8 (printed). Set consumption_w from 90 to 71, the device's own 'PoE++ 71 W max'; 90 W is the PSE class budget. Sarix Enhanced 4/4P domes: poe_class 3 to 4, because the datasheet prints PoE+ 802.3at Class 4 and the 25 W max needs it. The 802.3af Class 3 mode is reduced/no-IR operation. Source: pelco.com - Pelco (onvif_missing): Spectra Mini IP SD4N line (8 records): the datasheet lists no ONVIF, so onvif_port was removed and protocols were left unchanged. The generic spectra-mini-ip record was not flagged and is untouched. Source: https://files.pelco.com/media/wp-content/uploads/2020/05/12192320/Spectra-Mini-IP-Network-Dome-System-Specification-Sheet.pdf - Foscam (onvif_missing): The Foscam firmware/manual family has an ONVIF switch and an ONVIF port, so "onvif" was added to the 21 models with an official manual package (or the ONVIF FAQ). PD8-W and W5EP-WB were left unresolved because no manual exists for them. Source: https://www.foscam.com/downloads/file.html?cate=manual&id=146 - Sparsh (poe_class_vs_draw): Both PTZ datasheets print 'PoE+ (802.3at)' with no class number, so poe_class was deleted. consumption_w stays 30 W (datasheet max). Source: b2b.sparshsecuritech.com - Sparsh (rtsp_no_url): Unresolved: no official RTSP path in any Sparsh document. No guide file was created. Source: https://www.sparshsecuritech.com/pages/support - DITS Vision (rtsp_no_url): Unresolved: the vendor publishes only OEM client software and no RTSP documentation. Source: https://ditsvision.in/download/ - ESP (rtsp_no_url): Unresolved: the datasheets and QSGs confirm RTSP/ONVIF but give no path. Source: https://espuk.com/product/HC428BB
From the 2026-10-01 CCTV expert audit: RTSP paths for cameras that listed RTSP but had none, ONVIF missing from protocols, PoE class vs power draw, and max resolution vs main stream. Every change cites the manufacturer's own documentation and was re-checked by an independent reviewer (kept 16, reverted 0 unsupported edits). 9 item(s) left unresolved where no official source exists; third-party RTSP lists were not used. - FLIR (onvif_missing): The Ariel Full HD, Quad HD and 4K UHD Bullet/Mini-Dome lines are certified ONVIF Profiles S, G & T, so I added 'onvif' to protocols on all 8 records and kept onvif_port 80. The datasheets themselves do not mention ONVIF. Source: https://flir.netx.net/file/asset/12312/original/attachment - FLIR (max_res_vs_main_stream): Thermal false positive (320x240 core, 640x512 native stream output). No change. Source: https://flir.netx.net/file/asset/10953/original/attachment - Redvision (rtsp_no_url): Unresolved: Redvision's public documentation gives no RTSP path. No guide file was created. - Verint (rtsp_no_url): Unresolved: no public official RTSP documentation. No guide file was created. - Arecont Vision (poe_class_vs_draw): The datasheets print the stated class and wattage exactly as recorded, so these are inconsistencies in the manufacturer's own data. No change. Source: sales.arecontvision.com/marketing/contents/*_DS_*.pdf - Infinova (poe_class_vs_draw): I kept the printed classes. On the PoE+ PTZs, consumption_w now holds the PoE figure instead of the 24V AC/DC figure: VS231 and VT231 changed from 55 to 50, VT230 from 35 to 25. VT230 is now within its class; the rest stay as datasheet inconsistencies. Source: infinova.com/DownloadPdf - Infinova (max_res_vs_main_stream): Main stream now uses the maximum resolution (30fps mode); 1080p becomes the sub stream and 384x256 is added as the third stream. max_width/max_height were already correct. Source: infinova.com/DownloadPdf - Jooan (rtsp_no_url): Unresolved: no official RTSP path. jooan.json stays unverified. Source: https://www.jooancam.com/en/support - Toshiba (rtsp_no_url): Created strix/verified/toshiba.json with the factory-default access names: /live.sdp main, /live2.sdp sub, /live3.sdp third, port 554. This covers 12 records. The IK-WP41A PTZ gets its own record-level /livestream template. Source: https://web.archive.org/web/20140330095606/http://toshibasecurity.com/pdf/_manuals/IK-WB81A_UserManual_v1.00.pdf
… (45 files)
From the 2026-10-01 CCTV expert audit: RTSP paths for cameras that listed
RTSP but had none, ONVIF missing from protocols, PoE class vs power draw,
and max resolution vs main stream. Every change cites the manufacturer's
own documentation and was re-checked by an independent reviewer (kept
45, reverted 1 unsupported edits). 8 item(s) left unresolved
where no official source exists; third-party RTSP lists were not used.
- TVT Digital (onvif_missing): The TD-9xxxS4-D line supports ONVIF ('Interface Protocol: ONVIF' in both sampled datasheets), so I added 'onvif' to protocols on all 9. Source: https://en.tvt.net.cn/file/other/e54b895119305f7a54915e6164a6dfa9.pdf
- TVT Digital (poe_class_vs_draw): The maker prints class 3 alongside an over-class draw. I kept the printed class and the max W, and only set last_verified. Source: https://en.tvt.net.cn/products/1532.html,
- Linovision (rtsp_no_url): Unresolved: no official RTSP doc, so no guide was created. Source: https://support.linovision.com/portal/en/kb
- AVTech (max_res_vs_main_stream): The DGM 5MP line's main stream outputs 2592x1944, while the 'Max. Resolution 2560x1944' row is a different figure. I set max_width to 2592 on all 9. Source: http://www.surveillance-download.com/user/datasheets/IPCAM/DGM/
- Digital Watchdog (max_res_vs_main_stream): The 2001x1121 and 1945x1109 values were total pixels, so I set max to 1920x1080 on the 4 MEGApix 1080p models. Source: DW
- Digital Watchdog (poe_class_vs_draw): The maker prints 802.3af Class 3 alongside a 13.9-15 W draw. No value change. Source: DW
- Hi-Focus (onvif_missing): The QA / T4 budget lines' datasheets and product page leave ONVIF out of the protocol list, while the brand lists ONVIF on its ONVIF-capable lines. I removed onvif_port on all 9. Source: api.hifocuscctv.com
- KBVision (onvif_missing): Unresolved: no official source states ONVIF either way. Source: https://kbvisiongroup.com/product/
- KBVision (max_res_vs_main_stream): Max main is 2688x1520@20, so I set the main stream to 2688x1520 at 20 fps. max_width/max_height were already correct. Source: https://kbvisiongroup.com/product/kx-c4012an3.html
- 360 Vision Technology (rtsp_no_url): Created the guide with /h264main and /h264sub on port 554, as documented in the V2.1.x installation manuals for Predator, Predator HD, Radar, Invictus and Visiondome HD. The 2025 V2.3 manuals only show a 'Copy RTSP URL' button (explained in notes). Source: https://www.360visiontechnology.com/wp-content/uploads/dlm_uploads/2016/03/Predator-HD-Installation-Manual-V2.1.23.2.pdf
- GeoVision (max_res_vs_main_stream): Fixed per model from the GV-IPCAM spec tables. Where the record used picture elements, I set max to the highest fps-table resolution (BL4713, EFER3700, SD4825-IR). Otherwise I set the main stream to the highest stated mode (BX4700, BX4700-E, EBD4700, EBD4704, FER12203). Source: https://dlcdn.geovision.com.tw/Manual/IPCAM/GV-IPCAM_Spec_table.pdf
- HikMicro (rtsp_no_url): Unresolved: no HikMicro-published RTSP path, so no hikmicro.json was created. Source: https://www.hikmicrotech.com/en/support/download-center/user-manual/
- HikMicro (onvif_missing): The HM-TD3118T R&D box cameras list only the ISAPI SDK and no ONVIF, so I removed onvif_port on both. Source: https://assets.hikvision.com/prd/normal/all/doc/m000148580/HM-TD3118T-1_Q_Datasheet_20240527.pdf
- HikMicro (max_res_vs_main_stream): Bi-spectrum false positives (thermal max vs optical main). Left as is.
- Mobotix (max_res_vs_main_stream): On MOVE VD1A, max was changed from effective pixels 2720x1976 to the stream max 2688x1944. The x26 (Mx6) cameras are not an error: 6MP is MxPEG-only and H.264 is capped at QXGA. Source: https://www.mobotix.com/sites/default/files/2022-10/Mx_TS_MOVE_Mx-VD1A-5-IR-VA_V1.13_EN_20221018.pdf
- Mobotix (poe_class_vs_draw): The maker prints class 0 and max 13.68 W. No value change. Source: https://www.mobotix.com/sites/default/files/2021-03/mx_TS_MOVE%20VB1A-4-IR_en_20210331.pdf
From the 2026-10-01 CCTV expert audit: RTSP paths for cameras that listed RTSP but had none, ONVIF missing from protocols, PoE class vs power draw, and max resolution vs main stream. Every change cites the manufacturer's own documentation and was re-checked by an independent reviewer (kept 32, reverted 2 unsupported edits). 7 item(s) left unresolved where no official source exists; third-party RTSP lists were not used. - Cinnado (onvif_missing): No ONVIF on any model. Removed onvif_port from all 6 records. Source: https://www.cinnado.com/newsinfo/1006524.html - Cinnado (rtsp_no_url): Unresolved. No official path is published (the URL is shown only in the app). No guide created. Source: https://www.cinnado.com/d15mp - Costar (rtsp_no_url): Costar Video StarNET/DirectNET line uses /trackID=1/2/3 on port 554, confirmed in all 7 operation manuals. Guide set to verified. AV* (Arecont) records keep their own template. Source: https://costarvideo-wpimages.sfo3.digitaloceanspaces.com/wp-content/uploads/2023/04/17013917/StarNET_Cameras_Bullet_Cameras_CBI5D4IW_Manual_CBI5D4IWOperation_ManualV1.1.pdf - Galayou (rtsp_no_url): Unresolved. The official FAQ only says to copy the URL from the Wansview Cloud app. Guide stays unverified. Source: https://www.galayou-store.com/g25mp - Galayou (onvif_missing): The Y1 official page makes no ONVIF claim (G2/G6/G7/Y4 do). Removed onvif_port from Y1. Source: https://www.galayou-store.com/y1 - D-Link (onvif_missing): All 6 datasheets state ONVIF compliant. Added onvif to protocols. DCS-2670L had no protocols array, so it got rtsp/onvif/http from its datasheet. Source: D-Link - Intelbras (onvif_missing): The VIP 7200 TH, VIP 1020 D and VIP SD1.3 MIR datasheets/manuals list no ONVIF (Intelbras-1 only). Removed onvif_port. Source: backend.intelbras.com - Intelbras (max_res_vs_main_stream): VIP 3430 B/D main stream corrected to 2560x1440 @ 20 fps (4M, 1-20 FPS). Source: https://backend.intelbras.com/sites/default/files/2021-06/Manual_VIP_3430_BD_01-21_A1.pdf - IQinVision (rtsp_no_url): Created strix/verified/iqinvision.json: main /now.mp4, port 554, from the archived official IQeye Network API Manual. Stream-based /stream1-4 is described in the notes only. Source: https://web.archive.org/web/2020/http://www.iqeye.com/Collateral/Documents/English-US/Products/IQDocs-Dwgs/Network%20API%20manual_Vicon.pdf - Sunell (max_res_vs_main_stream): Fixed max_width/max_height on 2 visible-light records (8088 fisheye and 8146) from their datasheets. The 4 thermal records are not errors (upscaled output). Source: sunellsecurity.com/resources/file - HiLook (onvif_missing): The consumer -C/-UC/-D models list API ISAPI/SDK only, with no ONVIF. Removed onvif_port. Source: assets.hikvision.com - HiLook (max_res_vs_main_stream): PTZ-N2C400C-DE left unchanged. The datasheet contradicts itself (max 2560x1440 vs main stream 1080p). Source: PTZ-N2C400C-DEB_Datasheet_20241219.pdf - HOLOWITS (onvif_missing): HWT pro line supports ONVIF (checked on 4 sibling datasheets): added onvif to the 2 HWT records. The R5A/U2-4RA consumer line datasheets list no ONVIF: removed onvif_port. Source: resources.holowits.com - HOLOWITS (poe_class_vs_draw): P5-4RV(4x)A: the datasheet prints no PoE class and no consumption figure. Removed both poe_class and the derived 18 W. Source: https://resources.holowits.com.sg/material/%5BDatasheet%5D%20HOLOWITS%20P5-4RV%284x%29A%20Datasheet%20v2.0.pdf - TKH Security (poe_class_vs_draw): FD980 left unchanged. The datasheet itself prints class 0 and max 13.68 W including the heater. Source: catalog.tkhsecurity.com/product/fd980/ - TKH Security (max_res_vs_main_stream): PD900/PD910 max resolution set to 2048x1536, the datasheet's maximum stream size. 2065x1553 is effective pixels. Source: catalog.tkhsecurity.com/product/pd900/, - TKH Security (rtsp_no_url): Unresolved for XCU-C-Thermal and XCU-Fusion: no official XCU RTSP doc was found. No guide created.
From the 2026-10-01 CCTV expert audit: RTSP paths for cameras that listed RTSP but had none, ONVIF missing from protocols, PoE class vs power draw, and max resolution vs main stream. Every change cites the manufacturer's own documentation and was re-checked by an independent reviewer (kept 32, reverted 2 unsupported edits). 17 item(s) left unresolved where no official source exists; third-party RTSP lists were not used. - Jennov (rtsp_no_url): No official path; left unresolved Source: jennov.com - Jennov (onvif_missing): PoE PTZ line (P87/P92) lists 'Support ONVIF2.2 protocol', so onvif added Source: https://jennovshop.com/products/4k-ptz-ip-camera-p87-8mp-poe - Kedacom (onvif_missing): China-market models list only GB/T 28181 / GA/T 1400 / GB 35114, so onvif_port removed on all 4 Source: https://www.kedacom.com/cn/rykksxj/41262.jhtml - Sanyo (max_res_vs_main_stream): Main stream set to the datasheet's largest network resolution (WB2000/WB4000 720x480; DP9584N 640x480, max fixed from sensor 768x494). fps dropped where it is stated only for another size Source: archived - Sanyo (rtsp_no_url): Unresolved, no official RTSP doc - Sony (onvif_missing): SNC-RX550N spec protocol list has no ONVIF, so onvif_port removed Source: https://web.archive.org/web/20080508171909/http://pro.sony.com/bbsc/ssr/product-SNCRX550N/B/ - Sony (max_res_vs_main_stream): SNC-RZ30N/P main stream set to max image size 736x480 / 736x544 Source: SNC-RZ30 - Sony (poe_class_vs_draw): SNC-VB770: no class printed, so poe_class removed and 16 W kept Source: sony.jp - Kenik (rtsp_no_url): Unresolved; official manuals point to the web UI only Source: https://files.kenik.pl/Instrukcje/Kamery%20i%20Rejestratory/ - Safire (onvif_missing): Datasheets list ONVIF Profile S/G/T, so onvif added to all 3 Source: Safire - Tapo (onvif_missing): C225: product page ONVIF Yes, so added. D225/D235 battery doorbells: official docs cover only RTSP, left unresolved Source: https://www.tapo.com/us/product/smart-camera/tapo-c225/ - Zebronics (max_res_vs_main_stream): Fisheye max set to main 2048x2048; IPPBSL5/IPPDSL5 main set to 2880x1620@20 Source: zebronics.com - ABUS (poe_class_vs_draw): Unresolved; abus.com blocked (403) - ABUS (max_res_vs_main_stream): Unresolved; abus.com blocked (403) - Akuvox (rtsp_no_url): Created strix/verified/akuvox.json from the official IPC admin guide: /live/ch00_0 main, /live/ch00_1 sub, port 554 Source: https://knowledge.akuvox.com/docs/streaming-and-integration-ipc - Ctronics (rtsp_no_url): Unresolved, no official path - EmpireTech (onvif_missing): Unresolved, no official ONVIF statement - eneo (poe_class_vs_draw): Datasheets print 802.3af with no class, so poe_class removed; 16 W / 15 W kept Source: eneo - IC Realtime (max_res_vs_main_stream): Main stream set to 2688x1520@20 per datasheet Source: IC - LaView (onvif_missing): F1: onvif added from the hardware-tested config report (#327) that ONVIF must be enabled in the app Source: #327 - LaView (rtsp_no_url): L2 unresolved, no official RTSP doc - Speco Technologies (onvif_missing): DD1/DD2 datasheet protocol lists have no ONVIF (only a trademark footer), so onvif_port removed Source: Speco - Tiandy (onvif_missing): Unresolved; spec files need a password - Uniview (poe_class_vs_draw): 802.3bt with no class printed, so poe_class removed on both; 31 W / 74 W kept Source: Uniview - Vitek (max_res_vs_main_stream): VTC-CB5N max set to 2592x1944 Source: Specs_VTC-CB5N.pdf - Vitek (poe_class_vs_draw): Datasheet prints Class 3 with 30 W itself; values kept and reported Source: VT-TPTZ30HRA-4PNS_Spec-Sheet.pdf - Brickcom (max_res_vs_main_stream): Max set to image resolution 2720x2040 Source: Brickcom - ClareVision (max_res_vs_main_stream): Max set to the 1080P main stream (2048x1536 is the sensor image) Source: Clare - Honeywell (poe_class_vs_draw): Datasheet prints Class 3 with 22 W itself; values kept and reported Source: ba-security-HC20WZ2R25-DS.pdf - IMOU (onvif_missing): Unresolved, spec page has no protocol rows - Jovision (rtsp_no_url): Unresolved; official FAQ unreachable - LiTokam (rtsp_no_url): Unresolved, no official path - Lorex (poe_class_vs_draw): No class printed, so poe_class removed; 40 W (PoE) kept Source: Lorex - Panasonic (max_res_vs_main_stream): Unresolved, datasheet 403 (likely a fisheye false positive) - Shelly (rtsp_no_url): Unresolved; official docs give no URL Source: https://shelly-api-docs.shelly.cloud/gen2/ComponentsAndServices/Camera
ch-bas
added
bug
build: mirror rtsp-patterns.json alongside cameras.json
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.1: data-consistency fixes from the second CCTV expert audit (2026-10-01). No new cameras.
Contents
/primarystreamto the official Gen4/videoStreamId=1and/videoStreamId=2.protocolsandonvif_portfall from 804 to 35.rtspadded to protocols on 653 cameras,etherneton 333 PoE cameras,storage.onboardon 181. Blue Iris and Home Assistant names normalized.Every value change cites the manufacturer's own documentation and was re-checked by an independent reviewer: 1,763 changes verified and kept, 24 reverted. Where a maker publishes nothing, the record is unchanged (161 items, listed per brand in the commit messages). Third-party RTSP lists were not used.
package.jsonis 2.27.1, the CHANGELOG entry is in, aggregates are regenerated and the data lint passes.Merging to
maincuts the public v2.27.1 release.