Feedback

[mpass2345]

Hey team,

This is a great card and I really want to use it, but there are some key blockers that prevent me from adopting it. The main issue is the inability to hide functionality I don’t need.

In my setup, I have Music Assistant AirPlay entities. Some of these are AVRs with multiple zones (e.g. one AVR serves living, kitchen, and dining). That’s a single MA AirPlay source, but I also have three individual non‑AirPlay entities that must be used to control volume, power, and source. MA can’t see or control the AVR directly, so while the card is perfect for AirPlay playback, the majority of my setup can’t use Mediocre’s volume controls.

I can surface hardware controls with other media cards, but because Mediocre always shows volume/power, it creates confusion for other users in the house. Without the ability to hide those controls, Mediocre becomes unusable for me — which is a shame, because the search, browser, and multi‑player features are superb.

Queue visibility and management would also be a great addition, though I know others have already suggested this.

[antontanderup]

This sounds like a perfect opportunity to use universal media player to volume control working for those entities.
With universal media player you can combine multiple media players into one.
For example you can use you can specify which entity controls volume and power and which entity controls the rest.

[antontanderup]

https://github.com/antontanderup/mediocre-hass-media-player-cards/blob/main/docs/README_UMP.md
For a simple example in the bottom.
Homeassistant docs are ofc much more comprehensive.

[mpass2345]

Thanks for the response and I wasn't aware of UMPs until you sent this. However, I've spent many hours trying to make it wirk with UMPs now and they're just too unreliable in my set up to be of any use.
For now, I'll just keep using the mini media cards to control volume, power and source inputs, mass queue to view and manage the queue and the mediocre card to search and browse MA, display artwork and control playback. It is a super great card so thanks for your work on it.
In the furutre, for my set up as it stands, it'd be great if i could hide all volume controls in Mediocre.
Further ahead, I'd happily use mediocre as a standalone card if I could select one entity as the artwork and music control player and a second entity as the hardware (power, volume, source) entity. As well as view the music queue and have the ability to move tracks up/down or remove them.
Thank you!

[antontanderup]

Too bad its not really working for you as thats probably the exact reason UMP exists.
Feel free to post your UMP and card yaml. I can take a quick look if you'd like.

[mpass2345]

Thanks for the offer to help, however I removed my UMPs and I should have been more explicit with my issue. I'll also start by clarifying, I'm not qualified to be doing this - my entire set up is built off AI search, copy, paste, so I don't expect you to invest time in this for me.

I'm running MA with airplay players. I have 3 AVRs and 2 of them are running additional zones. My problem is getting those additional AVR zones (2&3) to surface volume controls in Mediocre wehn they're active. I tried many UMP set ups with various static and dynamic child settings, but noting seemed to make the active additional zones appear AND controllable when active.

My player set up is below so I'd really appreacite it if you could just let me know if you think it's possible or not. If you think it's possible, I'm happy to keep trying with AI.

The use case for me is my 'baddest amp airplay' player is often grouped with 'bad amp airplay'. These are playing on 'middle', 'kitchen' and 'garden'. This means 'Living' and 'Garage' volumes surface in Mediocre, but not the zones actually playing

    - media_player.baddest_amp_airplay is the airplay player for the avr with the follow zones
	'Living' zone
          - media_player.sc_lx901
	'Middle' zone
          - media_player.sc_lx901_zone_2
	'Kitchen' zone
          - media_player.sc_lx901_zone_3

    - media_player.bad_amp_airplay is the airplay player for the avr with the follow zones
	'Garage' zone
          - media_player.garage
	'Garden' zone
          - media_player.garden

    - media_player.bad_cave_amp_airplay is the airplay player for the avr with the follow zones
	'A+M Bedroom' zone
          - media_player.vsx_1131

    - media_player.archie_airplay is the airplay player for a single speaker with the follow zone
	'Archie' zone
          - media_player.archie

    - media_player.harriet_airplay is the airplay player for a single speaker with the follow zone
	'Harriet' zone
          - media_player.harriet

[antontanderup]

The simple ones are the ones with only one zone. Because you know that player X will always use player Y volume, you don't need any fancy dynamic stuff in the UMP config.

So for example for harriet:

media_player:
  - platform: universal
    name: Harriet
    unique_id: harriet_universal
    children:
      - media_player.harriet_airplay
      - media_player.harriet
    commands:
      volume_set:
        action: media_player.volume_set
        target:
          entity_id: media_player.harriet
        data:
          volume_level: "{{ volume_level }}"
    attributes:
      volume_level: media_player.harriet|volume_level

For the multi zone ones it's similar:

media_player:
  - platform: universal
    name: Bad Amp
    unique_id: bad_amp_universal
    children:
      - media_player.bad_amp_airplay
      - media_player.garden
      - media_player.garage
    commands:
      volume_set:
        action: media_player.volume_set
        target:
          entity_id: 
            - media_player.garden
            - media_player.garage
        data:
          volume_level: "{{ volume_level }}"
    attributes:
      volume_level: media_player.garden|volume_level

This should work. But test out the simple ones first.
The drawback to the multi zone ones is that you will set the volume of both zones to be identical so if 40% is not the same db level you'll probably be a bit bothered by this setup. You could mitigate this if you create a script to be used instead of the default volume action.