How to Add a Security Camera to Home Assistant

Overview

The best way to approach a Home Assistant camera integration is to decide your goal first, not your method first. Many people begin by asking, “How do I add this camera?” A better question is, “What do I need Home Assistant to do with this camera?”

That answer changes the setup:

• If you only want a live view, a direct stream such as RTSP is often enough.
• If you want discovery plus controls, ONVIF may be the better starting point.
• If you use an NVR, it can be cleaner to integrate the recorder rather than each camera one by one.
• If your camera is cloud-first, the brand’s Home Assistant integration may be the easiest path, but features can be more limited.
• If you want automations, you also need reliable entities such as motion sensors, binary sensors, doorbell presses, or person detection events.

Before you add anything, keep these baseline expectations in mind:

• Not every camera exposes the same stream types or controls.
• Battery-powered cameras are usually less flexible than plug-in or PoE models.
• Live view is easier than two-way audio, pan-tilt control, or full event history.
• Home Assistant works best when the camera or recorder supports local access.
• “Supported” does not always mean every feature is supported.

If you are still deciding on camera hardware, this matters. Cameras designed around local streaming and open standards are generally easier to integrate than cameras built mainly around a locked app experience. Our related guide on ONVIF vs RTSP Cameras: What Works Best for Local NVR Setups? is useful if you are comparing camera types before buying.

Use this quick pre-checklist before opening Home Assistant:

• Confirm the camera and Home Assistant are on the same network, or that routing rules allow access.
• Assign the camera a reserved IP address if possible.
• Update the camera firmware and Home Assistant before troubleshooting deeper issues.
• Check whether the camera offers RTSP, ONVIF, or an official integration.
• Create or confirm a camera username and password that Home Assistant can use.
• Decide whether you want direct camera feeds or feeds through an NVR.

Checklist by scenario

Use the scenario below that best matches your camera setup. In many homes, the cleanest answer is a mix: one method for your wired cameras, another for your doorbell, and perhaps an NVR integration for recording.

Scenario 1: Add a camera through an official brand integration

This is usually the easiest starting point for major consumer camera brands, especially when you already use the manufacturer’s app and do not need deep local control right away.

• In Home Assistant, check Settings > Devices & Services for the camera brand.
• Sign in or provide the required credentials if the integration asks for them.
• Confirm what entities appear: camera feed, motion sensor, doorbell button, battery level, spotlight, siren, and so on.
• Test whether the integration provides a live stream, snapshots, or only event metadata.
• Add the camera card to a dashboard and confirm the delay is acceptable.
• If the integration is cloud-dependent, note that outages or account changes may affect reliability.

This route is best when you want convenience and a quick setup. It is less ideal if your long-term goal is local-first control or a subscription-free setup. If that is your priority, our guide on How to Store Security Camera Footage Locally on SD Card, NAS, or NVR is a useful next read.

Scenario 2: Add an RTSP camera to Home Assistant

For many local storage security camera setups, RTSP is the practical middle ground. It is straightforward, widely supported, and useful for live viewing in dashboards.

• Log in to the camera’s web interface or app and enable RTSP if it is disabled by default.
• Confirm the RTSP URL format for your camera model. This varies by brand and sometimes by stream profile.
• Test the stream outside Home Assistant first in a media player that supports RTSP.
• Use the camera’s sub-stream if the main stream is too heavy for dashboards.
• Add the stream to Home Assistant using the appropriate camera or generic stream method.
• Name the entity clearly, such as Front Porch Substream rather than Camera 1.

RTSP is often the better choice when your priorities are low-friction local streaming, stable dashboard views, and compatibility with NVR tools. It is especially common with PoE security camera and Wi-Fi camera systems that offer local admin access.

If you are balancing image quality against performance, keep resolution and bit rate realistic. A 4K stream can look impressive, but a lighter stream is often better for dashboards and mobile loading. Our article on 2K vs 4K Security Cameras: When Higher Resolution Actually Matters can help you decide when high resolution is useful and when it is unnecessary overhead.

