@quizzical & others: I did some testing with the mini-media-player and the official integration join/unjoin features. It seems to me that the card is working fine as it is. I only did some basic join/unjoin testing and didn’t test all the buttons, but at least the basic stuff is working already.
However, it is necessary to modify the card config parameter platform from heos to media_player. Then it seems to be working fine. I realized this when looking at the code of the card here.
I did some testing based on your example.
The grouping doesn’t work for me. I have not uninstalled the hack, but assume that should not have an influence.
I must also say my case seems less straightforward than yours. You seem to only have Heos devices. While I have a normal Heos1 in the bathroom but then I have a Denon AVR in the entertainment room that is controlling the speakers over there as well as in the kitchen (trough it’s zone1 output).
THe AVR has HEOS integrated but the Home assistant HEOS integration can only control it to a very limited extent. For many features I have to use the Denon AVR integration.
In any case the HEOS hack works fine for me for grouping so I guess I’ll continue using that for now.
I think you need to remove the custom integration for it to work, because when a custom integration is installed with the same domain as an official, the official will be disregarded. So the services won’t be available unless you remove the custom integration (to my understanding at least).
I have a similar configuration. 3x HEOS1 speakers and 1x HEOS3 speaker.
I’ve noticed the following difference in grouping with the official integration vs the custom one.
Whereas selecting additional speakers in the custom integration would add them to the Group, the official integration does not. Eg: The TV replaces the Kitchen speaker below rather than being added along with it:
Also, GROUP ALL behaves as expected, but UNGROUP does not.
Can anyone confirm this behavior, or am I doing something wrong?
You’re right, I get the same behavior on my system. I’m not sure if this is perhaps a problem in the card or if it is in the integration. Maybe this is what direx meant when he said the card neeeded some updates to support it. I will try to check this later.
I did some more testing, and I was able to tweak the mini-media-card to achieve what we want. I opened an issue on github, let’s see what the card owner thinks. Used your animation as illustration, hope thats ok.
Logger: homeassistant.components.heos
Source: components/heos/__init__.py:303
Integration: Denon HEOS (documentation, issues)
First occurred: 17:34:51 (42 occurrences)
Last logged: 17:54:26
Failed to group media_player.denon_avr_x2400h with ['media_player.heos_kuche']: System error -9 (12)
Failed to group media_player.kuche with ['media_player.heos_kuche', 'media_player.denon_avr_x2400h']: Processing previous command (13)
Failed to group media_player.kuche with ['media_player.heos_kuche']: Processing previous command (13)
Failed to group media_player.kuche with ['media_player.denon_avr_x2400h']: Command timed out
Failed to group media_player.kuche with ['media_player.heos_kuche', 'media_player.denon_avr_x2400h']: Command not executed (7)
In HEOS at least, the power off feature is not implemented. I believe the reasons is that you actually don’t power the HEOS units off, but merely stop then and they go into sleep mode by themselves. In my custom-integration I did add the power-off feature to do a stop just as a hack, but it is not in the official integration. I considered making a PR for it, but instead I changed the card config to something like this:
In my case this hides the power button, and shows a play/stop button which I use to stop See if that works for you too.
PS! I also have had some issues with the Processing previous command (13) error, and this seemed to be some hickup in my system so I rebooted my players and it solved my issue.
You shouldn’t name the master speaker also in the group list. So your Kuche speaker is the master, and the added group speaker is the living room speaker.
Are you sure about this @bjornb? I see that I have all speakers in the group list, including the main entity (or master) as well. It seems to be working fine in my case.
i am not quite sure if i totaly understand it right, but here is my analysis what i have to do (sorry when this isnt the right topic to put out the questions - then i will open up a new one):
As i tested out, i can switch on my denon zone 2 trough meda_player.turn_on and select an source (not quite sure what the source is called because in the gui i get printed out an “heos music” → is their an option to look that up?)
Now i thinking about using my own input_select that triggers states that turn on the right device and select the heos source.
Not quite sure how to let them join the devices then? media_player.join would be they way… that i understand but not quite sure how to create the right groups…
Hi! I did a PR to add/improve the handling of HEOS grouping for the mini-media-card, and card author kalkih released a new version today (v.1.16.0).
Note that platform must be changed to ‘heos’ again and not ‘media_player’. This may be changed later though, but was necessary to add some tweaks for HEOS different than for other devices in media_player domain.
Try it out and see if it works better, at least it did on my installation when I did the PR. Open an issue on the card github in case anything doesn’t work and I can assist kalkih to look at it.
Yes, I’ve been meaning to thank you! I’ve been using it in beta a couple days now and grouping seems to be working perfectly.
I’m curious to know what your experience has been with the media browser. I just upgraded to 2022.3 and was hoping to play around with the new features now I have access to a lot more media. But my speakers (3 x Heos1, 1 x Heos3) do not appear as options to play on. Is this expected? Are we likely to get this functionality with a future update in the media browser or HEOS integration?
Media Browser is not implemented for HEOS yet, but I have been playing around with it and have some extremely basic stuff working. My plan is to find some time to first add it and test it out on the custom integration, and then hopefully propose a PR to the official integration. Media browser has really got a lot of love lately, and I really liked the recent Radio Browser integration too. Currently I’m able to play favorites and some stuff, but I haven’t figure out Spotify yet, so it is really work in progress.
The mini media player card looks really crisp, but at least the grouping is working perfectly for now. I just made some different input booleans to group and ungroup speakers to different setups. Works like a charm.
Question to the developer, would it be possible to make an option for group volume? This is one of the features from the mini media player that I do miss. Thanks!
That’s great news, Tor. I’m excited to hear you are working on it. I was worried there was some inherent limitation in HEOS that made it impossible, so I’m relieved to know it will come eventually.
Currently I play my heos favorites (including radio stations), and spotify playlists using the lovelace interface (not the media browser) on a wall tablet. But I have to switch to the BubbleUPNP app to play the music on my DLNA server. Now that it all shows up in the media browser, I’m looking forward to ditching bubble and playing everything from the same interface.
Some good news: I noticed balloob made a PR on the official integration for Media Browser support. I’ve tested it and it works great, but right now it only supports local files and Radio Browser. I have it working for favorites with my tweak, but I’m having a hard time playing Spotify direct from the Media Browser. Not sure if it is supported by HEOS at all since even in the HEOS-app we need to open the Spotify-application. On the other hand, HEOS devices appears as spotify-connect devices in spotify, so it should be possible somehow.
See if that works for you too.