Skip to content
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

Add model_id to device filters #36926

Open
wants to merge 3 commits into
base: next
Choose a base branch
from
Open

Add model_id to device filters #36926

wants to merge 3 commits into from

Conversation

karwosts
Copy link
Contributor

@karwosts karwosts commented Jan 15, 2025

Proposed change

Add model_id to device filters for device-picking selectors.

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 selector documentation to include a new optional model_id filtering option.
    • Enhanced selector filtering capabilities for areas, devices, floors, and targets.
    • Added clarification on using model_id to limit selections based on specific model identifiers.

@home-assistant home-assistant bot added has-parent This PR has a parent PR in a other repo next This PR goes into the next branch labels Jan 15, 2025
Copy link

netlify bot commented Jan 15, 2025

Deploy Preview for home-assistant-docs ready!

Name Link
🔨 Latest commit 5258c24
🔍 Latest deploy log https://app.netlify.com/sites/home-assistant-docs/deploys/67876f301b08fc000882e016
😎 Deploy Preview https://deploy-preview-36926--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 site configuration.

Copy link
Contributor

coderabbitai bot commented Jan 15, 2025

📝 Walkthrough

Walkthrough

The documentation for selectors has been updated to introduce a new optional model_id configuration parameter. This parameter allows users to filter areas, devices, floors, and targets based on a specific model identifier. The update enhances the filtering capabilities of these selectors by providing a more granular way to limit selections to items matching a particular model ID, while maintaining the existing documentation structure.

Changes

File Change Summary
source/_docs/blueprint/selectors.markdown Added model_id option to multiple selectors:
- Area selector
- Device selector
- Floor selector
- Target selector
New option allows filtering based on model ID. Updated filtering options in Device selector to include model_id in the description.

Sequence Diagram

sequenceDiagram
    participant User
    participant Selector
    participant Entity List
    
    User->>Selector: Configure with model_id
    Selector->>Entity List: Filter entities
    Entity List-->>Selector: Return matching entities
    Selector-->>User: Display filtered list
Loading

The sequence diagram illustrates how the new model_id filter works: when a user configures a selector with a specific model ID, the selector filters the available entities to only those matching that model, then presents the refined list to the user.


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
🪧 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.

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/_docs/blueprint/selectors.markdown (1)

158-158: Remove trailing spaces.

There are trailing spaces at the end of these lines that should be removed.

-      required: false      
+      required: false

Also applies to: 574-574, 811-811, 1365-1365

🧰 Tools
🪛 Markdownlint (0.37.0)

158-158: Expected: 0 or 2; Actual: 6
Trailing spaces

(MD009, no-trailing-spaces)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 38e8c87 and fd9aff1.

📒 Files selected for processing (1)
  • source/_docs/blueprint/selectors.markdown (5 hunks)
🧰 Additional context used
🪛 Markdownlint (0.37.0)
source/_docs/blueprint/selectors.markdown

158-158: Expected: 0 or 2; Actual: 6
Trailing spaces

(MD009, no-trailing-spaces)


574-574: Expected: 0 or 2; Actual: 6
Trailing spaces

(MD009, no-trailing-spaces)


811-811: Expected: 0 or 2; Actual: 6
Trailing spaces

(MD009, no-trailing-spaces)


1365-1365: Expected: 0 or 2; Actual: 6
Trailing spaces

(MD009, no-trailing-spaces)

⏰ 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/_docs/blueprint/selectors.markdown (4)

153-158: LGTM! Area selector documentation updated correctly.

The new model_id filter option is well-documented and follows the established pattern for device filter options.

🧰 Tools
🪛 Markdownlint (0.37.0)

158-158: Expected: 0 or 2; Actual: 6
Trailing spaces

(MD009, no-trailing-spaces)


570-574: LGTM! Device selector documentation updated correctly.

The new model_id filter option is well-documented and follows the established pattern for device filter options.