Scenario 3: Use ONVIF for discovery and camera features

ONVIF is often the more structured option when the camera supports it well. Compared with RTSP alone, ONVIF can help with discovery, profiles, and sometimes additional camera data.

• Enable ONVIF in the camera settings if the feature exists.
• Create an ONVIF-specific user if the camera allows separate accounts for integrations.
• Make sure the ONVIF port is open on your local network.
• Add the ONVIF integration in Home Assistant and let it discover the device, or enter the IP manually.
• Review which entities appear. You may get camera entities plus motion-related or device information, depending on the model.
• Test stream reliability over time, not just once. Discovery can work even when the selected stream profile is not ideal.

ONVIF is worth trying when you want more than a bare live stream, but the quality of support can vary by brand and firmware. In practice, some users end up using ONVIF for detection and RTSP for the actual stream, which is a perfectly reasonable hybrid setup.

Scenario 4: Integrate cameras through an NVR instead of directly

If you already run a local recorder, this is often the cleanest long-term design. Rather than asking Home Assistant to manage every camera separately, you let the NVR handle recording, retention, and stream organization.

• Decide whether Home Assistant should connect to the NVR only, or also directly to a few important cameras.
• Use the NVR for recording and event review, and Home Assistant for dashboards and automations.
• Prefer sub-streams for dashboard cards if the NVR exposes multiple profiles.
• Keep naming consistent between the NVR and Home Assistant so automations remain readable.
• Check whether the NVR exposes motion events, person detection, or just video streams.

This approach scales better in larger homes and small business security camera setups. It is also a good fit when you use multiple brands but want one surveillance backbone.

Scenario 5: Add a battery-powered camera or video doorbell

This is where expectations matter most. Battery cameras and many video doorbells are built around power saving, cloud relays, and app-first workflows. That can limit always-on local streaming.

• Check whether the device supports continuous streaming at all.
• Look for an official integration before assuming RTSP or ONVIF is available.
• Expect shorter live sessions, wake-up delays, or fewer local features than a wired camera.
• For automations, rely on doorbell press or motion events if live stream availability is inconsistent.
• If your goal is fast dashboard viewing, a plug-in or wired alternative may work better.

For renters and apartment users, convenience may still outweigh these limits. If installation flexibility matters more than deep integration, our related articles on How to Install a Video Doorbell in an Apartment Without Drilling and Battery vs Plug-In Security Cameras: Which Is Better for Your Home? can help you choose the right compromise.

Scenario 6: Build simple smart camera automation

Once the camera is visible in Home Assistant, the real value comes from actions tied to events. Keep the first automation simple.

• Turn on entry lights when driveway motion is detected after dark.
• Send a phone notification when the front door camera detects motion during away mode.
• Show the doorbell camera on a dashboard tablet when the button is pressed.
• Trigger a recording workflow or snapshot to local storage when a motion entity changes state.
• Mute noisy alerts during known home hours to reduce notification fatigue.

The key is to automate off dependable signals. If the camera’s own motion entity is inconsistent, use other context such as time, occupancy, or an NVR’s detection event.

What to double-check

Most Home Assistant camera problems are not really “integration problems.” They are stream, network, permission, or expectation problems. Check these items before changing your whole setup.

Stream path and credentials

• Make sure the username and password are correct and still valid.
• Confirm the stream URL points to the right profile.
• Test the stream outside Home Assistant before blaming the integration.
• If the main stream fails, try the sub-stream first.

Local network reliability

• Give cameras static or reserved IPs so addresses do not change.
• Check Wi-Fi signal strength for wireless cameras, especially outdoor models far from the router.
• Separate camera network issues from Home Assistant issues by testing direct access in a browser or player.
• If you have many cameras, consider whether your current network can handle the traffic.

Camera settings

