The button card is invisible and sits on top of the media interface, so that when you click/tap it, it opens the interface with controls. Without it, nothing will happen.
i got this so far
card_mod:
style:
mxmp-player$ mxmp-player-header$ mxmp-progress$: |
.progress {
display: none !important;
visibility: hidden;
mxmp-player$: |
.artwork {
display: none;
}
.controls {
display: none;
mxmp-player-header {
background-color: transparant !important;
}
mxmp-player$ mxmp-player-controls$: |
mxmp-volume {
display: none;
}
However the background is white and i want it transparant.
Is it also possible to have the black text in white and the titel/artis in blue but neon light
if not, all text in blue neon?
You have the background-color in the wrong section, something like below should work:
card_mod:
style:
.: |
ha-card {
background-colour: transparent;
}
Example 19 should get you close to changing the text color.
i tried for this card mod
card_mod:
style:
mxmp-player$ mxmp-player-header$: |
.entity {
display: none;
}
.song {
font-color: rgb(107, 235, 243)
mxmp-player$ mxmp-player-header$ mxmp-progress$: |
.progress {
display: none !important;
visibility: hidden;
}
mxmp-player$: |
.artwork {
display: none;
}
.controls {
display: none;
}
mxmp-player$ mxmp-player-controls$: |
mxmp-volume {
display: none;
}
.: |
ha-card {
background: rgba(0, 0, 0, 0) !important;
}
Still only title is blue, rest of the info is not
Just found this card in it looks really nice. I am right now trying it out with my own integration for Samsung multi room speakers and works like a charm. Grouping and favorites.
I have idea for improvement. When adding the card to the dashboard it says āNo supported players foundā. So first I thought it might only support Sonos speakers, but I saw that others was useing with cast devices. I have several Google Home Minis, but still got the message. Then I finally found that I have to enter the domain for the speakers I want to show. Maybe this option should be moved to be the first option you see?
Then I have ea question. Is there a easy way to exclude all āfavoritesā except custom ones? I have radio browser integration and I donāt want it show up in favorites. I would actually like to exclude the media exposed by the speaker it self as well, and only have my custom favorites.
Good suggestions, can you please create requests on Github?
I have a WiiM Pro device that Iād like to use as a media player for notifications to my Amazon Echo connected speaker groups.
For example, the ability to use the WiiM Pro as a media output in an action for specific automation triggers to either play a sound or eventually repeat notification text.
Would this media player integration allow for that or can someone recommend the solution/integration I need?
No, you need to look at integrations and automations. This is āonlyā a card for dashboards.
Is there a way to hide the album?
It tried album and albumname, but it didnt vanish
I got this already but want to hide album as well
card_mod:
style:
mxmp-player$ mxmp-player-header$: |
.entity {
display: none;
}
.song {
display: none;
}
thx overlooked that ! Gracias.
Has anyone gotten Squeezebox (now Lyrion) favorites to work? Theyāve been recently added to HA-- they now show up under Mediaā>Favorites, but they donāt show up in the Maxi Media player favorites section.
Do they show up correctly on the normal default media player card? Not sure why it wouldnāt work tbh. If it doesnāt work with the normal media player card, raise an issue on GitHub and Iāll take a look.
edit: actually, I just installed Maxi, and it doesnāt show favs, but if you click on Browse Media, to pull up the normal media browser, then they work fine. So, the question is actually how does Maxi identify favorites. Thereās no special category for favorites in the media browser - theyāre just called āfavoritesā. If Maxi needs something specific to know what a favorite looks like, we can take a look.
Or,do favorites in Maxi require you to manually add them to the yaml? Never used it, but thatās what their doc seems to say.
Yep - looks like Favorites in Maxi have to be created manually in the cardās yaml I think from my short read - people here may know betterā¦
Edit. The easiest way to get the actual favorite media content id would be to look in the Lyrion UI for the favorite and copy it from there. Copying it from HA state as described in the Maxi player wonāt always work (.e.g if your favorite is a playlist, the HA state will show you the content of the playlist)
Ah, thatās too bad. The closely-related āSonos Cardā pulls in the sonos favorites automatically so I had just assumed that this card would do the same since HA āknowsā what they are. Thanks for taking a look!
Now that Iām digging, I think this should be able to work the way I expected, without having to manually add every single favorite. According this issue, the card looks for favorites in two ways:
It is looking for favorites in two places:
- media_player/browse_media with content_id=favorites
- Link to Home Assistant docs: Media player entity | Home Assistant Developer Docs)
- Link to where itās used in the card: https://github.com/punxaphil/maxi-media-player/blob/a9fcba2384187a0f318aead73066515a50c136da/src/services/media-browse-service.ts#L36
.- on the attribute āsource_listā on the player entity
- Link to where itās used in the card: https://github.com/punxaphil/maxi-media-player/blob/a9fcba2384187a0f318aead73066515a50c136da/src/services/media-browse-service.ts#L49
So the question is, why arenāt the Squeezebox/Lyrion favorites being picked up automatically?
Edit: I submitted an issue on Github.
Those links donāt work for me to the repo - 404. Could you repost them and Iāll take a look. Simple answer as to why it doesnāt work is that thereās no standard way of implementing favorites, or any other browsed media. As you linked to in the developer docs, thereās just a mechanism for building a hierarchical set of lists of media. Favorites is just the name weāve given to one of them - theyāre not really special in anyway and thereās nothing that says favorites should have a content_id or type of favorites.
Likely the same reason that spotify doesnāt work in that issue - sonos just happens to do it in one way which isnāt the same as others since thereās actually no standard way of doing it.
Actually, donāt worry. I found the code, Iāll take a look, but not holding my breath right now.
No, thatās one of my PRs - doesnāt affect this one. This one Add support for Apps and Radios to Squeezebox Media Browser by peteS-UK Ā· Pull Request #134142 Ā· home-assistant/core (also mine) adds support for Apps and Radios to the media browser, but also wonāt affect this. Whilst I can take a look at this, I wonāt be submitting any new PRs ATM until we get some approved - we have 9 PRs waiting at the moment and itās getting too difficult to add anything new on top of all of the pending changesā¦
OK - Iāll answer on the github issue, but I donāt think thereās anything we can do on the squeezebox size. maxi currently looks for items with media_content_type=āfavoritesā. We donāt do that. For us, favorites can have different content types - e.g. media or playlists are the obvious ones, but thereās also some internal squeezebox types they could be. So, we need the type of item which is a favorite, rather than it just being a favorite. Iāll have a think if thereās a way to identify them which the maxi team might use - I think the current approach is derived from the way sonos does it.