Skip to main content
The Recorder (recorder) node publishes start_recording / stop_recording to a twin’s webrtc-command MQTT topic so the media service persists the already-running WebRTC stream to its configured bucket. The node never carries the media itself — the camera or microphone must already be streaming.
Palette category: Actuation. Edge-only. Toggles persistence on the media service; it does not create the stream.
The Recorder node, the audio widget’s REC button in the environment view, and the microphone driver’s fallback relay all publish the exact same payload on cyberwave/twin/{uuid}/webrtc-command. The three paths converge on the same media-service handler and the same webrtc-command/status ACK, so you can mix and match without changing the consumer.

Inputs

MQTT payload

Published to {prefix}cyberwave/twin/{twin_uuid}/webrtc-command with QoS 1:
To stop, send the same payload with "command": "stop_recording". Status is published back by the media service on {prefix}cyberwave/twin/{twin_uuid}/webrtc-command/status.

Outputs

Execution targets