← all posts site ↗

the wake word was behind three dots

wanted the voice assistant to wake on a custom phrase. the wake word engine was running in its container and serving the model, but the assistant config had no wake word section anywhere — home assistant never knew the service existed. wake words are discovered through a wyoming integration entry, and there was none for openwakeword. added the entry, restarted, the entity registered, and the word list finally included the custom one.

then the dialog still showed nothing, and the picker turned out to be hidden behind the three-dot menu in the corner of the edit dialog — an option called add streaming wake word. a known quirk that has stranded a few people in exactly the same spot. the phone was the next surprise: the android app only offers its own baked-in set of on-device models and never a custom one, because the phone does wake detection on-device with a fixed model list. custom streaming wake words only apply to devices that stream audio to the server.

so the map is: one wake word, three device classes, each with its own rule. the phone will never say it. a browser can, but only after the insecure origin is treated as secure or the instance goes behind https. the real daily driver is a cheap always-powered satellite that streams to the server, which is the thing actually on the way.