Build Your Own Raspberry Pi Smart Home Security System

Yes—a Raspberry Pi can run a capable, mostly local smart-home security system. The practical design is not just a Pi connected to a camera. Use Home Assistant as the control layer, local IP cameras for video, Frigate for recording and object detection, MQTT for communication, and door or window sensors for dependable intrusion signals.

This setup can provide live video, event recordings, person detection, lights, sirens, and phone notifications without making a cloud subscription the center of the system. It is still a DIY monitoring and automation system—not automatically a professionally monitored alarm with cellular backup, certified equipment, or emergency-service dispatch.

As an Amazon Associate I earn from qualifying purchases.

The recommended architecture

IP cameras ──RTSP/ONVIF──> Frigate ──MQTT──> Home Assistant
                                      │             │
                                      │             ├── phone alerts
                                      │             ├── lights
                                      │             ├── siren
                                      │             └── door/window sensors
                                      │
                                      └── recordings on SSD/NVR storage

Each component has a distinct job:

• Home Assistant: dashboards, automations, alarm modes, sensors, lights, and notifications.
• Frigate: local video recording, motion detection, object detection, and event data.
• MQTT: the message bus that connects Frigate and Home Assistant.
• IP cameras: live streams and video evidence.
• Door, window, and motion sensors: more predictable intrusion signals than cameras alone.
• SSD, NVMe, or NVR storage: a durable destination for frequent video writes.

For a new build, choose a Raspberry Pi 5. A Pi 4 remains suitable for Home Assistant and a light workload, especially if camera-side detection or a separate video host is used. Home Assistant’s current Raspberry Pi guidance supports Pi 4 and Pi 5, specifies at least 2 GB of RAM, recommends a 32 GB or larger A2-rated microSD card, and strongly recommends Ethernet for installation and reliability: Home Assistant’s Raspberry Pi installation guide.

What this system is—and is not

“Home security” can describe several different systems:

1. Video monitoring: live camera views, event clips, local recording, and remote access.
2. Intrusion detection: door and window contacts, PIR sensors, glass-break or vibration sensors, and camera-based person detection.
3. Automation: turning on lights, changing alarm modes, sending notifications, or sounding a siren after defined conditions.
4. Professional alarm service: certified sensors, battery-backed equipment, cellular communication, monitoring staff, dispatch procedures, and sometimes regulatory or insurance requirements.

A Raspberry Pi build can cover the first three categories. It should not be described as a replacement for a professionally monitored alarm unless it has been engineered, certified, maintained, and supported to meet the relevant requirements in your jurisdiction.

Parts list

Minimum practical build

• Raspberry Pi 4 or 5
• Correctly rated power supply
• Case and cooling
• 32 GB or larger A2-rated microSD card
• Ethernet cable
• One compatible local IP camera
• One or more door, window, or PIR sensors
• Optional smart light, smart plug, or siren

Recommended security-oriented build

• Raspberry Pi 5, preferably with 4 GB or 8 GB of RAM
• Active cooling, particularly for sustained Pi 5 workloads
• SSD, NVMe drive, or dedicated NVR disk for recordings
• PoE switch or injector
• PoE cameras with documented RTSP and, where useful, ONVIF support
• Home Assistant OS
• Mosquitto MQTT broker
• Frigate
• Optional Coral or Hailo accelerator if detection load requires it
• UPS for the Pi, router, switch, and camera power path
• Separate backup destination for important clips

Keep the operating system and recordings conceptually separate. A microSD card can be adequate for Home Assistant itself, but continuous video recording creates frequent writes. Direct recordings to SSD, NVMe, or dedicated NVR storage, set a retention limit, and alert before the disk fills.

Raspberry Pi 4 or Pi 5?

Pi 5 provides a quad-core 2.4 GHz Cortex-A76 processor, Gigabit Ethernet, two USB 3 ports, two USB 2 ports, PCIe connectivity, and two four-lane MIPI interfaces. See the Raspberry Pi 5 product brief. Those capabilities make it a better new-build controller, but they do not guarantee a particular number of cameras or detection frame rate. Workload depends on camera count, resolution, frame rate, codec, detector, recording mode, and hardware acceleration.

