Home Assistant Voice for small business voice control
How small businesses use Home Assistant Voice for local, self-hosted voice control, and how MILabs sets it up for a site.
Updated 2026-05-23
What Home Assistant Voice is
Home Assistant Voice is the voice control feature of Home Assistant, an open-source home automation platform maintained by the Open Home Foundation. A person speaks a request to a device in a room, and the platform carries out the action, whether that means switching a light, adjusting a heater or reading out the state of a connected sensor. Because the platform is designed to run on hardware the owner controls, it can be self-hosted, so everyday commands do not have to depend on a cloud service. Each request moves through a pipeline that converts speech to text, interprets what was asked and returns a spoken or written reply. The speech engines and devices available depend on the setup chosen, and the vendor's own site lists the current options. For a business, the tool suits a fixed set of spoken commands that covers a task repeated on the premises. It acts as a control layer for connected equipment, so the devices and integrations added to it define what it can reach.
Home Assistant Voice in plain language
Think of Home Assistant Voice as a chain of swappable parts rather than one fixed product. A wake word starts the exchange, then separate modules turn speech into text, work out what was meant and speak back the reply. The owner picks each part, and can run it on their own hardware or use a hosted service. Those picks shape accuracy, data movement and upkeep.
Interpretation is the step people most often misjudge. By default, the platform matches what is said against entities already in the system, such as named lights, switches, thermostats, sensors and scenes. A request that fits a known sentence pattern, like switching off a named group of lights, runs quickly and predictably. A request about something nobody named, or a device with a vague label, tends to fail. An optional language model agent can handle looser phrasing, though it adds another part to maintain, so clear device names remain the first job.
Hardware is flexible. A dedicated voice satellite can sit in a room and send audio to the central platform, and a phone or compatible device can take the same role. Because the central platform is software the owner runs, updates, backups and network exposure become ongoing tasks.
What businesses use it for
- Turning lights, locks and heating on around a site on a schedule or on request.
- Reading the state of doors, sensors or equipment from wherever the speaker stands.
- Offering staff a hands-free spoken route through routine tasks on site.
- Playing short announcements or reminders aloud in a shared room.
- Keeping building controls on local hardware when the owner prefers that setup.
- Covering routine checks on a rental or serviced office between visits.
Who it suits
- Owners of small sites who want spoken control over lights and heating.
- Property managers who run several rooms or units from a single panel.
- Teams that would rather keep building controls on hardware they run themselves.
How MILabs sets it up
The easiest first step is to say hello through the enquiry form, and we'll take it from there. MILabs then talks with the owner or team lead about which rooms, devices and routine tasks the voice setup should cover. Together we choose the hosting arrangement, whether that is hardware on site or a machine the business already controls. We connect the lights, sensors, locks or other systems the business already uses, then test each spoken command where people will use it. Permissions come next, so only the right people can trigger each control, and sensitive actions such as unlocking doors can be limited. Before handover, the owner and MILabs agree who looks after updates, the speech engine and the device list.
Builds it fits
Industries it fits
Home Assistant Voice in practice
A working setup starts with a walk through each room and a list of what people ask for. A property manager might note that a cleaner wants the entry lights on before arrival, while a serviced office team wants the meeting room heater set before a booking begins. Each request becomes a sentence the platform can recognise, tied to a named entity, and the business settles on labels staff already use.
Testing happens in the room itself, since microphone placement, background noise and a closed door all change whether a command is heard. Misses get logged with the words spoken and what the system returned, which turns a vague complaint into a short list of phrases to adjust.
Access is handled as a separate step. Some commands suit every occupant of a building, while others belong to a named role. In a childcare or aged care setting, staff may be free to change heating, while anything touching doors or alarms stays with a supervisor.
Ongoing use depends on a short routine. Someone checks that devices still respond after updates, reviews the phrase log now and then and removes entities that have been replaced. Handover is where such a setup either keeps working or quietly fails.
Frequently asked questions
- What are the limits of Home Assistant Voice?
- Home Assistant Voice acts only on the devices and integrations connected to the platform, so a command aimed at a system that has not been added will fail. Recognition depends on the speech engine chosen, the microphone and the room, and a noisy space may call for a different arrangement. It suits short, defined commands more than open conversation. Testing it in the room shows the real limits.
- Who looks after Home Assistant Voice after setup?
- Ownership is agreed during setup and written down. MILabs can look after the platform, the speech engine and the device list under an arrangement the owner agrees to, or the business can keep those tasks in house. Either way, one named person should apply updates, confirm that devices still respond and change permissions when staff move on. Ask who receives the alert when a device goes offline.
- What should I check on the vendor's site before using Home Assistant Voice?
- The Home Assistant voice control documentation at home-assistant.io sets out the supported speech engines, languages, hardware options and hosting requirements. Where audio is processed depends on the components chosen, so the privacy notes on that site matter for each option. Because the documentation changes over time, the current version is the one to rely on for any installation.
- How do I know whether Home Assistant Voice is paying off?
- Measure it against a task the business does by hand. Time how long that task takes without the voice command, compare the result with the time taken afterwards, and count how often the command is used in a typical week. Staff can say whether it saves a trip or a step. If the command is rarely used or the old way is just as quick, the setup has not earned its place.
- Which industries use Home Assistant Voice?
- Businesses that run a physical site with repeated, controllable equipment are the most likely users. Property managers, serviced offices, hotels, childcare centres and aged care or disability services all check lights, heating or access points often. Whether it fits depends on the rules that apply to each site and the devices already installed, so both are worth a look before deciding.
