Chapter 8
Connect an assistant, and make it ask first
The chapter in a minute
- Whatever is on the assistant's list can be switched with no yes, so keep it short, low in stakes and free of locks, cameras and alarms.
- A yes counts only when the hub holds the action until a person presses a switch the assistant can't see.
- Whatever the reply says, the lamp and the history tell you what happened.
Try it now
Ask first
0 of 16 steps done
Step 1 of 16
Write the row first. Under 'may see', name your devices and the routine. Under 'may do', put what it can switch with no yes and 'start Yes lamp, which waits for my press'.
Tools and settings, as of a date
The book points to the ‘Connect an assistant’ section of the companion page. Here it is in full, with the date each detail was checked. Open it on the companion page
Chapter 8 points here "with today's names for each control and a dated note on each" path. It also names a companion page option for a voice device.
What was tested, and on which version
The yes switch in chapter 8 was run on a test hub with simulated devices on 8 November 2026, on Home Assistant core version 2026.10.4. The newest release that day was 2026.11.0, which was not run. Your lamp and your phone are the part only you can check.
Today's names on the local-first path (Home Assistant)
| Job | Where it was on 8 November 2026 |
|---|---|
| Add an assistant | Settings, Devices and services, Add Integration, then the assistant's name (Ollama, Google Gemini, OpenAI, Anthropic, OpenRouter) |
| Let it control only what you chose | Under AI tools, choose the device control option that reaches only the devices you expose. The other option "accesses everything and only works for administrators" |
| The list it can see | Settings, Voice assistants, the Expose tab |
| Stop new devices joining the list | The Expose new entities switch on the Assist card ("Should new entities be exposed?") |
| Make the yes switch | Settings, Devices and services, Helpers, Create helper, Toggle |
| Make the routine | Scripts, Create script, Create new script, Add action, Save |
| Offer the routine to the assistant | In the script's menu (three dots), Settings, Voice assistants, on for Assist, Save |
| The wait | Add action, Blocks, Wait for a trigger, Add trigger, then fill in Timeout |
| The trap | Continue on timeout is on by default. Turn it off. In newer versions it may stay greyed out until a Timeout is filled in |
| Read what it did | Activity, History, and the trace of each run |
Sources: Ollama (opens in a new tab); Exposing entities to Assist (opens in a new tab); Input boolean (opens in a new tab); Scripts (opens in a new tab); Exposing scripts to LLM conversation agents (opens in a new tab); Wait for a trigger (opens in a new tab); Activity (opens in a new tab); History (opens in a new tab). The Expose new entities wording comes from the hub's own screen code, not its documentation.
Lights and switches start on the list. On a fresh test hub the lamp and the plug were already in view. Lights, switches, fans, covers, scenes, climate, media players, to-do lists, vacuums, water heaters and humidifiers start in view by default. Locks and cameras don't. Read the whole list.
Fewer is better. For experiments with a local model, Home Assistant recommends exposing fewer than 25 devices. Only models that support tools can control the hub.
The assistants at the other end
- The hub's own built-in assistant. Needs no extra computer and no paid key. It matches what you type against sentences it knows, so you use the routine's name. Confirmed end to end on the test hub.
- A language model on one of your own computers. Home Assistant's page connects to a program called Ollama on Windows, macOS or Linux. Ollama's app has a switch labelled Expose Ollama to the network in its settings; that wording comes from the app's code, not its documentation. The computer must be on when you use it. Nobody has run this route for the book. Sources: Ollama integration (opens in a new tab); Ollama for Windows (opens in a new tab).
- An online service. OpenAI's and Anthropic's integrations are a paid service: you enable billing and make a key on the provider's site (OpenAI (opens in a new tab); Anthropic (opens in a new tab); OpenRouter (opens in a new tab)). Google Gemini's page describes a free, rate limited plan whose prompts are used for product improvement, but Google's own terms say the service is for developers and "not for consumer use". The book doesn't offer a free online route (Google Gemini (opens in a new tab)). With an online service, what it needs to know about the devices in view leaves your home.
A dated note on the mainstream path
As of 8 November 2026, we found no way to limit Google's assistant to named devices: connecting it gives it "the same homes and devices" as your account. The confirmations on this path, such as a yes or no or a PIN, are set by whoever built the device or its add on, not by you (Google, secondary user verification (opens in a new tab); Amazon, Alexa discovery objects (opens in a new tab), last modified 4 October 2026). Google says its home controls are "for convenience only". Amazon's own help page on making routines by voice says Alexa "creates and saves the routine in the Alexa app" and then tells you whether it worked. It describes no check with you before saving, and no way to choose which devices Alexa may control (About Routines by Voice with Alexa+ (opens in a new tab), no date on the page, read on 14 November 2026).
Google's app keeps an Activity tab; activity from other makers' devices needs a Google Home Premium subscription (Google Home app Activity (opens in a new tab)).
The companion page option: a voice device
On the local-first path, spoken commands can stay in your home with the local voice options, or you can use the maker's paid cloud voices (Set up a fully local voice assistant (opens in a new tab)). A voice satellite sends sound to the hub, which listens for the wake word; an Android phone listens on the phone (The Home Assistant approach to wake words (opens in a new tab)). You can also type to the assistant and never speak (Starting Assist from your dashboard (opens in a new tab)).
Setting up a voice device, step by step. Nabu Casa, which makes the Green, gives these steps for its own voice device, the Home Assistant Voice Preview Edition. It is named as an example, not an endorsement, and nobody has set one up for the book. You need a USB-C cable and a USB power supply (neither is in the box), your hub updated to its latest version, a user with Administrator rights, and the password for your 2.4 GHz Wi-Fi. The easiest way is the Home Assistant phone app, with Bluetooth on and the app allowed to use it.
- Plug the device in. A warm white twinkle shows it is ready. If it was used with another hub before, reset it first.
- Open the Home Assistant app on your phone.
- Go to Settings, Devices and services. Under Discovered, find the device, then choose Add and Submit.
- Enter the name and password of your 2.4 GHz Wi-Fi.
- When asked, press the centre button on the device, to show it's you.
- Under Discovered, add the Home Assistant Voice device and choose Submit.
- Follow the steps on screen. If you're not signed in to the paid cloud service, it asks what hardware to use. Choosing Do it yourself, then Setup with apps, installs speech programs on the hub; then add the Whisper and Piper integrations under Discovered. The maker doesn't recommend this choice on lower-power hardware, because speech can be slow.
Then try a command such as "What's the time", using room names exactly as your hub has them. If a device doesn't answer, check that it is on the Expose list. Source: Getting started with Home Assistant Voice Preview Edition (opens in a new tab) (page showed "Last updated: 9 months ago"). Checked on 14 November 2026.
Checked on: 8 November 2026, and 14 November 2026 for Amazon's page and the voice device steps.
From the book
The assistant can only act on what is in its view, so look at the list again whenever you add a device.