How to replace Ring, Arlo, or Eufy with fully local cameras

Ring and Arlo cameras work fine until you notice the monthly fee for cloud storage or realize your footage is floating around on someone else’s servers. Eufy skips the fee but is still cloud-dependent, and its app-and-account model gives you little of the control or longevity a local-first home offers. If you want full local control with zero ongoing costs, here’s how to replace any of them with cameras that stay entirely on your network.

Short version: Reolink gives you the best balance of local-only operation, Home Assistant integration, and no subscription. The Reolink TrackMix PoE outdoors and the Reolink Video Doorbell WiFi at the front door replace Ring cleanly; budget for local storage and a little more notification setup. The same playbook works for Arlo and Eufy, with the brand-specific notes at the end of this guide.

Why go local?

Ring’s primary value proposition is convenience - easy setup, cloud backups, and the app just works. But that convenience comes with a recurring subscription and zero guarantee that Amazon won’t change pricing or kill the service entirely. With local cameras, your footage stays on your hardware. You control retention, access, and what happens to the data.

The tradeoffs are real: local systems require more setup, you lose some cloud AI features, and mobile notifications work differently. But for Home Assistant users, the control you gain outweighs the hassle. You get persistent recordings without monthly fees, integration with your existing automation stack, and no dependency on third-party servers.

Camera options that stay local

The easiest drop-in replacement for Ring is Reolink. Their cameras work completely offline - record to NVR, microSD card, or network storage without touching the cloud. The Reolink TrackMix PoE is a solid outdoor option with dual lenses for wide and zoomed views, and for fixed coverage the wired PoE models such as the RLC-810A (4K bullet) and RLC-820A (4K dome) are the ones I’d point most people at. I haven’t run them myself; the pick rests on the spec sheets and what people running them in Home Assistant report. They have a first-party Reolink integration in Home Assistant that works locally, they also support plain RTSP/ONVIF, and they can record to onboard microSD, to a Reolink NVR, or to an FTP/NAS target with no cloud account required. For doorbells, the Reolink Video Doorbell PoE or Reolink Video Doorbell WiFi replaces Ring doorbells without requiring a subscription. One caveat matters here more than usual: Ring is a battery-first brand, so Ring owners often reach for Reolink’s battery and solar models such as the Reolink Argus 4 Pro. Those expose no RTSP or ONVIF on their own, and reach Home Assistant or Frigate only through a Reolink Home Hub or NVR that re-exposes them locally, and Reolink notes that not every battery model supports Home Hub integration, so check the specific camera before you buy. The mains-powered cameras and doorbells named above, including the wired Wi-Fi doorbell, do RTSP directly.

Amcrest cameras are another reliable option. The Amcrest IP8M-2496E is a 4K outdoor camera that supports RTSP and ONVIF, integrates with Home Assistant via ONVIF, and records to microSD, an Amcrest NVR, or a Synology/QNAP NAS, Blue Iris, or FTP. It’s not as polished as Reolink on the native app side, but it works well for local-only setups.

For a unified system, UniFi Protect from Ubiquiti (what I run at home) delivers the closest experience to Ring’s plug-and-play simplicity while staying fully local. You’ll need their hardware, but it handles everything - cameras, NVR, and mobile app - without subscriptions.

Connecting cameras to Home Assistant

The glue is Home Assistant, running on something like a Home Assistant Green or one of the best mini PCs for Home Assistant for a dedicated local setup. A mini PC with Intel QuickSync is the better pick if you plan to run Frigate for object detection: the same iGPU decodes the streams and runs detection through OpenVINO, which is where Frigate’s own hardware guidance now starts for a new build (a discrete GPU or a Hailo-8/8L module are the step up, and a Google Coral still works but is no longer the recommended starting point). How to build a Frigate NVR from scratch covers the box itself. For cameras, add the ONVIF integration or use each manufacturer’s native integration.

