Thank you for your donation!


Cloudsmith graciously provides open-source package management and distribution for our project.


Problem: Controlling volume Moode Sender via MPD (Multiroom)
#11
(01-20-2024, 07:13 PM)Nutul Wrote:
(01-20-2024, 06:42 PM)ubergoober Wrote:
(01-20-2024, 03:36 PM)Tim Curtis Wrote: The best way to help is to provide information that can be used to understand:

1. The format of the commands that are sent to to moOde along with with a set of actual examples
2. What communication protocol is used (http, other) and what protocols are available

It's the only way to know whether or how a new command can be developed that can be used to control volume for a Multiroom setup.

Quoted from the Home Assistant MPD integration page:

"This platform works with Music Player Daemon and mopidy with Mopidy-MPD as used by Pi MusicBox. While all of these rely on the common MPD protocol, not all implementations support all features, especially with regard to album artwork, embedded artwork and volume control. The platform will fall back gracefully if support isn’t detected."

https://www.home-assistant.io/integrations/mpd/

They do warn that volume may not be suported in all cases.

From what I can read online this thing is meant to talk directly to MPD, it opens a session to it and sends it commands; so it doesn't talk with moOde at all.


Agreed.  More information on the MPD Protocol is here: https://mpd.readthedocs.io/en/latest/protocol.html

Which means HomeAssistant can see only the player at the IP address in the integration, and thereby controls only the volume of that one device.

I'd suggest to the Original Poster that they reference the HomeAssistant MPD integration page for an example script.  It's likely they can use a push button to trigger a script that will raise volume by x% and another to reduce volume by X% and place that on the same dashboard as their media player control.
Reply
#12
(01-20-2024, 08:05 PM)ubergoober Wrote:
(01-20-2024, 07:13 PM)Nutul Wrote:
(01-20-2024, 06:42 PM)ubergoober Wrote:
(01-20-2024, 03:36 PM)Tim Curtis Wrote: The best way to help is to provide information that can be used to understand:

1. The format of the commands that are sent to to moOde along with with a set of actual examples
2. What communication protocol is used (http, other) and what protocols are available

It's the only way to know whether or how a new command can be developed that can be used to control volume for a Multiroom setup.

Quoted from the Home Assistant MPD integration page:

"This platform works with Music Player Daemon and mopidy with Mopidy-MPD as used by Pi MusicBox. While all of these rely on the common MPD protocol, not all implementations support all features, especially with regard to album artwork, embedded artwork and volume control. The platform will fall back gracefully if support isn’t detected."

https://www.home-assistant.io/integrations/mpd/

They do warn that volume may not be suported in all cases.

From what I can read online this thing is meant to talk directly to MPD, it opens a session to it and sends it commands; so it doesn't talk with moOde at all.


Agreed.  More information on the MPD Protocol is here: https://mpd.readthedocs.io/en/latest/protocol.html

Which means HomeAssistant can see only the player at the IP address in the integration, and thereby controls only the volume of that one device.

I'd suggest to the Original Poster that they reference the HomeAssistant MPD integration page for an example script.  It's likely they can use a push button to trigger a script that will raise volume by x% and another to reduce volume by X% and place that on the same dashboard as their media player control.

I wonder if that thing has script-invoking capabilities. If yes, of course, this is going to be an easy cake to eat...
Reply
#13
Well, the existing MPD Automation plugin for Home Assistant could be hacked to add more capability (it's written in Python) or one could write a new moOde Autiomation plugin. Not something I'd bother doing with my own Home Assistant installation since I already have access to my moOde players directly from phones, tablet, laptop.

But, did you see that cool Button+ controller the OP mentioned? I gotta think of an application that makes it imperative for me to buy one of them! Trouble is, it would cost me as much as another DAC once I add up the costs of all the individual parts I'd want.

Regards,
Kent
Reply
#14
Button+ seems cool.

If HA is just sending MPD commands over port 6600 then it would indeed be necessary to modify or develop something to control moOde special features like Multiroom sender because thats outside of the MPD command set.

Maybe a dev will take an interest in this.
Enjoy the Music!
moodeaudio.org | Mastodon Feed | GitHub
Reply
#15
(01-20-2024, 07:13 PM)Nutul Wrote:
(01-20-2024, 06:42 PM)ubergoober Wrote:
(01-20-2024, 03:36 PM)Tim Curtis Wrote: The best way to help is to provide information that can be used to understand:

1. The format of the commands that are sent to to moOde along with with a set of actual examples
2. What communication protocol is used (http, other) and what protocols are available

It's the only way to know whether or how a new command can be developed that can be used to control volume for a Multiroom setup.

Quoted from the Home Assistant MPD integration page:

"This platform works with Music Player Daemon and mopidy with Mopidy-MPD as used by Pi MusicBox. While all of these rely on the common MPD protocol, not all implementations support all features, especially with regard to album artwork, embedded artwork and volume control. The platform will fall back gracefully if support isn’t detected."

https://www.home-assistant.io/integrations/mpd/

They do warn that volume may not be suported in all cases.

From what I can read online this thing is meant to talk directly to MPD, it opens a session to it and sends it commands; so it doesn't talk with moOde at all.

So it looks as if I should move to two separate moOde players, and control them Multi-room using Mopidy.

https://www.home-assistant.io/blog/2016/...-snapcast/

I'll further check this route.
Reply
#16
(01-20-2024, 10:10 PM)TheOldPresbyope Wrote: But, did you see that cool Button+ controller the OP mentioned? I gotta think of an application that makes it imperative for me to buy one of them! Trouble is, it would cost me as much as another DAC once I add up the costs of all the individual parts I'd want.

It is indeed a nice product, this is how it looked when it just arrived and we were adding the moOde player to the button+. It showed the content it is playing, I can select different radiostations, play/pause/stop the music and control the volume*. And of course much more, not related to audio.

[Image: 93jE8mw5xS7nv8SObq10Qvpq.jpg?f=user_large]
Reply
#17
(01-21-2024, 10:15 AM)voorstad Wrote: So it looks as if I should move to two separate moOde players, and control them Multi-room using Mopidy.

https://www.home-assistant.io/blog/2016/...-snapcast/

I'll further check this route.

TTYTT I have no idea how moOde controls the volume of the satellites in a multiroom environment; but if every satellite has its own volume, and it is usually regulated FROM the satellite itself, then yes, that's the way to go.
Although I am not sure whether moOde will be aware of the volume change applied directly to the underlying MPD, and not through its API / UI.
Reply


Forum Jump: