Files
frigate/web
Josh Hawkins c5826df806 Scope every review page query to the cameras visible in review
The segments and the summary counts were derived from different camera sets: the list was fetched for all cameras and filtered client side, while the summaries were fetched for the visible cameras only when no explicit camera filter was set. A ?cameras= link can name a camera hidden from review, which left the count above zero with an empty list, pinning the new items to review popover open and making the auto refresh effect loop. Intersect an explicit camera selection with the visible list rather than trusting it, pass that to the segment and summary queries alike, and drop the now redundant client side filter, which the raw segments handed to the history view were bypassing anyway.
2026-07-30 12:44:18 -05:00
..
2024-06-19 08:11:51 -06:00
2026-06-16 08:56:52 -05:00
2024-05-18 10:36:13 -06:00
2026-06-04 09:56:11 -06:00
2026-06-04 12:48:58 -06:00
2024-06-19 08:11:51 -06:00
2026-04-22 09:19:30 -06:00
2024-01-31 12:56:11 +00:00
2024-01-31 12:56:11 +00:00
2026-02-27 08:55:36 -07:00

This is the Frigate frontend which connects to and provides a User Interface to the Python backend.

Web Development

Installing Web Dependencies Via NPM

Within /web, run:

npm install

Running development frontend

Within /web, run:

PROXY_HOST=<ip_address:port> npm run dev

The Proxy Host can point to your existing Frigate instance. Otherwise defaults to localhost:5000 if running Frigate on the same machine.

Extensions

Install these IDE extensions for an improved development experience:

  • eslint