Migrating a third-party camera fleet to UniFi Protect
UniFi Protect will adopt your existing third-party cameras. That sentence is true, and it is also where most fleet migrations go wrong — because it is only half the story. Since UniFi Protect 5.0.33, the platform can adopt ONVIF-compatible cameras directly, giving you live view and recorded playback from the Hikvision, Dahua, Axis, Hanwha, Amcrest or Reolink hardware already on your walls. What it does not give you, on those same cameras, is the intelligence — motion and smart detections, licence-plate and face recognition, audio, PTZ control. That layer sits behind a separate accessory, the AI Port, whose per-camera economics quietly decide whether a large migration makes sense at all. And the traffic runs one way: ONVIF cameras flow into Protect, but a UniFi Protect camera will not flow back out into a third-party recorder. This is the honest map of what migrates, what does not, what it costs, and the phased path we use so the gap between video and intelligence never becomes a surprise on site.
Yes for the video. No, by default, for the intelligence.
When a business with an existing camera system asks whether it can move to UniFi Protect “without ripping everything out,” the honest answer has two halves that point in different directions.
The first half is genuinely good news. UniFi Protect natively supports ONVIF-compatible third-party cameras at the controller level — a capability Ubiquiti added in UniFi Protect 5.0.33.¹² Ubiquiti’s own documentation frames it exactly as a migration aid: it lets you fold existing infrastructure into the UniFi ecosystem and “gradually transition to a UniFi-only setup at your own pace,” giving you live view and playback without replacing every camera at once.¹
The second half is the part that gets glossed over in the sales conversation. Ubiquiti’s documentation carries a one-line caveat that decides the whole project: on a natively-adopted third-party camera, advanced features like audio, detections and PTZ control may not be supported.¹ “Detections” is the load-bearing word. A camera that records but produces no person, vehicle, or smart-motion events is a camera you have to watch rather than one that watches for you — and proactive detection is usually the entire reason a business is upgrading in the first place. Recovering that intelligence on a third-party camera means adding hardware, and the cost of that hardware is what the rest of this article is really about.
Three doors — and only one of them is free.
There are exactly three ways to get a non-UniFi camera’s video into UniFi Protect. They are not interchangeable, and the difference between them is measured in money and in features.
Door one — native ONVIF adoption (free). In Protect, open Settings → System and enable Discover Third-Party Cameras; the camera appears on the UniFi Devices page for adoption using its ONVIF credentials.¹ This is the path Ubiquiti documents, and it requires no extra hardware. The practical gotchas are consistent and worth knowing before you quote a job: ONVIF has to be enabled on the camera with its own ONVIF username and password; the camera’s date and time must be correct or authentication fails; the authentication token type often needs to be Digest & ws-username; Hikvision cameras specifically need their ONVIF authentication set that way; and the camera must reach the Protect console on the network — if it sits on a different subnet you adopt it by IP through Advanced Adoption.¹ What you get at the end is live view and recording. What you may not get is audio, detections, or PTZ control.¹
Door two — the AI Port (about $199 per unit). The AI Port is the accessory Ubiquiti built to give legacy and third-party cameras the AI layer that native adoption omits. It takes the camera’s stream, runs real-time analysis, and surfaces the results in Protect: motion, people, vehicles, animals and speech detection; vehicle colour and type classification; and face and licence-plate recognition.³ Operators who have paired an AI Port with a quality ONVIF camera report the results are, in daylight, essentially indistinguishable from a native UniFi AI camera.⁴ The AI Port is also the only way third-party or older G3 cameras can reach the AI Key’s advanced features.⁵ The catch is density and cost, covered in the next section.
Door three — replace the camera with UniFi hardware. UniFi’s G4, G5 and G6 cameras all run person and vehicle detection on board, classifying motion at the camera’s edge. On the G4 and G5 generations, face and licence-plate recognition require a separate AI Key or AI Port accessory; the dedicated AI-series cameras (such as the AI Pro and AI Turret) build face and licence-plate recognition in with no accessory needed — the AI-360 being the exception, as it omits both.⁶⁷ The newer G6 line brings that native, on-device recognition into affordable bullet, turret and instant models priced around or under $200, with no AI Key required for the recognition itself. For any camera position where you want full intelligence and the existing hardware is aging anyway, a UniFi camera is cheaper and simpler than a legacy camera plus its share of an AI Port.
One 4K legacy camera per port. Do the multiplication.
This is where large-fleet migrations live or die, so it is worth being precise. Ubiquiti’s specification is that each AI Port supports up to five cameras — but the “five” only applies to UniFi HD cameras. The real number depends on resolution and on whether the camera is UniFi or third-party, and you cannot mix the two on a single port:³
| Camera type | 4K | 2K | HD |
|---|---|---|---|
| Third-party (ONVIF) | 1 camera | up to 2 cameras | up to 3 cameras |
| UniFi Protect | up to 2 cameras | up to 3 cameras | up to 5 cameras |
Read the top row again, because it is the one that matters for a migration. A single AI Port drives intelligence for one 4K third-party camera, or two at 2K, or three at HD.³ At roughly $199 per AI Port, a forty-camera 4K legacy fleet that you want fully AI-enabled implies forty AI Ports — an outlay that comfortably exceeds the cost of replacing the cameras outright.⁴ This is not an accident of the product; experienced integrators read the AI Port as a device designed to bridge existing cameras onto the UniFi platform for the few positions that need it, not to retrofit an entire fleet.⁴ When somebody says “we’ll just put AI Ports on the existing cameras,” the spreadsheet is the rebuttal.
A few more hard limits from Ubiquiti’s specification, each of which has bitten a real deployment: the AI Port handles a maximum of 4K (3840 × 2160) at 30 FPS, so higher-resolution cameras must be turned down before connecting; it is built for single-stream cameras within that aspect ratio and is not compatible with multisensor cameras or unusually wide panoramics; and it does not work with UniFi’s own AI-series cameras, which already have the analysis on board.³ Power is PoE+ (up to 12.95 W) or PoE++ (up to 25.5 W) to a directly connected camera, and it can record to a local SD card at the edge.³
Where the AI Key fits. The AI Key is a second, distinct appliance that sits on top of everything above and adds the “find anything” layer — natural-language footage search, AI-triggered alarms, automatic event summaries, speech-to-text and face image enhancement.⁵ It is throughput-limited, and this is one of the few places Ubiquiti’s own sources disagree: the current AI Key technical-specifications sheet rates it at 1,800 smart-detection events per hour, while the support FAQ still states a 1,000-per-hour figure with a 200-event internal queue and processing delays of up to fifteen minutes when that queue is full.⁶⁵ Either way the practical guidance is the same: a busy site spreads the load across more than one AI Key, and there is no limit on how many you attach to a console.⁵ Crucially for a migration, the AI Key only reaches third-party and G3 cameras through an AI Port — it cannot analyse a natively-adopted ONVIF camera on its own.⁵
ONVIF cameras flow in. UniFi cameras do not flow out.
Most migration thinking assumes symmetry: if you can mix brands one way, you can mix them the other way, and you can always leave later. With UniFi Protect, that assumption is wrong, and the asymmetry is strategic rather than incidental.
Modern UniFi Protect cameras do not run a standalone, camera-hosted ONVIF or RTSP endpoint that a third-party NVR can pull from directly — any RTSP(S) access is brokered by the Protect console, with the stream URL pointing at the recorder, never the camera. The direct open-stream Standalone mode that older UniFi Video-era cameras (such as the G3 series) once exposed has no equivalent on current Protect-generation hardware; owners who try to pull a current Protect camera into Home Assistant, Frigate or a competing VMS find there is no camera-hosted RTSP server to point at, and reaching a direct stream at all depends on legacy firmware that survives only on those older models.⁸ Protect can re-share a UniFi camera over RTSP(S) through the per-camera Share Livestream setting — which is how the well-supported Home Assistant integration ingests UniFi cameras — but that still runs through a Protect console.⁹ The camera is not independently usable in a foreign recorder the way a generic ONVIF camera is.
There is a second, subtler version of the same lock-in pointing inward. Operators report that once a third-party ONVIF camera is adopted into Protect, Protect tends to take exclusive control of that camera’s streams — so an app that was previously pulling the camera’s RTSP feed can lose access to it after adoption.¹⁰ Adoption into Protect is, in practice, a fairly committing act for the camera as well.
The strategic implication is clean and worth stating to any stakeholder before money is spent: standardising on UniFi cameras means committing to the UniFi Protect platform. That is a perfectly reasonable decision — the platform is genuinely good — but it should be a decision made with open eyes, not discovered eighteen months later when someone wants to add a specialist analytics package that only speaks to a third-party VMS.
No licence fees, local storage, one pane of glass — and the Hikvision/Dahua problem.
Given the constraints above, why is this migration so common? Four reasons, and the fourth has become urgent.
No per-camera licensing. UniFi Protect is included free on any UniFi recorder, with no per-camera licence and no recurring subscription.¹¹ For an organisation coming off a platform that charges per-camera or per-channel licences — the long-standing model for Milestone, Genetec and Avigilon — removing that line item permanently is often the headline business case on its own.
Footage stays local, with painless remote access. Every Protect camera records locally to a UniFi recorder, and remote viewing is brokered through your Ubiquiti account over an encrypted connection — so you get access from anywhere without opening a port on the firewall, and your primary recordings stay on-premises.¹¹ Protect also offers optional off-site archiving, which copies footage to a cloud or network destination — Google Drive, OneDrive, or a NAS — for redundancy. (This is not a recent addition: off-site archiving has been part of UniFi Protect since the 3.0.x line in early 2024.)¹¹
One interface for network and cameras. For a business already running UniFi switching, gateways and Wi-Fi, folding cameras into the same console and the same mobile app removes a whole separate management plane — the operational argument that tends to close the decision once the budget argument has opened it.
The Hikvision and Dahua compliance problem. This is the driver that has moved fastest. Under Section 889 of the 2019 National Defense Authorization Act, the federal government is barred from procuring or obtaining any equipment, system or service that uses covered telecommunications or video-surveillance equipment from Hikvision, Dahua, Huawei, ZTE and Hytera (Part A), and — under Part B — agencies may not contract with any company that uses such equipment anywhere in its operations, not only on the federal contract.¹²¹⁵ The statute names Huawei and ZTE for telecommunications equipment, and Hytera, Hikvision and Dahua for video-surveillance and telecommunications equipment used for public-safety, government-facility-security, critical-infrastructure-surveillance or other national-security purposes. Federal grant and loan recipients cannot spend those funds on covered equipment either.¹⁵ Layered on top, on 25 November 2022 the FCC adopted a Report and Order that halted new equipment authorisations for Hikvision, Dahua and Hytera — freezing all of their telecommunications and video-surveillance authorisation applications until each submits, and the FCC approves, a plan ensuring the gear is not marketed or sold for prohibited purposes (for Huawei and ZTE, all such equipment is blocked outright). A 2024 federal appeals decision upheld the core of that bar while sending the FCC’s definition of “critical infrastructure” back for being too broad, and a December 2025 FCC proposal to redraw that definition means the precise boundary remains unsettled into 2026.¹²¹³¹⁴ Several states — among them Florida, Texas, Louisiana, Nebraska and Maine — have adopted their own restrictions for state agencies, via statute, executive order, or a state prohibited-technology list.¹⁵
Two honest clarifications, because this is exactly the kind of claim that has to be exact. First, there is no federal law requiring an ordinary private business with no federal contracts or funding to rip out existing Hikvision or Dahua cameras; ordinary commercial and consumer use remains legal.¹⁴¹⁶ The pressure on those businesses is practical rather than statutory — the supply of new equipment and replacement parts through compliant US channels has steadily narrowed since the FCC’s November 2022 authorisation ban, the firmware-and-support pipeline is closing, and cyber-insurance underwriters increasingly scrutinise camera inventories at renewal.¹⁴¹⁶ Second, the trap that catches the most organisations is not deliberate purchasing but inherited inventory: cameras installed before the rules, cameras absorbed through an acquisition, and white-labelled hardware that is Hikvision or Dahua underneath a Western-sounding brand — Lorex hardware, for instance, is still Dahua-built (Dahua sold the Lorex brand to Taiwan-based Skywatch in early 2023 but continues to supply its components), and devices built on Huawei’s HiSilicon chips fall in scope regardless of the badge on the housing.¹⁶ Any serious migration starts with an inventory that records the silicon, not just the logo.
On the other side of that decision, Ubiquiti does not appear on the FCC Covered List, and UniFi is generally regarded as Section 889-compliant for federal and DoD installs — though Ubiquiti scopes that compliance product-by-product in each item’s tech specs, so federally-funded buyers should confirm it per SKU rather than assume it across the board. It is commonly cited on replacement shortlists alongside Axis, Avigilon (now Motorola Solutions), Hanwha and Bosch, each independently confirmed Section 889-compliant.¹⁶¹¹
Match the console to the camera count, then leave headroom.
UniFi Protect runs on a UniFi console, and the right one is a function of camera count and retention. The current tiers, with representative US pricing at the time of writing:
| Recorder | Bays | Capacity | Notes |
|---|---|---|---|
| NVR Instant (~$199) | 1 × 3.5″ | ~6 cameras at 4K / 15 at HD | Integrated 6-port PoE switch; entry tier |
| UNVR (~$299) | 4 | ~18 cameras at 4K / 60 at HD, ~30 days | The default for most small sites |
| UNVR Pro (~$499) | 7 | ~24 cameras at 4K / 70 at HD, ~60 days | RAID 1/5/10; the small-business workhorse |
| Enterprise NVR (~$1,999) | 16 | ~70 cameras at 4K / 210 at HD | Standard enterprise tier |
| Enterprise NVR Core (~$4,999) | 16 (→48) | ~300 cameras at 4K / 500 at HD | Campus scale; RAID; 3U |
Gateways such as the Dream Machine Pro, SE and Pro Max include Protect built in, which is fine for smaller counts but ties surveillance compute to your router (full continuous recording on these gateways requires adding a drive).⁸ For genuinely large estates, Vantage Point unifies the view across multiple recorders, connecting up to five consoles in a single interface — and because each ENVR Core handles up to 500 cameras at HD, a five-console deployment can present well over a thousand cameras on one screen.⁸ Two operational facts belong in any plan at scale: you can stack up to two NVRs, but the AI features (face and licence-plate recognition) only run on the primary “parent” console, and third-party ONVIF cameras tend to behave less reliably on the stacked child unit — so a deployment that depends on AI everywhere wants a single larger recorder rather than a stack.¹⁷ And use surveillance-rated drives (WD Purple, Seagate SkyHawk); avoid SMR drives, which can corrupt the Protect database under continuous write load.¹⁷
Phase it. Don’t flip it.
The mistake we are most often called in to unwind is the overnight cutover — someone adopts forty cameras in an afternoon, discovers the detections are gone, panics, and orders forty AI Ports. Here is the sequence that avoids that, in the order we run it.
- Inventory before you touch anything. Record every camera by make, model, resolution, and underlying silicon — flagging anything that is Hikvision, Dahua or one of their OEM rebrands, and noting which network segment each camera sits on. This baseline sets both the urgency (any NDAA exposure) and the scope (how many positions truly need AI).
- Stand up the recorder for the end state, not today’s count. Size the console for where the fleet is going in eighteen months, and put cameras on their own segmented VLAN with firewall rules that let them reach the Protect console but not the wider internet.
- Native-adopt the existing fleet for continuity. Bring the ONVIF cameras into Protect for live view and recording so nothing goes dark during the transition — accepting, deliberately and on the record, that these cameras have limited or no detection until they are dealt with in step 4 or 5.
- AI-enable selectively, never wholesale. Reserve AI Ports for the handful of legacy positions where you genuinely need smart detection or licence-plate reads now and the camera is worth keeping — an entrance, a gate, a loading dock. Test each camera model against an AI Port before you commit, because compatibility is not guaranteed (see the caveats below).
- Replace rather than retrofit, over time. As cameras age out, or anywhere intelligence needs to be everywhere, install UniFi AI-series or G6 cameras that carry detection on board. This is almost always cheaper per position than a legacy camera plus its slice of an AI Port, and it removes a moving part.
- Decommission the legacy fleet on its own schedule. With continuity preserved and the priority positions handled, the remaining old cameras come out as budget and time allow — not under the pressure of a single hard cutover.
The throughline is that the video migrates immediately and cheaply, while the intelligence migrates deliberately and selectively. Keeping those two timelines separate is the entire technique.
Where this is firmer, and where it’s softer.
- ONVIF compatibility is not guaranteed model-by-model. Native adoption and the AI Port both rely on a camera’s ONVIF implementation behaving, and not all do. Operators have reported some Dahua-OEM cameras (for example, certain Empiretech units) failing to hold a connection and rebooting on an AI Port, while other Dahua-OEM cameras such as Amcrest work fine.⁴ Test the specific models you own before you build a plan around them.
- Night-time licence-plate recognition has a real gap. Protect’s licence-plate recognition is triggered by vehicle detection, so in scenes dark enough that the camera never registers a vehicle, plate reads can simply never fire — operators have reported getting no night reads at all on otherwise-working setups.⁴ For serious overnight ANPR, a purpose-built camera and dedicated illumination still outperform the UniFi pipeline.
- UniFi’s analytics are simpler than a dedicated VMS. UniFi reads plates and vehicle colour; high-end platforms from Dahua, Axis, Genetec and Milestone extract richer vehicle metadata and offer deeper search and forensic tooling.⁴ For most commercial sites UniFi is more than enough and far more usable; for specialist analytics it is not a like-for-like replacement.
- The AI Key throughput figure is genuinely ambiguous in Ubiquiti’s own sources. The spec sheet says 1,800 events per hour; the support FAQ says 1,000 with a 200-event queue.⁶⁵ Size against your real detection volume and add AI Keys rather than assuming a single one will keep up at a busy site.
- Native third-party support is still evolving. Ubiquiti has improved ONVIF handling across Protect releases, and exact behaviour (which detections, which cameras, which features) can change version to version. Verify against the current Protect release before promising a specific capability.¹
- Very large or regulated estates may still favour an enterprise VMS. If you need granular audit logging, controller redundancy beyond NVR stacking, or deep third-party integrations, weigh those against the platform lock-in described in §04 before standardising on UniFi cameras.
- Prices and SKUs move. The figures here are current as of publication; confirm against the UniFi Store before quoting.
None of these caveats changes the headline: an existing camera fleet can move onto UniFi Protect, the video comes across immediately and for free, and the only real engineering decision is how — and how selectively — to buy back the intelligence on the cameras you keep.
References [17]
- [1]Ubiquiti Help Center — Third-Party Cameras in UniFi Protect. Primary source for native ONVIF adoption, the Settings → System → Discover Third-Party Cameras path, the live-view-and-playback scope, the “advanced features like audio, detections and PTZ control may not be supported” caveat, and the adoption gotchas (ONVIF credentials, time sync, Digest & ws-username, the Hikvision authentication setting, same-subnet / Advanced Adoption). help.ui.com — Third-Party Cameras
- [2]home-assistant/core, GitHub issue #127610. Source for the specific UniFi Protect version that introduced third-party ONVIF camera support (5.0.33) and for the observation that Protect does not currently provide RTSPS streams for third-party ONVIF cameras. github.com — issue #127610
- [3]Ubiquiti Help Center — Protect AI Port FAQs. Primary source for the per-port camera limits by resolution and camera type (third-party ONVIF: 1 × 4K / 2 × 2K / 3 × HD; UniFi: 2 × 4K / 3 × 2K / 5 × HD), the no-mixing rule, the supported detections/classifications/recognitions, the 4K-30 FPS maximum, the multisensor/wide-aspect incompatibility, the AI-series incompatibility, PoE+/PoE++ output, and edge SD recording. help.ui.com — AI Port FAQs
- [4]IP Cam Talk — AI Port owner threads (Ubiquiti UniFi AI Port; Unifi AI Port — Works great!). Practitioner source for the ~$199 price (matching Ubiquiti’s official $199 MSRP), the launch-era one-camera limit later expanded by firmware, the daytime parity with native UniFi AI cameras, the model-specific ONVIF incompatibilities (Empiretech vs. Amcrest), the night-time LPR gap (LPR predicated on vehicle detection), the cost-at-scale critique, and the comparison with Dahua/Axis analytics depth. Treated as field-experience reports, not vendor specification. ipcamtalk.com — UniFi AI Port · ipcamtalk.com — AI Port works great · store.ui.com — AI Port $199
- [5]Ubiquiti Help Center — UniFi AI Key Setup and FAQs. Primary source for the AI Key feature set (NeXT AI natural-language search, AI alerts, summaries, speech-to-text, face enhancement), the requirement that G3/ONVIF cameras reach the AI Key only via an AI Port, compatible camera families (G4/G5/AI/AI-Port), the 1,000-per-hour figure with 200-event queue and up-to-15-minute delay, the unlimited-cameras / unlimited-AI-Keys statements, and the current English-only NeXT AI language support. help.ui.com — AI Key FAQs
- [6]Ubiquiti Tech Specs — UniFi AI Key. Primary source for the AI Key compute capacity rated at 1,800 smart detections per hour (the figure that conflicts with the support FAQ’s 1,000), plus the hardware (Arm Cortex-A78AE, 16 GB LPDDR5, 256 GB SSD, GbE, PoE++). techspecs.ui.com — AI Key
- [7]JDB Consulting — Unlock Smarter Surveillance with UniFi Protect: AI Key & AI Port Explained. Supporting source for the camera-tier behaviour: G4/G5 built-in person/vehicle detection, G6 native AI, and AI-series cameras carrying face and licence-plate recognition with no AI Port or AI Key required. Corroborated by Ubiquiti’s AI-detection documentation. jdb.net — AI Key & AI Port
- [8]Ubiquiti Help Center — UniFi Protect: Supported Camera Limits, and the UniFi physical-security recorder pages. Source for the recorder lineup (NVR Instant, UNVR, UNVR Pro, Enterprise NVR, ENVR Core), the gateways with Protect built in, and Vantage Point connecting up to five consoles for 1,000-plus-camera scale. Console-without-RTSP context corroborated by The Stack Canary’s teardown of running UniFi cameras outside Protect. help.ui.com — Supported Camera Limits · ui.com — Video Recorders
- [9]Home Assistant — UniFi Protect integration. Source for the per-camera Share Livestream / RTSP(S) re-stream that lets a Protect console feed UniFi camera video to Home Assistant, confirming that re-streaming a UniFi camera still requires a Protect console. home-assistant.io — UniFi Protect
- [10]Home Assistant Community — UniFi cameras without UniFi Protect (and IP Cam Talk’s ONVIF camera added to UniFi Protect). Source for the absence of a standalone RTSP server on modern UniFi Protect cameras (“Ubiquiti removed this feature”) and for the report that Protect can take exclusive control of an adopted third-party ONVIF camera’s streams. community.home-assistant.io — UniFi cameras without Protect
- [11]Ubiquiti product material and independent reviews — UniFi physical-security pages; Ubiquiti’s Exporting Clips & Cloud Archiving with UniFi Protect and NDAA Compliance help articles; PVR Blog’s UniFi NVR explainer. Source for UniFi Protect’s no-subscription / no-per-camera-licence model (software free on any UniFi recorder), local recording with remote access brokered through your Ubiquiti account over an encrypted connection and no port forwarding, the optional off-site archiving to Google Drive / OneDrive / NAS, and Ubiquiti’s position that most UniFi products meet NDAA requirements (verified per SKU) while the brand is absent from the FCC Covered List. pvrblog.com — UniFi NVR · help.ui.com — Cloud Archiving · help.ui.com — NDAA Compliance
- [12]Congressional Research Service — New FCC Rules Ban Authorizations for Equipment Posing National Security Risks (LSB10895). Source for the 25 November 2022 FCC rule, the FCC Covered List membership (Huawei, ZTE, Hytera, Hikvision, Dahua and others), the NDAA Section 889 framework, and the “prohibited purposes” limitation on Hikvision/Dahua/Hytera surveillance equipment. congress.gov — LSB10895
- [13]Federal Register — Protecting Against National Security Threats to the Communications Supply Chain Through the Equipment Authorization Program (4 December 2025). Source for Hikvision USA, Inc. v. FCC, 97 F.4th 938 (D.C. Cir. 2024), the partial remand of the FCC’s “critical infrastructure” definition, and the December 2025 Second Further Notice of Proposed Rulemaking addressing it. federalregister.gov — EA Security FNPRM
- [14]LegalClarity — FCC Hikvision Ban: Rules, Restrictions, and Penalties. Source for the 2 April 2024 D.C. Circuit decision (Hikvision USA, Inc. v. FCC, 97 F.4th 938 — a unanimous panel granting the petitions in part and denying them in part, not a divided court), the unsettled “critical infrastructure” boundary into early 2026, the absence of any federal obligation on private businesses to remove existing equipment, and the narrowing firmware/support window through compliant US channels. legalclarity.org — FCC Hikvision Ban
- [15]IPVM — Where Dahua and Hikvision Are Banned, with Texas’s state Prohibited Technologies list as a supplementary source. Source for Section 889 Part A vs. Part B scope, the grant/loan funding prohibition, and the state-level restrictions: Florida (Executive Order 22-216), Louisiana (RS 39:1753.1), Nebraska (Executive Order 23-05) and Maine (L.D. 877) per IPVM; Texas via the Governor’s Prohibited Technologies list naming Dahua and Hikvision. ipvm.com — Hik/Dahua bans
- [16]CCTV Info — NDAA-Compliant CCTV Cameras: 2026 Guide; Get Safe and Sound — Hikvision NDAA Compliant; Connextivity — Hikvision and Dahua Ban: What Businesses Need to Know; TechCrunch — US lawmakers urge Costco to cut ties with Lorex (Dahua’s early-2023 sale of the Lorex brand to Taiwan-based Skywatch while continuing to supply its components). Source for the legality of ordinary private/commercial use, the practical (non-statutory) pressures on private operators, the OEM/white-label trap (Lorex hardware Dahua-built; HiSilicon-chip devices in scope regardless of brand), and Ubiquiti’s place on NDAA-compliant alternative shortlists alongside Axis, Avigilon, Hanwha and Bosch. cctvinfo.com — NDAA-compliant cameras · getsafeandsound.com — Hikvision NDAA · connextivity.com — Hik/Dahua ban · techcrunch.com — Lorex/Dahua
- [17]iFeeltech — UNVR vs UNVR Pro: Complete UniFi NVR Comparison (2026). Source for NVR stacking behaviour (up to two NVRs; AI features run only on the primary “parent” console; third-party ONVIF cameras less reliable on the child unit) and drive guidance (surveillance-rated WD Purple / Seagate SkyHawk; avoid SMR drives). ifeeltech.com — UNVR vs UNVR Pro