ONVIF camera setup in Home Assistant looks simple until the first stream fails, the motion event never fires, or a Reolink camera appears in one place but not another.
This troubleshooting guide is designed for users who already tried the basic setup and need the next layer: what to check when discovery works but video does not, how RTSP fits beside ONVIF, when Reolink's native integration is better, and how a local gateway such as iSG Box SE can keep camera automations private and resilient.
Introduction: ONVIF discovery is only the first checkpoint
Home Assistant can discover an ONVIF camera and still fail to deliver a usable camera workflow. Discovery confirms that the device is reachable and advertises ONVIF services. It does not guarantee that the correct stream profile, event service, username, password, and network route are ready for automation.
That distinction matters because many users stop at the wrong layer. They remove and re-add the integration when the real issue is an RTSP path. They rebuild automations when the camera web UI has ONVIF events disabled. They blame Home Assistant when the camera is isolated on a guest network.
Use this guide as a checklist: network first, camera settings second, Home Assistant integration third, automation logic last.
Fix 1: Confirm the camera is reachable on the local network
Start with the basics. The Home Assistant host and the camera must be on network segments that can talk to each other. If the camera sits on a guest WiFi network, a VLAN without routing, or a subnet blocked by firewall rules, ONVIF discovery may be inconsistent and streams may fail.
- Confirm the camera IP address in the router or camera app.
- Open the camera web UI from the same network as Home Assistant.
- Use a fixed IP reservation so the camera address does not change after reboot.
- Disable guest-network isolation for the camera or create a controlled firewall rule.
If you are using iSG Box SE as the Home Assistant gateway, keep cameras, sensors, and remote-control hubs on the same trusted local network where possible. That makes discovery and automation troubleshooting much simpler.
Fix 2: Separate ONVIF control from RTSP video
ONVIF and RTSP often work together, but they are not the same thing. ONVIF helps Home Assistant discover camera capabilities and sometimes receive events. RTSP is commonly the actual video stream path. A camera can answer ONVIF requests while its RTSP stream is disabled, password-protected, or configured with a codec Home Assistant does not handle well.
Check the camera web UI for stream settings. Enable RTSP if the camera requires a separate toggle. Test the stream in a local player before changing Home Assistant settings. If the camera offers multiple streams, use the lower-resolution substream for dashboards and reserve the main stream for recording or detailed review.
The most common mistake is using an app-only camera setting and assuming Home Assistant can inherit it. Local camera automation needs local stream access.
Fix 3: Reolink ONVIF vs native Reolink integration
Reolink cameras create a common decision point. The native Reolink integration can expose camera-specific features and may be easier for entities such as motion, person detection, or siren controls. ONVIF is useful when you want a standard camera path or when you need to compare behavior across different brands.
Do not treat this as a loyalty question. Treat it as a workflow question. If the native integration exposes the entities you need and remains local enough for your setup, use it. If the native path is missing a stream or event you need, test ONVIF and RTSP directly.
For mixed-camera homes, document the working path for each camera. One Reolink model may behave differently from another because firmware, stream settings, and event support vary.
Fix 4: Motion events are not the same as useful automations
Many ONVIF troubleshooting searches happen because motion events do not show up in Home Assistant. Start by checking whether the camera itself has motion detection enabled. Some cameras require ONVIF events, smart detection, or alarm output to be enabled separately from video streaming.
After events appear, decide whether they should drive automations directly. Camera motion can be noisy outdoors and too slow indoors. For room-level automation, combine camera context with dedicated sensors such as LinknLink presence sensors. For appliance control, bridge the action through Home Assistant and remote hubs such as eRemote HA.
The better pattern is layered: camera events for security context, presence sensors for room occupancy, and Home Assistant as the local rule layer.
Fix 5: Use local recording and notification paths carefully
A local camera workflow should keep the core signal inside the home. That does not mean every notification must be local, but the camera stream, event trigger, and automation rule should not collapse when a vendor cloud is slow.
If you record clips, confirm storage expectations before enabling continuous recording. If you send notifications, tune the automation to avoid alert fatigue. A reliable camera setup is not the one with the most triggers. It is the one that sends fewer, better alerts.
Where iSG Box SE fits in an ONVIF camera setup
iSG Box SE is useful when buyers want a compact Home Assistant gateway rather than a full DIY server project. For camera automations, the gateway role is to host the local rule layer: detect device state, combine camera signals with sensors, and trigger scenes without turning every action into a cloud dependency.
The strongest setup path is simple: run Home Assistant on the gateway, add cameras through the working native or ONVIF path, add presence sensors for indoor occupancy, then use eRemote HA or eHome HA when the automation needs to control IR or RF appliances.
Step-by-step diagnostic checklist
- Confirm the camera and Home Assistant gateway are on reachable local networks.
- Reserve a fixed camera IP address in the router.
- Enable ONVIF and RTSP in the camera web UI.
- Test the RTSP stream in a local player before editing Home Assistant.
- Add the native integration if it exposes better entities for your camera model.
- Add ONVIF as the standard fallback and compare event behavior.
- Create one simple automation, then layer in sensors and appliance controls.
FAQ
Why is my ONVIF camera discovered but not streaming in Home Assistant?
Discovery only proves that Home Assistant can see the camera. Streaming still depends on RTSP credentials, camera stream settings, network reachability, and whether the camera exposes a compatible profile.
Does Reolink work better through ONVIF or its native integration?
Use the native Reolink integration when it exposes the entities you need. Use ONVIF or RTSP as a fallback when you want a more standard local camera path or need to troubleshoot stream behavior.
Can iSG Box SE run a local camera workflow?
iSG Box SE is positioned as a ready Home Assistant gateway, so it can be the local automation base for ONVIF camera discovery, sensor-triggered scenes, and privacy-first routines.
Why do ONVIF motion events not trigger automations?
Some cameras disable ONVIF events by default, expose motion only through a vendor API, or require separate event settings. Check the camera web UI before rebuilding Home Assistant automations.
Should camera automations depend on the cloud?
No. Security and occupancy routines should be designed around local network paths where possible, then optional cloud notifications can be added on top.
Conclusion
Home Assistant ONVIF troubleshooting becomes easier when you stop treating the camera as one black box. Check the network, separate ONVIF from RTSP, choose the right integration path for Reolink, and keep camera automations local where possible.
For buyers building a new local smart home base, iSG Box SE can host the Home Assistant layer, while LinknLink sensors and remote hubs turn camera context into practical room automation.