Custom integration for Home Assistant to support Yamaha AV receivers with the YNCA protocol (serial and network).
According to reports of users and info found on the internet the following AV receivers should be working, there are probably more, just give it a try. If your receiver works and is not in the list please post a message in the discussions so the list can be updated.
HTR-4065, HTR-4071, HTR-6064, RX-A660, RX-A700, RX-A710, RX-A720, RX-A740, RX-A750, RX-A800, RX-A810, RX-A820, RX-A840, RX-A850, RX-A1000, RX-A1010, RX-A1020, RX-A1030, RX-A1040, RX-A2000, RX-A2010, RX-A2020, RX-A2070, RX-A3000, RX-A3010, RX-A3020, RX-A3030, RX-A3070, RX-S600D, RX-V475, RX-V477, RX-V481D, RX-V483, RX-V671, RX-V673, RX-V675, RX-V677, RX-V771, RX-V773, RX-V775, RX-V777, RX-V867, RX-V871, RX-V1067, RX-V1071, RX-V2067, RX-V2071, RX-V3067, RX-V3071, TSR-700, TSR-7850
In case of issues or feature requests please submit an issue on Github
- Full UI support for adding devices
- Connect through serial, IP or any URL handler supported by PySerial
- Support for zones
- Power on/off
- Volume control and mute
- Source selection
- Soundmode selection
- Show metadata like artist, album, song (depends on source)
- Control playback (depends on source)
- Activate scenes
- Send remote control commands (experimental)
- Several controllable settings (if supported by receiver):
- CINEMA DSP 3D mode
- Adaptive DRC
- Compressed Music Enhancer
- HDMI Out enable/disable
- Initial volume
- Max volume
- Sleep timer
- Speaker bass/treble (default disabled)
- Headphone bass/treble (default disabled)
- Surround Decoder
- Pure Direct
-
Q: Entities unavailable when receiver in standby
The receiver does not allow changing of settings when it is in standby, so the entities become Unavailable in Home Assistant to indicate this. -
Q: Scene buttons are not created automatically
On newer receivers it is not possible to autodetect the amount of scenes supported by a zone, so no scenes are detected.Solution: You can specify the amount of scenes supported by each zone in the integration configuration.
-
Q: Scene buttons are not working
On the RX-V475 with firmware 1.34/2.06 the command to activate the scenes does not work even though scenes seem to be supported by the receiver. There might be more receivers with this issue, please report them.As a workaround try sending scene commands using the remote entity. Please drop a message in the discussions if this actually works as I don't have an RX-V475 to test with.
-
Q: Sources do not match receiver zone capabilities
For most receivers the total amount/type of inputs available on the receiver can be detected, but it is not possible to detect which of those inputs are available per zone.
Solution: Select the sources that are supported by the zone in the integration configuration. If a source is not listed at all it might not be supported or could be a bug, submit an issue in that case.
-
Q: Soundmodes do not match receiver
The list of suppoerted soundmodes can not be detected, for some models the list is known, for the rest the whole list of known soundmodes is shown.
Solution: Select the Soundmodes that are supported by your receiver in the integration configuration.
If you want your receiver added to the list of models with known soundmodes start a discussion or submit an issue
-
Q: How can I fix the connection settings if the connection is not working
When the integration can not connect to the receiver (e.g. due to changed IP address) you can use the "Configure" button on the integration card. A dialog will appear with a message that it can't connect. Press "Submit" in this dialog to mark the integration for reconfiguration. Home Assistant will now allow you to reconfigure the integration (reload of the page in the browser seems required to show the reconfigure card).
This is currently experimental because it is unknown how well this works on different types of receivers and it is a bit complicated to use (see wall of text below). Please post feedback in discussions
The remote control entity allows sending remote control codes and commands to the recevier. There is remote entity for each zone. Some remote commands are forwarded through HDMI-CEC and can be used to control other devices that way. I guess the commands are also sent over the remote out of the receiver, but that needs to be validated by someone that has equipment connected to the remote out port.
The current list of commands is below, but not all zones support all commands. For the list of supported commands for a specific entity check the "commands" attribute of the remote entity. Note that this command list does not take zone capabilities into account, just that there is a known remote control code for that command.
on, standby, receiver_power_toggle, source_power_toggle, info, scene_1, scene_2, scene_3, scene_4, on_screen, option, up, down, left, right, enter, return, display, top_menu, popup_menu, stop, pause, play, rewind, fast_forward, previous, next, 1, 2, 3, 4, 5, 6, 7, 8, 9, 0, +10, ent"
More remote control commands exist, but for now the commands included are the ones that are not available on the normal entities or that are potentially useful in other ways. E.g. sending scene_1
might be usable as a workaround for unsupported scene command on some receivers and commands like play
are forwarded over HDMI-CEC so it allows you to control devices that do not have an API otherwise. More can be added later if more use cases are discovered.
Next to sending the predefined commands it is possible to send IR codes directly in case you want to send something that is not in the commands list. The Yamaha IR commands are NEC commands and are 4, 6 or 8 characters long. E.g. the on
command for the main zone has code 7E81-7E81
. The separator is optional. Since each code is per zone it is possible to send a code through any entity, the separation of an entity per zone is done for the commands.
Sending the commands is done through the remote.send_command
service offered by Home Assistant. For manualy experimentation use the Developer Tools in Home Assistant. Select the device or entity and type the command or IR code you want send and call the service. The repeat, delay and hold options are not supported.
Example:
service: remote.send_command
data:
command: info
target:
entity_id: remote.rx_a810_main_remote
In case you want to have buttons on a dashboard to send the commands the code below can be used as a starting point. It uses only standard built-in Home Assistant cards, so should work everywhere.
On a dashboard add a "manual" card. Paste the code below and search and replace the entity name with your own.
Grid with buttons for remote control commands.
type: vertical-stack
cards:
- square: false
columns: 2
type: grid
cards:
- show_name: true
show_icon: false
type: button
name: 'ON'
tap_action:
action: call-service
service: remote.send_command
data:
command: 'on'
target:
entity_id: remote.rx_a810_main_remote
- type: button
show_icon: false
name: STANDBY
tap_action:
action: call-service
service: remote.send_command
data:
command: standby
target:
entity_id: remote.rx_a810_main_remote
- type: button
show_icon: false
name: RECEIVER POWER
tap_action:
action: call-service
service: remote.send_command
data:
command: receiver_power_toggle
target:
entity_id: remote.rx_a810_main_remote
- type: button
show_icon: false
name: SOURCE POWER
tap_action:
action: call-service
service: remote.send_command
data:
command: source_power_toggle
target:
entity_id: remote.rx_a810_main_remote
- square: true
columns: 4
type: grid
cards:
- type: button
show_icon: false
name: SCENE 1
tap_action:
action: call-service
service: remote.send_command
data:
command: scene_1
target:
entity_id: remote.rx_a810_main_remote
- type: button
show_icon: false
name: SCENE 2
tap_action:
action: call-service
service: remote.send_command
data:
command: scene_2
target:
entity_id: remote.rx_a810_main_remote
- type: button
show_icon: false
name: SCENE 3
tap_action:
action: call-service
service: remote.send_command
data:
command: scene_3
target:
entity_id: remote.rx_a810_main_remote
- type: button
show_icon: false
name: SCENE 4
tap_action:
action: call-service
service: remote.send_command
data:
command: scene_4
target:
entity_id: remote.rx_a810_main_remote
- square: false
columns: 3
type: grid
cards:
- type: button
show_icon: false
name: ON SCREEN
tap_action:
action: call-service
service: remote.send_command
data:
command: on_screen
target:
entity_id: remote.rx_a810_main_remote
- type: button
icon: mdi:arrow-up-bold
tap_action:
action: call-service
service: remote.send_command
data:
command: up
target:
entity_id: remote.rx_a810_main_remote
- type: button
show_icon: false
name: OPTION
tap_action:
action: call-service
service: remote.send_command
data:
command: option
target:
entity_id: remote.rx_a810_main_remote
- type: button
icon: mdi:arrow-left-bold
tap_action:
action: call-service
service: remote.send_command
data:
command: left
target:
entity_id: remote.rx_a810_main_remote
- type: button
show_icon: false
name: ENTER
tap_action:
action: call-service
service: remote.send_command
data:
command: enter
target:
entity_id: remote.rx_a810_main_remote
- type: button
icon: mdi:arrow-right-bold
tap_action:
action: call-service
service: remote.send_command
data:
command: right
target:
entity_id: remote.rx_a810_main_remote
- type: button
show_icon: false
name: RETURN
tap_action:
action: call-service
service: remote.send_command
data:
command: return
target:
entity_id: remote.rx_a810_main_remote
- type: button
icon: mdi:arrow-down-bold
tap_action:
action: call-service
service: remote.send_command
data:
command: down
target:
entity_id: remote.rx_a810_main_remote
- type: button
show_icon: false
name: DISPLAY
tap_action:
action: call-service
service: remote.send_command
data:
command: display
target:
entity_id: remote.rx_a810_main_remote
- square: false
columns: 2
type: grid
cards:
- show_name: true
show_icon: false
type: button
name: TOP MENU
tap_action:
action: call-service
service: remote.send_command
data:
command: top_menu
target:
entity_id: remote.rx_a810_main_remote
- type: button
show_icon: false
name: POPUP MENU
tap_action:
action: call-service
service: remote.send_command
data:
command: popup_menu
target:
entity_id: remote.rx_a810_main_remote
- square: false
columns: 4
type: grid
cards:
- type: button
show_icon: false
name: INFO
tap_action:
action: call-service
service: remote.send_command
data:
command: info
target:
entity_id: remote.rx_a810_main_remote
- type: button
icon: mdi:stop
tap_action:
action: call-service
service: remote.send_command
data:
command: stop
target:
entity_id: remote.rx_a810_main_remote
- type: button
icon: mdi:pause
tap_action:
action: call-service
service: remote.send_command
data:
command: pause
target:
entity_id: remote.rx_a810_main_remote
- type: button
icon: mdi:play
tap_action:
action: call-service
service: remote.send_command
data:
command: play
target:
entity_id: remote.rx_a810_main_remote
- type: button
icon: mdi:rewind
tap_action:
action: call-service
service: remote.send_command
data:
command: rewind
target:
entity_id: remote.rx_a810_main_remote
- type: button
icon: mdi:fast-forward
tap_action:
action: call-service
service: remote.send_command
data:
command: fast_forward
target:
entity_id: remote.rx_a810_main_remote
- type: button
icon: mdi:skip-backward
tap_action:
action: call-service
service: remote.send_command
data:
command: previous
target:
entity_id: remote.rx_a810_main_remote
- type: button
icon: mdi:skip-forward
tap_action:
action: call-service
service: remote.send_command
data:
command: next
target:
entity_id: remote.rx_a810_main_remote
- square: false
columns: 4
type: grid
cards:
- type: button
show_icon: false
name: '1'
tap_action:
action: call-service
service: remote.send_command
data:
command: '1'
target:
entity_id: remote.rx_a810_main_remote
- type: button
show_icon: false
name: '2'
tap_action:
action: call-service
service: remote.send_command
data:
command: '2'
target:
entity_id: remote.rx_a810_main_remote
- type: button
show_icon: false
name: '3'
tap_action:
action: call-service
service: remote.send_command
data:
command: '3'
target:
entity_id: remote.rx_a810_main_remote
- type: button
show_icon: false
name: '4'
tap_action:
action: call-service
service: remote.send_command
data:
command: '4'
target:
entity_id: remote.rx_a810_main_remote
- type: button
show_icon: false
name: '5'
tap_action:
action: call-service
service: remote.send_command
data:
command: '5'
target:
entity_id: remote.rx_a810_main_remote
- type: button
show_icon: false
name: '6'
tap_action:
action: call-service
service: remote.send_command
data:
command: '6'
target:
entity_id: remote.rx_a810_main_remote
- type: button
show_icon: false
name: '7'
tap_action:
action: call-service
service: remote.send_command
data:
command: '7'
target:
entity_id: remote.rx_a810_main_remote
- type: button
show_icon: false
name: '8'
tap_action:
action: call-service
service: remote.send_command
data:
command: '8'
target:
entity_id: remote.rx_a810_main_remote
- type: button
show_icon: false
name: '9'
tap_action:
action: call-service
service: remote.send_command
data:
command: '9'
target:
entity_id: remote.rx_a810_main_remote
- type: button
show_icon: false
name: '0'
tap_action:
action: call-service
service: remote.send_command
data:
command: '0'
target:
entity_id: remote.rx_a810_main_remote
- type: button
show_icon: false
name: '+10'
tap_action:
action: call-service
service: remote.send_command
data:
command: '+10'
target:
entity_id: remote.rx_a810_main_remote
- type: button
show_icon: false
name: ENT
tap_action:
action: call-service
service: remote.send_command
data:
command: ent
target:
entity_id: remote.rx_a810_main_remote
Recommended as you get notified of updates.
HACS is a 3rd party downloader for Home Assistant to easily install and update custom integrations made by the community. More information and installation instructions can be found on their site https://hacs.xyz/
- Add integration within HACS (use the + button and search for "YNCA")
- Restart Home Assistant
- Go to the Home Assistant integrations menu and press the Add button and search for "Yamaha (YNCA)". You might need to clear the browser cache for it to show up (e.g. reload with CTRL+F5).
- Install the custom component by downloading the zipfile from the release
- Extract the zip and copy the contents to the
custom_components
directory as usual. - Restart Home Assistant
- Go to the Home Assistant integrations menu and press the Add button and search for "Yamaha (YNCA)". You might need to clear the browser cache for it to show up (e.g. reload with CTRL+F5).