Hello, My aim is to use mopidy with Peppymeter. So far: I successfully install mopidy and the mopidy iris client: Everything works as expected. I installed Peppymeter which rely on PeppyAlsa=ALSA plugin GitHub - project-owner/PeppyMeter.doc: PeppyMeter documentation Here is the asound.conf file…

Setting the system default device like that through /etc/around.conf should remove the need for explicitly defining alsasink device in Mopidy’s config. I’m not sure why it’s not working for you.

Yes indeed…and i tried multiple time (Live OS) That’s why i ask… It seems that mopidy do not read the asound configuration file, because if i make a typo, for instance [audio] output = alsasink device=peppyalsa1 with no peppyalsa1 device, then it is exactly the same… Therefore would it be possib…

Correct, Mopidy doesn’t read that file. Only ALSA does. That sink config is passed straight to gstreamer which uses it to talk to ALSA. I have a vague memory that you can’t use alsa names and it has to be actual alsa devices (listed in aplay -l) but I thought it gave an error if that was wrong, have…

Hi, Thanks for your interest. After starting mopidy, i ran: sudo systemctl status mopidy and didn’t see any error, not even a warning. Also, when i typed: aplay -L (Capital L) then peppyalsa was in the list. In fact it was the only device with is name only (others had a comment). Also, i for…

I said lower case in order to list ALSA devices. ALSA devices is normally what alsasink devices param expects. If it uses a fifo then perhaps the permissions are a problem when running Mopidy as a service. You could try to run Mopidy as your user but with the same config settings.

Hello, I reinstalled everything from a fresh Live system. Here is what i get: sudo systemctl status mopidy mopidy.service - Mopidy music server Loaded: loaded (/lib/systemd/system/mopidy.service; disabled; vendor preset: enabled) Active: active (running) since Tue 2025-05-13 09:38:25 …

[image] kingosticks: If it uses a fifo then perhaps the permissions are a problem when running Mopidy as a service. You could try to run Mopidy as your user but with the same config settings. See Everything is set up, but I hear nothing - #9 by FlorianReiterer

Hello, Thanks for your suggestion. Yes indeed, i do use fifo. I’m going to try to run as a user and not as a service. I’ll keep you post. To be more precise, here is the result of what i did this morning (see my previous post): It works with mpg123, but if i quit mpg123 and relaunch it, i might …

So good news:)) IT WORKS when i run Mopidy as a user. Well done and thanks a lot Kingosticks:)) Still i have two questions though: Does it mean that i should give up using Mopidy as service, or is there a workaround? As mentioned earlier, sometimes the alsa plugin stay active when i leave the app…

Just made a typo for one internet radio…and got the (same) error in Mopidy: WARNING 2025-05-13 15:28:22,997 [19905:Audio-2] mopidy.audio.actor Setting GStreamer state to GST_STATE_PLAYING failed ERROR 2025-05-13 15:28:22,998 [19905:MainThread] mopidy.audio.gst GStreamer error: Could not ope…

Peppymeter and mopidy

Help and support

kingosticks May 13, 2025, 12:30pm 8

See Everything is set up, but I hear nothing - #9 by FlorianReiterer

Topic		Replies	Views
<SOLVED> No sound w/ Mopidy running as a service Misc	8	11980	May 24, 2020
No sound with mopid-musicbox Help and support	7	255	April 9, 2024
Trouble setting up Mopidy on Raspberry Pi 4 Help and support	13	2001	April 9, 2021
Mopidy.audio.gst GStreamer error: Could not open audio device for playback Help and support	16	5953	December 23, 2020
[Solved] USB Dac Wont Play Through Mopidy But Works Everywhere Else Misc	10	10977	April 16, 2016

Peppymeter and mopidy

Related topics