Docs: keeping a camera's snapshot

This commit is contained in:
Melvin Strobl
2026-10-16 21:15:15 +02:00
parent 312f35be3e
commit 464490bc37
+8 -1
View File
@@ -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`, 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 `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 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 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). its frames there too, as described under [Live events](../code/api.md#live-events).