Releases: mvdwetering/yamaha_ynca
v7.2.0
What's Changed
- Added RX-V777 to readme, thanks for reporting 👍
- Add multiline support for raw YNCA commands service
Full Changelog: v7.1.0...v7.2.0
v7.1.0
What's Changed
- Extended README with several more confirmed working receivers. Thanks for reporting 👍
- Fix song title not showing for Spotify and (probably) Pandora sources
- Allow changing of connection settings when unable to connect to receiver. See FAQ section in readme for more details if needed.
Full Changelog: v7.0.0...v7.1.0
v7.0.0
Breaking change
Leading and trailing whitespace from source names is now stripped. If you have automations that are checking against literal names that have spaces you need to update the automation.
Note this is only an issue where you have spaces embedded in the string to compare. For example if current source equals " HDMI4 ". Setting sourcenames with spaces still works as spaces are removed/ignored now.
What's Changed
- Remove (and ignore) leading and trailing whitespace on sourcenames. Some receivers have (default) sourcenames like " HDMI4 " and since the Home Asisstant frontend hides those spaces it is hard to use the names in automations. The integration has been updated to strip whitespace for in the sources list and current source. It also ignores whitespace when setting source.
- Add Pure Direct mode switch
- Extended README with several more confirmed working receivers. Thanks for reporting 👍
Full Changelog: v6.2.0...v7.0.0
v6.2.0
What's Changed
- Fixed AirPlay source
- Extend AirPlay support with playback status and Album, Artist, Song metadata.
All pull requests
- Add RX-V677 to list of working receivers by @mvdwetering in #130
- Add RX-V773 to readme by @mvdwetering in #134
- Update ynca to 5.4.0, fixes and improves AirPlay by @mvdwetering in #136
Full Changelog: v6.1.0...v6.2.0
v6.1.0
What's Changed
- Device names in Home Assistant update when zonename is changed on receiver
- Add Surround Decoder select entity (for receivers with Dolby Prologic and DTS:Neo decoders)
Full Changelog: v6.0.0...v6.1.0
v6.0.0
Breaking change
Device automations for Zone2, Zone3 or Zone4 won't work properly after updating to this version due to the split up in multiple devices. They need to be updated to use the new zone devices. Device automations for the MAIN zone will still work.
Note that automations using entities are not impacted.
What's Changed
Minimum supported Home Assistant version is now 2023.1.0
This is a rather big release with quite a few topics, next to some smaller tweaks and bugfixes.
Device per zone
The biggest change is that each zone is now exposed as a device. So on a 2 zone receiver there will be 2 devices exposed by the integration.
This was done to have a better way to organize entities across zones. Due to the entities added in this release the total amount of entities on the one device became overwhelming especially on 4 zone receivers and it was hard to find the entities you were looking for. Next to that previously the zone name was included in the entity name, but that reduced the visible space for that actual entity name a lot.
With this change a zone device has only relevant entities associated with it and entitynames are less likely to be cut off since the zone prefix is not needed anymore.
Integration configuration
The integration configuration settings have been reworked. There is now a screen per zone and a general screen for non-zone specific options.
The configuration got extended with an option to override the Scenes autodetection. On newer receivers it is not possible to detect the amount of supported Scenes on a zone, so this setting allows you to manually specify the amount supported Scenes for your receiver.
Configuration entities
A number of configuration entities have been added. Availability depends on receiver capabilities. These are the new entities:
- CINEMA DSP 3D mode
- Adaptive DRC
- Compressed Music Enhancer
- HDMI Out selection (Off, HDMI1, HDMI2 or Both)
- Initial volume
- Max volume
- Sleep timer
- Speaker bass/treble
- Headphone bass/treble (default disabled)
Note that the receiver does not allow changing the settings while it is in standby which is why the entities become unavailable when the zone is in standby.
All changes
- Be robust against optional volume, mute, input, pwr by @mvdwetering in #100
- Give message when trying to configure without active connection by @mvdwetering in #101
- Split options into screen per zone by @mvdwetering in #102
- Make number of scenes configurable by @mvdwetering in #103
- Fix volume mapping when maxvol is 0 by @mvdwetering in #104
- Add number platform with maxvol, bass, treble by @mvdwetering in #105
- Add switch platform by @mvdwetering in #107
- Add select platform by @mvdwetering in #108
- Extend workflow with typing check by @mvdwetering in #109
- Device per zone by @mvdwetering in #112
- Change translation keys to snake_case by @mvdwetering in #113
- Fix update of some entities by @mvdwetering in #114
- Add power on volume settings by @mvdwetering in #115
- Bump dependencies to match HA 2023.1.0 by @mvdwetering in #116
- Handle YncaConnectionFailed exception when connecting by @mvdwetering in #117
- Prepare for release by @mvdwetering in #118
Full Changelog: v5.3.0...v6.0.0
v5.3.0
What's Changed
- Add DAB and RDS support by @mvdwetering in #96
- Bump ynca to 4.1.0b1 by @mvdwetering in #95
- Bump ynca to 4.1.0 by @mvdwetering in #99
- Update list of receivers by @mvdwetering in #98
- Bump test and dev dependencies to match HA 2022.12.6 by @mvdwetering in #94
Full Changelog: v5.2.0...v5.3.0
v5.3.0b0
What's Changed
- Bump test/dev dependencies to match HA 2022.12.6 by @mvdwetering in #94
- Bump ynca to 4.1.0b1 by @mvdwetering in #95
- Add DAB and RDS support by @mvdwetering in #96
Full Changelog: v5.2.0...v5.3.0b0
v5.2.0
What's Changed
- Updated the communication library to make it easier to add new features.
- Fixed USB listed multiple times in sources list
Full Changelog: v5.1.0...v5.2.0