Skip to content

Documentation for new victron_ble integration #39829

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

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

Conversation

rajlaud
Copy link
Contributor

@rajlaud rajlaud commented Jul 3, 2025

Proposed change

Add documentation for a new integration, victron_ble.

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

Uses existing brands: home-assistant/brands#4182

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 Victron BLE integration, including setup instructions, device discovery, encryption key retrieval via the VictronConnect app, supported sensor features, and removal procedures.

@Copilot Copilot AI review requested due to automatic review settings July 3, 2025 12:42
@home-assistant home-assistant bot added has-parent This PR has a parent PR in a other repo 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 Jul 3, 2025
@home-assistant
Copy link

home-assistant bot commented Jul 3, 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.

Copy link

netlify bot commented Jul 3, 2025

Deploy Preview for home-assistant-docs ready!

Name Link
🔨 Latest commit 11d6c5b
🔍 Latest deploy log https://app.netlify.com/projects/home-assistant-docs/deploys/68669bd12b267e0007f5ec5a
😎 Deploy Preview https://deploy-preview-39829--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 project 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.

Pull Request Overview

Adds documentation for the new victron_ble integration, guiding users through setup, configuration, and removal.

  • Introduces victron_ble.markdown with frontmatter and integration overview
  • Details prerequisites for obtaining the device encryption key
  • Outlines removal steps and data update behavior
Comments suppressed due to low confidence (2)

source/_integrations/victron_ble.markdown:28

  • Use the correct casing for OS names according to brand guidelines: change [IOS] to [iOS] and [OSX] to [macOS].
