Local voice terminals need careful limits around smart locks
A cloud-dependent voice assistant setup has been replaced with a local voice setup running OpenClaw on a -based open hardware device called Hoorii Stage. Voice data stays inside the home network instead of being sent to outside servers. The device turns spoken commands into structured meanings and sends them directly to .
Because the hardware is open, it connected more easily to custom and template switches. The feels fast enough for a desktop voice terminal. The unresolved issue is how to protect high-risk devices, such as a garage door or smart locks, at the server level.
One option under consideration is a long-lasting, low-permission token in so the voice terminal cannot directly reach sensitive devices.
Key points
- The setup removes cloud voice assistants and keeps voice data inside the .
- Hoorii Stage and OpenClaw are used to send voice commands into .
- The open hardware made it easier to connect custom and template switches.
- Garage doors and smart locks should not be exposed directly to a voice terminal without limits.
- A low-permission token is one possible way to reduce what the voice terminal can access.