A single Pi is reasonable for Home Assistant plus one or two modest camera workloads. More cameras, high-resolution streams, or intensive detection can make a used x86 mini-PC, NAS, or dedicated NVR a better Frigate host.

Choose cameras for local integration

Prefer wired PoE IP cameras where possible. A PoE switch or injector can carry power and data over one Ethernet cable, while wired connections avoid many of the reliability problems of Wi-Fi.

Look for

• RTSP for the live video stream
• ONVIF where camera discovery or events are useful
• H.264 availability for broad compatibility
• A low-resolution substream for detection
• A higher-quality main stream for recording
• Fixed local IP support or a DHCP reservation
• Outdoor weather protection when required
• Useful night illumination and a suitable field of view
• Separate local camera credentials

Wireless cameras can work, but Wi-Fi congestion, exterior-wall signal loss, power interruptions, and battery-saving behavior can undermine a security system. Many battery cameras do not provide a continuously available RTSP stream. Cloud-only models may not expose the local feed Frigate needs.

Verify the exact camera model before purchase. A camera may advertise ONVIF while exposing only limited controls or events. RTSP may be disabled by default, firmware updates can change behavior, and H.265 may be less compatible with some processing paths.

Reolink has an official Home Assistant integration with camera streams and detection-related entities on supported models. Its documentation notes that privacy mode disables many entities and that using multiple third-party integrations simultaneously can cause connection problems. Treat this as model-specific guidance, not a guarantee for every camera in the range.

Install Home Assistant OS

For a Pi whose main job is home automation, Home Assistant OS is the simplest and officially recommended installation type.

1. Install Raspberry Pi Imager.
2. Select Choose OS.
3. Choose Other specific-purpose OS.
4. Choose Home automation, then Home Assistant.
5. Select the image for your Pi 4 or Pi 5.
6. Select the microSD card or supported storage and write the image.
7. Insert the storage into the Pi.
8. Connect Ethernet and apply power.
9. Open http://homeassistant.local:8123.

If the hostname does not resolve, find the Pi’s address in your router and open http://PI_IP_ADDRESS:8123. Home Assistant normally becomes available within a few minutes on a Pi 4 or Pi 5. If it is still unavailable after about five minutes, reflash the card or connect a monitor to inspect the boot output.

Complete onboarding by creating a unique administrator account, setting the correct location and time zone, reserving the Pi’s address in your router, and installing updates. Enable multi-factor authentication if it is available in your current release.

Secure remote access before adding cameras

Do not expose Home Assistant, camera interfaces, or RTSP ports directly to the public internet. For remote access, use Home Assistant Cloud, a VPN such as WireGuard or Tailscale, or a carefully configured HTTPS reverse proxy with strong authentication.

Use different credentials for Home Assistant, cameras, MQTT, and the router. Put cameras on an isolated IoT network or VLAN where practical, and restrict unnecessary communication between that network and personal computers. Remote access is not automatically secure simply because it works.

Add MQTT

Install the official Mosquitto broker app or add-on where it is available, create credentials, and add the MQTT integration in Home Assistant. The essential relationship is:

Frigate ──MQTT──> same broker <──MQTT── Home Assistant

Frigate’s Home Assistant integration depends on MQTT. Frigate and Home Assistant must use the same broker for the relevant entities to appear and function. The current documentation is at Frigate’s MQTT guide and Frigate’s Home Assistant integration guide.

Add Frigate for local recording and detection

Frigate is useful when you need more than a live camera tile: event recordings, motion detection, person or vehicle detection, zones, snapshots, and Home Assistant entities.

Frigate on the Home Assistant machine

Running Frigate as a Home Assistant app or add-on is attractive for a small installation because it keeps the components together. The trade-off is resource contention: a video workload, storage problem, or reboot affects both automation and surveillance.

Frigate on a separate host

A separate Docker host is preferable for several cameras, continuous recording, larger storage, or hardware acceleration. It isolates video processing from Home Assistant and makes expansion easier, but adds another computer, operating system, network connection, and backup plan.

Frigate’s deployment and configuration syntax change over time. Use its current installation guide and configuration reference rather than copying an old compose file or tutorial.

This illustrates the architecture, not a universal drop-in configuration:

mqtt:
  enabled: true
  host: MQTT_BROKER_IP
  user: MQTT_USERNAME
  password: MQTT_PASSWORD