The simplest method is to use the VictronConnect app ([Android](https://play.google.com/store/apps/details?id=com.victronenergy.victronconnect), [IOS](https://apps.apple.com/us/app/victron-connect/id943840744), [Linux](https://www.victronenergy.com/support-and-downloads/software#victronconnect-app), [OSX](https://apps.apple.com/us/app/victronconnect/id1084677271?ls=1&mt=12), [Windows](https://www.victronenergy.com/support-and-downloads/software#victronconnect-app)):

source/_integrations/victron_ble.markdown:28

  • [nitpick] Convert the inline list of OS links into a bullet list for better readability, since the items are non-sequential.
The simplest method is to use the VictronConnect app ([Android](https://play.google.com/store/apps/details?id=com.victronenergy.victronconnect), [IOS](https://apps.apple.com/us/app/victron-connect/id943840744), [Linux](https://www.victronenergy.com/support-and-downloads/software#victronconnect-app), [OSX](https://apps.apple.com/us/app/victronconnect/id1084677271?ls=1&mt=12), [Windows](https://www.victronenergy.com/support-and-downloads/software#victronconnect-app)):

Copy link
Contributor

coderabbitai bot commented Jul 3, 2025

📝 Walkthrough

"""

Walkthrough

A new documentation file for the Victron BLE integration has been added. This file details the setup, requirements, and usage instructions for integrating Victron Energy Bluetooth Low Energy devices with Home Assistant, including steps to obtain necessary encryption keys and information on supported features.

Changes

File(s) Change Summary
source/_integrations/victron_ble.markdown Added documentation for the new Victron BLE integration, including setup, configuration, encryption key retrieval, supported platforms, and removal instructions.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant HomeAssistant
    participant VictronDevice
    participant VictronConnectApp

    User->>HomeAssistant: Initiate Victron BLE integration setup
    HomeAssistant->>User: Prompt for encryption key
    User->>VictronConnectApp: Retrieve device encryption key
    VictronConnectApp-->>User: Provide encryption key
    User->>HomeAssistant: Enter encryption key
    HomeAssistant->>VictronDevice: Discover via BLE (Bluetooth integration required)
    VictronDevice-->>HomeAssistant: Broadcast sensor data (local push)
    HomeAssistant->>User: Display device and sensor states
Loading

"""


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge Base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between ca54498 and 11d6c5b.

📒 Files selected for processing (1)
  • source/_integrations/victron_ble.markdown (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • source/_integrations/victron_ble.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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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: 1

🧹 Nitpick comments (2)
source/_integrations/victron_ble.markdown (2)

30-30: Grammar nit: “setup” → “set up” (verb form)

-Install the **VictronConnect** app, ideally on the device you are using to setup this integration
+Install the **VictronConnect** app, ideally on the device you are using to set up this integration

46-47: Add a single trailing newline to satisfy MD047

The file currently has no newline at EOF, triggering markdown-lint.
Simply add \n after line 47.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge Base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between bba763e and 1d3f2c0.

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

[grammar] ~30-~30: The word “setup” is a noun. The verb is spelled with a white space.
Context: ... ideally on the device you are using to setup this integration so you can simply cut ...

(NOUN_VERB_CONFUSION)

🪛 markdownlint-cli2 (0.17.2)
source/_integrations/victron_ble.markdown

47-47: Files should end with a single newline character

(MD047, single-trailing-newline)

🪛 GitHub Actions: home-assistant.io Test
source/_integrations/victron_ble.markdown

[error] 28-28: textlint: Incorrect term: “OSX”, use “MacOS” instead (terminology)

⏰ 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

@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 Jul 3, 2025
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
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

♻️ Duplicate comments (1)
source/_integrations/victron_ble.markdown (1)

28-35: Insert a blank line before the ordered list + use the verb “set up”

Markdown-lint flags this block for missing blank lines around the list (MD032) and for the noun/verb confusion “setup” (LanguageTool). Apply the diff below to resolve both issues:

-The simplest method is to use the VictronConnect app ([Android](https://play.google.com/store/apps/details?id=com.victronenergy.victronconnect), [iOS](https://apps.apple.com/us/app/victron-connect/id943840744), [Linux](https://www.victronenergy.com/support-and-downloads/software#victronconnect-app), [macOS](https://apps.apple.com/us/app/victronconnect/id1084677271?ls=1&mt=12), [Windows](https://www.victronenergy.com/support-and-downloads/software#victronconnect-app)):
-1. Install the **VictronConnect** app, ideally on the device you are using to setup this integration so you can simply cut and paste the key.
+The simplest method is to use the VictronConnect app ([Android](https://play.google.com/store/apps/details?id=com.victronenergy.victronconnect), [iOS](https://apps.apple.com/us/app/victron-connect/id943840744), [Linux](https://www.victronenergy.com/support-and-downloads/software#victronconnect-app), [macOS](https://apps.apple.com/us/app/victronconnect/id1084677271?ls=1&mt=12), [Windows](https://www.victronenergy.com/support-and-downloads/software#victronconnect-app)):
+
+1. Install the **VictronConnect** app, ideally on the device you are using to set up this integration so you can simply cut and paste the key.
🧹 Nitpick comments (1)
source/_integrations/victron_ble.markdown (1)

46-46: Ensure file ends with a single trailing newline

markdownlint (MD047) expects exactly one newline at EOF. Add a newline character after the final period to satisfy this rule.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge Base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between 1d3f2c0 and 36e8719.

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

[grammar] ~29-~29: The word “setup” is a noun. The verb is spelled with a white space.
Context: ... ideally on the device you are using to setup this integration so you can simply cut ...

(NOUN_VERB_CONFUSION)

🪛 markdownlint-cli2 (0.17.2)
source/_integrations/victron_ble.markdown

29-29: Lists should be surrounded by blank lines

(MD032, blanks-around-lists)


46-46: Files should end with a single newline character

(MD047, single-trailing-newline)

⏰ 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

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
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 (3)
source/_integrations/victron_ble.markdown (3)

18-18: Avoid “BLE protocol” redundancy & expand acronym on first use

“BLE” already contains “Protocol”; expand on first mention for clarity and drop the extra word.

-Integrates Victron Energy devices that support the BLE protocol into Home Assistant.
+Integrates Victron Energy devices that support Bluetooth Low Energy (BLE) into Home Assistant.

28-29: Insert a blank line before the ordered list to satisfy MD032

Markdown-lint is flagging blanks-around-lists. Add an empty line after the colon.

-...VictronConnect app (...):
-1. Install the **VictronConnect** app, ideally on the device you are using to set up this integration so you can simply cut and paste the key.
+...VictronConnect app (...):
+
+1. Install the **VictronConnect** app, ideally on the device you are using to set up this integration so you can simply cut and paste the key.

45-46: Ensure file ends with a single trailing newline (MD047)

Add one newline character at EOF to keep tooling and linters happy.

-as often as the updates are received.
+
+as often as the updates are received.
+
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge Base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between 36e8719 and b8df472.

📒 Files selected for processing (1)
  • source/_integrations/victron_ble.markdown (1 hunks)
🧰 Additional context used
🪛 markdownlint-cli2 (0.17.2)
source/_integrations/victron_ble.markdown

29-29: Lists should be surrounded by blank lines

(MD032, blanks-around-lists)


46-46: Files should end with a single newline character

(MD047, single-trailing-newline)

⏰ 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

@c0ffeeca7 c0ffeeca7 added the new-integration This PR adds documentation for a new Home Assistant integration label Jul 3, 2025
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

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge Base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between b8df472 and ca54498.

📒 Files selected for processing (1)
  • source/_integrations/victron_ble.markdown (1 hunks)
🧰 Additional context used
🪛 markdownlint-cli2 (0.17.2)
source/_integrations/victron_ble.markdown

29-29: Lists should be surrounded by blank lines

(MD032, blanks-around-lists)

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

7-8: Double-check the target release identifier
ha_release: '2025.8' assumes the August 2025 version exists and will include this integration. Please verify the correct release tag (e.g., 2025.7 or 2025.9) before merge to avoid broken links in the generated docs.

c0ffeeca7 and others added 2 commits July 3, 2025 16:38
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>

## Adding a device

To configure a discovered device, you will need to supply the per-device encryption key. For more information, see these [instructions](https://github.com/keshavdv/victron-ble/tree/main#fetching-keys).
Copy link
Contributor

Choose a reason for hiding this comment

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

does it mean without the app, I cannot use the integration in Home Assistant?

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

2 participants