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