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 new integration refoss_rpc #36820

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

Conversation

ashionky
Copy link
Contributor

@ashionky ashionky commented Jan 9, 2025

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

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

Summary by CodeRabbit

  • New Features

    • Added support for Refoss Smart Wi-Fi Switch (R11) integration in Home Assistant.
    • Introduced new device platforms: binary sensors, switches, sensors, events, updates, and buttons.
    • Enabled automatic device discovery via Zeroconf.
    • Supports various button interaction types and device actions, including firmware updates and device reboot.
  • Documentation

    • Provided comprehensive setup guide for Refoss RPC integration.
    • Explained entity naming and configuration strategies, including automation triggers based on button presses.

@home-assistant home-assistant bot added the has-parent This PR has a parent PR in a other repo label Jan 9, 2025
@home-assistant
Copy link

home-assistant bot commented Jan 9, 2025

It seems that this PR is targeted against an incorrect branch. Documentation updates which apply to our current stable release should target the current branch. Please change the target branch of this PR to current and rebase if needed. If this is documentation for a new feature, please add a link to that PR in your description.

@home-assistant home-assistant bot added in-progress This PR/Issue is currently being worked on needs-rebase The PR has been branched of the wrong base branch or targets an incorrect target branch next This PR goes into the next branch labels Jan 9, 2025
@ashionky ashionky marked this pull request as draft January 9, 2025 01:11
Copy link

netlify bot commented Jan 9, 2025

Deploy Preview for home-assistant-docs ready!

Name Link
🔨 Latest commit 59af7db
🔍 Latest deploy log https://app.netlify.com/sites/home-assistant-docs/deploys/677f2243199d090008f5a27e
😎 Deploy Preview https://deploy-preview-36820--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 9, 2025

📝 Walkthrough

Walkthrough

The pull request introduces a new Home Assistant integration for Refoss devices using the RPC protocol. The integration supports the Refoss Smart Wi-Fi Switch, R11, and provides comprehensive functionality across multiple platforms including binary sensors, switches, sensors, events, updates, and buttons. It offers automatic device discovery through Zeroconf and a configuration flow, with detailed support for various device interactions such as button clicks and input sensor modes.

Changes

File Change Summary
source/_integrations/refoss_rpc.markdown - Added new integration documentation for Refoss RPC
- Documented Refoss Smart Wi-Fi Switch, R11 device support
- Defined entity platforms: binary sensors, switches, sensors, events, updates, buttons
- Explained configuration flow and Zeroconf discovery
- Detailed entity naming strategy
- Described input sensor modes and button click events
- Provided automation examples for button interactions

Sequence Diagram

sequenceDiagram
    participant User
    participant HomeAssistant
    participant RefossDevice
    
    User->>HomeAssistant: Configure Refoss Integration
    HomeAssistant->>RefossDevice: Discover via Zeroconf
    RefossDevice-->>HomeAssistant: Device Details
    HomeAssistant->>HomeAssistant: Create Entities
    HomeAssistant->>User: Integration Ready
    
    User->>RefossDevice: Interact with Device
    RefossDevice->>HomeAssistant: Trigger Events/State Changes
    HomeAssistant->>User: Update UI/Trigger Automations
Loading

Finishing Touches

  • 📝 Generate Docstrings

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 (6)
source/_integrations/refoss_rpc.markdown (6)

28-28: Enhance the introduction with more details

Consider expanding the introduction to include:

  • Brief explanation of what RPC protocol is
  • Key benefits of using this integration
  • Common use cases

34-36: Fix table formatting and clarify version support

  1. Remove trailing spaces in the table header line
  2. Consider specifying the actual firmware versions supported instead of using all
-| Model                            | Version            |             
-|----------------------------------|--------------------|
-| `Refoss Smart Wi-Fi Switch, R11` | `all`              |
+| Model                            | Version    |
+|----------------------------------|------------|
+| `Refoss Smart Wi-Fi Switch, R11` | `>=1.0.0` |
🧰 Tools
🪛 Markdownlint (0.37.0)

34-34: Expected: 0 or 2; Actual: 13
Trailing spaces

(MD009, no-trailing-spaces)


42-44: Add configuration examples

Consider adding YAML examples showing how the entity names appear in the actual configuration:

# Example when Channel Name is set to "Kitchen"
switch.kitchen_switch

# Example with default Channel Name
switch.r11_switch_1

47-47: Improve clarity and fix grammar

  1. Add missing article: "if the device's input"
  2. Consider adding details about how to configure input modes
-It's possible to select if a device's input is connected to a button or a switch. Binary sensors are created only if the input mode is set to `switch`. When the input mode is set to `button` you can use events for your automations.
+It's possible to select if the device's input is connected to a button or a switch. Binary sensors are created only if the input mode is set to `switch`. When the input mode is set to `button`, you can use events for your automations. You can configure the input mode through the device's configuration page in the Home Assistant UI.

51-61: Add YAML automation example

Consider adding a YAML automation example for users who prefer manual configuration:

