Skip to content

Update miele.markdown for describing how temperature sensors are created #39139

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 15, 2025

Conversation

aturri
Copy link

@aturri aturri commented May 22, 2025

Proposed change

Describe how temperature sensors are created after home-assistant/core#144585

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).
  • Added documentation for a new feature I'm adding to Home Assistant (next branch).
  • Removed stale or deprecated documentation.

Additional information

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
    • Clarified the conditions under which temperature-related sensors for Miele appliances are dynamically created, providing more precise details for refrigerators, freezers, and ovens.

@home-assistant home-assistant bot added has-parent This PR has a parent PR in another repo next This PR goes into the next branch labels May 22, 2025
Copy link

netlify bot commented May 22, 2025

Deploy Preview for home-assistant-docs ready!

Name Link
🔨 Latest commit f9969ce
🔍 Latest deploy log https://app.netlify.com/projects/home-assistant-docs/deploys/682eb7f9eca790000875a343
😎 Deploy Preview https://deploy-preview-39139--home-assistant-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

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

@aturri aturri changed the title Update miele.markdown for #144585 Update miele.markdown for describing how temperature sensors are created May 22, 2025
@aturri aturri marked this pull request as ready for review May 22, 2025 05:42
Copy link
Contributor

coderabbitai bot commented May 22, 2025

📝 Walkthrough

Walkthrough

The documentation for the Miele integration was updated to provide more precise conditions under which certain temperature-related sensors are dynamically created. The changes clarify the requirements for the appearance of sensors related to refrigerators, freezers, and ovens, specifying when each sensor becomes available based on appliance state and sensor data.

Changes

File(s) Change Summary
source/_integrations/miele.markdown Updated documentation to clarify the dynamic creation conditions for temperature, core temperature, and target core temperature sensors in refrigerators, freezers, and ovens.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Appliance (Fridge/Oven/Freezer)
    participant Miele Integration

    User->>Appliance (Fridge/Oven/Freezer): Turns on appliance
    Appliance (Fridge/Oven/Freezer)-->>Miele Integration: Reports valid temperature value
    Miele Integration->>Miele Integration: Dynamically creates Temperature sensor (zone 2/3)

    User->>Appliance (Oven): Starts program
    User->>Appliance (Oven): Connects temperature probe / Sets core target temperature
    Appliance (Oven)-->>Miele Integration: Reports probe status / core target temperature
    Miele Integration->>Miele Integration: Dynamically creates Core temperature/Target core temperature sensor
Loading

Note

⚡️ AI Code Reviews for VS Code, Cursor, Windsurf

CodeRabbit now has a plugin for VS Code, Cursor and Windsurf. This brings AI code reviews directly in the code editor. Each commit is reviewed immediately, finding bugs before the PR is raised. Seamless context handoff to your AI code agent ensures that you can easily incorporate review feedback.
Learn more here.


Note

⚡️ Faster reviews with caching

CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 30th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.
Enjoy the performance boost—your workflow just got faster.


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
🪧 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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
source/_integrations/miele.markdown (1)

162-162: Add missing comma for clarity in the Temperature sensor description.

For readability, consider adding a comma after "zones" in the second sentence:

- Entities are created for up to 3 zones depending on the device capabilities.
+ Entities are created for up to 3 zones, depending on the device capabilities.

This aligns with the static analysis hint and improves the sentence flow.

🧰 Tools
🪛 LanguageTool

[uncategorized] ~162-~162: Possible missing comma found.
Context: ...ovens. Entities are created for up to 3 zones depending on the device capabilities. F...

(AI_HYDRA_LEO_MISSING_COMMA)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge Base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between ca19430 and f9969ce.

📒 Files selected for processing (1)
  • source/_integrations/miele.markdown (1 hunks)
🧰 Additional context used
🪛 LanguageTool
source/_integrations/miele.markdown

[uncategorized] ~162-~162: Possible missing comma found.
Context: ...ovens. Entities are created for up to 3 zones depending on the device capabilities. F...

(AI_HYDRA_LEO_MISSING_COMMA)

🔇 Additional comments (2)
source/_integrations/miele.markdown (2)

164-164: Clarify dynamic creation conditions for the Core temperature sensor.

The new text clearly states that the Core temperature sensor is only created when the oven is on, a program is running, and a probe is attached. This accurately reflects the changes in the core code.


165-165: Validate dynamic creation for the Target core temperature sensor.

The description for Target core temperature correctly specifies the conditions (appliance on, program started, target temperature set) for dynamic creation. It aligns with the corresponding core implementation.

Copy link
Contributor

@c0ffeeca7 c0ffeeca7 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you, @aturri 👍

@c0ffeeca7 c0ffeeca7 added the awaits-parent Awaits the merge of an parent PR label May 23, 2025
@home-assistant home-assistant bot added the parent-merged The parent PR has been merged already label Jul 15, 2025
@silamon silamon merged commit 5b6f787 into home-assistant:next Jul 15, 2025
7 checks passed
@home-assistant home-assistant bot removed awaits-parent Awaits the merge of an parent PR parent-merged The parent PR has been merged already labels Jul 15, 2025
@github-actions github-actions bot locked and limited conversation to collaborators Jul 16, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
has-parent This PR has a parent PR in another repo next This PR goes into the next branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy