Quick answer
Frigate is purpose-built around local detection and MQTT, Scrypted bridges camera platforms, and SmartRTSP is the Apple-device viewer alongside the automation stack.
The decision that matters
Choose Frigate for automation-rich detection, Scrypted for platform bridging and SmartRTSP for native daily viewing. This page is written for Home Assistant users integrating existing cameras. The key decision is: Home automation needs event metadata and reliable entities; human viewing needs a fast native interface. One component need not do both.
The right recommendation changes with the operating system, whether a server can stay online and where people actually watch the cameras.
Evaluation priorities
Event and MQTT integration
Camera restreaming
Native viewing endpoint
Server hardware
How this guide evaluates software
Search results often place media players, mobile camera apps, self-hosted recorders and enterprise video-management systems in the same list. That is misleading because they own different parts of the workflow. This guide first identifies the operating role, then compares current official product documentation for platform support and the features relevant to that role.
Compatibility is evaluated by exact camera model and firmware, not brand name alone. RTSP controls a real-time media session; ONVIF can add discovery, profiles, events, PTZ and audio, but optional features still vary between conformant devices and clients. A successful camera discovery result therefore does not prove that every stream, codec or control will work.
rtsp://camera.example:554/<vendor-path>Illustrative format only. Use the camera manufacturer’s documented path and never publish a real username or password.
Role-based shortlist
The products below are not ranked by the length of their feature lists. They are shortlisted because each represents a distinct, defensible role for this search.
| Product | Platforms | Best fit | Watch for |
|---|---|---|---|
| Frigate | Linux or Docker, commonly with Home Assistant | A local NVR built around object detection, event retention, MQTT and RTSP restreaming for automation-heavy homes. | Hardware acceleration, detector selection and YAML configuration make it a poor fit for someone who only wants to open a camera feed. |
| Scrypted | Server, Docker and supported home platforms | A camera integration platform that can bridge local cameras to HomeKit, Google Home, Alexa and Home Assistant, with an optional NVR workflow. | The server, plugins and camera preparation steps are unnecessary if the goal is simply local live viewing. |
| SmartRTSP | iPhone, iPad, Mac, Apple TV and Windows; Android closed beta | A camera-focused RTSP and ONVIF viewer for everyday monitoring on supported Apple devices and Windows, multi-camera grids, compatible PTZ and local-first processing. | It is not a Linux NVR or always-on recorder. The Windows app is now available from the Microsoft Store, but a full recorder may still be needed for 24/7 retention. |
| Agent DVR | Windows, macOS, Linux, Docker and Raspberry Pi | A self-hosted, cross-platform NVR with RTSP and ONVIF inputs, recording, motion tools and optional remote services. | Server deployment, storage and remote-access choices add operational work compared with a native local viewer. |
Where SmartRTSP fits
SmartRTSP gives household members a direct camera viewer without forcing every live check through the Home Assistant dashboard.
SmartRTSP is promoted when the required job is direct, camera-focused viewing on supported Apple devices or Windows. It connects to compatible RTSP and ONVIF cameras, supports multi-camera viewing and keeps the normal local viewing path on the user’s devices. Android is currently offered as a closed beta, and the Windows app is now available from the Microsoft Store: https://apps.microsoft.com/store/detail/9NJWJKG6DK11
SmartRTSP
SmartRTSP gives household members a direct camera viewer without forcing every live check through the Home Assistant dashboard.
When another product is the better choice
Avoid opening multiple full-resolution camera sessions from every integration; restream or use substreams when the camera has client limits.
SmartRTSP is not presented as a universal replacement for an always-on recorder, Linux server or enterprise VMS. If the workflow requires continuous retention, evidence export, centralized permissions or server-side automation, keep or add software built for those duties.
Pilot checklist
Diagram each camera connection so duplicate decode and bandwidth costs are visible.
- Inventory the exact camera model, firmware, RTSP path, ONVIF profile and main/substream codecs.
- Create a unique view-only camera account; do not reuse an administrator account in everyday viewer apps.
- Test the real device, camera count and network for at least one normal operating shift.
- Verify live video, audio, PTZ, reconnects and recording separately instead of treating “connected” as complete compatibility.
- For remote viewing, use a managed VPN. Do not forward RTSP port 554 or camera administration ports to the public internet.
- Record the rollback plan and keep a second stream test tool available during the pilot.
Security and privacy baseline
Put cameras on a separated network or VLAN where practical, change default credentials, apply supported firmware updates and synchronize time. Use the least-privilege camera account that still provides the required stream or control.
Local-first does not mean risk-free. Public port forwarding, abandoned firmware, shared passwords and unnecessary retention can undermine an otherwise private design. Document where live video, clips, thumbnails, credentials and backups travel.
Frequently asked questions
What is the short answer for this search?
Frigate is purpose-built around local detection and MQTT, Scrypted bridges camera platforms, and SmartRTSP is the Apple-device viewer alongside the automation stack.
Is SmartRTSP the right choice?
SmartRTSP gives household members a direct camera viewer without forcing every live check through the Home Assistant dashboard.
When should I choose an NVR or another product?
Avoid opening multiple full-resolution camera sessions from every integration; restream or use substreams when the camera has client limits.
What should I test first?
Diagram each camera connection so duplicate decode and bandwidth costs are visible.
Official sources read for this guide
- IETF / RFC Editor — RTSP 2.0 (RFC 7826)
- ONVIF — Profile T for advanced video streaming
- SmartRTSP — official product and platform status
- Frigate — official documentation
- Scrypted — official camera and NVR documentation
- iSpyConnect — Agent DVR official overview
- SmartRTSP for Windows — Microsoft Store listing