jasperproject / jasper-client

Client code for Jasper voice computing platform
MIT License
4.52k stars 1.01k forks source link

Many Issues with Jasper Installation #648

Open actuallytomato opened 6 years ago

actuallytomato commented 6 years ago

So recently I've been trying to install Jasper on my Raspberry Pi 2 B+, and I've encountered a series of errors. I'm using wit.ai as my stt, and using Svox as my tts. This is what I get when i run jasper.py or ./start.sh.

`***

actuallytomato commented 6 years ago

By the way, I installed this from scratch on Raspbian Stretch, the newest version of Raspbian, and I used this tutorial for the install: http://www.knight-of-pi.org/raspberry-pi-3-installing-jasper-with-wit-ai-for-voice-recognition/

DrLeot commented 6 years ago

Just installed JASPER from scratch like you from the official documentation facing with the same or similar issues. Will keep you up to date if I can find a solution.

paulmunns commented 6 years ago

Im in the same situation. I think the bad request has to do with the connection between Jasper and witai. I also get a authentication problem when i try to connect, but my access-token is 100% correct. Not sure if you need to write it down as 'YOURKEY' with the apostrophe. Will update if i find a solution.

paulmunns commented 6 years ago

Okey guys these are the steps that fixed my problem:

"1. Enter "cd /home/pi/jasper-client/client"

  1. Then enter "sudo nano tts.py"
  2. Go down to where it says "cmd = ['aplay', ' -D', 'plughw:1,0', str(filename)]"
  3. Change the part that says 'plughw:1,0' to 'plughw:0,0'
  4. Enter "sudo reboot"
  5. Start Jasper by typing "/home/pi/jasper-client/jasper.py""

This fixed all my issues. Been searching for days now but got it finally working. If you have questions, i will try to help.

DrLeot commented 6 years ago

Didn't try it. I formatted the disk and bought Echo :-P

deepaktri333 commented 6 years ago

./jasper/jasper.py


Now Getting Bad Request again and again.

G10DRAS commented 6 years ago

Run Jasper script with --debug flag and check the debug log for issue.