Skip to content

Add Rehlko (formerly Kohler Energy Management) integration #38782

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 14 commits into from
Apr 30, 2025

Conversation

PeteRager
Copy link
Contributor

@PeteRager PeteRager commented Apr 28, 2025

Proposed change

Add documentation for the new Rehlko integration.

Kohler Energy was been split off into a new brand called Rehlko. Some of the branding is still Kohler Energy. The Oncue brand and integration has been retried as well.

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 new documentation for the Rehlko integration, detailing setup, configuration, and supported features for monitoring Kohler generators via Home Assistant. Includes authentication requirements, sensor availability notes, and links to relevant generator model datasheets.

@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 Apr 28, 2025
@PeteRager PeteRager marked this pull request as draft April 28, 2025 11:24
Copy link

netlify bot commented Apr 28, 2025

Deploy Preview for home-assistant-docs ready!

Name Link
🔨 Latest commit 236e46d
🔍 Latest deploy log https://app.netlify.com/sites/home-assistant-docs/deploys/681205971d363a00084e97b1
😎 Deploy Preview https://deploy-preview-38782--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 Apr 28, 2025

📝 Walkthrough

Walkthrough

A new documentation file has been added for the Rehlko integration in Home Assistant. This documentation outlines support for monitoring Kohler generators via the Rehlko platform, details the required configuration steps, including authentication with user credentials, and explains the cloud polling nature of the integration. The document also provides setup instructions, configuration parameters, and references to supported generator models and their datasheets.

Changes

File(s) Change Summary
source/_integrations/rehlko.markdown Added new documentation for the Rehlko integration, including setup, configuration, and model support.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant HomeAssistant
    participant RehlkoCloud
    participant Generator

    User->>HomeAssistant: Initiate Rehlko integration setup
    HomeAssistant->>User: Prompt for email and password
    User->>HomeAssistant: Provide credentials
    HomeAssistant->>RehlkoCloud: Authenticate with credentials
    RehlkoCloud-->>HomeAssistant: Authentication response
    HomeAssistant->>RehlkoCloud: Poll for generator data
    RehlkoCloud->>Generator: Retrieve sensor data
    Generator-->>RehlkoCloud: Send sensor data
    RehlkoCloud-->>HomeAssistant: Return generator data
    HomeAssistant-->>User: Display generator sensor status
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 63094d8 and 236e46d.

📒 Files selected for processing (1)
  • source/_integrations/rehlko.markdown (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • source/_integrations/rehlko.markdown
⏰ 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

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.

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

🧹 Nitpick comments (4)
source/_integrations/kem.markdown (4)

21-21: Improve grammar and terminology in configuration instructions.

Add a comma after “integration” and use the noun “login” for credentials.

--- a/source/_integrations/kem.markdown
+++ b/source/_integrations/kem.markdown
@@
- To configure the integration you will need your log in credentials (email and password) for the Kohler app.
+ To configure the integration, you will need your login credentials (email and password) for the Kohler app.
🧰 Tools
🪛 LanguageTool

[typographical] ~21-~21: It seems that a comma is missing.
Context: ...he Oncue integration. To configure the integration you will need your log in credentials (...

(IN_ORDER_TO_VB_COMMA)


[grammar] ~21-~21: Did you mean the noun “login” instead of the verb ‘to log in’?
Context: ...gure the integration you will need your log in credentials (email and password) for th...

(PREPOSITION_VERB)


23-23: Fix spelling of “available.”

Correct the typo in “avaiable.”

--- a/source/_integrations/kem.markdown
+++ b/source/_integrations/kem.markdown
@@
- Note: The set of sensors avaiable depends on the specific instrumentation installed on your generator and transfer switch. There is wide variation within the same model.
+ Note: The set of sensors available depends on the specific instrumentation installed on your generator and transfer switch. There is wide variation within the same model.

27-27: Correct typo and improve phrasing for tested generators.

Fix “geneator” → “generator” and reword for clarity.

--- a/source/_integrations/kem.markdown
+++ b/source/_integrations/kem.markdown
@@
- There are the geneator models that have been tested.
+ These are the generator models that have been tested.

33-34: Ensure the include snippet is on its own line and file ends with a newline.

Add a trailing newline if missing to comply with POSIX conventions.

--- a/source/_integrations/kem.markdown
+++ b/source/_integrations/kem.markdown
@@ 32,34c32,35
- {% include integrations/config_flow.md %}
+ 
+ {% include integrations/config_flow.md %}
+
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 3bbb6c9 and a43a19f.

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

[typographical] ~21-~21: It seems that a comma is missing.
Context: ...he Oncue integration. To configure the integration you will need your log in credentials (...

(IN_ORDER_TO_VB_COMMA)


[grammar] ~21-~21: Did you mean the noun “login” instead of the verb ‘to log in’?
Context: ...gure the integration you will need your log in credentials (email and password) for th...

(PREPOSITION_VERB)

⏰ 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

@bdraco bdraco changed the title feat: add kohler energy management Add Rehlko integration Apr 30, 2025
@bdraco bdraco changed the title Add Rehlko integration Add Rehlko (formerly Kohler Energy Management) integration Apr 30, 2025
@home-assistant home-assistant bot added the parent-merged The parent PR has been merged already label Apr 30, 2025
@bdraco bdraco marked this pull request as ready for review April 30, 2025 10:44
@c0ffeeca7 c0ffeeca7 added the new-integration This PR adds documentation for a new Home Assistant integration label Apr 30, 2025
c0ffeeca7
c0ffeeca7 previously approved these changes Apr 30, 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, @PeteRager 👍

@c0ffeeca7 c0ffeeca7 merged commit 30abc40 into home-assistant:next Apr 30, 2025
7 checks passed
@home-assistant home-assistant bot removed the parent-merged The parent PR has been merged already label Apr 30, 2025
@github-actions github-actions bot locked and limited conversation to collaborators May 1, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
has-parent This PR has a parent PR in a other repo new-integration This PR adds documentation for a new Home Assistant integration next This PR goes into the next branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants