Files
frigate/web
Josh Hawkins 3f7e2c4686 fix auto quality recovery after a downswitch
The downswitch callback armed the upswitch probe, but `triggerDownswitch` reset the stall history right after the callback returned, which disarmed it again. Auto quality stayed on the sub stream until the next chunk boundary no matter how much the connection recovered. The governor now arms the probe itself after the reset.

The chunk boundary effect also ran on mount, so when coverage was already cached it immediately undid the low quality cold start the seed effect had just picked. It now only runs when the chunk actually changes.
2026-09-28 08:46:58 -05:00
..
2024-06-19 08:11:51 -06:00
2026-06-16 08:56:52 -05:00
2024-06-19 08:11:51 -06:00
2026-04-22 09:19:30 -06:00
2026-09-14 07:16:31 -06:00
2024-01-31 12:56:11 +00:00
2026-09-15 14:02:02 -06: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