Skip to content

Documents the added binary_sensor in the Velux integration #39894

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 6 commits into from
Jul 28, 2025

Conversation

wollew
Copy link

@wollew wollew commented Jul 7, 2025

Proposed change

Documentation for the added binary_sensor platform in the Velux 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).
  • 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
    • Updated Velux integration documentation to include "binary_sensor" as a supported platform reporting rain detection.
    • Added details about rain sensor polling intervals and default disabled status due to battery and radio usage.

@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 Jul 7, 2025
Copy link

netlify bot commented Jul 7, 2025

Deploy Preview for home-assistant-docs ready!

Name Link
🔨 Latest commit 2c15a0e
🔍 Latest deploy log https://app.netlify.com/projects/home-assistant-docs/deploys/686b7e566a0b7c0008045292
😎 Deploy Preview https://deploy-preview-39894--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.

Copy link
Contributor

coderabbitai bot commented Jul 7, 2025

Warning

Rate limit exceeded

@wollew has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 8 minutes and 31 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between b709b1c and 2c15a0e.

📒 Files selected for processing (1)
  • source/_integrations/velux.markdown (2 hunks)
📝 Walkthrough

"""

Walkthrough

The documentation for the Velux integration was updated to include "binary_sensor" as a supported platform. This update is reflected in both the metadata and the list of supported device types. Additional details about rain sensor polling and default disablement were added. No code or functional changes were made.

Changes

File Change Summary
source/_integrations/velux.markdown Added "binary_sensor" to supported platforms and device types; detailed rain sensor polling behavior and default disablement in documentation.

Sequence Diagram(s)

No sequence diagram generated as the changes are documentation-only.
"""


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 (2)
source/_integrations/velux.markdown (2)

15-20: Consider alphabetizing ha_platforms for consistency.

The newly-added binary_sensor entry is correct, but the list is now out of alphabetical order (cover, light, scene, binary_sensor). Many integration front-matters keep these lists sorted to reduce merge-conflicts and aid scanning.

 ha_platforms:
-  - cover
-  - light
-  - scene
-  - binary_sensor
+  - binary_sensor
+  - cover
+  - light
+  - scene

28-34: Add a short description of the new Binary Sensor.

The bullet is correctly inserted, but users benefit from knowing what the sensor reports (e.g., rain sensor, window open/closed, fault state). A one-sentence parenthetical note right after the bullet list (or a dedicated subsection) would improve clarity.

Example:

- Binary Sensor  *(reports rain detection and gateway fault status)*
📜 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 ea4c369 and 6ce32de.

📒 Files selected for processing (1)
  • source/_integrations/velux.markdown (2 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)
  • GitHub Check: Redirect rules - home-assistant-docs
  • GitHub Check: Header rules - home-assistant-docs
  • GitHub Check: Pages changed - home-assistant-docs

c0ffeeca7
c0ffeeca7 previously approved these changes Jul 7, 2025
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, @wollew 👍

@c0ffeeca7 c0ffeeca7 added the awaits-parent Awaits the merge of an parent PR label Jul 7, 2025
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/velux.markdown (1)

35-35: Tighten grammar & remove trailing space

Minor language fixes and removal of trailing whitespace flagged by markdown-lint.

-Rain sensors of supported windows do not report automatically but need to be polled every 5 minutes. For this reason they are disabled per default because polling will use more radio bandwidth and battery power than just regularly reporting of changed window positions. 
+Rain sensors of supported windows do not report automatically and must be polled every 5 minutes. For this reason, they are disabled by default, because polling uses more radio bandwidth and battery power than simply reporting changed window positions.
📜 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 d4fb11c and 2049ed8.

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

[typographical] ~35-~35: Use a comma after an introductory phrase.
Context: ... but need to be polled every 5 minutes. For this reason they are disabled per default because p...

(COMMA_INTRODUCTORY_WORDS_PHRASES)

🪛 markdownlint-cli2 (0.17.2)
source/_integrations/velux.markdown

35-35: Trailing spaces
Expected: 0 or 2; Actual: 1

(MD009, no-trailing-spaces)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)
  • GitHub Check: Redirect rules - home-assistant-docs
  • GitHub Check: Header rules - home-assistant-docs
  • GitHub Check: Pages changed - home-assistant-docs
🔇 Additional comments (2)
source/_integrations/velux.markdown (2)

15-19: Front-matter addition looks correct

binary_sensor is correctly added to ha_platforms, and the list remains alphabetical.
No further action required.


28-32: Bullet entry accepted

The “Binary Sensor” list item now matches the terminology and style of the other device types.
No issues spotted.

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

♻️ Duplicate comments (1)
source/_integrations/velux.markdown (1)

30-30: Use sentence-style capitalization for bullet

Per the doc style guide, only the first word is capitalized.

- - Binary Sensor (reports rain detection for windows that support it)
+ - Binary sensor (reports rain detection for windows that support it)
🧹 Nitpick comments (2)
source/_integrations/velux.markdown (2)

16-19: Keep ha_platforms list alphabetically sorted

Insert binary_sensor in alphabetical order (after cover, before light) to preserve the existing convention and improve scan-ability.


35-35: Remove superfluous comma before “because”

- … they are disabled by default, because polling uses more radio bandwidth …
+ … they are disabled by default because polling uses more radio bandwidth …
📜 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 2049ed8 and b709b1c.

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

[formatting] ~35-~35: If the ‘because’ clause is essential to the meaning, do not use a comma before the clause.
Context: ...his reason, they are disabled by default, because polling uses more radio bandwidth and b...

(COMMA_BEFORE_BECAUSE)

Co-authored-by: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com>
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, @wollew 👍

@home-assistant home-assistant bot added the parent-merged The parent PR has been merged already label Jul 28, 2025
@c0ffeeca7 c0ffeeca7 merged commit 4e914a0 into home-assistant:next Jul 28, 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 28, 2025
@github-actions github-actions bot locked and limited conversation to collaborators Jul 29, 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.

2 participants