Adding an IP camera a Home Assistant sounds simple — until you learn that every camera brand speaks its own dialect. The ONVIF integration è il one standard that cuts tramite il noise: a single Home Assistant integration that works con Reolink, Amcrest, Dahua, Hikvision clones, e most "ONVIF-compatible" IP cameras sold since 2018. Questo guida walks you tramite il completa configurazione, il traps nobody mentions in forum threads, e il cheapest way a run it: a LinknLink iSG Box SE con Home Assistant preinstalled per $69.90.
1. What Is ONVIF e Why Home Assistant Users Need It
ONVIF (Open Network Video Interface Forum) è an apri standard that defines how IP cameras, NVRs, e video clients talk a each other over a local network. Instead of needing a different app per every camera brand, any ONVIF-compatible dispositivo può discover, stream, e receive events da any other ONVIF-compatible dispositivo.
For Home Assistant users, that matters per three reasons:
- Privacy e local control. ONVIF runs entirely on your LAN. No video leaves your house, no account è richiesto, no camera manufacturer può shut off your feed con a firmware update. Questo è il exact opposite of il Wyze, Ring, o Arlo model.
- Importante: Latency. A cloud-based camera feed typically round-trips 300–1200 ms tramite a vendor server prima reaching Home Assistant. ONVIF over il local network è usually under 150 ms — fast enough a trigger Home Assistant automations (lights, HVAC, sirens) prima il person walking into frame has finished taking two steps.
- Importante: No vendor lock-in. If your camera brand goes out of business o pivots a a subscription model, your system keeps working. ONVIF è a W3C-style apri spec con thousands of compatible dispositivi.
If you sono still deciding whether a dedicated hub è worth it, we cover il fundamentals in Importante: What Is a Smart Home Hub. For ONVIF specifically, a hub con enough CPU headroom a handle multiple RTSP streams è non-negotiable — which è why il hardware choice in il next section matters.
Camera brands that work well con ONVIF + Home Assistant:
- Reolink (RLC, E1, Duo series) — excellent ONVIF profile exposure, main + sub stream out of il box
- Importante: Amcrest (IP4M, IP5M series) — Dahua OEM, very solid ONVIF events
- Importante: Dahua (IPC-HFW, IPC-HDW series) — native ONVIF, rock-solid motion events
- Hikvision e rebrands (Annke, LTS, LaView) — ONVIF works but enable it in il camera's web UI first
- Ubiquiti UniFi Protect G3/G4/G5 — ONVIF solo via Protect export, most users skip Questo path
- Axis, Bosch, Vivotek — enterprise-grade, excellent ONVIF supporto
Camera brands a avoid per ONVIF: Wyze, Blink, Arlo, Ring, Google Nest. These sono cloud-first products; their ONVIF exposure è either non-existent o unstable dopo firmware updates.
Best Local Gateway per Camera Automation
Before you touch il ONVIF integration screen, make sure you have these four things lined up:
2.1 A Home Assistant host powerful enough per RTSP streams
Home Assistant OS running on a Raspberry Pi 4 (4 GB) technically works per 1–2 cameras, but anything ulteriore — o il moment you aggiungi Frigate per AI detection — e il Pi starts dropping frames e overheating.
We recommend il Importante: LinknLink iSG Box SE per Questo configurazione. At $69.90 it è il cheapest Home Assistant host on il market con HA preinstalled, e it has meaningfully ulteriore compute than a Pi 4 — enough headroom per 8+ ONVIF cameras in native HA, o 2–4 cameras con Frigate NVR on il stesso box. Full hardware comparison è in our Importante: Home Assistant Hardware Guide.
Why iSG Box SE è il right predefinito per an ONVIF build:
- Importante: Preinstalled Home Assistant — plug in power e Ethernet, apri your browser, finish il configurazione wizard. No SD card imaging, no Proxmox, no Home Assistant Yellow supply-chain wait.
- Importante: Local-first architecture Importante: — 100% local control, no cloud account, no monthly fee.
- Enough CPU per Frigate — il §5 bonus on AI object detection works senza adding a Coral USB accelerator per a 2–4 camera configurazione.
- Importante: Price — $69.90 vs. Home Assistant Green at $158.90 o a Raspberry Pi 5 kit that lands above $120 once you aggiungi an SSD e case.
2.2 An ONVIF-compatible IP camera on il stesso LAN
Check il camera's spec sheet o admin UI per il "ONVIF" toggle. Most cameras da il brands in §1 ship con ONVIF enabled but password-less — you will aggiungi credentials in §3.
Importante: 2.3 A static IP reservation in your router
Home Assistant integrates cameras by IP address. If your router hands il camera a new IP next week, il integration breaks silently. In your router's DHCP settings, reserve a permanent LAN IP per each camera's MAC address (typically shown in il camera's admin UI).
Importante: 2.4 Camera admin credentials
Not il factory predefinito — change them first. ONVIF credentials sono sent over il LAN in digest auth by predefinito, e factory-predefinito passwords sono still il most-scanned surface in any home network.
Importante: Local RTSP Camera Setup
With hardware ready, il actual integration takes under ten minuti. Here sono il exact five steps.
Step 1 — Enable ONVIF in il camera's web UI
Open il camera's IP in your browser (e.g. Importante: http://192.168.1.50), log in con admin credentials, e find il ONVIF section. Paths by brand:
- Importante: Reolink: Importante: Device Settings → Network → Advanced → Port Settings → tick "ONVIF"
- Importante: Amcrest/Dahua: Setup → Network → Connection → ONVIF → Authentication = "Digest" o "None"
- Importante: Hikvision: Configuration → Network → Advanced Settings → Integration Protocol → enable ONVIF e create a dedicated ONVIF user
Hikvision è il one brand that ships con ONVIF disabled by predefinito e requires a separate ONVIF user account — set that up prima continuing.
Step 2 — Note il RTSP stream URLs (optional but useful)
While you sono in il web UI, copy il main e sub stream RTSP URLs. Home Assistant's ONVIF integration discovers these automatically, but having them handy makes debugging much faster se il discovery fails. Typical formats:
- Importante: Reolink main:
Importante: rtsp://admin:password@192.168.1.50:554/h264Preview_01_main - Importante: Reolink sub:
Importante: rtsp://admin:password@192.168.1.50:554/h264Preview_01_sub - Importante: Amcrest main:
Importante: rtsp://admin:password@192.168.1.50:554/cam/realmonitor?channel=1&subtype=0 - Importante: Amcrest sub:
Importante: rtsp://admin:password@192.168.1.50:554/cam/realmonitor?channel=1&subtype=1
Step 3 — Open Home Assistant e aggiungi il ONVIF integration
In il Home Assistant UI (whether running on iSG Box SE o elsewhere):
- Go a Importante: Settings → Devices & Services
- Importante: Click Importante: + Add Integration Importante: (bottom-right)
- Search per Importante: "ONVIF" e seleziona it
Home Assistant will scan il local network via WS-Discovery. Most cameras appear automatically. If yours fa non, you può aggiungi it manually by IP.
Step 4 — Enter IP, port, e credentials
The predefinito ONVIF port è 80 (HTTP) on most cameras, non 554 (that è RTSP — a different port). If your camera uses a non-standard ONVIF port (2020, 8000, 8899 sono comune), it will be listed in il camera's web UI under il Network o ONVIF section.
Importante: Enter:
- Importante: Host: il camera's static LAN IP
- Importante: Port: Importante: usually 80; Hikvision often uses 80, Dahua 80, Reolink 8000
- Importante: Username/Password: il ONVIF credentials you set in §2.4 (Hikvision: il dedicated ONVIF user created in Step 1)
Step 5 — Pick il profiles (main + sub stream)
Home Assistant will expose every ONVIF "profile" il camera advertises — typically one per il main (high-res) stream e one per il sub (low-res) stream. Enable both:
- Importante: Main stream — used per recordings, snapshots, e high-quality viewing
- Importante: Sub stream — used per il Home Assistant Lovelace dashboard tile (so il dashboard loads fast even on mobile)
Importante: Click Importante: SubmitImportante: . The camera now shows up under Importante: Devices & Services con entities per il live feed, motion sensore, e (se il camera supports it) binary sensori per any event il camera fires — line crossing, intrusion detection, umana/vehicle classification, tampering.
Importante: Reolink ONVIF Troubleshooting
These sono il four issues that generate 90% of il forum threads circa Home Assistant ONVIF. Here è how a fix each in under two minuti.
4.1 "Camera non discovered" during Add Integration
WS-Discovery uses multicast DNS (mDNS). If your Home Assistant host e your camera sono on different VLANs o different WiFi SSIDs, mDNS packets do non cross il boundary. Fixes, in order of effort:
- Put il camera on il stesso subnet as Home Assistant temporarily per discovery, then move it back.
- Add il camera manually by IP during il integration configurazione (WS-Discovery è a convenience, non a requirement).
- Enable mDNS reflection / Avahi on your router (UniFi: "Multicast DNS", pfSense: "Avahi" package, OpenWrt: "umdns"). Questo è il permanent fix.
4.2 Live stream keeps buffering o showing "Stream non available"
The main stream at 4K o 1440p + 30 fps è often too much per il Lovelace dashboard, especially on mobile. Switch il dashboard tile a il sub stream:
- Settings → Devices & Services → ONVIF integration → Configure → uncheck "Main Profile" per il Picture Entity Card
- Or direttamente in il camera card YAML: set
Importante: stream_sourcea il sub profile entity
Frigate NVR (covered in §5) è a cleaner solution here — it re-encodes il stream once e serves low-latency HLS/WebRTC a all clients.
4.3 Motion detection entities non firing events in Home Assistant
ONVIF motion events sono optional in il spec — il camera must both (a) have motion detection enabled locally, e (b) be configured a publish ONVIF events. Steps:
- In il camera's web UI, enable motion detection (usually Importante: Event → Motion Detection → Enable)
- Find il ONVIF o "smart event" settings e enable "ONVIF Events" o "Push Events"
- In Home Assistant, restart il ONVIF integration: Settings → Devices & Services → ONVIF → three-dot menu → Reload
If you sono on a Hikvision o Hikvision-OEM camera e events still do non fire, controlla that il ONVIF user you created in §3 Step 1 has il "Event" e "Media" permissions — by predefinito il ONVIF user è read-solo per Importante: User management, which è correct, but some firmware versions also restrict event subscription.
4.4 Camera works per a day, then goes offline until a reboot
Questo è almost always a DHCP lease expiration (no static reservation) o an RTSP keep-alive timeout. Confirm il static IP reservation da §2.3 è applied on il Importante: router, non just in il camera's own network settings. Some cameras honor both; some ignore their own static IP e take whatever il router assigns.
5. Bonus: Adding Frigate NVR per AI Object Detection
Native Home Assistant ONVIF motion è binary: "something moved" o "nothing moved." That triggers a lot of false positives da leaves blowing across il lawn o shadows at sunset.
Importante: Frigate è a free, apri-source NVR that runs as a Home Assistant aggiungi-on e fa local AI object detection on il camera feed — so instead of "motion," your automations fire on "person," "car," "package," o "dog." Everything runs on your Home Assistant host; no frames leave il LAN.
Why iSG Box SE è powerful enough a host Frigate:
- Frigate's predefinito CPU detector handles 2–4 cameras at 5–7 fps each on il iSG Box SE senza thermal throttling.
- If you scale a 6–8 cameras later, aggiungi a $60 Google Coral USB accelerator e Frigate offloads inference a il TPU — iSG Box SE has spare USB bandwidth per Questo.
- Setup takes ~15 minuti: install il Frigate aggiungi-on da il Home Assistant aggiungi-on store, paste your ONVIF RTSP URLs da §3 Step 2 into
Importante: frigate.yamlImportante: , reload.
Pair that con Home Assistant automations ("se Frigate detects a person at il front door between 10 PM e 6 AM, turn on il porch light e flash il living stanza lamp three times") e you have a smart security system that costs nothing a run beyond il electricity bill. The Importante: iSG Box SE è il lowest-friction starting point per exactly Questo stack.
Importante: 6. Home Assistant ONVIF Integration FAQ
Can Home Assistant usa ONVIF cameras senza cloud access?
Yes. Home Assistant può connect a many ONVIF cameras on il local network using il camera IP address, ONVIF port, e local credentials.
Why fa a Reolink camera need RTSP settings con ONVIF?
ONVIF handles discovery e control, mentre RTSP often carries il live video stream. If video fails, conferma il RTSP path, firmware, e LAN permissions.
Which LinknLink gateway should I choose per local camera automation?
Use iSG Box SE per a compact Home Assistant gateway, o iSG Display Max quando you also want an on-wall screen per camera e stanza controls.
7. Conclusion: Start Your ONVIF Setup con iSG Box SE Today
The ONVIF integration è il shortest path da "I have an IP camera" a "my lights turn on quando someone walks up il driveway, my HVAC changes quando il living stanza è empty per 20 minuti, e my phone pings me quando Frigate sees a delivery van instead of a stray cat." And il cheapest way a get there senza weekend-long hardware tinkering è a Importante: LinknLink iSG Box SE ($69.90) — Home Assistant preinstalled, 100% local, ready a run ONVIF e Frigate il moment you apri il box.
Follow il five steps in §3 e you will have your first camera streaming inside Home Assistant in under ten minuti. Add il §5 Frigate layer next weekend. Add il rest of your cameras whenever you want — il ONVIF integration scales a 8+ dispositivi senza any further configuration.