Self-host Wyoming openWakeWord with Levelrail
Local wake word detection over the Wyoming protocol for Home Assistant voice assistants, preloaded with the ok nabu model.
- Authorrhasspy
- LicenceApache-2.0
- Memory256 MiB
- Services1
How to self-host Wyoming openWakeWord
-
Pull the images
One image is pulled on your server.
Show images
rhasspy/wyoming-openwakeword:2.1.0
-
Create the app
One service starts in a single Compose app, on port 10400.
-
Fill in the secrets
You do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
After the first start
- Add the Wyoming integration in Home Assistant and point it at port 10400.
Wyoming openWakeWord requirements
- Memory
- About 256 MiB
- Architectures
- amd64 unknown, arm64 unknown
- Ports
- 10400
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- Apache-2.0, permissive license
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Wyoming openWakeWord. New to Levelrail? Install it on a fresh VPS first.
docker pull ghcr.io/glincker/levelrail:latest Then levelrail-cli login --device. See Getting started and the Wyoming openWakeWord docs page.
Deploy Wyoming openWakeWord your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Wyoming openWakeWord from the CLI
levelrail-cli templates deploy wyoming-openwakeword --name my-wyoming-openwakeword Deploy Wyoming openWakeWord with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/wyoming-openwakeword/deploy Wyoming openWakeWord configuration
Wyoming openWakeWord services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| wyoming-openwakeword | rhasspy/wyoming-openwakeword:2.1.0 | 10400 | none |
Wyoming openWakeWord environment variables
The catalog lists no environment variables for this template.
Ports and volumes
- Ports
- 10400
- Volumes
- none
Wyoming openWakeWord FAQ
How much memory does Wyoming openWakeWord need?
The catalog lists about 256 MiB of memory for Wyoming openWakeWord.
Does Wyoming openWakeWord run on arm64?
For Wyoming openWakeWord, arm64 support is not confirmed; amd64 is unknown.
What licence is Wyoming openWakeWord under?
Wyoming openWakeWord is licensed under Apache-2.0, which is permissive, with few conditions on reuse.
Does Wyoming openWakeWord need configuration before it starts?
No. The template fills in its own defaults.
Which ports does Wyoming openWakeWord use?
Wyoming openWakeWord listens on port 10400 inside the stack.
Can I deploy Wyoming openWakeWord on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for Wyoming openWakeWord, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image rhasspy/wyoming-openwakeword:2.1.0 is what you deploy there.