Add caveat to docs on snapshot_frame_time pre-0.18

This commit is contained in:
leccelecce 2026-03-18 12:23:41 +00:00
parent a04f399b0b
commit 36fe0fa63d

View File

@ -21,11 +21,13 @@ MQTT snapshots are published more frequently — each time a better thumbnail fr
Frigate stores a single clean snapshot on disk: Frigate stores a single clean snapshot on disk:
| API / Use | Result | | API / Use | Result |
| --- | --- | | ---------------------------------------- | ----------------------------------------------------------------------------------------------------- |
| Stored file | `<camera>-<id>-clean.webp`, always unannotated | | Stored file | `<camera>-<id>-clean.webp`, always unannotated |
| `/api/events/<id>/snapshot.jpg` | Starts from the camera's `snapshots` defaults, then applies any query param overrides at request time | | `/api/events/<id>/snapshot.jpg` | Starts from the camera's `snapshots` defaults, then applies any query param overrides at request time |
| `/api/events/<id>/snapshot-clean.webp` | Returns the same stored snapshot without annotations | | `/api/events/<id>/snapshot-clean.webp` | Returns the same stored snapshot without annotations |
| [Frigate+](/plus/first_model) submission | Uses the same stored clean snapshot | | [Frigate+](/plus/first_model) submission | Uses the same stored clean snapshot |
Note that for tracked objects pre Frigate 0.18, the snapshot frame time was not stored. If you request to annotate a pre-0.18 snapshot with a timestamp, this will be defaulted to the event start time, which may appear confusing.
MQTT snapshots are configured separately under `cameras -> your_camera -> mqtt` and are unrelated to the stored event snapshot. MQTT snapshots are configured separately under `cameras -> your_camera -> mqtt` and are unrelated to the stored event snapshot.