From cca2af69c78e3907ca0876c5c3e9f41b4d7d357d Mon Sep 17 00:00:00 2001 From: Joshua Boniface Date: Tue, 13 Mar 2018 01:21:40 -0400 Subject: [PATCH] Add bit about using API for anything --- content/post/self-hosted-voice-control.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/post/self-hosted-voice-control.md b/content/post/self-hosted-voice-control.md index 8bd4295..1e30372 100644 --- a/content/post/self-hosted-voice-control.md +++ b/content/post/self-hosted-voice-control.md @@ -37,7 +37,7 @@ Assembly of the unit is very straightfoward. The ReSpeaker attaches to the main ## Software - Kalliope, ReSpeaker, and Raspbian -To start, this post doesn't document my HomeAssistant configuration - to do so would require its own post entirely! What is important for our purposes though is that my HomeAssistant interface is exposing multiple API endpoints, one for each room, that handle the various lighting events that happen there. +To start, this post doesn't document my HomeAssistant configuration - to do so would require its own post entirely! What is important for our purposes though is that my HomeAssistant interface is exposing multiple API endpoints, one for each room, that handle the various lighting events that happen there. You can use this method for communicating almost anything to HomeAssistant via voice control. For example, the following endpoint + data combination triggers a "lights-on" event for my bedroom: