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