cameras:
  front_door:
    ffmpeg:
      inputs:
        - path: rtsp://CAMERA_USER:CAMERA_PASSWORD@CAMERA_IP/SUBSTREAM
          roles:
            - detect
        - path: rtsp://CAMERA_USER:CAMERA_PASSWORD@CAMERA_IP/MAINSTREAM
          roles:
            - record
    detect:
      enabled: true

Replace the stream paths with those documented for your exact camera. Configure detection, recording, retention, hardware acceleration, and detectors according to the current Frigate release. Do not publish real camera credentials in configuration files, screenshots, or support requests.

After MQTT is configured, the dependency order is:

1. Install and test the MQTT broker.
2. Start Frigate.
3. Enable MQTT in Frigate.
4. Point Frigate to the same broker used by Home Assistant.
5. Add the Frigate integration to Home Assistant.
6. Confirm camera, motion, object, recording, and snapshot entities.
7. Create automations only after the entities are visible and reliable.

Add physical sensors and alarm modes

Cameras should not be the only detection method. A magnetic contact sensor answers “did the door open?” more reliably than a camera trying to infer the same event. PIR sensors are useful for movement; mmWave sensors can help with occupancy-aware automation. Zigbee and Z-Wave are often better choices than Wi-Fi for battery sensors and network load, although neither protocol is universally best.

Useful modes include:

• Disarmed: cameras may record, but no siren is sounded.
• Home: monitor exterior doors and selected zones while suppressing ordinary indoor movement.
• Away: monitor all configured zones and send immediate notifications.
• Night: monitor exterior doors, windows, and selected indoor areas.

Include a physical keypad, alarm button, or manual disarm action if the system will be used regularly. Build an entry delay where appropriate, and make sure a false alarm can be silenced without disabling every safety automation.

Build useful automations

1. Person detected while Away

When:    a person is detected in the front-door zone
Only if: alarm mode is Away and the cooldown has expired
Then:    save or reference the event snapshot
         turn on the porch light
         send a mobile notification
         optionally sound the siren after verification

Use a zone and an object type instead of sending an alert for every pixel change. Shadows, insects, pets, headlights, rain, snow, plants, reflections, and infrared switching can all produce false positives.

2. Door opened while Away

When:    the rear door contact changes to open
Only if: alarm mode is Away
Then:    send an immediate alert
         turn on nearby lights
         check for a matching camera event
         start the defined alarm response

Combining signals increases confidence:

Door opens + system is Away + person detected near entry = high-confidence event

3. Camera event turns on a light

Not every camera event should sound a siren. A person detected at the porch can turn on a light and send a notification, while the siren waits for a door contact, a second detection, or manual confirmation. This reduces nuisance alarms and avoids teaching household members to ignore alerts.

Notifications with snapshots

A useful notification identifies:

• Which camera or sensor triggered
• Whether it was a person, vehicle, or generic motion event
• The time
• A snapshot or event clip
• A button to open the camera or dismiss the alarm

Add a cooldown so one person walking through a zone does not create dozens of notifications. Test delivery while away from home. Local detection and recording can continue during an internet outage if the LAN and power remain available, but remote push notifications generally cannot arrive without an internet or alternate communications path. Push services may also involve a third-party relay, so review their privacy implications.

Storage, power, and reliability

Use durable recording storage

• Direct continuous recordings to SSD, NVMe, or dedicated NVR storage.
• Set retention by days or disk usage.
• Alert when free space is low.
• Back up important event clips to a separate destination.
• Keep at least one backup device physically separate from the Pi.

Do not assume the only copy of a recording is safe because it is local. A stolen Pi, damaged disk, or fire can remove both the system and its evidence.

Power the complete system

A UPS helps only when it powers the equipment needed for the security path: the Pi, router, network switch or PoE switch, and possibly the cameras. A Pi-only UPS does not preserve camera connectivity if the switch has failed. Higher-risk installations may need battery-backed alarm equipment and cellular backup.

Do not switch mains voltage directly from GPIO. Use certified low-voltage equipment or a properly enclosed relay module, with appropriate electrical isolation and safety practices.

Plan for recovery

