Skip to main content
Design custom voice AI Agents, extend them with Python-based Abilities, and deploy them to dedicated hardware — all from a single platform built for voice-first development.

What You Can Do

Custom Agents

Build Agents with unique personalities, voices, and behaviors tailored to your vision.

Custom Abilities

Extend your Agent with Python-based skills that unlock new capabilities.

Hardware Integration

Connect to LEDs, sensors, GPIO pins, and other devices for full hardware control.

Manage Your DevKit with the OpenHome DevKit App

Manage your DevKit, switch Agents, and configure everything from the OpenHome - Voice AI DevKit App.

Smart Home with Home Assistant

Install Home Assistant on your DevKit from the dashboard and control your smart home by voice.

Got an OpenHome DevKit?

Onboard your OpenHome DevKit with the OpenHome - Voice AI DevKit App on your iOS device.

Onboard OpenHome DevKit with OpenHome - Voice AI DevKit App

Quick setup using the OpenHome - Voice AI DevKit App on iOS. Requires iPhone running iOS 17.0 or later.
Don’t have an iOS device? You can onboard your OpenHome DevKit using the Terminal from your Mac, Linux, or Windows computer.

Onboard OpenHome DevKit via Terminal

Setup via command line using the OpenHome Client.

Don’t Have an OpenHome DevKit?

Apply to get your own OpenHome DevKit and start building voice AI experiences on dedicated hardware.

Apply for an OpenHome DevKit

Submit your application to get access to an OpenHome DevKit.
Don’t have an official OpenHome DevKit but have your own Raspberry Pi? You can flash OpenHome OS on it and explore the platform today.

Setup Raspberry Pi with OpenHome OS

Flash OpenHome OS on your own Raspberry Pi (Zero 2 W, Pi 4, or Pi 5).

Ran Into Trouble With Your DevKit?

If your DevKit is unresponsive, fails a firmware upgrade or factory reset, or can’t be recovered through the OpenHome - Voice AI DevKit App, reflashing OpenHome OS on the SD card restores the device to a clean working state.

Flash OpenHome OS on DevKit

Reflash your DevKit’s SD card with a fresh OpenHome OS image to recover from a broken or unresponsive state.

FAQ

Getting Started

You can manage everything from either of these surfaces:
  • Dashboard at app.openhome.com — full management for Agents, Abilities, settings, and linked accounts.
  • OpenHome - Voice AI DevKit App — manage your DevKit, switch Agents, and sync Abilities directly from your iOS device. See the DevKit App Overview.
Yes. The iOS DevKit App offers the fastest onboarding flow, but if you don’t have an iOS device you can onboard your DevKit from the Terminal on Mac, Linux, or Windows.
Yes. You can flash OpenHome OS on a Raspberry Pi Zero 2 W, Pi 4, or Pi 5 and use it as a development device.Note: interruption is not supported on custom Raspberry Pi hardware — the Agent cannot be interrupted while speaking or during music mode.See Setup OpenHome OS on Your Own Raspberry Pi for the full flow.
Yes. A DevKit runs one active Agent at a time, but you can create multiple Agents on your OpenHome account and switch between them.
  • From the Dashboard, set the active Agent for your DevKit under your Agent list.
  • From the DevKit App, open the Agents list and select the Agent you want to run on the DevKit.
See the DevKit App Overview for the in-app flow.

Troubleshooting

If you’re connecting the DevKit to a mobile hotspot or a modem’s Wi-Fi, make sure the network name (SSID) has no spaces and no special characters — use only letters and numbers. Names with spaces or special characters can prevent the DevKit from connecting. Rename the hotspot or Wi-Fi network accordingly, then connect the DevKit again.
Open the OpenHome - Voice AI DevKit App, go to the Wi-Fi section, and use the change button to switch your DevKit to the new network.If your DevKit is no longer reachable from the App, re-onboard it from scratch to point it at the new network:
Power-cycle the DevKit by unplugging it, waiting a few seconds, and powering it back on. Once it boots, retry the action from the OpenHome - Voice AI DevKit App:
  • Firmware upgrade — open the Firmware section and re-run the firmware update.
  • Factory reset — open the dashboard and tap Factory Reset again.
See the DevKit App Overview for where each control lives in the App.
You can reset your DevKit from the OpenHome - Voice AI DevKit App. Open the dashboard and tap Factory Reset — this erases all local settings and restores the DevKit to its original state.See the DevKit App Overview for the Factory Reset control and other DevKit options.
Changes made in the Dashboard or the DevKit App — including installing or uninstalling Abilities, updating configurations, or adding or removing an Agent — require an Agent restart to take effect if your DevKit is currently active. If the DevKit is offline when changes are made, it will pick them up automatically the next time it starts up.From the Dashboard:
  1. Open the Dashboard and go to OpenHome DevKit.
  2. Click Restart Agent.
From the DevKit App:
  1. Open the OpenHome - Voice AI DevKit App.
  2. Go to your DevKit dashboard and tap Restart Agent.
Once the Agent restarts, it picks up the latest configuration and installed Abilities.
First, check the following:
  • DevKit onboarding — confirm you have completed DevKit onboarding and an Agent is assigned to your DevKit. Without an active Agent, the DevKit has nothing to run. See Onboard OpenHome DevKit with the DevKit App or Onboard via Terminal.
  • Wi-Fi network — confirm your DevKit is connected to the same Wi-Fi network it was onboarded on. If the network has changed, open the OpenHome - Voice AI DevKit App, go to the Wi-Fi section, and point the DevKit at the correct network.
If both look correct, power-cycle the DevKit by unplugging it, waiting a few seconds, and powering it back on.
This is usually a wake word setting. If the wake word is enabled, the Agent only responds to utterances that include one of the configured wake words — any query without the wake word is ignored.To check and adjust:
  1. Open the Dashboard and go to Settings → Configuration, or open the DevKit App and go to Profile → Configuration.
  2. If Wake Word Mode is on, make sure you include the configured wake word in each request — for example, say “openhome, what’s the weather?” instead of “what’s the weather?”.
  3. If you prefer to speak without a wake word, toggle Wake Word Mode off and restart the Agent for the change to take effect.
See Wake Word & Sleep Interaction for the full guide on wake word configuration and sleep mode behavior.
Your DevKit only connects to the Wi-Fi network it was last onboarded on. If that network is no longer available — for example, you changed your router, rotated your Wi-Fi password, or moved to a new location — the DevKit will keep trying to reach the old network and fail.Open the OpenHome - Voice AI DevKit App, go to the Wi-Fi section, and use the change button to point your DevKit at the network you’re using now. You don’t need to remember the previous network credentials.If the App can’t reach the DevKit, re-onboard it from scratch:

See also