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

FieldDefaultDescription
device_typevoice_assistantWhich OVOS capabilities to expose.
namen/aFriendly name for the device in Home Assistant.
hostn/aHiveMind hub host (e.g. ws://192.168.1.10).
access_keyn/aHiveMind client access key.
passwordn/aHiveMind client password.
port5678HiveMind WebSocket port.
site_idunknownOVOS site id.
allow_self_signedfalseAccept a self-signed TLS certificate from the hub.

Device types

device_type selects which platforms are set up for the device:

TypeDescriptionPlatforms
agentText input/output only (e.g. an LLM-backed OVOS).binary_sensor, button, switch
media_playerAudio output (playback, volume, TTS).the above + notify + media_player
voice_assistantFull 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 →