Skip to content

Document and clarify upstream devices and hierachies #38574

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 3 commits into from
Apr 16, 2025
Merged

Conversation

frenck
Copy link
Member

@frenck frenck commented Apr 16, 2025

Proposed change

Add some context to device hierarchy in the energy dashboard + fixes feedback from #38567

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
    • Added a new section explaining how to set up upstream devices and hierarchies for energy-consuming devices, enabling more accurate energy usage reporting and preventing double-counting in the energy dashboard.

@home-assistant home-assistant bot added the current This PR goes into the current branch label Apr 16, 2025
@frenck frenck requested a review from Copilot April 16, 2025 16:01
Copy link

netlify bot commented Apr 16, 2025

Deploy Preview for home-assistant-docs ready!

Name Link
🔨 Latest commit be42170
🔍 Latest deploy log https://app.netlify.com/sites/home-assistant-docs/deploys/67fff2d11400c60008e42e53
😎 Deploy Preview https://deploy-preview-38574--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

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

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

Copilot reviewed 1 out of 1 changed files in this pull request and generated 1 comment.

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Copy link
Contributor

coderabbitai bot commented Apr 16, 2025

📝 Walkthrough

Walkthrough

A new section titled "Upstream devices and hierarchies" has been added to the energy documentation. This section explains the concept of designating upstream devices to create hierarchical relationships among energy-consuming devices, which helps prevent double-counting energy usage. The documentation clarifies that only devices already added as individual devices can be selected as upstream devices, and provides instructions for establishing these relationships. An important note is included to address user confusion regarding the selection of upstream devices.

Changes

File(s) Change Summary
source/_docs/energy/individual-devices.markdown Added a new section explaining upstream devices, device hierarchies, and clarified selection criteria.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant EnergyDashboard

    User->>EnergyDashboard: Add energy consumption entity as individual device
    User->>EnergyDashboard: Select individual device as upstream device for another device
    EnergyDashboard-->>User: Establish parent-child device hierarchy
Loading

Assessment against linked issues

Objective Addressed Explanation
Clarify that only devices listed under individual devices can be selected as upstream devices (#38567)

📜 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 1216ac5 and be42170.

📒 Files selected for processing (1)
  • source/_docs/energy/individual-devices.markdown (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • source/_docs/energy/individual-devices.markdown

🪧 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 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/energy/individual-devices.markdown (1)

26-40: Clarify the example sentence about double-counting.

The new section is clear and well-structured, but the example sentence about double-counting could be misread as contradictory. For maximum clarity, consider rewording it as follows (adapting the suggestion from the past review):

-For example, imagine having a breaker monitoring the total energy consumption of a circuit, but also separately tracking individual devices connected to that circuit. Without setting the device hierarchies, Home Assistant might double-count this usage. By setting the hierarchy, it understands these relationships and accurately shows the individual device usage without duplication.
+For example, imagine having a breaker monitoring the total energy consumption of a circuit, but also separately tracking individual devices connected to that circuit. Without setting the device hierarchies, Home Assistant might double-count this usage. By setting the hierarchy, Home Assistant understands these relationships and accurately shows the individual device usage without duplication.

This makes it clear that the hierarchy prevents double-counting, not causes it.

Otherwise, the section is a valuable and well-written addition!

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between fd05df8 and 1216ac5.

📒 Files selected for processing (1)
  • source/_docs/energy/individual-devices.markdown (1 hunks)

abmantis
abmantis previously approved these changes Apr 16, 2025
Copy link
Member

@abmantis abmantis left a comment

Choose a reason for hiding this comment

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

Minor nit, otherwise LGTM

Co-authored-by: Abílio Costa <abmantis@users.noreply.github.com>
Copy link
Member

@abmantis abmantis left a comment

Choose a reason for hiding this comment

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

Thanks!

@abmantis abmantis merged commit 31311c1 into current Apr 16, 2025
9 checks passed
@abmantis abmantis deleted the frenck-2025-0180 branch April 16, 2025 20:53
@github-actions github-actions bot locked and limited conversation to collaborators Apr 17, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
current This PR goes into the current branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

"Integrating individual device energy usage "
2 participants