| Name | ynca JSON |
| Version |
5.19.0
JSON |
| download |
| home_page | None |
| Summary | Package to control Yamaha receivers that support the YNCA protocol. |
| upload_time | 2025-01-16 19:35:51 |
| maintainer | None |
| docs_url | None |
| author | None |
| requires_python | >=3.8 |
| license | MIT License Copyright (c) 2017 Michel van de Wetering Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. |
| keywords |
|
| VCS |
 |
| bugtrack_url |
|
| requirements |
No requirements were recorded.
|
| Travis-CI |
No Travis.
|
| coveralls test coverage |
|
# YNCA
Package to control Yamaha receivers that support the YNCA protocol.
>Note that only 1 YNCA connection to a receiver can be made at the time. This is a restriction on the receiver side, not this library.
>It is usually not a problem since the Yamaha AV Control App uses a different protocol which can be used at the same time, but something to be aware of when testing the library.
## Models
The list of working models below is based on reports from users and info found on the internet, because Yamaha does not mention in the manuals if a model supports the YNCA protocol that this integration uses.
Based on this information, receivers in the mentioned series from 2010 onwards are likely to work. So even if your model is not listed, just give it a try.
If your receiver works and is not in the list, please post a message in the [discussions](https://github.com/mvdwetering/yamaha_ynca/discussions) so it can be added.
| Series | Models |
| --- | --- |
| AVANTAGE | RX-A2A, RX-A4A, RX-A6A |
|| RX-A660 |
|| RX-A700, RX-A710, RX-A720, RX-A730, RX-A740, RX-A750 |
|| RX-A800, RX-A810, RX-A820, RX-A830, RX-A840, RX-A850, RX-A870 |
|| RX-A1000, RX-A1010, RX-A1020, RX-A1030, RX-A1040 |
|| RX-A2000, RX-A2010, RX-A2020, RX-A2030, RX-A2040, RX-A2070 |
|| RX-A3000, RX-A3010, RX-A3020, RX-A3030, RX-A3040, RX-A3050, RX-A3070, RX-A3080 |
| RX-V | RX-V4A |
|| RX-V475, RX-V477, RX-V481D, RX-V483 |
|| RX-V500D, RX-V573, RX-V575, RX-V585 |
|| RX-V671, RX-V673, RX-V675, RX-V677, RX-V679, RX-V681, RX-V685 |
|| RX-V771, RX-V773, RX-V775, RX-V777 |
|| RX-V867, RX-V871 |
|| RX-V1067, RX-V1071, RX-V1075, RX-V1077, RX-V1085 |
|| RX-V2067, RX-V2071, RX-V2075, RX-V2077 |
|| RX-V3067, RX-V3071, RX-V3075, RX-V3077 |
| HTR | HTR-4065, HTR-4066, HTR-4071, HTR-4072, HTR-6064 |
| TSR | TSR-700, TSR-7850 |
| Other | CX-A5000, R-N500, RX-S600D, RX-S601D |
## Installation
```bash
python3 -m pip install ynca
```
## Contents
The intended API to use is exposed from the toplevel package.
### Classes
#### YncaApi
This is the main class to interact with. The YncaApi class is exposing YNCA subunits and their functions as Python classes/datatypes and allows to connect to devices supporting that API. It keeps a cache which gets updated when values are received from the device so reading attributes is instant as it does not need to query the receiver.
#### YncaConnection
The YncaConnection class creates a basic connection with a YNCA receiver and allows to send/receive YNCA commands. It handles throttling as required by the protocol and informs of received values through a callback. The YncaApi class uses this under the hood.
Use this if all that is needed is a basic connection to a receiver.
#### YncaModelInfo
The YncaModelInfo class is information about features that a specific model supports.
It is technically not really related to the protocol, but since there seems to be no other repository with this info I decided to keep it here.
### Tools
#### YNCA Terminal
The YNCA Terminal provides an interactive terminal for manually sending YNCA commands. It is only intended for manual debugging.
It can be started with commands like below.
```
python3 -m ynca.terminal /dev/ttyUSB0
python3 -m ynca.terminal socket://192.168.178.21:50000
```
#### YNCA Server
This is a very basic YNCA server intended to be just enough for debugging and testing without connecting to a real device.
The server needs to be filled with data from an actual device and it will basically just repeat the same answers as the real device gave (with a few exceptions).
Filling the server can be done by providing it with YNCA logging of a real device, like the ones in the YCNA package repository or a log from your own device e.g. by running `example.py` with loglevel DEBUG (uncomment the line in the example code).
It has some additional commandline options for using different ports, binding to a specific host or testing disconnects
```
python3 -m ynca.server <ynca_repo>/logs/RX-A810.txt
python3 -m ynca.server --host localhost --port 12345 <ynca_repo>/logs/RX-A810.txt
python3 -m ynca.server --help
```
## Example usage
```python
# Create a YncaApi class by specifying the port on your receiver.
# Port could also be e.g. COM3 on Windows or any `serial_url` as supported by PySerial
# Like for example `socket://192.168.178.21:50000` for IP connection
receiver = YncaApi("/dev/tty1")
# Initializing takes a while (~10 seconds for a 2 zone receiver) since it communicates
# quite a lot with the actual device to determine its capabilities.
# Later calls to the subunits are fast.
# The attributes that are still None after initialization are not supported by the subunits
receiver.initialize()
# Every subunit has a dedicated attribute on the `YncaApi` class.
# The name of the attribute is the subunit id as used in YNCA.
# The returned subunit class can be used to communicate with the subunit
sys = receiver.sys
main = receiver.main
print(sys.modelname) # Print the modelname of the system
print(main.zonename) # Print the name of the main zone
# To get notifications when something changes register callback with the subunit
# Note that callbacks are called from a different thread and should not block.
def update_callback(function, value):
print(f"{function} changed to {value} on the MAIN subunit")
main.register_update_callback(update_callback)
# Examples to control a zone
main.pwr = Pwr.ON
main.mute = Mute.OFF
main.inp = Input.HDMI3
main.vol = -50.5
main.vol_up(2)
# When done call close for proper shutdown
receiver.close()
```
Raw data
{
"_id": null,
"home_page": null,
"name": "ynca",
"maintainer": null,
"docs_url": null,
"requires_python": ">=3.8",
"maintainer_email": null,
"keywords": null,
"author": null,
"author_email": "Michel van de Wetering <michel.van.de.wetering+ynca@gmail.com>",
"download_url": "https://files.pythonhosted.org/packages/b5/a0/a8b3caf74d233037adfeedd1261f648721033c5be83c4c131c5c163478c5/ynca-5.19.0.tar.gz",
"platform": null,
"description": "# YNCA\n\nPackage to control Yamaha receivers that support the YNCA protocol.\n\n>Note that only 1 YNCA connection to a receiver can be made at the time. This is a restriction on the receiver side, not this library.\n>It is usually not a problem since the Yamaha AV Control App uses a different protocol which can be used at the same time, but something to be aware of when testing the library.\n\n## Models\n\nThe list of working models below is based on reports from users and info found on the internet, because Yamaha does not mention in the manuals if a model supports the YNCA protocol that this integration uses. \n\nBased on this information, receivers in the mentioned series from 2010 onwards are likely to work. So even if your model is not listed, just give it a try. \n\nIf your receiver works and is not in the list, please post a message in the [discussions](https://github.com/mvdwetering/yamaha_ynca/discussions) so it can be added.\n\n| Series | Models |\n| --- | --- |\n| AVANTAGE | RX-A2A, RX-A4A, RX-A6A |\n|| RX-A660 |\n|| RX-A700, RX-A710, RX-A720, RX-A730, RX-A740, RX-A750 |\n|| RX-A800, RX-A810, RX-A820, RX-A830, RX-A840, RX-A850, RX-A870 |\n|| RX-A1000, RX-A1010, RX-A1020, RX-A1030, RX-A1040 |\n|| RX-A2000, RX-A2010, RX-A2020, RX-A2030, RX-A2040, RX-A2070 |\n|| RX-A3000, RX-A3010, RX-A3020, RX-A3030, RX-A3040, RX-A3050, RX-A3070, RX-A3080 |\n| RX-V | RX-V4A |\n|| RX-V475, RX-V477, RX-V481D, RX-V483 |\n|| RX-V500D, RX-V573, RX-V575, RX-V585 |\n|| RX-V671, RX-V673, RX-V675, RX-V677, RX-V679, RX-V681, RX-V685 |\n|| RX-V771, RX-V773, RX-V775, RX-V777 |\n|| RX-V867, RX-V871 |\n|| RX-V1067, RX-V1071, RX-V1075, RX-V1077, RX-V1085 |\n|| RX-V2067, RX-V2071, RX-V2075, RX-V2077 |\n|| RX-V3067, RX-V3071, RX-V3075, RX-V3077 |\n| HTR | HTR-4065, HTR-4066, HTR-4071, HTR-4072, HTR-6064 |\n| TSR | TSR-700, TSR-7850 |\n| Other | CX-A5000, R-N500, RX-S600D, RX-S601D |\n\n## Installation\n\n```bash\npython3 -m pip install ynca\n```\n\n## Contents\n\nThe intended API to use is exposed from the toplevel package.\n\n### Classes\n\n#### YncaApi\n\nThis is the main class to interact with. The YncaApi class is exposing YNCA subunits and their functions as Python classes/datatypes and allows to connect to devices supporting that API. It keeps a cache which gets updated when values are received from the device so reading attributes is instant as it does not need to query the receiver.\n\n#### YncaConnection\n\nThe YncaConnection class creates a basic connection with a YNCA receiver and allows to send/receive YNCA commands. It handles throttling as required by the protocol and informs of received values through a callback. The YncaApi class uses this under the hood.\n\nUse this if all that is needed is a basic connection to a receiver.\n\n#### YncaModelInfo\n\nThe YncaModelInfo class is information about features that a specific model supports.\nIt is technically not really related to the protocol, but since there seems to be no other repository with this info I decided to keep it here.\n\n### Tools\n\n#### YNCA Terminal\n\nThe YNCA Terminal provides an interactive terminal for manually sending YNCA commands. It is only intended for manual debugging.\nIt can be started with commands like below.\n\n```\npython3 -m ynca.terminal /dev/ttyUSB0\npython3 -m ynca.terminal socket://192.168.178.21:50000\n```\n\n#### YNCA Server\n\nThis is a very basic YNCA server intended to be just enough for debugging and testing without connecting to a real device.\n\nThe server needs to be filled with data from an actual device and it will basically just repeat the same answers as the real device gave (with a few exceptions).\nFilling the server can be done by providing it with YNCA logging of a real device, like the ones in the YCNA package repository or a log from your own device e.g. by running `example.py` with loglevel DEBUG (uncomment the line in the example code).\n\nIt has some additional commandline options for using different ports, binding to a specific host or testing disconnects\n\n```\npython3 -m ynca.server <ynca_repo>/logs/RX-A810.txt\npython3 -m ynca.server --host localhost --port 12345 <ynca_repo>/logs/RX-A810.txt\npython3 -m ynca.server --help\n```\n\n\n## Example usage\n\n```python\n# Create a YncaApi class by specifying the port on your receiver.\n# Port could also be e.g. COM3 on Windows or any `serial_url` as supported by PySerial\n# Like for example `socket://192.168.178.21:50000` for IP connection\nreceiver = YncaApi(\"/dev/tty1\")\n\n# Initializing takes a while (~10 seconds for a 2 zone receiver) since it communicates\n# quite a lot with the actual device to determine its capabilities.\n# Later calls to the subunits are fast.\n# The attributes that are still None after initialization are not supported by the subunits\nreceiver.initialize()\n\n# Every subunit has a dedicated attribute on the `YncaApi` class.\n# The name of the attribute is the subunit id as used in YNCA.\n# The returned subunit class can be used to communicate with the subunit\nsys = receiver.sys\nmain = receiver.main\n\nprint(sys.modelname) # Print the modelname of the system\nprint(main.zonename) # Print the name of the main zone\n\n# To get notifications when something changes register callback with the subunit\n# Note that callbacks are called from a different thread and should not block.\ndef update_callback(function, value):\n print(f\"{function} changed to {value} on the MAIN subunit\")\n\nmain.register_update_callback(update_callback)\n\n# Examples to control a zone\nmain.pwr = Pwr.ON\nmain.mute = Mute.OFF\nmain.inp = Input.HDMI3\nmain.vol = -50.5\nmain.vol_up(2)\n\n# When done call close for proper shutdown\nreceiver.close()\n```\n",
"bugtrack_url": null,
"license": "MIT License Copyright (c) 2017 Michel van de Wetering Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the \"Software\"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.",
"summary": "Package to control Yamaha receivers that support the YNCA protocol.",
"version": "5.19.0",
"project_urls": {
"Homepage": "https://github.com/mvdwetering/ynca"
},
"split_keywords": [],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "9b66cada8d6cc3443349047bda14d7a3f2efb3b0b4471cd2ecbcc7edd9e0e78a",
"md5": "432e79387622b6ce3ff87d479dd74763",
"sha256": "6d21f5d970553d556665e558bfdfcf013e002c238cff3d83a6d1b9171f7f2177"
},
"downloads": -1,
"filename": "ynca-5.19.0-py3-none-any.whl",
"has_sig": false,
"md5_digest": "432e79387622b6ce3ff87d479dd74763",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.8",
"size": 38667,
"upload_time": "2025-01-16T19:35:48",
"upload_time_iso_8601": "2025-01-16T19:35:48.788700Z",
"url": "https://files.pythonhosted.org/packages/9b/66/cada8d6cc3443349047bda14d7a3f2efb3b0b4471cd2ecbcc7edd9e0e78a/ynca-5.19.0-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": "",
"digests": {
"blake2b_256": "b5a0a8b3caf74d233037adfeedd1261f648721033c5be83c4c131c5c163478c5",
"md5": "79fd5cab8da127705529e5d71737e8dd",
"sha256": "484fd2799de09770a88337cd8af5455c78bddfe4cce6bedc5229fe54482d980c"
},
"downloads": -1,
"filename": "ynca-5.19.0.tar.gz",
"has_sig": false,
"md5_digest": "79fd5cab8da127705529e5d71737e8dd",
"packagetype": "sdist",
"python_version": "source",
"requires_python": ">=3.8",
"size": 44138,
"upload_time": "2025-01-16T19:35:51",
"upload_time_iso_8601": "2025-01-16T19:35:51.292902Z",
"url": "https://files.pythonhosted.org/packages/b5/a0/a8b3caf74d233037adfeedd1261f648721033c5be83c4c131c5c163478c5/ynca-5.19.0.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2025-01-16 19:35:51",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "mvdwetering",
"github_project": "ynca",
"travis_ci": false,
"coveralls": true,
"github_actions": true,
"lcname": "ynca"
}
