Closed claudioita closed 7 years ago
The serial portion of config.yaml is only used when you select serial as the platform. You should be using raspberrypi instead. So the application won't even look at that setting.
The initial settings of config.yaml can be found in /opt/AlexaPi/src/config.template.yaml so you can always look there for a way back to where you started.
As for the failure, the report has been shortened, so it's hard to tell what the error is. You might find more clues if you use the -l option as it suggests.
Meanwhile I'm suspecting that you don't have the audio devices configured correctly. If I'm right, try using the aplay -l
command to list what your output options are, and arecord -l
to list your input devices. Copy the best fit (probably the one that says plughw) into config.yaml under _inputdevice and _outputdevice.
For example I'd suggest output_device: 'plughw:CARD=USB,DEV=0'
based on what I see above.
See if that helps.
I'm having a similar issue but I don't seem to be able to save changes on the config.yaml file when I am editing it from the editor app from the RPI desktop. Seems like a permissions issue but I am signed in as 'pi'. Any suggestions for how I can successfully edit config.yaml?
I'm not so familiar with the RPi desktop, but you can edit it from the terminal.
Open a terminal, then use sudo nano /etc/opt/AlexaPi/config.yaml
.
This will edit it as root, with appropriate permissions.
Thanks, that worked. I thought I had done that before but I kept getting a new file opening like it wasn't there.
Pat
On May 17, 2017 12:18 AM, "Mason Stone" notifications@github.com wrote:
I'm not so familiar with the RPi desktop, but you can edit it from the terminal. Open a terminal, then use sudo nano /etc/opt/AlexaPi/config.yaml. This will edit it as root, with appropriate permissions.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/alexa-pi/AlexaPi/issues/229#issuecomment-301988138, or mute the thread https://github.com/notifications/unsubscribe-auth/AbWhFEqCYJjkP11NO98hwrw0Pj_0h4NQks5r6oMjgaJpZM4NTMCp .
If you solved your problem, can you close this issue please?
Emerick
Emerick, this was my first posting on github and I'm not sure how to close the issue. When I logged in to my account and clicked the 'issues' link, nothing came up. Can you assist?
Pat
On Tue, May 30, 2017 at 4:46 AM, Emerick Herve notifications@github.com wrote:
If you solved your problem, can you close this issue please?
Emerick
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/alexa-pi/AlexaPi/issues/229#issuecomment-304828013, or mute the thread https://github.com/notifications/unsubscribe-auth/AbWhFBGOWgrKnmPB3nXpKwsT0OFnPfpwks5r--VygaJpZM4NTMCp .
Hello, just go on the webpage of the issue (here) and click on Close Issue on the bottom of the page.
Emerick
Hello... My problem is. I say "Alexa" and she answer yes? But after this she not answer more... I execute systemctl status AlexaPi.service and i get error 403.
Any solution?
@guigobass https://github.com/alexa-pi/AlexaPi/issues/376 Here is the fix.
I receive this error
Your OS (including version) where you are running AlexaPi:
Python release (
python2 --version
):Description of problem: