DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to test chat and speech on the device without a mic with Esp32 Thinks

Run typed turns over serial to check the chat and TTS pipeline before a voice test.

Who it is forA developer bench-testing a flashed gadget who needs to confirm the models and speech output work before debugging the microphone.

The problemVoice tests mix microphone, wake word and network problems, so it is hard to tell which part is failing.

The outcomeYou get a typed question answered and spoken through the same chat and TTS pipeline the voice turns use, with a readable status dump if something hangs.

What you need first

  • A Seeed SenseCAP Watcher W1-B or another board the SDK supports
  • A Linux or macOS build host with ESP-IDF v6.0.x for esp32s3
  • Git and USB access to the device serial port
  • Wi-Fi credentials for the config step
  • API keys for the chosen provider (OpenAI, QuickSilver, or your own OpenAI-compatible server)
  • Docker or Node.js and optionally Tailscale for the openmuse agent

Steps

  1. Flash the firmware with a preset first, such as ./build-and-flash.sh ../muse-gadget-sdk /dev/ttyACM1
  2. Run a typed probe with a question: python3 scripts/tts_probe.py /dev/ttyACM1 "What can you do?" (inferred, check the README)
  3. Send a typed turn from any serial terminal: >chat=hello?
  4. Check device health if a turn stalls: >status
  5. Dump every task backtrace if the device looks wedged: >tasks

Prompt for your agent

In the esp32-thinks repo, run python3 scripts/tts_probe.py <port> "hello?" against the flashed device and report the chat reply text and whether speech was produced. Verify that the probe finishes without a stall and that >status shows Wi-Fi and heap healthy.

Caveat. The README says tts_probe.py opens a serial reader and resets the device, and typed turns skip microphone capture, so a passing probe does not prove the wake word works.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page