Configuration
September 3, 2026 · View on GitHub
You do all configuration through the Home Assistant config flow when you add the integration. There is no YAML.
Fields
| Field | Default | Description |
|---|---|---|
device_type | voice_assistant | Which OVOS capabilities to expose. |
name | n/a | Friendly name for the device in Home Assistant. |
host | n/a | HiveMind hub host (e.g. ws://192.168.1.10). |
access_key | n/a | HiveMind client access key. |
password | n/a | HiveMind client password. |
port | 5678 | HiveMind WebSocket port. |
site_id | unknown | OVOS site id. |
allow_self_signed | false | Accept a self-signed TLS certificate from the hub. |
Device types
device_type selects which platforms are set up for the device:
| Type | Description | Platforms |
|---|---|---|
agent | Text input/output only (e.g. an LLM-backed OVOS). | binary_sensor, button, switch |
media_player | Audio output (playback, volume, TTS). | the above + notify + media_player |
voice_assistant | Full device: agent + audio out + audio in (mic, VAD, wake word, STT). | the above + select + sensor |
Identity storage
The integration stores its HiveMind node identity under Home Assistant's
configuration directory (<config>/hivemind/<entry_id>/_identity.json),
created on first connection. This directory sits outside the
custom_components/ package directory, so the identity survives upgrades and
the integration never writes there at runtime.
The bus uses a fixed session id (default) so the hub does not assign a
random session per connection. hivemind-core only allows the default
session for admin clients. This is why you must provision the client with
--admin (see permissions).
← Setup · Home · Entities →