One technical point matters more than the rest: local IP cameras integrate over standard video protocols - RTSP and ONVIF - not MQTT. Any guide telling you to add a camera as an “MQTT camera” has it wrong. MQTT may carry a separate motion event, but the video stream itself is RTSP/ONVIF.

The per-camera setup is the same whichever brand you are leaving:

Wire and address the camera. Connect the PoE camera to a PoE switch or injector. Give it a static IP (or a DHCP reservation) so its address doesn’t change.
Enable RTSP/ONVIF on the camera. In the camera’s web interface, make sure RTSP and ONVIF are enabled. Note the RTSP URL and the camera’s username/password - you’ll need them.
Add it to Home Assistant. For Reolink, use the Reolink integration (Settings > Devices & Services > Add Integration) - it pulls in streams plus motion/AI sensors. For other cameras, use the Generic Camera or ONVIF integration and supply the RTSP stream URL, or add the camera to Frigate and let Frigate expose it to Home Assistant.
Configure local recording. Set the camera to record to microSD, your NVR, or your NAS - or let Frigate handle continuous/event recording on your server. Confirm nothing is routing to a vendor cloud.

Enable motion recording through Home Assistant automations rather than relying on cloud-based person/vehicle detection. Pair cameras with Philips Hue Motion Sensor or Aqara Motion and Light Sensor P2 positioned near camera field-of-view to trigger recordings only when it matters. Budget for the radio those sensors need: the Hue sensor is Zigbee and the P2 is Matter-over-Thread, while a Home Assistant Green has no built-in radios, so you add a USB stick such as the Home Assistant Connect ZBT-2, and Thread devices also need a border router on the network before they can be commissioned. This keeps storage manageable and reduces false alerts.

For doorbell automations, use a wired doorbell’s RTSP stream with Home Assistant’s camera integration. Create a notification that fires instantly when the doorbell presses - no cloud round-trip.

Swap one location at a time

Do not pull every Ring camera down in one weekend. Pick the location that matters most, usually the front door or the driveway, and replace only that one first. If the spot is the front door itself, a wired RTSP doorbell feeds the same pipeline: the Reolink Video Doorbell PoE is the one to buy, and an Amcrest AD410 or AD-110 you already own works too, though Amcrest no longer sells either new. The local doorbell cameras without subscriptions guide compares the wired options side by side.

With the first camera up, add its stream to Frigate, set its zones and object filters, and then recreate your three most-used Ring alerts as Home Assistant automations: a person in the driveway after sunset, a person on the front path while nobody is home, motion in the package zone during the delivery window. Once that one location is more dependable than Ring was, repeat the pattern. It does not need to be perfect before you move on, just better.

Keep Ring running in the low-priority spots while you do this; a hybrid setup for a few weeks is fine. Retire Ring coverage in this order: entry points and driveway first, then backyard and side access, then the convenience-only spots. That gets the security value early and keeps the house covered while you tune.

Tune detection before adding camera two

Most of the pain in a Ring migration is noisy motion, not missing features. Spend the time on Frigate before cameras two and three go up: mask the road, the trees and any high-traffic zone that is not a security concern, set confidence thresholds per object type, use per-camera zones instead of one global rule, and set snapshot and clip retention separately. Ring trained you to think in terms of “motion happened”; Frigate works better when the question is “which object, in which zone, under what condition”. Model the events that way and the false alerts drop off.

Test at night before you standardize on a camera model. Daylight demos are misleading, and a camera that looks fine at noon can lose detections or blow out its exposure under a porch light. Confirm RTSP support before buying, too: a proprietary or fragile stream path makes the whole local stack brittle.

Move the alert logic into Home Assistant

Ring’s alerts are cloud-shaped templates. The point of a local stack is that the alert logic lives in Home Assistant, where it can use context Ring never had: send an urgent push only when the house is empty, behave differently by day and overnight, escalate from a camera event to the porch light to a second event to a siren or an announcement, and route different alerts to different people in the household. Do not try to recreate every Ring notification one for one. Redesign around zones and object types and you end up with fewer, better alerts.

