Ah I think these two lines should start with “options” rather than “option”.
Hoping that makes a difference 
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
Hello folks,
pinging @djl @KathyReid
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?)
[EDIT]: I think i figured how to solve the default situation according to this ancient bug:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/295832
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.
I’ve updated the Picroft documentation with a column for hardware status, added that problems are being reported for Jabra, and linked to this thread.
This is a challenge as we want to add details on devices that have been reported as working, however as ALSA and Pulse update things sometimes break.
Hopefully we can find a resolution for these problems as I know a number of people in the Community use this mic.
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.
1 Like
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)
So the mic is working but audio output is not? Is this for all audio eg the wake up beep and playing the news, or just the spoken responses?
If it’s all audio, then I’d first try setting the play commands, which can now be done with the following commands:
mycroft-config set play_wav_cmdline "aplay %1"
mycroft-config set play_mp3_cmdline "mpg123 %1"
I’d also double check in alsamixer that the playback device is selected and the volume is at a reasonable level.
1 Like
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.
I’m a total novice so have no idea what to do.
Hi Storm, when connected to the Picroft in PuTTY, can you try the two commands above, reboot the Pi and see if there’s any difference?
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
Hey gez, you fixed him! Thank you so much!!!
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!
1 Like
Hooray, that’s excellent to hear 
Maybe he was just finding his way to the stage 
1 Like
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. 
1 Like
By default we use paplay which is the Pulse Audio player where as aplay is the ALSA player.
Gez, sorry to resurrect this old thread, but I just built out a Picroft with the Jabra 410 Speak also.
I tried the mycroft-config lines that you listed in your post as well as checking the alsamixer to verify the 410 is showing up.
When I go to the mycroft-cli-client, I can say “hey jarvis” and in the log viewer, it shows that it is recording and states the time back but no audio is heard. I would think since 2019 that this would have been updated? I am currently running v21.2.0
Thanks in advance!
Stephen
Actually, I got him working!
What I was missing was this:
pactl set-default-source XXX
pactl set-default-sink XXX
Once I set the sink, he started talking.
1 Like
I recently acquired the Jabra 410 too and with stable image (Picroft_v20.08_2020-09-07.img.zip) all I had to do was change the commands to aplay %1 and mpg123 %1 and reboot. With unstable image (Picroft_v21.02.0_20210604.img.zip) it worked out of the box. All this is on raspberry pi 4.
edit: I spoke too soon, the speaker worked fine during the setup of unstable (which it didn’t on stable), but not afterwards - I still had to do pactl set-default-sink 0 (where 0 was jabra index from pacmd list-sinks) and restart mycroft
edit2: Speaker stopped working after reboot on unstable, to fix I had to edit audio_setup.sh like so:
pactl set-default-sink 0
pactl set-sink-volume 0 99%
pactl set-default-source 1
where again the 0 and 1 are the jabra sink / source numbers from pacmd list-sinks / pacmd list-sources. So not so much out-of-the-box, but at least the setup weorks better 
3 Likes