Add button platform to miele integration

[astrandb]

Proposed change

Add button platform to miele integration

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: Add button platform to miele core#143508
• 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 Miele integration documentation to include new "Button" and "Climate" entity types.
  • Added explanations for button controls (e.g., Start, Pause, Stop) for supported appliances.
  • Described climate control features for refrigerators, freezers, and wine cabinets, including support for multiple temperature zones.

[netlify]

✅ Deploy Preview for home-assistant-docs ready!

Name	Link
🔨 Latest commit	b86acc5
🔍 Latest deploy log	https://app.netlify.com/sites/home-assistant-docs/deploys/6808c9acf16ad700084efbb6
😎 Deploy Preview	https://deploy-preview-38694--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 documentation for the Miele integration was updated to reflect support for two additional Home Assistant entity platforms: "Button" and "Climate." Metadata entries for these platforms and categories were added, and new sections detailing their functionality were introduced. The "Button" section describes control options for appliance program progress, while the "Climate" section covers temperature control for refrigeration appliances. No changes were made to code or existing platform descriptions; all updates are limited to documentation and metadata.

Changes

File(s)	Change Summary
source/_integrations/miele.markdown	Added "Button" and "Climate" to integration metadata and documented their supported functionality.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant HomeAssistant
    participant MieleIntegration

    User -> HomeAssistant: Interacts with Miele integration
    HomeAssistant -> MieleIntegration: Requests entity information
    MieleIntegration -> HomeAssistant: Returns entities (Sensor, Button, Climate, etc.)
    User -> HomeAssistant: Uses Button/Climate entity (e.g., Start program, Set temperature)
    HomeAssistant -> MieleIntegration: Sends command (Start/Pause/Stop or Set temperature)
    MieleIntegration -> HomeAssistant: Confirms action/status

Loading

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 2223ab5 and b86acc5.

📒 Files selected for processing (1)

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

⏰ Context from checks skipped due to timeout of 90000ms (3)

• GitHub Check: Redirect rules - home-assistant-docs
• GitHub Check: Header rules - home-assistant-docs
• GitHub Check: Pages changed - home-assistant-docs

🔇 Additional comments (4)

source/_integrations/miele.markdown (4)

5-6: Metadata update: ha_category adjusted for new platforms
The new entries Button and Climate are correctly added to ha_category and sorted alphabetically, ensuring the integration appears in the appropriate category listings.

---

16-17: Metadata update: ha_platforms extended
The button and climate platforms have been correctly added to ha_platforms (lowercase) and sorted alphabetically to reflect new entity support.

---

86-96: Documentation: Added Button section
The new Button section under Supported functionality follows the established formatting with a level‑3 heading and a {% details %} block. It clearly describes button entities and typical actions.

---

98-104: Documentation: Added Climate section
The Climate section is formatted consistently with other platform sections and accurately describes the climate entity capabilities.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this 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 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.