MusicCast
The Yamaha MusicCast integration allows you to control Yamaha MusicCast Receivers from Home Assistant.
Supported devices are listed on their site.
Configuration
Adding MusicCast to your Home Assistant instance can be done via the user interface, by using this My button:
MusicCast can be auto-discovered by Home Assistant. If an instance was found, it will be shown as “Discovered”, which you can select to set it up right away.
If there wasn’t any discovered automatically, don’t worry! You can set up a manual integration entry:
- Browse to your Home Assistant instance.
- In the sidebar click on Configuration.
- From the configuration menu select: Integrations.
- In the bottom right, click on the Add Integration button.
- From the list, search and select “MusicCast”.
- Follow the instruction on screen to complete the set up.
Grouping functionality
The Yamaha MusicCast integration implements the grouping services. There are some limitations in the MusicCast system for grouping:
- It is not possible to let mediaplayer entities of the same device (e.g., different zones) be in distinct groups.
- If a non-main zone is the master of a group, it is not possible to let other mediaplayers of the same device join this group.
Play Media functionality
The MusicCast integration supports the Home Assistant media browser for all streaming services, your device supports. For services such as Deezer, you have to log in using the official MusicCast app. In addition, local HTTP URLs can be played back using this service. This includes the Home Assistant text to text services.
It is also possible to recall NetUSB presets using the play media service. To do so “presets:<preset_num>” has to be used as media_content_id in the service call.
Examples:
This is an example service call that plays an audio file from a web server on the local network (like the Home Assistant built-in webserver):
service: media_player.play_media
target:
entity_id: media_player.sonos
data:
media_content_type: "music"
media_content_id: "http://192.168.188.18:8123/local/sound_files/doorbell-front.mp3"
This example call shows how to call netusb preset 1:
service: media_player.play_media
target:
entity_id: media_player.buro
data:
media_content_id: "presets:1"
media_content_type: "music"
Configuration/Diagnostic Entities
Depending on the features supported by the device, several entities will be added for every MusicCast Device. Some of the entities are related to the MusicCast device and some are related to a zone of the device. All device and main zone related entities will be assigned to the Home Assistant device of the main zone. Entities related to other zones will be assigned to the Home Assistant device of the corresponding zone.
Number Entities
The following entities will be added, if they are supported by the MusicCast device:
- Equalizer (configuration, zone level)
- One number entity each is added for high, mid and low
- Tone Control (configuration, zone level)
- One number entity each is added for bass and treble
- Dialogue Level (configuration, zone level)
- Set the volume of dialogues in relation to the general volume
- Dialogue Lift (configuration, zone level)
- Set the vertical position of the dialogues in the surround system
- DTS Dialogue Control (configuration, zone level)
- Control the volume of dialogues for DTS:X content
Troubleshooting
In this section known problems and their resolution are documented.
Errors on handling UDP messages
The Yamaha MusicCast integration is working with updates sent from the device to Home Assistant instead of pulling all information every few seconds. There is no error correction mechanism in these messages, so that only 100% correct messages can be processed. Whenever there is a corrupt message the Yamaha MusicCast integration will update all device information and log an error message like these:
Received invalid message: <message>Received non UTF-8 compliant message: b'<binary>'
If you receive these errors frequently, you should first try to disconnect your MusicCast devices from the power, wait 30 seconds and reconnect them to the power. If this does not help, you can try to use a LAN cable instead of WiFi to connect the device to the network.