EchoMuse is a free, open source internet of things (iot) project written in Python and released under MIT. It has 1,507 GitHub stars, 124 forks and 156 open issues, and was last pushed 32 hours ago. On this registry it ranks #68 of 110 tracked projects in Internet of Things (IoT), with 5 head-to-head comparisons available.

What is EchoMuse?

EchoMuse is an MIT-licensed, Python-based project that replaces the software on a second-hand Amazon Echo Dot (2nd generation, 2016) or Echo (2nd generation, 2017) so the device becomes a local voice satellite for Home Assistant, with no Amazon software left on it and no Amazon account required.

What it is

EchoMuse is a replacement for the software that ships on the Echo Dot 2nd generation and the Echo 2nd generation. It installs its own Linux userspace, called emOS, along with its own audio pipeline and a wake word that runs on the Echo itself, so nothing is sent anywhere until the wake word is spoken. The original hardware continues to work: the microphones, speaker, LED ring and buttons all remain in service. The project lives in the Home Assistant ecosystem, and a companion controller that runs on the user's own network detects the wake word, manages the devices and serves a web dashboard.

The concrete problem it solves is the Amazon software stack on hardware people already own. EchoMuse removes the requirement for an Amazon account, Alexa and any cloud service operated by the project, and it replaces them with Home Assistant's Assist pipeline, so the assistant can do what the user's Home Assistant can do. The Dot appears in Home Assistant as an ordinary ESPHome voice satellite, which means there is nothing extra to install on the Home Assistant side.

Key capabilities

  • Wake word detection runs on the Echo itself, so no audio leaves the device until the wake word is spoken.
  • Ships emOS, the project's own Linux userspace, released as a separately versioned artefact alongside the firmware releases.
  • Runs a controller on the local network, distributed both as a Home Assistant add-on and as the echomuse-controller container image on the GitHub Container Registry.
  • Registers the Echo with Home Assistant as an ESPHome voice satellite over the ESPHome API, with no additional integration to install.
  • Keeps the Echo's microphones, speaker, LED ring and buttons functional after the reflash.
  • Provides a setup wizard that runs in Chrome or Edge and talks to the Echo over USB directly from the browser.
  • Offers two unlock targets on the Dot, unlock fireos5 and unlock fireos6 (the default), documented in docs/rooting.md.

Who uses it and how

  • Home Assistant households that already run an Assist pipeline and want a voice satellite without a cloud dependency.
  • Owners of second-hand Echo Dot 2nd generation and Echo 2nd generation hardware, which the README notes sells for very little.
  • Self-hosters with an always-on computer for the controller; the Home Assistant machine itself is sufficient if it runs add-ons.
  • Hardware hackers and tinkerers, reflected in the hardware-hacking and open-source-firmware topics, who are willing to perform a one-time USB unlock with firebreak.
  • Users who want voice control with no Alexa skills, shopping, calling, Drop In or Amazon account.

Getting started

The Echo must first be unlocked over USB with firebreak, which runs R0rt1z2's amonet-biscuit unlock for the Dot and amonet-radar for the Echo; afterwards the controller is started either as a Home Assistant add-on from the EchoMuse repository or as the echomuse-controller Docker container.

How it compares

No list of paid products that EchoMuse replaces is provided in the facts, so this page makes no such comparison. Where it fits: it presents the Echo to Home Assistant as an ordinary ESPHome voice satellite, and its topic list places it alongside Music Assistant and Bermuda within the local-first Home Assistant ecosystem.

When to use it — and when not to

Choose EchoMuse only if a working Home Assistant with an Assist pipeline is already in place, because the project is explicitly not standalone and Home Assistant performs the speech recognition, the understanding and the voice. The one-time USB unlock is performed at the user's own risk: a failed step can leave the Echo soft-bricked, and recovery depends on the linked XDA threads for the Dot and the Echo. It is also not ready out of the box, supports only the Dot 2nd generation and the Echo 2nd generation for now, with the Dot 3rd generation merely planned, and the repository currently carries 156 open issues.

project readme (upstream, from github) — read inline

EchoMuse

Turn an old Amazon Echo Dot (2nd gen) or Echo (2nd gen) into a local voice assistant for Home Assistant.

CI Firmware emOS Controller License: MIT

Join the community — Discord · r/echomuse

Buy Me a Coffee

