Skip to main content
Prepare a Raspberry Pi prototype that can test its microphone and speaker locally, show whether it is recording, and recover predictably after a restart. Keep the device test separate from a future agent connection.
No Threetone Raspberry Pi runtime package or released live voice walkthrough is verified. Local audio and server-side API reads can be tested independently; they do not start a Threetone conversation.

​
Before you begin

Record the board model, Raspberry Pi OS release, power supply, network, and audio devices. Use a controlled location and test audio without bystanders’ conversations. Decide how a user can stop capture physically or through the device interface.
1

Prepare the operating system and access

Follow Raspberry Pi’s operational security guidance for maintained software, limited user permissions, and SSH access. Give the application only the device access it needs. Keep remote administration separate from the public user interface.
2

Verify the actual audio route

Record and play a short local sample with the selected input and output. Check clipping, speaker feedback, and device removal. Raspberry Pi’s audio documentation explains the available audio frameworks; verify the stack installed on your OS image instead of assuming desktop and headless images match.
3

Define the server boundary

For a shared kiosk, keep workspace API keys on an application backend and give the device a narrowly scoped application identity. Use the server-side quickstart for authorized configuration reads. Do not place secrets in an image distributed to multiple devices.
4

Exercise offline and restart cases

Test unplugged audio, network loss, restart, and user cancellation. Show an offline state, bound any local queue, and start with capture stopped after reboot. Do not replay recorded speech or external actions after reconnect without a supported replay contract and current user intent.
Keep the resulting device inventory and recovery behavior with your custom-channel design. A future release still needs session authorization, supported audio transport, and end-to-end execution verification.

​
Frequently asked questions

No local Threetone agent runtime is documented. This guide prepares device input, output, and an application boundary.
Choose an explicit product policy. The default preparation workflow stops capture and does not retain a backlog of speech for automatic upload.