Skip to content

Update history-graph.markdown #38858

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 2 commits into from
May 5, 2025
Merged

Conversation

jackjourneyman
Copy link
Contributor

@jackjourneyman jackjourneyman commented May 3, 2025

Adds long-term statistics

Proposed change

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

  • Link to parent pull request in the codebase:
  • 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
    • Added a new section explaining long-term statistics, including details on how Home Assistant stores and displays sensor statistics over time.

Adds long-term statistics
@home-assistant home-assistant bot added the current This PR goes into the current branch label May 3, 2025
Copy link

netlify bot commented May 3, 2025

Deploy Preview for home-assistant-docs ready!

Name Link
🔨 Latest commit 4f01170
🔍 Latest deploy log https://app.netlify.com/sites/home-assistant-docs/deploys/68187e0254b6be000878a769
😎 Deploy Preview https://deploy-preview-38858--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 May 3, 2025

Caution

Review failed

The pull request is closed.

📝 Walkthrough

Walkthrough

A new section titled "Long term statistics" was added to the documentation for the history graph. This section explains how Home Assistant stores and manages statistics for sensors with specific state classes. It details the intervals and retention policies for short-term and long-term statistics, and describes how the history graph card selects which statistics to display based on the configured time range.

Changes

File Change Summary
source/_dashboards/history-graph.markdown Added a new section explaining long-term and short-term statistics storage, retention, and usage in the UI.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant HistoryGraphCard
    participant StatisticsStorage

    User->>HistoryGraphCard: Request to display sensor history (with hours_to_show)
    HistoryGraphCard->>StatisticsStorage: Query statistics data
    alt hours_to_show > purge_keep period
        StatisticsStorage-->>HistoryGraphCard: Return long-term statistics (hourly)
        HistoryGraphCard-->>User: Display long-term statistics
    else hours_to_show <= purge_keep period
        StatisticsStorage-->>HistoryGraphCard: Return short-term statistics (5 min intervals, bold)
        HistoryGraphCard-->>User: Display short-term statistics (bold)
    end
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 e9b389a and 4f01170.

📒 Files selected for processing (1)
  • source/_dashboards/history-graph.markdown (1 hunks)

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

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/_dashboards/history-graph.markdown (1)

96-101: Fix compound adjectives, punctuation, and option formatting
Line 96 (section header) and line 100 (compound adjective) should use hyphens, and line 98 needs a comma after “For short-term statistics.” Also, wrap config option names in backticks for clarity.

Apply this diff:

-### Long term statistics
+### Long-term statistics

-Home Assistant saves long-term statistics for a sensor if the entity has a state_class of measurement, total or total_increasing. For short-term statistics a snapshot is taken every 5 minutes. For long-term statistics, an hourly aggregate is stored of the short-term statistics. Short-term statistics are automatically purged after a predefined period (default is 10 days). Long-term statistics are never purged.
+Home Assistant saves long-term statistics for a sensor if the entity has a `state_class` of `measurement`, `total`, or `total_increasing`. For short-term statistics, a snapshot is taken every 5 minutes. For long-term statistics, an hourly aggregate of the short-term data is stored. Short-term statistics are automatically purged after a predefined period (default: 10 days), while long-term statistics are never purged.

-In the history graph card, if the hours to show variable is set to a figure higher than the purge_keep period, long-term statistics will be used, with short term statistics shown in bold.
+In the history graph card, if the `hours_to_show` option is set to a value greater than the `purge_keep` period, long-term statistics are used, and the short-term statistics are shown in bold.
🧰 Tools
🪛 LanguageTool

[uncategorized] ~96-~96: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...ype: string {% endconfiguration %} ### Long term statistics Home Assistant saves long-t...

(EN_COMPOUND_ADJECTIVE_INTERNAL)


[uncategorized] ~98-~98: A comma might be missing here.
Context: ...tal or total_increasing. For short-term statistics a snapshot is taken every 5 minutes. Fo...

(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)


[uncategorized] ~100-~100: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...long-term statistics will be used, with short term statistics shown in bold. ### Examples...

(EN_COMPOUND_ADJECTIVE_INTERNAL)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 696a1f3 and e9b389a.

📒 Files selected for processing (1)
  • source/_dashboards/history-graph.markdown (1 hunks)
🧰 Additional context used
🪛 LanguageTool
source/_dashboards/history-graph.markdown

[uncategorized] ~96-~96: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...ype: string {% endconfiguration %} ### Long term statistics Home Assistant saves long-t...

(EN_COMPOUND_ADJECTIVE_INTERNAL)


[uncategorized] ~98-~98: A comma might be missing here.
Context: ...tal or total_increasing. For short-term statistics a snapshot is taken every 5 minutes. Fo...

(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)


[uncategorized] ~100-~100: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...long-term statistics will be used, with short term statistics shown in bold. ### Examples...

(EN_COMPOUND_ADJECTIVE_INTERNAL)

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, @jackjourneyman 👍

@c0ffeeca7 c0ffeeca7 merged commit c42a963 into home-assistant:current May 5, 2025
5 of 7 checks passed
@jackjourneyman jackjourneyman deleted the patch-1 branch May 5, 2025 09:47
@github-actions github-actions bot locked and limited conversation to collaborators May 6, 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.

2 participants