🧰 Tools
🪛 Markdownlint (0.37.0)

574-574: Expected: 0 or 2; Actual: 6
Trailing spaces

(MD009, no-trailing-spaces)


806-811: LGTM! Floor selector documentation updated correctly.

The new model_id filter option is well-documented and follows the established pattern for device filter options.

🧰 Tools
🪛 Markdownlint (0.37.0)

811-811: Expected: 0 or 2; Actual: 6
Trailing spaces

(MD009, no-trailing-spaces)


1362-1365: LGTM! Target selector documentation updated correctly.

The new model_id filter option is well-documented and follows the established pattern for device filter options.

🧰 Tools
🪛 Markdownlint (0.37.0)

1365-1365: Expected: 0 or 2; Actual: 6
Trailing spaces

(MD009, no-trailing-spaces)

source/_docs/blueprint/selectors.markdown Outdated Show resolved Hide resolved
source/_docs/blueprint/selectors.markdown Outdated Show resolved Hide resolved
source/_docs/blueprint/selectors.markdown Outdated Show resolved Hide resolved
source/_docs/blueprint/selectors.markdown Outdated Show resolved Hide resolved
c0ffeeca7
c0ffeeca7 previously approved these changes Jan 15, 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, @karwosts 👍

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 (4)
source/_docs/blueprint/selectors.markdown (4)

153-158: Fix trailing spaces in the model_id configuration.

The model_id parameter documentation has trailing spaces that should be removed.

    model_id:
      description: >
-        When set, the list of areas is limited to areas with devices that have
-        the set model ID.      
+        When set, the list of areas is limited to areas with devices that have
+        the set model ID.
      type: string
      required: false
🧰 Tools
🪛 Markdownlint (0.37.0)

158-158: Expected: 0 or 2; Actual: 6
Trailing spaces

(MD009, no-trailing-spaces)


494-494: Fix trailing spaces and improve description consistency.

The model_id parameter documentation has trailing spaces and its description should be consistent with other filter parameters.

-    manufacturer, model, or model ID of the device, the entities the device provides or based
+    manufacturer, model, or model ID of the device, the entities the device provides, or based

    model_id:
      description: >
-        When set, the list of devices is limited to devices that have the set model ID.      
+        When set, the list of devices is limited to devices that have the set model ID.
      type: string
      required: false

Also applies to: 570-574


806-811: Fix trailing spaces in floor selector documentation.

The model_id parameter documentation has trailing spaces that should be removed.

    model_id:
      description: >
-        When set, the list only includes floors with devices that have
-        the set model ID.      
+        When set, the list only includes floors with devices that have
+        the set model ID.
      type: string
      required: false
🧰 Tools
🪛 Markdownlint (0.37.0)

811-811: Expected: 0 or 2; Actual: 6
Trailing spaces

(MD009, no-trailing-spaces)


1362-1365: Fix capitalization and trailing spaces in target selector.

The Description field should be lowercase and trailing spaces should be removed.

    model_id:
-      Description: When set, the targets are limited to devices that have the set model ID.      
+      description: When set, the targets are limited to devices that have the set model ID.
      type: string
      required: false
🧰 Tools
🪛 Markdownlint (0.37.0)

1365-1365: Expected: 0 or 2; Actual: 6
Trailing spaces

(MD009, no-trailing-spaces)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between fd9aff1 and 91860bf.

📒 Files selected for processing (1)
  • source/_docs/blueprint/selectors.markdown (5 hunks)
🧰 Additional context used
🪛 Markdownlint (0.37.0)
source/_docs/blueprint/selectors.markdown

158-158: Expected: 0 or 2; Actual: 6
Trailing spaces

(MD009, no-trailing-spaces)


574-574: Expected: 0 or 2; Actual: 6
Trailing spaces

(MD009, no-trailing-spaces)


811-811: Expected: 0 or 2; Actual: 6
Trailing spaces

(MD009, no-trailing-spaces)


