Fix valve names

[joostlek]

Proposed change

Apparently the names where wrong. Shout out to @Petro31 and his broken fingers.

Type of change

• Spelling, grammar or other readability improvements (current branch).
• Adjusted missing or incorrect information in the current documentation (current branch).
• Added documentation for a new integration I'm adding to Home Assistant (next branch).
  • I've opened up a PR to add logos and icons in Brands repository.
• Added documentation for a new feature I'm adding to Home Assistant (next branch).
• Removed stale or deprecated documentation.

Additional information

• Link to parent pull request in the codebase:
• Link to parent pull request in the Brands repository:
• This PR fixes or closes issue: fixes #

Checklist

• This PR uses the correct branch, based on one of the following:
  • I made a change to the existing documentation and used the current branch.
  • I made a change that is related to an upcoming version of Home Assistant and used the next branch.
• The documentation follows the Home Assistant documentation standards.

Summary by CodeRabbit

• Documentation
  • Updated valve control action commands for improved clarity
  • Renamed commands to provide more descriptive context:
    • valve.open → valve.open_valve
    • valve.close → valve.close_valve
    • valve.set_position → valve.set_valve_position

[netlify]

✅ Deploy Preview for home-assistant-docs ready!

Name	Link
🔨 Latest commit	8eb471e
🔍 Latest deploy log	https://app.netlify.com/sites/home-assistant-docs/deploys/6771d6cdf138830008172771
😎 Deploy Preview	https://deploy-preview-36606--home-assistant-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request introduces modifications to the valve integration documentation in Home Assistant, focusing on renaming action commands to provide more explicit and descriptive names. The changes aim to improve clarity by adding more context to the valve-related commands, specifically updating valve.open to valve.open_valve, valve.close to valve.close_valve, and valve.set_position to valve.set_valve_position. The core functionality remains unchanged, with the modifications primarily addressing naming conventions.

Changes

File	Change Summary
source/_integrations/valve.markdown	- Renamed valve.open to valve.open_valve - Renamed valve.close to valve.close_valve - Renamed valve.set_position to valve.set_valve_position - Updated automation examples to reflect new command names

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, 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 generate docstrings to generate docstrings for this PR. (Beta)
• @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 or @coderabbitai title 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 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 for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

source/_integrations/valve.markdown (1)

Line range hint 69-91: Consider enhancing position parameter documentation.

While the documentation is accurate, consider making the position range more explicit in the parameter description:

 | Data attribute | Optional | Description |
 | ---------------------- | -------- | ----------- |
 | `entity_id` | yes | String or list of strings that point at `entity_id`'s of valves. Use `entity_id: all` to target all.
-| `position` | no | Integer between 0 (fully closed) and 100 (fully open).
+| `position` | no | Integer between 0 and 100, where 0 represents fully closed and 100 represents fully open.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 76eed77 and 8eb471e.

📒 Files selected for processing (1)

• source/_integrations/valve.markdown (3 hunks)

🔇 Additional comments (2)

source/_integrations/valve.markdown (2)

49-50: LGTM! Command naming improvements enhance clarity.

The renamed commands (valve.open_valve, valve.close_valve, valve.set_valve_position) are more explicit and follow a consistent pattern, which reduces potential ambiguity for users.

---

64-68: LGTM! Example correctly demonstrates the new command.

The automation example accurately reflects the renamed command and maintains a clear, simple demonstration.