automation:
  trigger:
    platform: event
    event_type: refoss.click
    event_data:
      device_id: YOUR_DEVICE_ID
      click_type: double_push
      button: Button1
  action:
    - service: light.toggle
      target:
        entity_id: light.example
🧰 Tools
🪛 LanguageTool

[uncategorized] ~51-~51: Possible missing article found.
Context: ...ts for your automations. ## Events If device's input mode is set to button, integr...

(AI_HYDRA_LEO_MISSING_THE)


70-80: Enhance device actions documentation

Consider adding more details for each action:

  1. Firmware update: Expected duration, network requirements, and potential risks
  2. Check latest firmware: Where to find the results
  3. Reboot: Expected downtime and impact on automations

Also, consider adding a troubleshooting section for common issues.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 29bcf7d and 59af7db.

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

[uncategorized] ~51-~51: Possible missing article found.
Context: ...ts for your automations. ## Events If device's input mode is set to button, integr...

(AI_HYDRA_LEO_MISSING_THE)

🪛 Markdownlint (0.37.0)
source/_integrations/refoss_rpc.markdown

34-34: Expected: 0 or 2; Actual: 13
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/_integrations/refoss_rpc.markdown (1)

11-11: Verify the release version

The release version is set to 2025.2. Please ensure this aligns with the planned release schedule. If this is intended for an earlier release, adjust accordingly.

@home-assistant home-assistant bot removed the needs-rebase The PR has been branched of the wrong base branch or targets an incorrect target branch label Jan 9, 2025
@ashionky ashionky marked this pull request as ready for review January 9, 2025 02:00
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/refoss_rpc.markdown (5)

34-34: Remove trailing spaces in the table header.

There are trailing spaces after the "Version" column header.

-| Model                            | Version            |             
+| Model                            | Version            |
🧰 Tools
🪛 Markdownlint (0.37.0)

34-34: Expected: 0 or 2; Actual: 13
Trailing spaces

(MD009, no-trailing-spaces)


28-28: Enhance the introduction with protocol details.

Consider providing more context about what the RPC protocol is and its benefits. This helps users understand the technical aspects of the integration.

-Integrate Refoss devices that support `RPC` protocol into Home Assistant.
+Integrate Refoss devices that support the `RPC` (Remote Procedure Call) protocol into Home Assistant. This protocol enables real-time, bidirectional communication between Home Assistant and Refoss devices over the local network.

34-37: Clarify version compatibility.

The version column states "all" which might be ambiguous. Consider specifying the minimum firmware version required for compatibility.

| Model                            | Version            |
|----------------------------------|--------------------|
-| `Refoss Smart Wi-Fi Switch, R11` | `all`              |
+| `Refoss Smart Wi-Fi Switch, R11` | `>= 1.0.0`         |
🧰 Tools
🪛 Markdownlint (0.37.0)

34-34: Expected: 0 or 2; Actual: 13
Trailing spaces

(MD009, no-trailing-spaces)


76-76: Fix grammar in firmware check description.

Add the missing article "the" for better readability.

-Trigger check latest firmware of device.
+Trigger check for the latest firmware of device.
🧰 Tools
🪛 LanguageTool

[uncategorized] ~76-~76: You might be missing the article “the” here.
Context: ...## Check latest firmware Trigger check latest firmware of device. ### Reboot Trigge...

(AI_EN_LECTOR_MISSING_DETERMINER_THE)


66-81: Add YAML examples for device actions.

Consider adding YAML examples for each device action to help users implement them in their automations.

Add examples like:

# Example automation for firmware update
automation:
  - alias: "Update R11 Firmware"
    trigger:
      - platform: time
        at: "03:00:00"
    action:
      - device_id: your_device_id
        domain: refoss_rpc
        type: check_firmware
      - device_id: your_device_id
        domain: refoss_rpc
        type: update_firmware
🧰 Tools
🪛 LanguageTool

[uncategorized] ~76-~76: You might be missing the article “the” here.
Context: ...## Check latest firmware Trigger check latest firmware of device. ### Reboot Trigge...

(AI_EN_LECTOR_MISSING_DETERMINER_THE)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 59af7db and c771556.

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

[uncategorized] ~76-~76: You might be missing the article “the” here.
Context: ...## Check latest firmware Trigger check latest firmware of device. ### Reboot Trigge...

(AI_EN_LECTOR_MISSING_DETERMINER_THE)

🪛 Markdownlint (0.37.0)
source/_integrations/refoss_rpc.markdown

34-34: Expected: 0 or 2; Actual: 13
Trailing spaces

(MD009, no-trailing-spaces)

⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Pages changed - home-assistant-docs
🔇 Additional comments (2)
source/_integrations/refoss_rpc.markdown (2)

40-44: LGTM! Clear naming strategy documentation.

The entity naming strategy is well documented with helpful examples.


25-25: Verify integration type classification.

The integration is classified as a device integration. Let's verify this matches the implementation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
has-parent This PR has a parent PR in a other repo in-progress This PR/Issue is currently being worked on next This PR goes into the next branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant