I created an automation using rest http calls , documented in Yamaha advanced api doc.
To group two speakers it takes few http calls, so it is easy enough to do.
Example or rest calls - part of configuration.yaml:
That is all, i have speakers linked.
The ip adress can change if dhcp is used - it is better to have the ip static for the speakers.
GroupId is whathever, as long as it is the same in both rest calls.
With the above, can you control individual volumes for each zone? Say if I have ‘Kitchen’ as the master, and link ‘bedroom’, you still only get volume control for Kitchen. Could you include a volume control for each zone linked to the master zone?
Actually I was also having issue with volume sync not working, the code just needed slight tweaking from above. The sync_volume: true needed to be under speaker_group:. Here is my working code.
After countless hours messing with this, I can confirm that this solution is working for the official MusicCast integration using platform: media_player.
I noticed that if I add the sync volume= true after the speaker group, my main source volume didn’t work on the card. Could you please check yours. Please let me know.
Hi. I have sync volume = true enabled. If I change the grouped card’s volume, it is reflected in the individual main source card’s volume too, and vice versa. Hope that’s what you were asking.
I can confirm that in March 2024, this is all working. For any newbies visiting, like me, here is the summary:
Install Advanced SSH and Terminal
so that you can then install HACS
so that you can then install Mini Media Player
then create a card on the dashboard and paste some of the above codes into it, pay attention to the following:
a. rename the device id to those of your own
b. Musiccast integration in HACS is no longer present and is not needed. Musiccast is now baked into HA.
c. If you pasted codes from earlier in this thread, you would have trouble with the join service. You need to use the later codes users have posted, which use the media_player as “platform” instead of musiccast_yamaha or yamaha_mussicast.
Hope this summary at March 2024 helps some newbies.
@Jinster Thanks for this!! I started playing with this over a year ago and then gave up. My only question is, should I remove the existing HACS MusicCast integration and start over again?
I’ve linked my Patio System, Living Room System and Garage system. The question I have is, with this the way it’s coded currently, the Patio always has to be the master of the group. Is there any way at all to change this so I can choose the master source, and then based on that selection, have the nested group option change to reflect the other rooms being available. In other words, if I choose the Living Room as the master source for the group, then the linking option would show Patio and Garage. If I choose the Patio as the master source, then the group list would change to reflect that the Living Room and Garage are now the other rooms available to be linked. You can see that I’ve added the Patio in to the group so it reflects as being the “Master” (this was also necessary to have my RX-602 have it’s volume changed when I moved the master volume slider.
Made a few more changes and I’m really happy with the layout so far. I think in order to manage my groups, I am going to buy one more MusicCast Device (probably the WXC-50 preamplifier) and just make that the group master that doesn’t actually play out to any speakers. Then I can link each room to that master.