You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
René Kliment edited this page Aug 21, 2019
·
5 revisions
Service status
If you encounter any problems, first check sudo systemctl status AlexaPi.service to see if your AlexaPi is running.
Logs
If your AlexaPi isn't running on startup you can check the log for errors.
If you're on systemd, run
sudo journalctl -u AlexaPi.service,
if you've stuck to the classic, run
sudo less /var/log/AlexaPi.log.
Debug mode
For better debugging, stop the AlexaPi service: sudo systemctl stop AlexaPi.service
and run AlexaPi interactively in debug mode: /opt/AlexaPi/src/main.py -d or python3 /opt/AlexaPi/src/main.py -d if you're on Debian/Raspbian to force Python 3
Always make sure that the service is stopped before you try to run AlexaPi interactively, because otherwise the service will be using your sound card and it won't work.
Notes
You can set various things in the configuration file.
If you installed into /opt as recommended, it is /etc/opt/AlexaPi/config.yaml.
If you installed elsewhere, the file config.yaml is in your AlexaPi/src directory.
If you hear the word hello multiple times and your AlexaPi doesn't work, it's because the service keeps crashing (for example due to a faulty config) and gets restarted because you chose this option in setup. Follow the instructions above to find and fix your problem.