Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

After reboot again comes: [FATAL:audio_input_stream.cc(47)] Input device could not be opened: default Aborted #72

Open
vivian0239 opened this issue Aug 7, 2020 · 5 comments

Comments

@vivian0239
Copy link

I solved this issue before, assistant.py can run. But MMM still not working. So I reboot RP.
After that, I meet this again:
[FATAL:audio_input_stream.cc(47)] Input device could not be opened: default Aborted
This time the /home/pi/.asoundrc looks good.
I refer #63 use mouse and keyboard directly on RP to open folder manager, and found an extra
file named: packagelock.json, I delete this file, but still has the FATAL issue above.
I tested google assistant again, it works well. But I cannot run assistant.py and MMM.

@vivian0239
Copy link
Author

One thing strange I found there, the speaker icon is gray.

@vivian0239
Copy link
Author

No assistant.py works with this command: python3 -u assistant.py
but when I run MMM, it has error:
[ERROR] Error: Cannot find module 'pubnub'
I already installed pubnub. I don't know why I meet this?

@vivian0239
Copy link
Author

I enter MMM-GoogleAssistant again and npm install, after that MMM can run without error, but assistant.py report error: [FATAL:audio_input_stream.cc(47)] Input device could not be opened: default Aborted
It's weird!

@vivian0239
Copy link
Author

I checked after I run MMM, the assistant.py has run:
(env) pi@raspberrypi:~/MagicMirror/modules/MMM-GoogleAssistant/pi $ ps -aef | grep python
pi 1228 898 4 11:31 pts/0 00:00:51 python3 -u assistant.py
pi 1624 1282 0 11:51 pts/1 00:00:00 grep --color=auto python
but no voice output?

@vivian0239
Copy link
Author

I found the reason, because when I run MMM, assistant.py already run. And I run assistant.py again, mic was used by the first time, so nothing error. And finally MMM run(at the same time I run assistant.py???The first time assistant.py was run by MMM, and after I killed python, it cannot run automatically). The experience is bad. Most of time it cannot get what I said.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant