Files
gx a1090a5f4c controller: Phase 4a — overlay infrastructure (data models + API + Frigate bridge skeleton)
Phase 4a deliverable (no filter rendering yet — это Phase 4b).
End-to-end pipeline: HA/HTTP/MQTT → controller → ZMQ → FFmpeg (logged).

Modules:
- overlays.py — 7 discriminated union types через pydantic:
  rect, text, icon, image, dim, graph, chat. Normalized coords (0.0-1.0),
  optional cell binding, z_order, opacity, visible.
- state.py — overlay storage per instance (CRUD: add/remove/update/get/clear)
- dispatch.py — overlay.add/remove/clear actions:
  - parses JSON payload в Overlay через TypeAdapter
  - serializes to ZMQ string: "<id> <type> <full-json>"
  - sends via FFmpeg process_command (filter will парсить в Phase 4b)
  - updates state + publishes events (overlay_added, overlay_removed, overlays_cleared)
- http_api.py — REST endpoints:
  - POST /overlay/{inst}/add (body = Overlay JSON, returns id)
  - GET /overlay/{inst} — list all
  - DELETE /overlay/{inst}/{id} — single
  - DELETE /overlay/{inst} — clear all
  - PATCH /overlay/{inst}/{id} — update
- mqtt_loop.py — already subscribes cuda_grid/cmd/<inst>/+/+; teper handles
  overlay/add (JSON payload), overlay/remove (id), overlay/clear
- frigate_bridge.py — FrigateBridge skeleton:
  - subscribe frigate/+/motion + frigate/events
  - mapping camera_name → target_instance + cell index
  - Phase 4a: log received events (rendering в Phase 4b)
- config.py — frigate: optional section
- examples/controller.yaml — frigate mappings для 4 наших камер

State management:
- ControllerState.add/remove/update/get/clear_overlay (asyncio.Lock guarded)
- InstanceState.overlays: dict[str, Overlay]
- IDs generated via uuid4()[:8]

Phase 4a limitations:
- Filter side ничего не рендерит (just logs ZMQ commands)
- Frigate bridge принимает events но не auto-generates overlays
- HA Discovery не имеет overlay-specific entities (overlays через REST API)

Phase 4b: filter-side AVFrame side data + CUDA kernels (rect first, NPP-based,
потом text via freetype atlas, потом icon sprite blit).
2026-05-19 22:03:20 +01:00

52 lines
1.1 KiB
YAML

# Sample config для cuda-grid-controller.
broker:
host: localhost
port: 1883
client_id: cuda-grid-controller
username_env: MQTT_USERNAME
password_env: MQTT_PASSWORD
keepalive_sec: 30
instances:
- name: livingroom_tv
zmq_endpoint: tcp://127.0.0.1:5555
default_layout: quad
filter_target: Parsed_cuda_grid_0
- name: public_stream
zmq_endpoint: tcp://127.0.0.1:5556
default_layout: dual_horizontal
filter_target: Parsed_cuda_grid_0
ha_discovery:
enabled: true
prefix: homeassistant
device_name: CUDA Grid Composer
device_identifier: cuda_grid_controller
http:
host: 0.0.0.0
port: 8080
log:
level: INFO
# Phase 4a — Frigate bridge для auto-overlay (rendering в Phase 4b)
frigate:
enabled: true
base_topic: frigate
mappings:
- frigate_camera: parking_overview
target_instance: livingroom_tv
cell: 0
- frigate_camera: front_yard
target_instance: livingroom_tv
cell: 1
- frigate_camera: gate_lpr
target_instance: livingroom_tv
cell: 2
- frigate_camera: back_yard
target_instance: livingroom_tv
cell: 3