Docs: keeping a camera's snapshot
Docs / docs (push) Successful in 23s
Playwright Tests / test-playwright (1, 2) (push) Failing after 4m9s
Playwright Tests / test-playwright (2, 2) (push) Successful in 2m6s
pre-commit / pre-commit (push) Failing after 2m19s
Test Backend / test-backend (3.12) (push) Successful in 4m34s
Test Backend / test-backend (3.14) (push) Successful in 4m23s
Compose Smoke Test / test-compose (push) Successful in 29s
Playwright Tests / merge-reports (push) Successful in 1m28s

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0138N7k5PT4dcR1iEqXaaQ9k
This commit is contained in:
Melvin Strobl
2026-10-16 21:15:15 +02:00
co-authored by Claude Opus 5.5
parent 50e6e22da4
commit 9ee0731bdd
+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).