Skip to content

Add data update details for Shelly integration #38852

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 4 commits into from
May 3, 2025

Conversation

thecode
Copy link
Member

@thecode thecode commented May 2, 2025

Proposed change

Describe how Shelly updates data from devices docs-data-update

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 "Data updates" section to clarify how Shelly devices send updates to Home Assistant.
    • Organized configuration instructions for different device generations under new subheadings.
    • Listed entities that use polling (updated every 60 seconds) for both generation 1 and generation 2+ devices.
    • Improved clarity on update mechanisms and polling behavior for Shelly integration.

@home-assistant home-assistant bot added the current This PR goes into the current branch label May 2, 2025
Copy link

netlify bot commented May 2, 2025

Deploy Preview for home-assistant-docs ready!

Name Link
🔨 Latest commit 6ffce20
🔍 Latest deploy log https://app.netlify.com/sites/home-assistant-docs/deploys/68160be3844f0500086ca78f
😎 Deploy Preview https://deploy-preview-38852--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 2, 2025

📝 Walkthrough

Walkthrough

The documentation for the Shelly integration was updated by adding a new "Data updates" section, which explains how Shelly devices communicate updates to Home Assistant. Existing configuration instructions for generation 1 and generation 2+ devices were reorganized under new subheadings within this section. Two new subsections were included to list entities that are disabled by default and rely on polling every 60 seconds, with separate lists for generation 1 and generation 2+ devices. No changes were made to code or public APIs.

Changes

File Change Summary
source/_integrations/shelly.markdown Added a "Data updates" section, reorganized configuration instructions under new subheadings, and listed polling entities.

Sequence Diagram(s)

No sequence diagram generated as the changes are limited to documentation structure and content.


📜 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 af066fb and 6ffce20.

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

[grammar] ~99-~99: You’ve repeated a verb. Did you mean to only write one of them?
Context: ...ng disabled by default entities {% term polling poll %} data from the device every 60 second...

(REPEATED_VERBS)


[uncategorized] ~101-~101: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...ta from the device every 60 seconds: - Cloud connected sensor - RSSI sensor - Uptime sensor - ...

(EN_COMPOUND_ADJECTIVE_INTERNAL)


[grammar] ~108-~108: You’ve repeated a verb. Did you mean to only write one of them?
Context: ...ng disabled by default entities {% term polling poll %} data from the device every 60 second...

(REPEATED_VERBS)

⏰ 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 (3)
source/_integrations/shelly.markdown (3)

65-66: Approve new "Data updates" section header
The addition of the ## Data updates section clearly scopes the upcoming content and aligns with the surrounding documentation structure.


97-97: Approve generation 1 polling entities header
The new subsection heading ### Shelly entities that poll data from the device (generation 1) is clear and correctly positioned under Data updates.


106-106: Approve generation 2+ polling entities header
The ### Shelly entities that poll data from the device (generation 2+) heading correctly mirrors the generation 1 subsection and maintains consistency.


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 (5)
source/_integrations/shelly.markdown (5)

65-67: Fix grammar and add link to developer docs
"devices needs" should be "devices need" for correct subject-verb agreement. Also, consider linking to the official Data update rules page to guide integrators:

@@ 67
-For push updates to work correctly some devices needs additional configuration:
+For push updates to work correctly some devices need additional configuration.
+For more details, see [Data update rules](https://developers.home-assistant.io/docs/core/integration-quality-scale/rules/docs-data-update).

97-97: Correct plural verb usage in heading
Use "poll" instead of "polls" since "entities" is plural:

-### Shelly entities that polls data from the device (generation 1)
+### Shelly entities that poll data from the device (generation 1)
🧰 Tools
🪛 LanguageTool

[grammar] ~97-~97: Possible subject-verb agreement error.
Context: ...{% endnote %} ### Shelly entities that polls data from the device (generation 1) Th...

(NNS_THAT_AGREEMENT)


99-99: Improve phrasing and hyphenation
Streamline the sentence and hyphenate the compound adjective:

-The following disabled by default entities {% term polling polls %} data from the device every 60 seconds:
+The following disabled-by-default entities poll data from the device every 60 seconds:
🧰 Tools
🪛 LanguageTool

[grammar] ~99-~99: You’ve repeated a verb. Did you mean to only write one of them?
Context: ...ng disabled by default entities {% term polling polls %} data from the device every 60 second...

(REPEATED_VERBS)


106-106: Correct plural verb usage in heading
Apply the same plural correction for generation 2+:

-### Shelly entities that polls data from the device (generation 2+)
+### Shelly entities that poll data from the device (generation 2+)
🧰 Tools
🪛 LanguageTool

[grammar] ~106-~106: Possible subject-verb agreement error.
Context: ...rmware update ### Shelly entities that polls data from the device (generation 2+) T...

(NNS_THAT_AGREEMENT)


108-108: Improve phrasing and hyphenation
Mirror the fix for the generation 2+ polling description:

-The following disabled by default entities {% term polling polls %} data from the device every 60 seconds:
+The following disabled-by-default entities poll data from the device every 60 seconds:
🧰 Tools
🪛 LanguageTool

[grammar] ~108-~108: You’ve repeated a verb. Did you mean to only write one of them?
Context: ...ng disabled by default entities {% term polling polls %} data from the device every 60 second...

(REPEATED_VERBS)

📜 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 aeb8380.

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

[grammar] ~97-~97: Possible subject-verb agreement error.
Context: ...{% endnote %} ### Shelly entities that polls data from the device (generation 1) Th...

(NNS_THAT_AGREEMENT)


[grammar] ~99-~99: You’ve repeated a verb. Did you mean to only write one of them?
Context: ...ng disabled by default entities {% term polling polls %} data from the device every 60 second...

(REPEATED_VERBS)


[uncategorized] ~101-~101: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...ta from the device every 60 seconds: - Cloud connected sensor - RSSI sensor - Uptime sensor - ...

(EN_COMPOUND_ADJECTIVE_INTERNAL)


[grammar] ~106-~106: Possible subject-verb agreement error.
Context: ...rmware update ### Shelly entities that polls data from the device (generation 2+) T...

(NNS_THAT_AGREEMENT)


[grammar] ~108-~108: You’ve repeated a verb. Did you mean to only write one of them?
Context: ...ng disabled by default entities {% term polling polls %} data from the device every 60 second...

(REPEATED_VERBS)

⏰ 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/_integrations/shelly.markdown (1)

86-86: Configuration section nesting is correct
The "Shelly device configuration (generation 2+)" subsection is properly nested under the new Data updates section with the correct heading level.

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: 3

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between aeb8380 and af066fb.

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

[grammar] ~99-~99: You’ve repeated a verb. Did you mean to only write one of them?
Context: ...ng disabled by default entities {% term polling poll %} data from the device every 60 second...

(REPEATED_VERBS)


[uncategorized] ~101-~101: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...ta from the device every 60 seconds: - Cloud connected sensor - RSSI sensor - Uptime sensor - ...

(EN_COMPOUND_ADJECTIVE_INTERNAL)


[grammar] ~108-~108: You’ve repeated a verb. Did you mean to only write one of them?
Context: ...ng disabled by default entities {% term polling poll %} data from the device every 60 second...

(REPEATED_VERBS)

🔇 Additional comments (1)
source/_integrations/shelly.markdown (1)

86-86: Heading structure for Generation 2+ configuration is clear
The “### Shelly device configuration (generation 2+)” section mirrors the generation 1 subsection and requires no changes.

bieniu
bieniu previously approved these changes May 2, 2025
Copy link
Member

@bieniu bieniu left a comment

Choose a reason for hiding this comment

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

Looks good, thanks!

@thecode thecode merged commit 9b1322e into home-assistant:current May 3, 2025
7 checks passed
@thecode thecode deleted the shelly-data-update branch May 3, 2025 14:08
@home-assistant home-assistant bot added has-parent This PR has a parent PR in a other repo parent-merged The parent PR has been merged already labels May 3, 2025
@github-actions github-actions bot locked and limited conversation to collaborators May 4, 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 has-parent This PR has a parent PR in a other repo parent-merged The parent PR has been merged already
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants