Troubleshooting Common Issues

Troubleshooting Common Issues

I have installed an app, Snips detects my wake word but doesn't reply me after my commands, why?

First and foremost, keep in mind that an app must have at least one action assigned to it to perform any response to voice input, please read that part of the Actions documentation.

Snips can only answer if:

For an overview of a complete app and how it handles scripts, you can check this tutorial made by a community member and if things are still unclear, feel free to read this other tutorial also made by a community member


Before anything else, please start with this step!

1) Check if packages are installed correctly with

dpkg -l | grep snips

2) Check if you have an audio configuration

cat /etc/asound.conf

It will output something close to this if you have the default audio configuration:

pcm.!default {
type asym
playback.pcm {
type plug
slave.pcm "hw:0,0"
capture.pcm {
type plug
slave.pcm "hw:1,0"

For more details about audio issues please check Troubleshooting Audio.

3) If you have another application using the audio, it could potentially block the access to the audio device.

Check the section More than one application using audio in the Troubleshooting Audio

4) Check if your assistant is installed correctly in the folder `/usr/share/snips/assistant/`` :

The folder should contain this:

|-- assistant.json
|-- custom_asr
| |-- a.snips
| |-- b.snips
| |-- config.json
| `-- w.snips
|-- custom_dialogue
| |-- sound
| | |-- config.json
| | |-- end_of_input.wav
| | |-- error.wav
| | `-- start_of_input.wav
| `-- speak
| |-- de.json
| |-- en.json
| `-- fr.json
|-- custom_hotword
| |-- config.json
| |-- model.pb
| `-- thresholds_curve.json
|-- dataset.json
`-- trained_assistant.json

5) Check that all services are active and running:

systemctl status 'snips-*'

To have a more concise output in the terminal you can use this instead:

systemctl status -n 0 'snips-*'

6) If a service is not running or continuously rebooting, then you can check its logs with:

journalctl -f -u <snips_service_name>

7) If the error is not clear from the output, stop the service and launch it manually. That way you will output more precise info to debug. Here an example with snips-asr service:

sudo systemctl stop snips-asr
snips-asr -vv

Don't forget to relaunch the service once you're done fixing it. You can do it by using:

sudo systemctl start snips-asr


apt-get fails

  • If server is down, try again later or use an alternative server address as the ones provided in the Installing Snips Platform section.

  • We could be updating the platform at this time, try again in a couple of minutes

apt-key fails

The gpg-key couldn't be downloaded when using the following command due to being down:

sudo apt-key adv --keyserver --recv-keys D4F50CDCA10A2849

You can try again later or try another server using or instead, e.g.:

sudo apt-key adv --keyserver --recv-keys D4F50CDCA10A2849


If you have an already working MQTT installation on the same device or on the network, you can point Snips to it by editing /etc/snips.toml [snips-common] section. Don't forget to relaunch the whole platform or the corresponding service when you finished editing the file.


Updating snips-platform can also trigger system packages update or update your local distribution. It can render other parts of your setup unstable, microphone mainly. Be advised.

We could also update the /etc/snips.toml format. During the apt update, the system will tell you about this.

Need more help?

Our Community and the Support team will be glad to help on our Forum. If you need professional services please contact our enterprise team using our contact form and speak to a Voice Specialist.