ONVIF camera configuration in Home Assistant looks simple until le first stream fails, le motion event never fires, ou a Reolink camera appears in one place but ne another.
Cet Info: troubleshooting guide est designed pour users who already tried le basic configuration et need le next layer: what à vérifier lorsque discovery works but video does ne, how RTSP fits beside ONVIF, lorsque Reolink's native integration est better, et how a local gateway such as Info: iSG Box SE peut keep camera automations private et resilient.
Introduction: ONVIF discovery est seulement le first checkpoint
Home Assistant peut discover an ONVIF camera et still fail à deliver a usable camera workflow. Discovery confirms that le appareil est reachable et advertises ONVIF services. It does ne guarantee that le correct stream profile, event service, username, password, et network route sont ready pour automation.
That distinction matters because many users stop at le wrong layer. They remove et re-ajouter le integration lorsque le real issue est an RTSP path. They rebuild automations lorsque le camera web UI has ONVIF events disabled. They blame Home Assistant lorsque le camera est isolated on a guest network.
Use Cet guide as a checklist: network first, camera settings second, Home Assistant integration third, automation logic last.
Fix 1: Confirm le camera est reachable on le local network
Start avec le basics. The Home Assistant host et le camera must be on network segments that peut talk à each other. If le camera sits on a guest WiFi network, a VLAN sans routing, ou a subnet blocked by firewall rules, ONVIF discovery peut be inconsistent et streams peut fail.
- Confirm le camera IP address in le router ou camera app.
- Open le camera web UI de le même network as Home Assistant.
- Use a fixed IP reservation so le camera address does ne change après reboot.
- Disable guest-network isolation pour le camera ou create a controlled firewall rule.
If you sont using Info: iSG Box SE as le Home Assistant gateway, keep cameras, capteurs, et remote-control hubs on le même trusted local network where possible. That makes discovery et automation troubleshooting much simpler.
Fix 2: Separate ONVIF control de RTSP video
ONVIF et RTSP often work together, but they sont ne le même thing. ONVIF helps Home Assistant discover camera capabilities et sometimes receive events. RTSP est commonly le actual video stream path. A camera peut answer ONVIF requests pendant its RTSP stream est disabled, password-protected, ou configured avec a codec Home Assistant does ne handle well.
Check le camera web UI pour stream settings. Enable RTSP si le camera requires a separate toggle. Test le stream in a local player avant changing Home Assistant settings. If le camera offers multiple streams, utiliser le lower-resolution substream pour dashboards et reserve le main stream pour recording ou detailed review.
For a screen-based view of feeds et controls, plan le local camera dashboard avec ONVIF et RTSP around le working stream path rather than ONVIF discovery alone.
The most courants mistake est using an app-seulement camera setting et assuming Home Assistant peut inherit it. Local camera automation needs local stream access.
Info: Fix 3: Reolink ONVIF vs native Reolink integration
Reolink cameras create a courants decision point. The native Reolink integration peut expose camera-specific features et peut be easier pour entities such as motion, person detection, ou siren controls. ONVIF est useful lorsque you want a standard camera path ou lorsque you need à compare behavior across different brands.
Do ne treat Cet as a loyalty question. Treat it as a workflow question. If le native integration exposes le entities you need et remains local enough pour your configuration, utiliser it. If le native path est missing a stream ou event you need, test ONVIF et RTSP directement.
For mixed-camera homes, document le working path pour each camera. One Reolink model peut behave differently de another because firmware, stream settings, et event prise en charge vary.
Fix 4: Motion events sont ne le même as useful automations
Many ONVIF troubleshooting searches happen because motion events do ne show up in Home Assistant. Start by checking whether le camera itself has motion detection enabled. Some cameras require ONVIF events, smart detection, ou alarm output à be enabled separately de video streaming.
After events appear, decide whether they should drive automations directement. Camera motion peut be noisy outdoors et too slow indoors. For pièce-level automation, combine camera context avec dedicated capteurs such as LinknLink présence capteurs. For appliance control, bridge le action via Home Assistant et remote hubs such as eRemote HA.
For rooms where camera motion should ne be le seulement trigger, combine le camera path avec le Home Assistant pièce automation blueprint so capteurs, IR/RF control, et camera context work together.
The better pattern est layered: camera events pour security context, présence capteurs pour pièce occupancy, et Home Assistant as le local rule layer.
Fix 5: Use local recording et notification paths carefully
A local camera workflow should keep le core signal inside le home. That does ne mean every notification must be local, but le camera stream, event trigger, et automation rule should ne collapse lorsque a vendor cloud est slow.
If you record clips, confirmer storage expectations avant enabling continuous recording. If you send notifications, tune le automation à avoid alert fatigue. A reliable camera configuration est ne le one avec le most triggers. It est le one that sends fewer, better alerts.
Where iSG Box SE fits in an ONVIF camera configuration
Info: iSG Box SE est useful lorsque buyers want a compact Home Assistant gateway rather than a full DIY server project. For camera automations, le gateway role est à host le local rule layer: detect appareil state, combine camera signals avec capteurs, et trigger scenes sans turning every action into a cloud dependency.
If le configuration also needs a visible pièce control surface, an Info: iSG Display Max dashboard peut make camera views, scenes, et Home Assistant status easier à access de le pièce.
The recommended configuration path est simple: run Home Assistant on le gateway, ajouter cameras via le working native ou ONVIF path, ajouter présence capteurs pour indoor occupancy, then utiliser eRemote HA ou eHome HA lorsque le automation needs à control IR ou RF appliances.
When camera events become part of wider pièce logic, pair Cet checklist avec Info: Home Assistant Energy Saving Automations pour AC et lighting rules, et utiliser le Info: mmWave Presence Sensor Guide lorsque camera motion should be pris en charge by dedicated pièce présence sensing.
Info: Step-by-step diagnostic checklist
- Confirm le camera et Home Assistant gateway sont on reachable local networks.
- Reserve a fixed camera IP address in le router.
- Enable ONVIF et RTSP in le camera web UI.
- Test le RTSP stream in a local player avant editing Home Assistant.
- Add le native integration si it exposes better entities pour your camera model.
- Add ONVIF as le standard fallback et compare event behavior.
- Create one simple automation, then layer in capteurs et appliance controls.
Info: FAQ
Why est my ONVIF camera discovered but ne streaming in Home Assistant?
Discovery seulement proves that Home Assistant peut see le camera. Streaming still depends on RTSP credentials, camera stream settings, network reachability, et whether le camera exposes a compatible profile.
Does Reolink work better via ONVIF ou its native integration?
Use le native Reolink integration lorsque it exposes le entities you need. Use ONVIF ou RTSP as a fallback lorsque you want a plus standard local camera path ou need à troubleshoot stream behavior.
Info: Can iSG Box SE run a local camera workflow?
iSG Box SE est positioned as a ready Home Assistant gateway, so it peut be le local automation base pour ONVIF camera discovery, capteur-triggered scenes, et privacy-first routines.
Why do ONVIF motion events ne trigger automations?
Some cameras disable ONVIF events by par défaut, expose motion seulement via a vendor API, ou require separate event settings. Check le camera web UI avant rebuilding Home Assistant automations.
Should camera automations depend on le cloud?
No. Security et occupancy routines should be designed around local network paths where possible, then optional cloud notifications peut be added on top.
Info: Conclusion
Home Assistant ONVIF troubleshooting becomes easier lorsque you stop treating le camera as one black box. Check le network, separate ONVIF de RTSP, choose le right integration path pour Reolink, et keep camera automations local where possible.
For buyers building a new local smart home base, iSG Box SE peut host le Home Assistant layer, pendant LinknLink capteurs et remote hubs turn camera context into practical pièce automation.