Researched from current Home Assistant documentation on November 1, 2026. The walkthrough and example below are documentation-based; Tara has not tested them in a vehicle. The cover is an illustration, not a product-test photograph.
Start with the official app and a short list
Home Assistant CarPlay lets an iPhone put selected home controls on a compatible car display. Start with Quick access and two or three clearly named items. You do not need to move your devices into Apple Home to follow this setup.
You need a CarPlay-compatible vehicle or head unit, an iPhone, and the official Home Assistant app signed in to your server. The current requirements specify iOS 16.4 or later; Grid layouts need iOS 26, and in-car Assist needs iOS 26.4. This guide follows the current documented interface. If your installed app has older menus, compare its version with the documentation before following newer settings.
The phone supplies the connection to Home Assistant. An app icon on the car screen therefore does not prove that commands can reach your house. Set up and verify the following while safely parked. Android users should follow the separate Home Assistant Android Auto guide.
1. Prove the phone can reach home
Open Home Assistant on the iPhone and confirm you are using the intended server. For access away from home, use your existing secure remote connection. Home Assistant Cloud requires a paid subscription; a VPN (an encrypted private connection into your home network) is another route, but it must be connected before the phone can reach the server.
2. Make a harmless confirmation rehearsal
A helper is a software control inside Home Assistant. Create a fresh one that no automation uses; changing it will then operate no household equipment. An entity is one individual control or reading, such as that helper or a lamp.
- In Home Assistant, open Settings → Devices & services → Helpers → Create helper → Toggle. Name it Car rehearsal. Leave it disconnected from scripts and automations. Confirm it changes on and off from the phone. The Toggle helper documentation explains this software-only state.
- Before connecting to wireless CarPlay, briefly turn off the phone’s Wi-Fi and operate Car rehearsal over cellular. It should change state remotely. Restore Wi-Fi afterwards: wireless CarPlay needs Wi-Fi and Bluetooth enabled. If cellular access fails, use our remote-access walkthrough before continuing.
- On the iPhone, open Settings → Companion app → CarPlay. Under Quick access, select Add item, choose the entity option, then Car rehearsal and the correct server if asked.
- Open that item’s settings, enable Require confirmation, and save. Connect the iPhone to the car and open Home Assistant. These controls are described in the CarPlay configuration guide.
- With the helper off, select Car rehearsal and cancel the prompt. Expected result: it stays off. Select it again and confirm. Expected result: it becomes on. Check the helper from the phone too.
If either result differs, stop at this harmless control and use the troubleshooting table below. Do not substitute a door lock or garage opener to see whether the app works.
3. Decide what each button means
For a household button, name the intended result before choosing its type. “Entrance lights on” is easier to understand than “Arrival 2.” The distinction matters when someone taps twice or returns to a list showing an old state.
On a narrow screen, swipe the table sideways.
| What you want | Use | What to expect |
|---|---|---|
| Reverse a lamp’s present state | The light entity | CarPlay toggles it: on becomes off. |
| Set the same lighting every time | A scene | The saved target states are applied again. |
| Check a condition or run steps | A script | The script runs; put the required checks inside it. |
A scene is a saved set of target states. It has no lasting “active” mode to turn off; use another scene or the normal controls for a different result. A script is a sequence of actions and can include checks. Our scene-versus-script guide explains when to choose each. The CarPlay controls reference confirms which items toggle and which activate.
Worked example: an arrival list with clear outcomes
Imagine you want the porch and hallway lit when you arrive with groceries, while leaving the bedrooms alone. Use the following plan as a starting point, not as a claim about a tested Tara home.
| Button label | Targets | Repeat-tap result |
|---|---|---|
| Entrance lights on | A scene containing only the porch and hallway lights, both on | Requests those same on states again |
| Porch light off | A second scene containing only the porch light, off | Requests off again; leaves the hallway alone |
| Car rehearsal | The unconnected Toggle helper | Reverses the helper after confirmation; keep it for diagnosis or remove it later |
Build the first scene at home: go to Settings → Automations & scenes → Scenes → Create scene. Add only the two individual light entities and set them on. Save as Entrance lights on. Create Porch light off separately with only the porch light set off. Review each target list before adding the scenes to Quick access.
The editor changes real lights: a new scene opens in Live Edit, which applies changes immediately. Choose a time when those lights can be operated safely and tell anyone using the rooms. The scene editor documentation explains that saving switches to Review Mode and restores the earlier device states. Do not include locks, alarm controls, heaters or garage doors in this exercise.
Verify each scene from the phone while you can see the lamps. Entrance lights on should light only those two targets; a second activation should leave them on. Porch light off should leave the hallway unchanged. These are intended results to verify, not measured results from Tara. Another automation can still change a lamp afterwards: a scene does not reserve the device or pause other routines. See the scene behavior reference.
If you want lights only after dark, use a script with that check, rather than assuming an “arrival” label adds it. If you want automatic arrival instead of a deliberate button press, the next step is our distance-and-direction arrival guide.
4. Put confirmation in the right place
Require confirmation applies to Quick access and custom-tab items. Selecting a device through Areas or Control generally runs it immediately. Locks always request confirmation. For a cover such as a garage door, do not assume the same lock rule applies. These distinctions come from the official confirmation rules.
Keep the rehearsal and household buttons in the route you actually intend to use. You can hide the built-in Areas or Control tabs to reduce clutter. Hiding them is not a security boundary: a shorter menu does not restrict the account to those devices. Home Assistant separates view visibility from server permission checks. A non-admin login with hidden controls does not establish device-only authorization.
Keep physical door and garage controls available. A confirmation prompt does not check for a person, pet or obstruction, and does not replace the equipment’s safety features.
5. Diagnose the failed layer before changing anything
After a connection error or timeout, check the current device state before retrying. The original request may still execute later; repeating a toggle can reverse it. A fixed-target lighting scene avoids that particular reversal, but it does not guarantee delivery.
| What you see | First check | Useful result |
|---|---|---|
| No Home Assistant icon | Confirm the app is installed on the connected iPhone. Check iOS Settings → General → CarPlay → your car and its app list. | The app is available to open; no home devices need re-pairing. |
| Quick access is empty | Add Car rehearsal on the phone; verify the server. If already listed there, close and reopen the app. | The same practice item appears in the car. |
| One entity is missing | Check its supported type and whether it is hidden or categorized as diagnostic/configuration. Confirm the selected server. | You can distinguish a list-filter issue from a failed device. |
| The practice button fails on cellular too | Check remote access or the VPN from the phone. | The helper changes remotely before you repeat the parked-car test. |
| Practice works, but a light does not | Operate that light directly from the phone, then activate its scene. | You can separate the device connection from the scene’s target list. |
The official troubleshooting guide also provides a Force close app option that keeps the configuration. Reset configuration deletes your CarPlay setup; it is not the first diagnostic step.
Can I use Assist from CarPlay?
Yes, on supported versions. The current Assist instructions require iOS 26.4 or later and an Assist pipeline: speech recognition, a conversation agent, and spoken replies. Start by verifying a simple request on the phone. A local conversation setup does not remove the car’s need to reach your server, and cloud components remain cloud components.
Does CarPlay make my home work offline?
No. Away from home, the iPhone still needs a working route to the server. Whether a lamp itself depends on the cloud is a separate property of its connection to Home Assistant. For a useful handoff, plan local household routines and shared controls around clear names and ordinary physical controls as well as the app.