• Some cameras disable local protocols by default.
• Firmware updates can reset streaming settings or account permissions.
• Video codec and stream settings can affect compatibility and latency.
• Very aggressive bit rates can make dashboard viewing less stable.

Automation inputs

• Know whether your automation is tied to video, motion, person detection, or a doorbell button event.
• Do not assume the camera entity itself equals a usable motion trigger.
• Name sensors clearly so you do not build automations from the wrong entity.

Privacy and security

• Use unique passwords for camera accounts.
• Prefer local access over unnecessary port forwarding.
• Create limited-access integration accounts where possible.
• Review smart camera privacy settings after firmware updates or app changes.

If privacy is a top concern, a local storage security camera or RTSP/ONVIF camera often gives you more control than a cloud-first product. That does not make every local setup automatically secure, but it does make the data path easier to understand.

Common mistakes

You can save a lot of time by avoiding a few predictable errors.

Choosing the wrong method for the job

If you want a quick dashboard stream, RTSP may be enough. If you want richer device discovery, ONVIF may help. If you want long retention and centralized recordings, the NVR should probably sit at the center. Problems start when you force one tool to do everything.

Expecting battery cameras to behave like wired cameras

A battery powered security camera is built around energy saving. That usually means slower wake times, shorter live viewing windows, and fewer always-on local options. If Home Assistant speed matters, wired wins more often.

Using the highest-quality stream everywhere

A dashboard card does not need the same stream profile as forensic playback. Use lower-bandwidth streams for always-visible views and reserve the high-quality stream for recording or detailed review.

Skipping manual testing

If you never test the stream URL or ONVIF login outside Home Assistant, you lose the fastest way to isolate the problem. Direct testing tells you whether the issue is the camera, the network, or the integration layer.

Building automations before the camera setup is stable

First make sure the stream loads reliably and the entities update correctly. Then automate. Otherwise you end up troubleshooting two layers at once.

Ignoring ecosystem limits

Some users expect one camera to behave identically across Home Assistant, Alexa, Google Home, or HomeKit. In reality, each ecosystem exposes different features and delays. If you also use voice displays, it helps to understand where each platform is strongest. See our guides to Best Google Home Security Cameras for Nest Hubs and Voice Control, Best Alexa-Compatible Security Cameras for Echo Users, and Best HomeKit Secure Video Cameras You Can Still Buy if you are trying to fit one camera into multiple smart home ecosystems.

When to revisit

This is not a one-time setup topic. Camera integrations should be revisited whenever your tools, priorities, or hardware change. Use this short review cycle to keep your Home Assistant camera setup useful over time.

• When you replace a camera: check whether the new model supports the same stream type, credentials, and event entities.
• When firmware changes: recheck RTSP, ONVIF, and account permissions after updates.
• When dashboard performance gets worse: consider switching cards to sub-streams or moving recording duties to an NVR.
• Before travel or seasonal planning: test motion alerts, remote views, and outdoor camera night visibility.
• When you add automations: confirm that triggers are based on stable entities, not assumptions.
• When you change ecosystems: revisit whether your camera is still the best fit for Home Assistant versus Alexa, Google Home, or HomeKit.

A practical maintenance routine looks like this:

1. Open each important camera in Home Assistant and confirm the live view still loads.
2. Trigger motion once and verify the expected entity changes state.
3. Run one notification automation and confirm it arrives on your phone.
4. Check recording and retention separately if you use local storage or an NVR.
5. Review device names and labels so future automations stay readable.

If you are still shopping for camera brands with Home Assistant in mind, prioritize local access, clear support for RTSP camera Home Assistant workflows, or reliable ONVIF Home Assistant setup options. In many cases, those practical details matter more than headline resolution or marketing features.

The short version: to add a security camera to Home Assistant successfully, start with your end goal, choose the simplest integration path that supports it, and test each layer one at a time. That approach is less exciting than chasing feature lists, but it produces a setup you can actually live with and return to later when your home surveillance needs evolve.