1365-1365: Expected: 0 or 2; Actual: 6
Trailing spaces

(MD009, no-trailing-spaces)

🔇 Additional comments (1)
source/_docs/blueprint/selectors.markdown (1)

153-158: LGTM: The model_id parameter is consistently documented.

The addition of the model_id parameter is well documented across all relevant selectors (Area, Device, Floor, and Target) with consistent type definitions and optional status.

Also applies to: 570-574, 806-811, 1362-1365

🧰 Tools
🪛 Markdownlint (0.37.0)

158-158: Expected: 0 or 2; Actual: 6
Trailing spaces

(MD009, no-trailing-spaces)

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 (4)
source/_docs/blueprint/selectors.markdown (4)

153-158: Improve description consistency for model_id filter.

The description is clear but could be more consistent with other filter descriptions in the documentation.

-        When set, the list of areas is limited to areas with devices that have
-        the set model ID.
+        When set, it limits the list of areas to areas with devices that have the set model ID.
🧰 Tools
🪛 Markdownlint (0.37.0)

158-158: Expected: 0 or 2; Actual: 6
Trailing spaces

(MD009, no-trailing-spaces)


570-574: Fix trailing spaces and improve description consistency.

The description should follow the same pattern as other filter descriptions, and trailing spaces should be removed.

-        When set, the list of devices is limited to devices that have the set model ID.
+        When set, it limits the list of devices to devices that have the set model ID.
🧰 Tools
🪛 Markdownlint (0.37.0)

574-574: Expected: 0 or 2; Actual: 6
Trailing spaces

(MD009, no-trailing-spaces)


806-811: Fix trailing spaces and improve description consistency.

The description should follow the same pattern as other filter descriptions, and trailing spaces should be removed.

-        When set, the list only includes floors with devices that have
-        the set model ID.
+        When set, it limits the list of floors to floors with devices that have the set model ID.
🧰 Tools
🪛 Markdownlint (0.37.0)

811-811: Expected: 0 or 2; Actual: 6
Trailing spaces

(MD009, no-trailing-spaces)


1362-1365: Fix trailing spaces and improve description consistency.

The description should follow the same pattern as other filter descriptions, and trailing spaces should be removed.

-      description: When set, the targets are limited to devices that have the set model ID.
+      description: When set, it limits the targets to devices that have the set model ID.
🧰 Tools
🪛 Markdownlint (0.37.0)

1365-1365: Expected: 0 or 2; Actual: 6
Trailing spaces

(MD009, no-trailing-spaces)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 91860bf and 5258c24.

📒 Files selected for processing (1)
  • source/_docs/blueprint/selectors.markdown (5 hunks)
🧰 Additional context used
🪛 Markdownlint (0.37.0)
source/_docs/blueprint/selectors.markdown

158-158: Expected: 0 or 2; Actual: 6
Trailing spaces

(MD009, no-trailing-spaces)


574-574: Expected: 0 or 2; Actual: 6
Trailing spaces

(MD009, no-trailing-spaces)


811-811: Expected: 0 or 2; Actual: 6
Trailing spaces

(MD009, no-trailing-spaces)


1365-1365: Expected: 0 or 2; Actual: 6
Trailing spaces

(MD009, no-trailing-spaces)

⏰ 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 (1)
source/_docs/blueprint/selectors.markdown (1)

Line range hint 153-1365: Overall documentation structure looks good!

The addition of the model_id filter option is well documented across all relevant selectors. The structure and placement are consistent with the existing documentation.

🧰 Tools
🪛 Markdownlint (0.37.0)

811-811: Expected: 0 or 2; Actual: 6
Trailing spaces

(MD009, no-trailing-spaces)

@c0ffeeca7 c0ffeeca7 added the awaits-parent Awaits the merge of an parent PR label Jan 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaits-parent Awaits the merge of an parent PR has-parent This PR has a parent PR in a other repo next This PR goes into the next branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants