Any documentation for this great solution

Some people might argue that this is not an issue, but it is a serious issue

There is not clear guidelines for beginners that shows us (beginners) how to do things?! And i believe that is why people don’t really know mopidy.

It lacks the steps, for me it is like, hey guys i made a car, who can drive it? Only very experts drivers, thus u don’t see it everywhere.

I want to use mopidy with YT Music and whole audio system. But really how, why the guidelines is somehow written assuming i know everything.

If i know everything, i wouldn’t come here, i would have built my own…

BTW. I am not sure why whenever someone says it is confusing the developers response qlways, i not sure how it is confusing?!!!

If more than one has said it, then it is a fact, people are not able to use your great work.

Please appreciate people have all kinds of different levels of experience. It is hard to write documentation at the correct level. If too basic, people get bored and stop reading. If too complex, it doesn’t help many people and alienates others. It’s also REALLY time consuming to write. We’ve done our best but recognise what we have won’t be enough for everyone. We always ask for people to suggest improvements because they are better placed to identify them, some people do this and it is much appreciated. We are very happy to merge these contributions.

The best thing we can do is for you ask whatever questions you have and kind people here will donate their time to help you. If you want. you can then make concrete documentation suggestions which we can add for others to benefit from. What might be really helpful for others, was if you could write up everything you find helpful. If you want, I can then spend my time reviewing that content and we can post it as a “guest post” on our blog.

BTW. I am not sure why whenever someone says it is confusing the developers response qlways, i not sure how it is confusing?!!!

Because what is there already makes sense to the person writing it. We can’t know what stuff people need us to tell them. And the need is different for each person. If you can’t understand this I don’t think we can help each other.


now, i follow the instructions (which honestly, need updates) till i reached
sudo apt install mopidy-mpd

when i try to excuse
sudo python3 -m pip install …
i get the following error (which is the same error i got a year ago and no answer at that time)
/usr/bin/python3: No module named pip

Please elaborate.

That’s a helpful point. You need to have pip installed to use pip. I find that obvious because I know it’s a third-party Python module but I can appreciate someone less familiar with Python wouldn’t know that. Do

sudo apt install python3-pip

What are you trying to install with pip? A Mopidy web client?

Docs improvement at docs: how to install pip from apt · mopidy/mopidy@6f7b93e · GitHub

1 Like

Let me give you my plan and you help me with the steps i need to follow (btw. I am working on documenting my steps so this can be used by all.

I would mopidy to be as a whole audio system thru several Pi4s available ( each pi can play the same song or different).

I would like it to work with YouTube Music, i believe there extension for it?

I would like to be able to cast to it from my Android device, not sure if this is doable?

Lastly, i would like to integrate it with HA

BTW. I am really bad at coding, so your patience.

As far as i understand, i think i need
Then mpd
Then snapcast
Then ytmusic

But i qm not sure how l, btw… Seriously I was trying by myself for a year now

OK, well keep in mind you are jumping straight to an advanced setup here.

There is Mopidy-YouTube. I don’t use it. I don’t know the current state but there’s an active maintainer who responds to Github issues and also on here.

This is not possible. Google Cast is closed-source and I’m not aware of any usable library for it. Thanks Google!

Presumably you’ve seen How to set up a full house audio system with X streams and Y speakers ?

You should get this working in stages:

  • Install Mopidy and Mopidy-MPD (from apt)
  • Install Mopidy-youtube (from pip for the latest version, I think…)
  • Install Iris webclient for Mopidy (from pip)
  • Get local playback working
  • Install and configure snapcast. They have great documentation.
  • Get remote snapcast playback working
  • Repeat for each system
  • Install and configure HA for the multi-room aspect. I have no experience using HA but others on here do.

I don’t think you need to install mpd for what you want.

Assuming you mean Home Assistant, you’ll probably need MPD to talk to it.

To be clear, Mopidy-MPD is sufficient.

Ah, yeah. Sorry. That’s what I meant. You don’t need to install as a separate application, in addition to Mopidy.

i will try this, i will be working in two direction, just to see the basic installation i think i would need

  • Install Mopidy and Mopidy-MPD (from apt)
  • Install Iris webclient for Mopidy (from pip)
  • Get local playback working

in addition, i will work on the advance level :slight_smile:

quick question, will this work with HiFiberry DAC or only 3.5 jack/ hdmi?

It’ll work with any soundcard supported by your system. But you will need to ensure each piece of software uses the correct soundcard.

  • The easiest way is to disable all other soundcards (i.e. disable onboard audio) so you only have one soundcard and it’s impossible for a program to use the wrong one!
  • Another way is to specify a particular system-wide default soundcard in your /etc/asound.conf file. it can be fiddily to get the ALSA syntax/naming correct.
  • Or you can specify which soundcard to use for each program. You’ll have to find the correct syntax for each program and make changes in multiple places - a bit annoying.

Anothering thing to note is that last time I checked (a while ago), The full GUI and Lite versions of Raspberry Pi OS used different audio subsystems. The GUI version uses Pulseaudio and is a little more tricky to setup for use with things like Mopidy. If you don’t want a GUI, use the Lite version.