Running Security-Camera Automations Locally Instead of Through a Subscription

Local camera systems can record, detect events and trigger Home Assistant automations without a cloud subscription when the cameras expose usable local streams and the recorder, detection and storage all run locally.

A subscription is not technically required for security-camera recording or automation if the cameras expose usable local streams and the rest of the system runs on hardware you control.

The key requirement is local camera access.

A cloud-locked camera cannot be made fully local just by installing different software somewhere else.

Start with the camera stream

Before planning a local NVR, verify that the camera exposes a supported local stream or local integration.

Common local paths include standards or protocols such as RTSP or ONVIF, depending on the camera.

Do not assume that every IP camera provides them.

If the vendor only exposes video through its cloud service, the local architecture may stop before it starts.

Frigate can provide local recording and detection

Frigate describes itself as a local NVR designed for Home Assistant with local AI object detection for IP cameras.

It can use separate camera streams for different jobs, such as detection, recording and restreaming.

Detection and recording are separate decisions

You may want continuous recording, event-based retention, snapshots or combinations of those.

Frigate supports retention based on detected events.

Plan storage around camera count, resolution, bitrate, retention period and available disk space.

Local recording avoids a subscription, but disks still cost money.

Object detection needs compute

Frigate strongly recommends a supported hardware detector for serious object-detection use.

Its current documentation treats CPU-only detection mainly as a testing path.

A machine that can save several camera streams may still struggle with real-time detection.

Home Assistant turns events into automations

Frigate's Home Assistant integration can expose camera and event-related entities that automations can use.

That allows workflows such as a person detection turning on a local light or preserving a recording.

Keep high-consequence security decisions conservative. Camera automation should supplement, not replace, any certified alarm or life-safety system.

Keep the camera network secure

Use strong credentials, keep firmware and server software updated, and avoid casually exposing camera interfaces to the public internet.

Network segmentation may also be useful where the hardware and home network support it.

Test without the internet

Disconnect WAN access while leaving the LAN powered.

Then verify that camera streams still open, Frigate still records, detection still works, Home Assistant receives events and local automations still run.

For the broader local-first architecture, see Building a Local Smart Home That Does Not Depend on Somebody Else's Cloud.

A subscription-free camera system is really a chain of local capabilities: camera stream, recorder, detector, automation and storage.