17 boards / one open-source ESP32 SDK

Muse Gadgets
supported boards.

Start with what you want the gadget to do: connect Muse to your home network, show status and pictures, or put push-to-talk beside a small screen. The upstream targets cover those different jobs; they do not all offer the same features.

Source: upstream ESP32 README Boards table and device feature table. This comparison uses the October 4, 2026 snapshot. Buying links remain pending.

Compare Muse Gadgets supported boards

These are upstream SDK targets. Browser installation on this site covers two boards; Raspberry Pi 5 follows a separate Linux path.

Browser Beta targets: M5Stack StickS3 and ESP32-C5 DevKitC-1. All other entries require the upstream build workflow.
BoardInterfaceUpstream featuresBuying link
ESP32-C5 DevKitC-1StatusStatus light and buttonPending
ideaspark ESP32 with 1.9″ displayStatusStatus on screen, imagesPending
Seeed SenseCAP IndicatorStatusStatus on a 4″ screen, imagesPending
Seeed reTerminal E1001Status7.5″ e-paper, black and white imagesPending
Seeed reTerminal E1002Status7.3″ e-paper, six-colour imagesPending
Home Assistant Voice Preview EditionStatusLED ring, push-to-talk, volume dialPending
Waveshare ESP32-S3-Touch-AMOLED-1.75CScreen UIUI, push-to-talk, settings, imagesPending
Waveshare ESP32-S3-Touch-AMOLED-1.75Screen UIUI, push-to-talk, settings, imagesPending
Espressif ESP32-S3-BOX-3Screen UIUI, touch, push-to-talk, settings, imagesPending
AIPI LiteScreen UIUI, push-to-talk, two-button menu, imagesPending
Waveshare ESP32-C6-Touch-AMOLED-1.8Screen UIUI, push-to-talk with text repliesPending
Seeed SenseCAP WatcherScreen UIUI, push-to-talk, settings, imagesPending
M5Stack Cardputer ADV (experimental)Screen UIUI, GO/Space push-to-talk, text replies, keyboard menuPending
M5Stack StickS3Screen UIUI, push-to-talk, two-button menu, imagesPending
M5Stack StopWatchScreen UIUI, push-to-talk, settings, imagesPending
M5Stack CoreS3Screen UIUI, touch, PWR push-to-talk, settings, imagesPending
M5Stack StickC Plus2Screen UIUI, push-to-talk, two-button menu, imagesPending

Choose the job before the display

A screen does not tell you whether a gadget can provide the home-network tunnel, play audio, or handle images. Check those capabilities separately.

Home-network access

The ESP32-C5 DevKitC-1 is the upstream guide’s quickest starting point, with a built-in status light and BOOT button. It supports the home-network tunnel without needing a screen. Choose it when network access matters more than an on-device conversation interface.

Status and pictures

ideaspark and SenseCAP Indicator show status on a screen and can display images. Seeed reTerminal E1001 uses black and white e-paper; E1002 uses six colours. These status displays are different from the avatar, push-to-talk and settings interface on the UI boards.

Buttons and conversation

StickS3 and AIPI Lite combine push-to-talk with a two-button menu. CoreS3 and BOX-3 add touch controls. Home Assistant Voice Preview Edition is a useful exception: it has push-to-talk and a volume dial, but shows status on an LED ring rather than a screen.

PSRAM changes what the SDK can do

The home-network tunnel needs PSRAM, an extra memory resource. The device table marks ideaspark, Waveshare C6 and Cardputer ADV as having none, so they cannot provide that tunnel. They can still connect to Muse themselves. StickC Plus2 does have PSRAM, despite using a classic ESP32 chip: check the actual board, rather than deciding from the chip family alone.

Image handling also differs. ideaspark draws pictures straight to its screen without PSRAM. The Waveshare C6 and Cardputer ADV UI cannot hold an image, so their push-to-talk path returns scrolling text instead. Those are real feature limits, even though both boards have screens and audio hardware.

Find your board family

M5Stack: pocket controls, touch and a keyboard

The five M5Stack targets are StickS3, StickC Plus2, StopWatch, CoreS3 and experimental Cardputer ADV. StickS3 uses its front button for talking and its side button for the menu. StopWatch has a round touch screen and a yellow talk button; CoreS3 uses PWR for talking and touch for settings. StickC Plus2 has a buzzer and microphone, rather than the same audio hardware as StickS3.