Power and network

Put the cameras and the Frigate host on a UPS if you can; a camera system that reboots with every power blip is not much of a security system. On the network side, do not over-engineer early. A clean, stable flat network beats a half-finished “secure” one, so leave VLANs until you already run them confidently. When you are ready, how to secure IoT devices on your network walks through putting the cameras on their own segment properly.

Storage and retention

Recording locally means you need local storage. Options include:

NVR (Network Video Recorder): Reolink and UniFi sell dedicated NVRs that handle multiple cameras and drive-based storage.
NAS: Add camera streams to your existing Synology or QNAP NAS (for doorbells specifically, see local doorbell cameras without subscriptions, which covers the models that snapshot to a NAS). Check the licensing before you count on this as the free option: Synology’s Surveillance Station typically includes two camera licenses (one on some entry models) and needs a paid per-device license beyond that, and QNAP’s current QVR Elite includes two channels and is otherwise billed per channel per month.
Home Assistant + microSD: Works for single-camera setups but hits limits fast.

Budget for at least 1TB of storage if you want more than a few days of retention at motion-triggered intervals. Plan for drive redundancy if footage matters.

Coming from Arlo

Arlo leans heavily on the cloud for storage, processing, and many alert features, and several capabilities sit behind a Secure subscription. Your footage lives on Arlo’s servers, and the system depends on Arlo’s service staying online. The swap is the same as for Ring: buy wired PoE cameras (the Reolink RLC-810A/820A or the Amcrest IP8M-2496E), connect them over RTSP/ONVIF, and record to microSD, an NVR, or Frigate on your own hardware. Skip battery Wi-Fi cameras like the Argus 4 Pro for primary recording, and don’t expect a HomePod to act as a camera.

That Argus caution deserves spelling out, because Arlo owners are used to battery cameras. The Reolink Argus 4 Pro is a battery-powered Wi-Fi camera, not a wired PoE cam, and it is not a HomeKit camera. Reolink reserves RTSP and ONVIF for its mains-powered models, so a battery camera does not expose a local stream on its own at all. Reaching one from Home Assistant or Frigate means adding a Reolink Home Hub or NVR to re-expose it locally. If you want dependable local recording with no extra box, choose a wired PoE model instead.

For multiple cameras, point their RTSP streams at a local NVR. Frigate (a Home Assistant add-on) is the popular choice: it does local recording plus object detection on your own hardware, and it works with any RTSP camera. A camera-brand NVR (Reolink, Amcrest) is the simpler appliance route. Either keeps footage entirely on your network.

If you use HomeKit, you can expose Home Assistant cameras to the Home app via the HomeKit Bridge integration. Most generic IP cameras are not native HomeKit cameras, so this bridge route is usually how you get them into HomeKit. (A HomePod is a speaker and Matter/Thread hub - it is not a camera and does not add camera support on its own.) If you use Hubitat, note that Hubitat’s strength is Zigbee/Z-Wave automation, not video; for live RTSP streams and recording you’ll still want Home Assistant or a dedicated NVR doing the camera work.

Local cameras take more setup than Arlo’s plug-and-play model, and you’re responsible for storage and keeping the system secure. Wired PoE means running cable. In exchange you get no subscription, full ownership of your footage, lower latency, and a system that keeps recording when the internet is down.

Coming from Eufy

Eufy’s ecosystem covers more than cameras, so the swap is a device-by-device one. A quick reality check up front: “local” usually means the device speaks Zigbee, Z-Wave, Thread/Matter, or ESPHome over your LAN. Wi-Fi cloud devices are only local if the manufacturer offers a local API or you can reflash them. Plain bulbs and many locks do not speak MQTT directly. Match each Eufy device to a real local protocol - Zigbee or Z-Wave sensors on your own coordinator, a Matter-over-Thread or Z-Wave lock, and ESPHome where you want full control - and skip the cloud-polling integrations if “fully local” is the goal.

