What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
For a Home Assistant household, the clearest ready-made choice is Home Assistant Voice Preview Edition. It is an open-source, ESPHome-based voice endpoint for Home Assistant Assist, with a mute switch, Wi-Fi, Bluetooth and a 3.5 mm output. If you prefer to build, an ESPHome device with a microphone and speaker can stream audio to Assist. Neither route should be treated as a universal replacement for every Alexa, Google Home or Apple Home speaker: compatibility depends on your controller, integrations, network and the way you want voice processing to run.
Start with the platform, not the speaker
An “open-source smart speaker” is not automatically compatible with every smart-home product. In this category, the speaker is usually an audio endpoint: it captures your request, sends it to a voice-assistant service and plays the response. The service and your home-automation controller determine which lights, switches, thermostats and scenes can actually be controlled.
As an Amazon Associate I earn from qualifying purchases.
Home Assistant Assist is the relevant control layer for the two options covered here. Home Assistant documents Assist on its dedicated Voice Preview Edition hardware and on voice devices built with ESPHome. If your home is controlled by a different platform, verify support before buying or assembling anything; the available material does not establish universal compatibility with Alexa, Google Home, Apple Home or every Matter product.
Make an inventory before choosing hardware
- List the controller that currently owns your automations. If that is Home Assistant, the two routes in this guide are designed for it.
- For each device you want to control, confirm that Home Assistant has an integration and that the integration exposes the action you need, such as turning on a light or setting a thermostat.
- Record whether your devices communicate over Wi-Fi, Ethernet, Thread or another technology. A speaker’s radio list does not prove that it can control a device.
- Decide whether you need voice control only or also broad music playback. The Voice Preview Edition is documented as a voice device; its documentation does not establish high-fidelity music-speaker performance.
- Choose where speech recognition and speech synthesis should run: on your own system or through Home Assistant Cloud.
The two practical open-source routes
| Route | What you receive | Best for | Important limitation |
|---|---|---|---|
| Home Assistant Voice Preview Edition | A ready-made ESPHome-based voice endpoint with ESP32-S3 hardware, microphone mute, Wi-Fi, Bluetooth and a 3.5 mm headphone jack | Home Assistant users who want dedicated hardware without designing a device | It is designed around Home Assistant Assist rather than established as a universal smart speaker for every platform |
| DIY ESPHome voice device | Your own microphone-and-speaker hardware configured to stream audio to Home Assistant | Builders who want custom enclosure, controls, placement or component choices | Audio and voice components consume substantial resources; hardware and configuration must be checked for the chosen build |
Both routes use the same basic architecture: the endpoint captures audio, Home Assistant receives it, Assist processes the request and the endpoint plays the response. The ready-made unit reduces hardware decisions. The ESPHome route gives you flexibility but makes you responsible for board resources, wiring, firmware and enclosure details.
#1 Best Overall
- Designed for Home Assistant Voice & Music Workflows: Preloaded with Home Assistant Voice Assistant and Music Assistant. Functions as both a voice input terminal and an audio playback endpoint.
- Dual Microphones for Voice Capture: Built with dual digital microphones for wake word or button-activated voice capture. Audio is streamed to the Home Assistant voice pipeline.
- Integrated 3W Speaker for Direct Playback: The built-in 3W/4Ω speaker supports TTS playback, Music Assistant streaming, and system audio without external speakers.
- Linux-Based Local Operation: Runs a lightweight Linux system on a quad-core ARM A53 CPU with 256MB RAM and 512MB flash for local audio processing.
- Development & Debugging Capabilities: Supports firmware flashing, and also provides access to live logs, on-device editing—suitable for routine development or issue diagnosis.
What Home Assistant Voice Preview Edition actually provides
Home Assistant presents Voice Preview Edition as voice hardware for Assist. It runs ESPHome and uses an ESP32-S3. The documented physical features are useful for a household device:
- A hardware microphone-mute switch, so muting does not depend solely on software.
- Wi-Fi for connecting to Home Assistant over your local network.
- Bluetooth support.
- A 3.5 mm headphone jack for an external speaker.
- Physical controls for interacting with the device.
Those features make it a practical voice endpoint, but they do not establish that it is a general-purpose music speaker or that every Bluetooth speaker and Matter accessory will work with it. Treat the 3.5 mm jack as the documented route for external audio when selecting a louder or differently placed speaker.
When the ready-made device is the better choice
- You already run Home Assistant and want the shortest path to Assist hardware.
- You want a physical mute control rather than a software-only setting.
- You prefer a documented device over selecting a microcontroller, microphone, amplifier and enclosure separately.
- You want the option of connecting an external speaker through 3.5 mm output.
When it is not the right fit
- Your primary controller is not Home Assistant and you have not confirmed a supported integration.
- You expect a high-fidelity music system rather than a voice endpoint.
- You need a particular language, region or third-party service that you have not verified in your own Home Assistant installation.
- You require every Matter device to be controllable without checking its integration and network path.
Building a voice device with ESPHome
ESPHome lets you create a voice endpoint from compatible hardware containing a microphone and speaker. The device streams microphone audio to Home Assistant, where Assist handles voice processing. This separates the physical endpoint from the speech stack: you can place several small devices around a home while keeping processing in Home Assistant.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minutePlan the hardware as a system
Do not begin with an arbitrary development board. Select the board, microphone, speaker or amplifier and power arrangement together, then verify that the combination has enough memory, processing capacity, pins and stable power for the ESPHome voice and audio components. A design that works for sensors may not have enough resources for audio.
- Controller: confirm that the chosen board is supported by ESPHome and has the interfaces required by your microphone and audio output.
- Microphone: check its electrical interface, voltage and placement. Mechanical noise and distance from the speaker affect recognition.
- Speaker path: determine whether the board can drive the speaker directly or needs an amplifier or dedicated audio output.
- Power: allow for the peak draw of the board and audio hardware, not just idle sensor consumption.
- Enclosure: leave openings for the microphone and speaker while reducing vibration and feedback.
ESPHome’s voice and audio components consume meaningful device resources. Bluetooth and BLE can also conflict with some combinations of audio components. If your build needs Bluetooth, test that combination before committing to an enclosure or multiple-room rollout.
A practical DIY workflow
- Choose an ESPHome-supported board and audio components whose interfaces and power requirements match.
- Install the board in ESPHome and create a configuration for the microphone, speaker output and network connection.
- Compile and flash the firmware, then confirm that the device remains connected to your Wi-Fi network.
- Add or adopt the device in Home Assistant and expose it as a voice device for Assist.
- Test a short command from the intended listening position. Check recognition, response audio, latency and any feedback loop.
- Only after the bench test succeeds, finalize the enclosure, cable routing and permanent power.
The exact component names and configuration syntax depend on the board and peripherals you select. Copying a configuration intended for different hardware can produce failed builds, unreliable audio or a device that runs out of memory.
Choose local processing or Home Assistant Cloud
Voice processing can be arranged locally or through Home Assistant Cloud. The local route keeps the processing stack under your control, but you must run and maintain the speech-to-text and text-to-speech components needed by Assist. The Cloud route is described as the simpler way to obtain those speech services.
| Processing path | Advantages | Costs and responsibilities |
|---|---|---|
| Local | More control over where audio is processed and how the stack is configured | You must provide, configure and maintain the required speech-recognition and speech-synthesis services; hardware and software resources matter |
| Home Assistant Cloud | Simpler setup for speech-to-text and text-to-speech | Voice requests use a hosted service, so review the service’s privacy terms and network requirements before enabling it |
Privacy is therefore a design decision rather than a label on the speaker. A locally connected microphone can still send audio to a cloud speech service if Cloud processing is selected. Conversely, a ready-made device does not force one processing location; the processing choice is made in the Home Assistant voice setup.
Rank #3
Check device compatibility before you buy or build
Use a three-layer check: controller integration, network transport and voice action.
1. Controller integration
Find the device in Home Assistant’s integrations and confirm that it exposes the entities and services you intend to use. A light may appear as a switch, a fan as a fan entity and a thermostat as a climate entity; the available voice commands depend on what the integration makes controllable.
2. Network transport
Matter is an application-layer control protocol that runs over an existing IP network. Depending on the product, Matter communication uses IPv6 over Wi-Fi or Ethernet, or Thread. Matter is not itself a single proprietary radio transport. Your Home Assistant controller, border-router arrangement, VLAN or firewall rules and the device’s network therefore matter as much as the Matter logo.
3. Voice action
Test the specific operation you care about, not merely device discovery. “Works with Matter” does not prove that every voice command, attribute or automation is available through your Assist setup. Confirm that the device is visible in Home Assistant, that its state updates and that an Assist command can invoke the intended service.
Rank #4
- Fitment For: Designed for Home Assistant Voice Preview Edition, ensuring a secure and stable wall mounting fit.
- Optimized Voice Interaction: Positions your device at a convenient height for better voice control experience.
- Stable Device Support: Provides firm support to keep the device securely positioned during daily use.
- Space Saving Wall Mount: Wall mount holder keeps your smart speaker off desks and counters for a cleaner setup.
- Multi Room Application: Ideal for kitchens, bedrooms, offices, and other smart home locations.
Set up the ready-made route
- Install or update Home Assistant and confirm that the devices you want to control are already integrated and controllable from its dashboard.
- Connect Voice Preview Edition to power and join it to the same reachable network as Home Assistant.
- Use Home Assistant’s voice-assistant configuration to add the device as an Assist endpoint and select your speech-processing path.
- Leave the microphone unmuted only when you are ready to test. Use the physical mute switch whenever you want a hardware-level pause in listening.
- Speak a simple command that targets one known entity, such as a single light. Verify both the spoken response and the entity’s state change.
- If more volume or a different room placement is needed, connect an external speaker through the documented 3.5 mm output and repeat the test.
Start with one endpoint and one device. Once recognition, processing and control work reliably, add rooms or more complex intents. This isolates whether a failure belongs to the microphone, network, speech service or device integration.
Set up a DIY ESPHome endpoint
- Document the selected board and every audio component, including voltage, interface and amplifier requirements.
- Create the ESPHome configuration for networking, microphone capture and audio output. Keep the first firmware build minimal so resource problems are easy to identify.
- Flash the device and confirm stable Wi-Fi before enabling optional features.
- Adopt the device in Home Assistant and connect it to Assist using the voice-device setup.
- Measure practical behavior: command recognition from normal speaking distance, response delay, speaker volume and acoustic feedback.
- Add Bluetooth or BLE only after the wired or baseline audio path works. If audio becomes unstable, remove optional radios and retest because ESPHome documents conflicts in some Bluetooth/audio combinations.
Troubleshoot by symptom
The device appears, but Assist does not respond
- Check that the endpoint and Home Assistant are on networks that can reach each other.
- Verify that the microphone is not muted in hardware.
- Confirm that a speech-to-text and text-to-speech path is configured, either locally or through Home Assistant Cloud.
- Try a short command and inspect whether audio is reaching Home Assistant before changing hardware.
Speech is recognized but the device does not control anything
- Open Home Assistant and test the device entity manually.
- Check that the integration exposes the desired service and that the entity is available.
- For Matter, verify the controller, IPv6 network path or Thread infrastructure rather than relying on the Matter label alone.
DIY firmware fails to build or audio is unreliable
- Compare the configuration with the exact board and peripherals; pin assignments and interfaces are not interchangeable.
- Reduce optional components to free resources for voice and audio.
- Test Bluetooth or BLE separately because radio use can conflict with some audio configurations.
- Check power delivery and amplifier requirements under playback, not only while idle.
Voice feedback or poor recognition occurs
- Move the microphone farther from the speaker or reduce speaker volume during testing.
- Improve enclosure isolation and keep the microphone opening clear.
- Test from the location where commands will actually be spoken rather than directly beside the device.
A decision checklist
Choose Voice Preview Edition when you want a documented, ready-made Assist endpoint, physical microphone muting and an optional 3.5 mm external speaker. Choose DIY ESPHome when enclosure size, placement, component choice or custom controls justify the additional configuration and testing.
Before committing, answer these questions:
- Is Home Assistant the platform that owns the devices I need to control?
- Have I verified each device’s integration and the exact voice action?
- Does my network support the device transport, including IPv6 or Thread where Matter requires it?
- Do I want local speech services, or is Home Assistant Cloud’s simpler setup preferable?
- Am I buying a voice endpoint, or do I actually need a music-focused speaker?
- If building, have I checked resource usage, power, interfaces and Bluetooth/audio interactions for the exact hardware?
What “open source” changes—and what it does not
ESPHome-based hardware gives you inspectable firmware and a path to custom devices, while Home Assistant Assist provides the automation-facing voice layer. The open ecosystem can make components shareable across projects; Home Assistant’s Wyoming initiative describes that interoperability goal. It should not be read as proof that all voice hardware is already interchangeable.
Free tools Windows power users keep installed
One-click scans. No signup required.
Open source also moves some responsibility to you. You gain control over firmware and processing choices, but you must maintain the Home Assistant installation, network, speech services and any DIY hardware. For most Home Assistant users, the ready-made endpoint is the lower-effort starting point; ESPHome is the better fit when the build itself is part of the goal.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