EchoMuse makes a second-hand Echo Dot a voice satellite for Home Assistant: say the wake word, ask something, and hear the answer from the Dot. There is no Amazon account, no Alexa and no cloud service of ours. The Dot shows up in Home Assistant as an ordinary ESPHome voice satellite, so there is nothing extra to install there.

At a glance

What it is

  • A replacement for the software on an Echo Dot 2nd generation (2016) or an Echo 2nd generation (2017). Their microphones, speaker, LED ring and buttons all work.
  • A controller you run on your own network, as a Home Assistant add-on or a Docker container. It detects the wake word, manages your devices and has a web dashboard.
  • A way to reuse hardware that sells second-hand for very little.

What it isn't

  • Not Alexa. No Alexa skills, shopping, calling, Drop In or Amazon account. The assistant is Home Assistant's Assist, so it can do what your Home Assistant can do.
  • Not standalone. You need a working Home Assistant with an Assist pipeline. Home Assistant does the speech recognition, the understanding and the voice.
  • Not ready out of the box. The Echo needs a one-time unlock over USB first, which firebreak runs from one command. If a step goes wrong the Echo can end up soft-bricked, and the XDA thread for the Dot or the Echo covers recovering it.
  • Not for other Echo models, yet. The Echo Dot 2nd gen and the Echo 2nd gen are supported. The Echo Dot 3rd gen is planned.
  • Not affiliated with Amazon.

What you need

An Echo Dot 2nd gen or an Echo 2nd gen The hardware being repurposed.
Home Assistant With a working Assist pipeline.
An always-on computer Runs the controller. The Home Assistant machine itself is fine if it runs add-ons.
A computer (macOS, Linux or Windows) and a micro-USB cable, once To unlock the Echo with firebreak.
Chrome or Edge, once The setup wizard talks to the Echo over USB from the browser.

Getting started

  1. Unlock the Echo with firebreak, which runs R0rt1z2's unlocks: amonet-biscuit for the Dot and amonet-radar for the Echo. On the Dot either target works: unlock fireos5 leaves it on FireOS 5, unlock fireos6 (the default) on FireOS 6, and the rooting guide explains the choice. The Echo has one, to FireOS 6. You do this at your own risk.

  2. Start the controller, as an add-on:

    Add the EchoMuse repository to Home Assistant

    or with Docker:

    mkdir echomuse && cd echomuse
    curl -O https://raw.githubusercontent.com/wilbowes/EchoMuse/main/controller/docker-compose.deploy.yml
    curl -o .env https://raw.githubusercontent.com/wilbowes/EchoMuse/main/controller/.env.example
    docker compose -f docker-compose.deploy.yml up -d
    
  3. Run the setup wizard from the dashboard with the Dot plugged in over USB. It installs everything and joins your WiFi. Approve the Dot in the dashboard and Home Assistant discovers it.

The quickstart walks through all three.

emOS or FireOS?

The wizard offers two ways to run EchoMuse on the Dot. The Echo 2nd gen runs emOS only:

  • emOS (the default) replaces Amazon's Android with our own small Linux userspace, keeping only the Dot's kernel. It runs on FireOS 5 and FireOS 6 devices, and the 3.5mm jack works properly on it. The wizard keeps a copy of your original boot image, and restoring it takes about ten seconds.
  • FireOS with root keeps Amazon's Android 5 and runs EchoMuse on top. FireOS 5 only. It is the older path, with the most hours behind it.

Features

  • Voice turns through Assist, with the answer played on the Dot.
  • Wake word on the Dot or on the controller. By default each Dot listens for the wake word itself and sends nothing until it hears it. The controller can do it instead, for every Dot or just one; that Dot then streams its microphone to the controller all the time. A Dot whose wake word model isn't installed yet, or failed to load, answers to its button only and says why. It never falls back to streaming.
  • Barge-in: say the wake word over a reply to interrupt it.
  • More than one Dot: the one that hears you loudest answers and the rest stay quiet.
  • Music: each Dot is a Home Assistant media player (media browser, Music Assistant, radio). Speaking over music lowers it under the answer rather than pausing it.
  • Timers and announcements from Home Assistant.
  • Custom wake words you train yourself with oww_forge and install from the dashboard.
  • Extras in Home Assistant: a Bluetooth proxy per Dot (handy with Bermuda), an ambient light sensor on Dots that have one, and the action button as an event you can automate.
  • A dashboard for setup, updates, per-device settings (EQ, LED ring, mic tuning), logs and a history of voice turns.
  • Updates over WiFi, for the firmware and for emOS itself, each with automatic rollback if the new version fails. emOS updates need emOS 0.10 as the release to install and controller 2.26.0 or later; before that, emOS is updated by re-running the wizard.

Privacy

  • The Echo listens for its wake word itself. Nothing leaves it until it hears the wake word. Then what you say goes to the controller on your LAN and on to Home Assistant, and stops when you stop speaking. Where it goes after that depends on your Assist pipeline (fully local with Whisper and Piper, or a cloud service if you chose one). A false wake sends a few seconds of audio you didn't mean to; that is true of every wake word system, Amazon's included. How it works.
  • You can detect the wake word on the controller instead, per Echo. That Echo then streams its microphone to the controller all the time, on your LAN and nowhere else, and the dashboard says so. Installs from before this keep their existing setting until you change it (Config → Wake word detection). Firmware that predates it streams in every mode and is labelled that way until you update it.
  • No telemetry. No analytics, no install counter. The controller only connects out to GitHub, to check for and download releases, and you can set how often it checks (details).
  • The mute button is a software mute. It silences the microphones in the audio chip and EchoMuse refuses to listen while it is on, but the Dot 2 has no hardware switch that disconnects them.

Status and known issues

EchoMuse is in active development and runs daily on a small fleet. emOS is newer than FireOS and has fewer device-hours behind it. Open issues worth knowing before you start:

  • The 3.5mm jack on FireOS (not emOS): unplugging can stall the microphone for about 30 seconds (#117, #141).
  • emOS on FireOS 6 cannot join WPA3 networks: the WiFi driver has no support for it. Use WPA2 (#536).
  • An announcement during a ringing timer can't be heard (#373).

Everything else is in the issue tracker.

Getting help

  • Questions and bugs about EchoMuse go to our issues, not to the XDA thread. The thread is for the unlock only.
  • Check the FAQ first.
  • Attach a support bundle (Settings → Support → Collect bundle, then Download). It holds the logs and versions we need, with transcripts, recordings and network names removed.

Documentation

Quickstart From nothing to talking to your Dot.
Rooting Unlocking the Echo, and which target to use.
Configuration Every setting, in plain language.
FAQ Common problems and their fixes.
emOS How our own userspace on the Dot works.
How the voice pipeline works The path from wake word to answer.
Device ↔ controller protocol For porting EchoMuse to new hardware.
Boards How the firmware finds its hardware by name, and how to describe a new board.
Profiling a new Echo Scripts that collect what a port needs from an unsupported device.
Contributing Building from source, tests, and how to send changes.
Engineering journal How each part was worked out, including the dead ends.

How it's built

EchoMuse is written largely with Claude, Anthropic's AI model, directed by the maintainer. More than half the commits carry a Co-Authored-By: Claude line, and replies on our issues are signed "Team EchoMuse (powered by Claude)". Nothing about that is hidden.

Credits

EchoMuse would not exist without:

  • R0rt1z2, for amonet-biscuit and amonet-radar, the unlocks that everything here depends on.
  • bboe, for firebreak, which runs them from one command.
  • Binozo, for EchoGo, the original SDK for this hardware, and GoTinyAlsa.
  • Dragon863, for EchoCLI.
  • David Scripka, for openWakeWord.
  • Xiph.Org, for SpeexDSP (the echo canceller), and Nils L. Westhausen, for DTLN (noise suppression).
  • Home Assistant and ESPHome, whose open voice stack EchoMuse plugs into.
  • Everyone who has contributed code, filed issues or tested on their own hardware.

Licence

EchoMuse is MIT licensed. It includes third-party components that keep their own licences, listed with their copyright notices in NOTICE.md. emOS releases also ship busybox (GPL-2.0), with its source and licence attached to each release, and wpa_supplicant (BSD).

Amazon, Echo, Echo Dot, Alexa and FireOS are trademarks of Amazon.com, Inc. or its affiliates. EchoMuse is an independent project, not affiliated with or endorsed by Amazon.

Frequently asked questions

Is EchoMuse free to use?

EchoMuse is open source under the MIT licence. There is no licence fee and no seat count — you can self-host it or, where the project offers one, pay a vendor for a managed version instead.

What does EchoMuse do?

A local voice assistant for Home Assistant on old Amazon Echoes, with no Amazon software left on them: our own Linux userspace (emOS), our own audio pipeline, a

What is EchoMuse written in?

EchoMuse is primarily written in Python. Its source is publicly available at https://github.com/wilbowes/EchoMuse, and it has 1,507 GitHub stars.