Different hardware paths
A Muse Home Link
alternative?
Home Link connects Muse to your home network through a small USB-C device made by Meta. If its initial offer does not fit your situation, the open-source ESP32 SDK provides a DIY route. Choose between a light-and-button board and a pocket screen by the experience you want to build.
Home Link offer details below reflect the October 4, 2026 factual snapshot. They describe the initial offer, not a live stock count. Consult Muse’s site for later availability and eligibility.
Choose a Muse Home Link alternative
The initial Home Link run was 5,000 units, free with an active Muse subscription in the United States, one per subscriber, with shipping planned for October 2026. A limited quantity, location requirement and subscription requirement are separate constraints. Being willing to buy hardware does not remove the conditions of that offer.
The DIY route starts with hardware you source and firmware you install. ESP32-C5 DevKitC-1 is the upstream guide’s quickest start: its built-in status light and BOOT button work without adding a display. Our independent Pocket Gadget preorder takes a different form, using M5StickS3 for a screen, buttons and voice-note input.
Both alternatives depend on Muse account access and your own SDK token. Hardware availability and token eligibility are separate decisions. Check that you can obtain a token before choosing a board or placing a preorder; this site does not provide, manage or share tokens.
Understand the home-network connection
On ESP32 boards with the home-network tunnel, Muse can reach devices on your home Wi-Fi that expose a local HTTP or HTTPS interface. This includes things you build with a local HTTP API. Start by checking how your intended device can be reached, rather than assuming a network-connected appliance is automatically compatible.
That scope does not establish support for every smart-home protocol or every appliance. C5 and StickS3 have tunnel support in the upstream feature table. Boards without PSRAM cannot provide that tunnel, even if they can connect to Muse and show a reply. For other form factors, use the supported board comparison.
Compare three hardware paths
Home Link’s offer, a self-sourced C5, and our independent hardware preorder have different access and setup requirements. The table uses only documented attributes.
| Attribute | Muse Home Link | ESP32-C5 DevKitC-1 DIY | Pocket Gadget |
|---|---|---|---|
| Access | Initial 5,000 units; US only; active Muse subscription; one per subscriber | Source your own board; own Muse access and SDK token required | Independent M5StickS3 preorder; own Muse access and SDK token required |
| Cost | Free under the initial offer’s conditions | Board cost depends on your supplier; no price quoted here | $79 hardware + $15 flat tracked shipping per order |
| Format | Small USB-C home-network device | Built-in status light and BOOT button | Colour screen, physical buttons, microphone and rechargeable battery |
| SDK experience | Connects Muse to your home network | Home-network tunnel; status and pairing button | Home-network tunnel; screen UI, push-to-talk, two-button menu and images |
| Setup route | Consult Muse’s instructions | Upstream ESP-IDF build or this site’s Beta browser flasher | Add your own token after receipt using Beta browser setup |
| Timing | Initial offer ships October 2026 | Source and prepare the board yourself | Dispatch from Shenzhen within 30 days of order |
Build the ESP32-C5 DIY route
1. Prepare the board and your own token
Use the ESP32-C5 DevKitC-1 target named in the upstream guide, a USB cable that carries data, and the Muse app on your phone. Obtain a personal token from your Muse account under Account > SDK tokens and read the SDK terms. Every self-built gadget needs a token to pair.
2. Choose browser setup or a local build
For this site’s browser flasher, select ESP32-C5 DevKitC-1 in desktop Chrome or Edge over HTTPS. Windows, macOS and Linux are supported by that browser path. The firmware is built, but the installer remains Beta because physical hardware testing is pending. That limitation applies even though the upstream SDK supports C5.
The upstream local workflow uses ESP-IDF v6.0.1; the main ESP32 guide describes macOS and Linux. From the SDK’s esp32 directory, use idf.py menuconfig to set your token under ESP32 Device SDK, then idf.py build. C5 is the default target. Follow the README’s flash and monitor command with your actual serial port.
3. Write firmware and check the device state
The browser writes your token into the firmware in memory before flashing; the token never leaves your browser during setup and is not saved in browser storage. With a local build, you supply the token to your own toolchain instead. These are two installation workflows for the same board, rather than a way to obtain token access.
After flashing C5, a breathing orange light means ready for setup. If the upstream flash command cannot connect, its guide says to hold BOOT, tap RESET, release BOOT and retry. Use the serial monitor for device logs when diagnosing a failure; a flashing page alone cannot confirm a working physical device.
4. Pair through the Muse app
Enable Settings > Devices > Developer mode. Choose Add Device using the plus icon and look for MuseGadget-XXXXXX. When the C5 light breathes blue, press BOOT to confirm pairing. Solid blue means joining Wi-Fi and connecting to Muse; green means connected. Pair on a network you trust, as the upstream guide recommends.
If you need to set C5 up again, hold the button for five seconds. Reflashing normally preserves pairing and Wi-Fi settings; the upstream erase-flash command starts fresh. Decide which outcome you need before erasing a board that is already paired.
When a pocket screen fits better
Pocket Gadget is our M5StickS3-based hardware preorder. Its upstream UI supports push-to-talk, a two-button menu, captions and images sent by Muse. That suits someone who wants to interact on the gadget itself as well as use the home-network tunnel. C5 supplies a light and button without that screen interface.
Push-to-talk sends a voice note and Muse normally answers in writing. A microphone and speaker do not guarantee spoken responses. Also distinguish hardware from SDK integration: the upstream StickS3 notes say its IMU, IR and Grove port are not yet used. Choose it for documented functions, rather than every peripheral in the enclosure.
The preorder is $79 plus $15 tracked shipping per order, with dispatch from Shenzhen within 30 days and a full refund before shipping. Devices ship without an SDK token. You add your own after receipt at Beta setup; buying independent hardware does not grant a subscription or token.
Read the token terms before buying
The SDK terms restrict tokens to personal, non-commercial projects, prohibit sharing, limit each token to 50 devices, and prohibit embedding a token in hardware sold to someone else. Our hardware ships without one. Review the terms for your intended project, and treat the choice of hardware separately from permission to use the SDK.
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.
Home Link alternative questions
Why look for an alternative to Muse Home Link?
The initial Home Link offer was limited to 5,000 units, free with an active Muse subscription in the United States, one per subscriber, with shipping planned for October 2026. Those conditions may not fit your location or account. The ESP32 SDK provides a self-built hardware route, but it still requires your own Muse account access and SDK token.
Is ESP32-C5 a complete replacement for Home Link?
It is a DIY route to the upstream home-network tunnel, with a status light and BOOT button. That supports a similar network-access goal, but does not establish feature-for-feature equivalence with Home Link. Muse can reach local devices exposing HTTP(S); do not assume every smart-home device or protocol is supported.
Can I buy hardware with a Muse SDK token included?
Our devices ship without an SDK token. You must obtain your own token from your Muse account and add it after delivery. The SDK terms prohibit embedding a token in a device sold to someone else, prohibit token sharing, restrict use to personal non-commercial projects, and allow up to 50 devices per token.
Is the C5 browser setup hardware-tested?
No. Our flasher supports ESP32-C5 DevKitC-1 and M5Stack StickS3 today, but it is Beta and has not yet been tested on physical hardware. Firmware is built and passes image checks. The upstream local build workflow is also available; read the board instructions and use a USB cable that carries data.
Should I choose C5 or the pocket screen?
Choose C5 when a light, button and home-network tunnel fit your project. Choose Pocket Gadget if you want an independent M5StickS3 hardware preorder with a screen, push-to-talk, two-button menu and image support. Both paths require your own SDK token. Neither purchase grants a Muse subscription or changes SDK token eligibility.