From 414806036a99830a9eabb097e7c04d412ef9ca24 Mon Sep 17 00:00:00 2001 From: Joshua Boniface Date: Fri, 6 Apr 2018 02:35:59 -0400 Subject: [PATCH] Replace GitLab link with GitHub repo --- 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 3f49409..9d8b0e5 100644 --- a/content/post/self-hosted-voice-control.md +++ b/content/post/self-hosted-voice-control.md @@ -73,7 +73,7 @@ One downside is, however, that the ReSpeaker technically supports directional au The LED portion of the ReSpeaker requires a little more work. The [examples library for the 4-mic hat](https://github.com/respeaker/4mics_hat) provides all the basic tools needed to get the LEDs working, including several samples based on Google and Amazon device patterns. In my case, I went for a very simple LED feedback design: the LEDs turn on blue while listening, then quickly turn either green on a successful command, or red on a failed command, giving some sort of user feedback without having to listen to the unit try and talk! -To do this, I created a simple Python "daemon" running under Systemd to listen for commands on a FIFO pipe and perform the required action, as well as a helper client utility to trigger the pipe. The code for these can be found [on my GitLab](https://dev.bonifacelabs.ca/joshua-automation/respeaker-led) for convenience. One interesting feature of this configuration is the Systemd unit file. It performs a git pull inside the service directory (e.g. the repo directory) to ensure the service is automatically up-to-date when the service is started. I do the same thing in my Kalliope unit file for its configuration. +To do this, I created a simple Python "daemon" running under Systemd to listen for commands on a FIFO pipe and perform the required action, as well as a helper client utility to trigger the pipe. The code for these can be found [on my GitHab](https://github.com/joshuaboniface/respeaker-led) for convenience. One interesting feature of this configuration is the Systemd unit file. It performs a git pull inside the service directory (e.g. the repo directory) to ensure the service is automatically up-to-date when the service is started. I do the same thing in my Kalliope unit file for its configuration. ### Kalliope configuration