From 464490bc3738c26caa2d7d7698fa647296038403 Mon Sep 17 00:00:00 2001 From: Melvin Strobl Date: Fri, 16 Oct 2026 21:15:15 +0200 Subject: [PATCH] Docs: keeping a camera's snapshot --- docs/interface/dashboards.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/docs/interface/dashboards.md b/docs/interface/dashboards.md index 2833b50..986ff9f 100644 --- a/docs/interface/dashboards.md +++ b/docs/interface/dashboards.md @@ -615,7 +615,14 @@ portal), or a node of a running flow reads its message. Once its flow wires `camera`, the device's page shows a **Camera** preview. A flow that reads `camera` keeps it sending all the time, about 300 GB a month through a cloud instance, so the Device node warns when a node in its flow reads a port that -sends on demand. Have flows read `snapshot` or `person` instead. +sends on demand. Have flows read `snapshot` or `person` instead. To keep the +picture of whoever came by, a node reading `snapshot` can hand it on to a +message of its own, which a media tile shows until the next one: + +```python +def process(snapshot): + return {"visitor": snapshot} +``` The device is told which of its ports have demand on its live socket, and sends its frames there too, as described under [Live events](../code/api.md#live-events).