@apocaliss92/scrypted-frigate-bridge/CHANGELOG.md

Import object/audio/motion events from Frigate, videoclips, birdseye and much more

### v0.1.22 — Frigate 0.15+ / 0.17.0 compatibility fixes

#### Bug fixes

**Authentication support for Frigate 0.15+ (external port / auth-enabled installs)**

Frigate 0.15 introduced optional authentication (required when accessing Frigate on the external port 8971 or when `auth.enabled: true` is set in the config). All HTTP requests made by the plugin were previously unauthenticated, causing them to fail with HTTP 401 on protected instances.

A new **Frigate API token** setting (`password` type) has been added to the plugin. Set it to the Bearer token generated in the Frigate UI under *Settings → Users*. When a token is configured, it is forwarded as an `Authorization: Bearer <token>` header on every outgoing request:

- `GET /api/config` — Frigate config fetch
- `GET /api/config/raw` — Raw YAML config fetch
- `GET /api/labels` — Available detection labels
- `GET /api/faces` — Registered face names
- `GET /api/events/<id>` — VOD URL resolution
- `GET /api/events/<id>/snapshot.jpg` — Audio & object detection thumbnails
- `GET /api/events` — Videoclip event listing (`videoclipsMixin`)
- Video probe HEAD requests (`videoclipsMixin`)
- Thumbnail fetches (`videoclipsMixin`, `main`)
- go2rtc stream path lookups (`camera`)

The token is optional — if left blank the plugin behaves exactly as before.

---

**Camera config array format in Frigate 0.17.0** (`TypeError` on plugin initialization)

Frigate 0.17.0 changed the `/api/config` response so that `cameras` is returned as an **array** of camera objects (each carrying a `name` field) instead of a plain **object** keyed by camera name. The plugin assumed the old object format everywhere (`Object.keys(config.cameras)`, `config.cameras[cameraName]`), resulting in a `TypeError` on startup that prevented all cameras from being discovered.

A `normalizeFrigateConfigCameras()` helper now converts the new array format into the legacy keyed-object shape immediately after the config is parsed, so all downstream code continues to work without further changes. Both formats (object and array) are handled transparently.

---

**Defensive guards against unexpected API shapes**

Two additional runtime guards were added to prevent crashes when the Frigate API returns an unexpected type:

- `GET /api/labels` — response is now validated to be an array before being used as one; a non-array response (e.g. an error object) is treated as an empty list.
- `GET /api/faces` — response is now validated to be a non-array object before `Object.keys()` is called on it; a missing or unexpected response is treated as an empty map.