• Back up Home Assistant configuration.
• Keep a written record of camera addresses, MQTT credentials, and recovery steps in a secure location.
• Update Home Assistant, Frigate, camera firmware, and integrations deliberately.
• Confirm that automations return to the correct state after reboot.
• Keep a manual fallback if the Pi fails.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Test the system like a security system

Before trusting it, test:

• Internet failure
• Pi reboot
• Camera disconnection
• Recording-disk removal or full-disk condition
• Day and night detection
• A person wearing dark clothing
• Pets and normal household movement
• Remote notification delivery
• Siren silencing and alarm reset
• Recovery to the correct armed mode after startup
• Recordings surviving a Home Assistant restart

Walk through every detection zone. Check that cameras do not unnecessarily record public areas, neighboring property, or private spaces.

Troubleshooting

homeassistant.local does not resolve

Use the Pi’s IP address from the router instead. Confirm Ethernet link and power, then check the boot output with a monitor if the dashboard is still unavailable.

The Pi boots but the dashboard is unavailable

Allow several minutes after first boot, verify the address, and confirm the storage image matches the Pi model. If the installation remains unavailable, reflash the storage and repeat onboarding.

The camera is discovered but has no stream

Confirm that RTSP is enabled, the local camera account is correct, the camera address has not changed, and the stream path matches the exact model. Test the substream separately and check whether a firmware update changed the URL or codec.

Frigate has no detections

Check that the camera feed is valid, the detect role uses the correct stream, MQTT is enabled, and the detector is configured according to the current Frigate release. Reduce resolution or frame rate, use a substream, or move Frigate to a stronger host if the Pi is overloaded.

MQTT entities are missing

Confirm that Frigate and Home Assistant use the same broker, credentials, hostname, and port. Restarting the integration after correcting broker settings may be necessary.

Notifications do not arrive

Test the mobile app independently, confirm that the automation actually ran, check the cooldown, and remember that remote delivery requires connectivity beyond the local network.

The recording disk fills up

Set retention limits, verify that old recordings are being deleted, check for duplicated streams, and configure a low-space alert. Move recordings off the microSD card if video writes are substantial.

The camera repeatedly drops offline

Prefer Ethernet, inspect PoE budget and cabling, reserve the camera’s IP address, check Wi-Fi signal if wireless, and avoid simultaneously connecting several integrations to the same camera unless its documentation supports that arrangement.

The Pi overheats or throttles

Use active cooling, a correctly rated power supply, adequate ventilation, and a lighter detection workload. More RAM does not by itself solve video-processing limits.

Privacy and legal considerations

Outdoor cameras may capture sidewalks, shared drives, neighbors, guests, or audio. Requirements vary by country, state, and municipality. Check local privacy law, landlord or rental rules, HOA policies, and workplace restrictions where relevant.

• Use privacy masks.
• Disable audio when it is unnecessary.
• Avoid pointing cameras at public areas or neighboring windows.
• Tell household members and guests where appropriate.
• Restrict access to recordings.
• Delete footage according to a defined retention policy.

When a Raspberry Pi is the wrong choice

Consider Home Assistant Green if you want a simpler automation hub and do not specifically need the Pi building experience. Consider a used or new x86 mini-PC, NAS, or dedicated PoE NVR when Frigate must handle several cameras, larger disks, or intensive detection. A separate host also prevents a video workload from making the automation system unresponsive.

Choose a professionally monitored alarm system when dispatch, cellular backup, certified installation, insurance compliance, or life-safety response matters more than local control. Choose cloud cameras when vendor-managed remote access and convenience are worth the subscription and privacy trade-offs.

A sensible staged build

1. Stage 1: Install Home Assistant and verify reliable Ethernet connectivity.
2. Stage 2: Add one local camera and confirm the stream.
3. Stage 3: Add one door contact and one notification.
4. Stage 4: Add Frigate, MQTT, event recording, and person detection.
5. Stage 5: Create Disarmed, Home, Away, and Night modes.
6. Stage 6: Add verified alerts, lights, and a siren with cooldowns and manual override.
7. Stage 7: Add durable storage, UPS coverage, network isolation, backups, and failure testing.

Starting with one camera and one sensor makes faults easier to diagnose. Expand only after the basic system continues working through reboots, camera outages, false triggers, and loss of internet connectivity.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.