Cameras and doorbells

Eufy’s “no monthly fee” pitch is true as far as it goes, but its doorbells expose no RTSP, so there is no stream on the Eufy side for Frigate to record. Replace the cameras with the Reolink or Amcrest picks above. For the doorbell, a fully local route is a Reolink doorbell (RTSP/ONVIF, works with Frigate/HA locally) or a wired camera doorbell integrated through Frigate; my guide to local doorbell cameras without subscriptions compares the best options and lists which Eufy models do and don’t expose RTSP. A Zigbee button such as a Third Reality Smart Button can serve as a simple local “someone’s here” trigger but is not a video doorbell.

Locks

Eufy locks lean on the cloud for key management and notifications. The Nuki Smart Lock Ultra is a good modern choice, but check the fit first: the Ultra replaces a European profile or round cylinder, so it is not a drop-in for a US single-cylinder deadbolt. For a standard US deadbolt the model to buy is the Nuki Smart Lock (Deadbolt), which mounts over your existing thumb-turn. Also know its protocols: it speaks Bluetooth, Wi-Fi, and Matter over Thread - not Z-Wave. Via Matter over Thread it integrates locally with Home Assistant (you’ll need a Thread border router). If you specifically want Z-Wave, look at a dedicated Z-Wave deadbolt such as a Yale or Schlage Z-Wave model, which pairs directly to Z-Wave JS with no cloud.

Avoid the August Wi-Fi Smart Lock as a “local” pick. I run one, and its native Home Assistant integration is cloud-polling. The only local path is exposing it through Apple HomeKit and using HomeKit Controller, which is a workaround rather than a clean local design.

Sensors

Replace Eufy’s contact and motion sensors with Zigbee or Z-Wave equivalents that report locally:

Third Reality Zigbee contact, motion, and water-leak sensors (pair via a local Zigbee coordinator running ZHA or Zigbee2MQTT).
Aqara Zigbee sensors via your own Zigbee coordinator.
For water leaks, the Third Reality Water Leak Sensor (Zigbee) or a frient Water Leak Detector (Zigbee) both work locally.

Note: Zigbee sensors only reach MQTT if you run Zigbee2MQTT - the device itself isn’t an MQTT device. The Zooz ZEN34 is a Z-Wave wall remote (for triggering scenes), not a sensor; pair it via Z-Wave JS.

Sirens, smoke, and relays

For local alerting and DIY security, the Zooz ZEN51 dry contact relay and the Zooz ZEN52 double relay (both Z-Wave) let you wire in sirens and contacts and trigger them entirely from Home Assistant automations over Z-Wave. Only the ZEN51 is a dry contact device: Zooz builds the ZEN52 for line voltage, switching two independent 120 V loads.

If you are not on Z-Wave, the same trick works over your LAN. A Shelly Plus 1 wired as a siren driver is a Wi-Fi device, but it is exactly the exception this section opened with: it exposes a local API, and Home Assistant’s Shelly integration drives it directly with no cloud account. Its relay output is potential-free (a dry contact) rated to 16 A and can be wired normally open or normally closed, so it can switch a plain 12 V piezo or strobe that has no smarts of its own. The catch is that this is a wiring project rather than a finished product: you source the sounder yourself, and you get on/off only, with no tone or volume selection unless the siren provides it. Shelly has since discontinued the Plus 1 this build is based on and shipped Gen3 and Gen4 versions of the 1-series relay, also with dry contacts, so buy the current Shelly 1 Gen4 and wire it the same way.

For smoke detection, a frient Intelligent Smoke Alarm (Zigbee) reports locally. Confirm any “Heiman” model’s exact radio (some are Zigbee, some Z-Wave) before buying, and pair accordingly.