Yamaha (YNCA)
mvdwetering/yamaha_ynca · vv9.7.0
Custom integration for Home Assistant to support Yamaha AV receivers with the YNCA protocol (serial and network).
In Apple Home through HomeKit Bridge
What HomeKit Bridge makes of each kind of entity this integration creates, read from its source code. A device only gets the ones that apply to it.
| Entity | Shows up as | Note |
|---|---|---|
switch | Switch or outlet | |
media_player | TV, receiver or media switches | Needs its own HomeKit Bridge in accessory mode |
remote | TV remote (activities) | Needs its own HomeKit Bridge in accessory mode |
sensor | Sensor (temperature, humidity, air quality…) | |
button | Button (as a switch) | |
select | Mode picker (as switches) |
What people report
Yamaha receivers that speak the YNCA protocol work locally, including newer ones like the TSR-700 after a maintainer fix. MusicCast-only soundbars may not expose the YNCA port.
- Works3
- Not working1
| Device | In Home Assistant | In Apple Home | What they said | Source |
|---|---|---|---|---|
| Yamaha RX-A1030 | Works Local | Sound program remote codes tested through YNCASaved copy… adds remote codes to control the sound programs on the receiver. Codes were sourced from https://www.avsforum.com/attachments/9348 and tested on my RX-A1030 through ynca directly and through this integration. My motivation for this is that as of the current beta firmware of the Unfolded Circle Remote 3, the Home Assistant integration does not support select entities, which is how the surround decoder is exposed. It looks like this will be changing in the somewhat near future, so no worries if this change is rejected due to the functionality being exposed by other means. ## Summary by … Excerpt saved from GitHub on 2026-10-23. | PR #512 · 2026-01 | |
| Yamaha RX-V685 | Works Local | Connects fine over YNCASaved copy… this is the _only_ application connecting to the receiver with the YNCA protocol. I have made sure there is nothing else connected. I also have an RX-V685 and that works fine. Both the Bar 400 and the RXV-685 work with the same Yamaha apps (AV Controller and MuscCast Controller), so I thought the bar should work. The bar also responds to the web API requests as shown below (exactly the same as the RX-V685) `http://x.x.x.x/YamahaExtendedControl/v1/system/getDeviceInfo` [code] Any suggestions on whether the above means this should work and / or what else I can try or any further infor Excerpt saved from GitHub on 2026-10-23. | Discussion #360 · 2024-12 | |
| Yamaha TSR-700 | Works Local | Supported from v4.3.0; zone names are generic and can be renamedSaved copy… extract from the logs after enabling logger for the component. ``` 2022-07-15 16:55:15 DEBUG (Thread-4 (_send_handler)) [ynca.connection] @SYS:MODELNAME=TSR-700 2022-07-15 16:55:46 DEBUG (Thread-4 (_send_handler)) [ynca.connection] @SYS:MODELNAME=TSR-700 2022-07-15 16:56:16 DEBUG (Thread-4 (_send_handler)) [ynca.connection] @SYS:MODELNAME=TSR-700 2022-07-15 16:56:46 DEBUG (Thread-4 (_send_handler)) [ynca.con Excerpt saved from GitHub on 2026-10-23. | Issue #8 · 2022-07 | |
| Yamaha MusicCast Bar 400 | Not working Local | Setup fails with connection error; YNCA port not accepting connectionsSaved copyI tried to get this working with a MusicCast Bar 400, but get the following error when trying to add the device > Failed to connect, check settings and make sure this is the _only_ application connecting to the receiver with the YNCA protocol. I have made sure there is nothing else connected. I also have an RX-V685 and that works fine. Both the Bar 400 and the RXV-685 work with the same Yamaha apps (AV Controller and MuscCast Controller), so I thought the bar should work. The bar also responds to the web API requests as shown below (exactly the same as the RX-V685) … Excerpt saved from GitHub on 2026-10-23. | Discussion #360 · 2024-12 |
Gathered from GitHub issues, pull requests, discussions and docs, and from r/homeassistant. These are individual reports, so check the linked thread and the date before you buy.
How it connects
Local push
Talks to the device on your network, and the device tells Home Assistant the moment something changes.
Details
| Installs (analytics) | 1,060 (0.15%) |
|---|---|
| GitHub stars | 114 |
| Latest version | v9.7.0 (2026-10-04) |
| Set up in the UI | Yes |
| Maintainers | @mvdwetering |
| License | Apache-2.0 |
Devices listed in its README
- Year
- 2010
- 2011
- 2012
- 2013
- 2014
- 2015
- 2016
- 2017
- 2018
- 2020
Limitations from the README
- The receiver can only accept 1 connection for the YNCA protocol that this integration uses. This means that is not possible to connect to the same receiver from multiple Home Assistant instances at the same time. It is possible to have multiple Yamaha (YNCA) integration instances connecting to multiple different …
In ReReHome
Whatever HomeKit Bridge shares reaches Apple Home as normal HomeKit accessories behind your Home Assistant bridge, so ReReHome shows and controls them like any other.
Bridges get their own settings page listing the accessories behind them.
Sources
- Documentation: https://github.com/mvdwetering/yamaha_ynca
- Source code: https://github.com/mvdwetering/yamaha_ynca
- Issues: https://github.com/mvdwetering/yamaha_ynca/issues
- HACS: https://hacs.xyz