Cardputer ADV uses GO or Space for voice notes and Esc, Enter and arrow controls for menus. Its keyboard does not currently support typing chat messages. The upstream port excludes images, spoken replies and the home-network tunnel. Treat the experimental label as part of the feature description when comparing it with the other M5Stack options.

Seeed: status panels and a conversation screen

Seeed’s four entries span different uses. SenseCAP Indicator has a 4-inch status display; reTerminal E1001 and E1002 use 7.5-inch black and white and 7.3-inch six-colour e-paper respectively. SenseCAP Watcher runs the screen UI with push-to-talk and images. For a still status panel, compare the reTerminals; for on-device interaction, look at Watcher.

Waveshare: S3 and C6 are different choices

The two 1.75-inch ESP32-S3 AMOLED variants support UI, push-to-talk, settings and images. The ESP32-C6-Touch-AMOLED-1.8 offers UI and voice notes with text replies, but no images or home-network tunnel. Similar product names do not make their memory or SDK capabilities interchangeable.

Espressif and other targets

Espressif’s C5 is the light-and-button starting point; its ESP32-S3-BOX-3 is a touch-screen UI option. AIPI Lite provides images and a two-button menu. ideaspark is a simple status-and-image screen, and Home Assistant Voice Preview Edition provides a ring, talk button and dial. Check the upstream feature table before counting on any extra peripherals a board physically contains.

Match the board to its installation path

Our Beta browser flasher supports StickS3 and ESP32-C5 DevKitC-1 today. Firmware is built, but physical hardware testing is still pending. Use desktop Chrome or Edge over HTTPS and a data-capable USB cable. The browser checks the firmware files, adds your own token locally and writes the connected board. It does not supply account access or a token.

For other targets, follow the upstream ESP32 guide and device configuration overlays. The main guide specifies ESP-IDF v6.0.1 and macOS or Linux. C5 is the default build; other boards need the matching chip target and settings. Do not flash a C5 or StickS3 image onto a different entry just because it also uses an ESP32.

After flashing, enable Developer mode in the Muse app under Settings > Devices, then choose Add Device and find the MuseGadget-prefixed device. On C5, breathing orange means setup is ready; breathing blue asks you to press BOOT to confirm pairing; green means connected. Follow your board’s own controls for confirmation.

Raspberry Pi 5 belongs to the Linux SDK

The Linux SDK turns a Raspberry Pi or another Bluetooth LE Linux computer into a gadget. Its commands can run a shell, read and write files, and report device health. They run with the installation account’s permissions. Choose this route for commands and services on a Linux machine; use the ESP32 table for dedicated board firmware.

Built around the open-source Muse Gadget SDK, licensed under Apache-2.0. Muse account access and your own SDK token are required. Read the SDK terms before use.

Supported board questions

Are all 17 boards available in the browser flasher?

No. The upstream SDK lists 17 ESP32 boards, but this site’s browser flasher supports only M5Stack StickS3 and ESP32-C5 DevKitC-1 today. It is Beta and has not yet been tested on physical hardware. Other boards follow the upstream build workflow with their own target and configuration overlays.

Which supported boards lack the home-network tunnel?

The ideaspark ESP32, Waveshare ESP32-C6-Touch-AMOLED-1.8, and experimental M5Stack Cardputer ADV have no PSRAM and run without the home-network tunnel. Muse can still reach and control those gadgets through their control session. Choose a tunnel-capable board if reaching other devices on your home network is your main goal.

Does push-to-talk mean I will hear spoken replies?

Push-to-talk sends a voice note; Muse transcribes it and normally replies in writing. Screen boards show replies as captions, while Home Assistant Voice Preview Edition replies appear in the Muse app. A speaker alone does not promise spoken answers. The upstream README describes adding a text-to-speech API as a customization.

Can I use a Raspberry Pi 5 instead of an ESP32?

Yes, through the separate Linux SDK. Raspberry Pi 5 is supported, with Bluetooth LE and a supported Linux system required. That path lets Muse run commands and read or write files as the account used for installation. It does not use this site’s ESP32 browser flasher or the board firmware in this table.

Do I need my own token for a board I already own?

Yes. Every gadget needs an SDK token from your own Muse account to pair, even if you already own the hardware. Buying our hardware does not include a token. Our browser installer writes your token into firmware locally; the token never leaves the browser during setup. Read the SDK terms before flashing.

Prefer a pocket screen?

Pocket Gadget is our independent M5StickS3 hardware preorder. It ships without an SDK token; you add your own after delivery. Compare its buttons-and-screen format with the C5 route before choosing.

Explore Pocket Gadget →