Update README.md, mention source name support

[mvdwetering]

Summary by CodeRabbit

• New Features
  • Enhanced documentation for Yamaha YNCA integration with clearer descriptions of features.
  • Added support for source names from the receiver.
  • Introduced store_preset action for storing presets in Home Assistant.
  • Expanded details on volume control using dB units.
  • Clarified remote control functionality and command options.
  • Updated presets section with activation and storage instructions.

[coderabbitai[bot]]

Walkthrough

The pull request includes significant updates to the README.md file for the Yamaha YNCA integration. Key modifications involve the addition of a new feature regarding source naming, an expanded explanation of the volume (dB) entity, a refined description of remote control functionalities, and updates to the presets section, including the introduction of a new action called store_preset. These changes aim to enhance the clarity and detail of the documentation.

Changes

File	Change Summary
README.md	- Added a feature about source names being taken from the receiver. - Expanded the volume (dB) entity section for clarity. - Refined the remote control section with detailed command information. - Updated the presets section, introducing the store_preset action with YAML configuration examples.

Possibly related PRs

• 309: This PR updates the README.md to enhance clarity and precision, which aligns with the main PR's goal of improving documentation for the Yamaha YNCA integration.

• 312: Similar to the main PR, this PR focuses on updating the README.md for better clarity and user understanding, particularly regarding the volume control and presets.

Poem

In the land of sound where receivers play,
New features sprout, brightening the way.
With presets stored and volumes clear,
Our Yamaha sings, bringing us cheer!
So hop along, let the music flow,
With each new change, our knowledge will grow! 🐰🎶

---

🪧 Tips

### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit , please review it.` - `Generate unit testing code for this file.` - `Open a follow-up GitHub issue for this discussion.` - Files and specific lines of code (under the "Files changed" tab): Tag `@coderabbitai` in a new review comment at the desired location with your query. Examples: - `@coderabbitai generate unit testing code for this file.` - `@coderabbitai modularize this function.` - PR comments: Tag `@coderabbitai` in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples: - `@coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.` - `@coderabbitai read src/utils.ts and generate unit testing code.` - `@coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.` - `@coderabbitai help me debug CodeRabbit configuration file.` Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. ### CodeRabbit Commands (Invoked using PR comments) - `@coderabbitai pause` to pause the reviews on a PR. - `@coderabbitai resume` to resume the paused reviews. - `@coderabbitai review` to trigger an incremental review. This is useful when automatic reviews are disabled for the repository. - `@coderabbitai full review` to do a full review from scratch and review all the files again. - `@coderabbitai summary` to regenerate the summary of the PR. - `@coderabbitai resolve` resolve all the CodeRabbit review comments. - `@coderabbitai configuration` to show the current CodeRabbit configuration for the repository. - `@coderabbitai help` to get help. ### Other keywords and placeholders - Add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. - Add `@coderabbitai summary` to generate the high-level summary at a specific location in the PR description. - Add `@coderabbitai` anywhere in the PR title to generate the title automatically. ### CodeRabbit Configuration File (`.coderabbit.yaml`) - You can programmatically configure CodeRabbit by adding a `.coderabbit.yaml` file to the root of your repository. - Please see the [configuration documentation](https://docs.coderabbit.ai/guides/configure-coderabbit) for more information. - If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: `# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json` ### Documentation and Community - Visit our [Documentation](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](http://discord.gg/coderabbit) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.