Skip to content

LPR: tolerate old + new Frigate event/attribute structure (snapshots, plate box, sub_label) #142

Description

@badbread

On Frigate 0.17.2-3d4dd3a (beta) LPR pictures stopped working. Investigation 2026-07-14: GET /api/events returns HTTP 200 but an EMPTY array — Frigate itself is producing/serving no events after the beta upgrade (a Frigate-side issue), so our ingest has no data (no data.recognized_license_plate, no data.attributes[].box, no snapshots to fetch). Earlier the same query returned normal plate events, confirming this is the upgrade.

BLOCKED until Jason gets Frigate healthy again (events flowing). THEN:

  • Re-inspect the event/attribute/snapshot shape on the new version and diff vs what services/api/src/detection/frigate.rs expects (recognized_license_plate under data, current_attributes/data.attributes[].box normalized [x,y,w,h], /api/events/<id>/snapshot.jpg).
  • Make the ingest + snapshot fetch tolerant of BOTH the old and new field locations / naming, and handle any new snapshot auth requirement (Frigate 0.14+ auth).
  • Add fixtures for both shapes so a future bump does not silently break LPR again.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingfrigateFrigate detection integration

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions