Sorry for the long time offline, I have been busy and will be busy for some time. My summer holidays are coming up so by then I will look at it again. Thanks in advance
I just wanted to put my 5 cents here. I spent the whole night yesterday trying to make Mycroft work with Jabra, and this thread has been invaluable, just like this random find:
I followed all the instructions and learnt a lot about pulseaudio and alsa in the process, but still can’t figure exactly out what’s wrong. So far Mycroft works, and the only differences with the approach mentioned above are:
Used the config from gist, renaming hw:1,0 into hw:0,0.
Replacing the /etc/asound.conf with the one from gist, with same changes.
Adding a “-D sysdefault” flag to the “play_wav_cmdline” parameter
I would love to know however what’s the reason why the default call to aplay %1 ends up producing no sound, as opposed to a -D sysdefault call (which I d guess supposed to be the same?)
the solution is to go into /usr/share/alsa/pulse-alsa.conf and replace the pcm.!default with your devices of choice (in my case):
pcm.jabra {
type hw
card 0
device 0
rate 48000
}
pcm.!default {
type asym
playback.pcm {
type plug
slave.pcm “jabra”
}
capture.pcm {
type plug
slave.pcm “hw:0,0”
}
}
I also cannot figure out still how to adjust the volume; I get the error:
amixer: Unable to find simple control 'PCM',0
It is surprising and frustrating at the same time that Jabra Speaker is mentioned on the front page, and yet causes so much btt-hurt. Imagine my frustration coming here after spending a previous weekend realizing that Bluetooth speaker / mic combo does not work well either…
I’m in the same boat, purchased a Jabra 410 because it was specifically listed as compatible. Spending a little over 4 hours this weekend attempting and failing to get it working isn’t really what I would describe as compatible. Please remove the Jabra 410 from the compatibility list since it clearly is not.
Thank you very much, I understand that finding a solution is difficult but than at least people should know about it. I am going to try again soon since there are new images out with Debian Buster and that could maybe help with the problems. If this not the case and after some trial and error someone can find a solution, it is not outdated as fast.
Okay, I have tried installing Mycroft again with the latest stable image. I haven’t got the speaker working yet but it is different now: in Mycroft, the microphone works fine but the answers don’t get throught. What is interesting is that the Alsa test (arecord -d 10 test.wav and then aplay test.wav) does work. Does this change the problem significantly? As far as I can see, at least in the audio log, there is nothing out of the ordinary except maybe:
Failed to load service. NameError(“no function ‘libvlc_new’”,)
P.S:
I have copied the log files over. The link to them is here (Google Drive)
I too am having the same problem with the Jabra 410 and Picroft.
The microphone works fine but the speaker does not. If I log into the Picroft using PuTTY, I can talk to MyCroft and read his responses through PuTTY but he doesn’t make any sound through the Jabra.
Hi gez, tried both commands and still nothing, am I doing it right?
When I tried the first command I copied it from above and right clicked in PuTTY and MyCroft said (wrote) something about there being no recording and he wanted me to tell him to make a recording by saying “start recording”, so I make a short recording, asked him to stop recording again and re-entered the command, I’m guessing he was supposed to try and play the recording but there was still no sound. It was the same thing with the second command, just silence while he did his thing.
Hey Storm, it sounds like you might have entered this into the Mycroft CLI?
I should have clarified that, we want to enter this into the shell, so you should see something like: pi@picroft:~$
If you’re in colored interface with log messages, utterances history etc, then hit Ctrl+C to exit that and get back to the shell. Once you have entered commands into the shell, you can reopen the CLI with the command: mycroft-cli-client
When he started working he scared the life out of me he was so loud, turns out he must be one of those Spinal Tap MyCrofts because he had his volume set to 11.
Really can’t thank you enough gez, I’ve been struggling with this off and on for longer than I’d care to admit and had given up and thrown him back into the drawer more than once, so I’m absolutely delighted he’s working now. Internet high five!
That did the trick
Thank you so much Gez! This afternoon I downloaded and installed the updated image to see if that made a difference. After I ran throught the setup again I thought that it didn’t work but these two lines did the trick. Can you maybe explain why this is? I am quite interested why these “magic lines” work.
