v7.5.0

[mvdwetering]

What's Changed

• Integration settings show selected sound modes and inputs instead of the hidden ones
• Add volume entity (hidden by default)
• Add remote entity (experimental) (hidden by default)
• Update entity naming to be translatable
• Update service description naming to be translatable
• Increase history buffer for diagnostics
• Add more receivers to the list in the readme, thanks for reporting 👍
• Minimum Home Assistant Core version is now 2023.8.0

Volume entity

The volume of mediaplayers in Home Assistant is always in a range of 0..1 which makes it complicated to work with as you can not just use the numbers shown on the receivers and converting the values is a bit tricky.

The volume entity is like the volume on the mediaplayer except that the unit is dB like on the receivers. This makes it a bit easier to work with because you can just use the numbers as shown on the receiver and not having to map it on the 0..1 range. It also means values on the entity stay the same even if you change the max volume of a zone. On the mediaplayer it would change as it is scaled from min_volume to max_volume.

Remote entity (experimental)

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 due to no default cards for this in Home Assistant. 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. It might be useful if you want to navigate menus, it might be possible to activate scenes for receivers that do not support the normal YNCA commands and control other devices since some commands seeem to be forwarded over CEC.

For more details like available commands, how to send raw remote control codes and an example on how to include in a dashboard see the section in the README

Full Changelog: v7.4.1...v7.5.0

---

This discussion was created from the release v7.5.0.