From Frigate to camera.ui
You already know your cameras and their URLs, and that is most of the work.
There is no importer. You add your cameras again. They keep their URLs, so there is not much to move.
What lives where
- Cameras with their inputsCameras with their sources
- Inputs with the roles detect and recordSources with High, Mid and Low Resolution
- go2rtc streamsgo2rtc is built in, stream URLs go in as sources
- Zones and masksZones and privacy areas, drawn in the editor
- DetectorsDetection plugins for your hardware
- Retention settingsStorage settings
- Home Assistant integrationcamera.ui integration and card
How the cameras come over
- 1
Install camera.ui next to Frigate
Most cameras serve several connections, so both can run while you compare.
- 2
Add your cameras
Turn on ONVIF and camera.ui finds them. Or copy the path lines from your Frigate config.
- 3
Set up detection
Pick the detection plugin for your hardware and draw your zones.
- 4
Turn Frigate off
Do it when everything runs the way you want. Not before.
What stays behind
Recordings and events stay in Frigate, camera.ui does not import them. Zones and rules you set up again. Keep Frigate as long as you need the old history.
Try it next to Frigate
Free to install, and your current setup keeps running.
Frigate is a trademark of its owner. camera.ui is an independent project and not affiliated with Frigate.