Skip to content

Madvr#33401

Closed
iloveicedgreentea wants to merge 17 commits into
home-assistant:nextfrom
iloveicedgreentea:madvr
Closed

Madvr#33401
iloveicedgreentea wants to merge 17 commits into
home-assistant:nextfrom
iloveicedgreentea:madvr

Conversation

@iloveicedgreentea
Copy link
Copy Markdown
Contributor

@iloveicedgreentea iloveicedgreentea commented Jun 25, 2024

Proposed change

This adds documentation for the upcoming madvr integration

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

  • New Features

    • Introduced integration for madVR Envy devices in Home Assistant, supporting commands, binary sensors, and sensors for device control and automation.
  • Changes

    • Updated Jewish calendar integration: weekly_portion is now parshat_hashavua and omer_count is now day_of_the_omer.
    • Removed strict_connection parameter from the ssl_profile configuration.
    • Provided updated error handling and messaging for UniFi Protect integration.
    • Added new binary sensor for Ethernet status and troubleshooting section in Verisure integration.
    • Improved warnings and error messages related to Zigbee Coordinator stability in ZHA integration.

@home-assistant home-assistant Bot added has-parent This PR has a parent PR in another repo next This PR goes into the next branch labels Jun 25, 2024
@netlify
Copy link
Copy Markdown

netlify Bot commented Jun 25, 2024

Deploy Preview for home-assistant-docs ready!

Name Link
🔨 Latest commit 9fd5dc1
🔍 Latest deploy log https://app.netlify.com/sites/home-assistant-docs/deploys/668b4231568d0700083af967
😎 Deploy Preview https://deploy-preview-33401--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.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Jun 25, 2024

Walkthrough

Walkthrough

This update involves several major and minor changes across multiple integrations, as well as the removal of specific extensions. New features were introduced, including support for madVR Envy devices and detailed monitoring metrics for Prometheus. Additionally, there were name changes for sensors in the Jewish calendar integration, modifications in error messaging for UniFi Protect, and additions to Verisure and ZHA integrations. These changes aim to enhance clarity, improve functionality, and ensure better reliability and monitoring capabilities.

Changes

Files Change Summary
.devcontainer/devcontainer.json Removed the "Shopify.ruby-lsp" extension from the list of extensions.
source/_integrations/http.markdown Removed the strict_connection parameter from the ssl_profile configuration.
source/_integrations/jewish_calendar.markdown Renamed sensors: weekly_portion to parshat_hashavua and omer_count to day_of_the_omer.
source/_integrations/madvr.markdown Added integration instructions for madVR Envy devices, including commands, binary sensors, and various monitoring sensors.
source/_integrations/prometheus.markdown Added section on supported metrics for specific domains in the Prometheus integration.
source/_integrations/unifiprotect.markdown Altered error message namespace from pyunifiprotect.NvrError to uiprotect.NvrError.
source/_integrations/verisure.markdown Added option_flow section, new binary sensor for Ethernet status, and troubleshooting section for lock code errors.
source/_integrations/zha.markdown Updated warning on Zigbee Coordinator use over unstable connections and added details on NCP entered failed state error.

Sequence Diagram(s)

Changes are too varied to generate a single comprehensive sequence diagram.


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>.
    • 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 generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @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 as 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 resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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
Copy Markdown
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: 2

Outside diff range comments (17)
source/_integrations/http.markdown (15)

Line range hint 35-35: Consider revising the preposition for clarity.

The phrase "By default the http integration auto-detects..." might be clearer with a comma after "By default," to improve readability.

- By default the `http` integration auto-detects...
+ By default, the `http` integration auto-detects...
Tools
LanguageTool

[typographical] ~86-~86: This sentence does not start with an uppercase letter. (UPPERCASE_SENTENCE_START)
Context: ...rations causing SSL handshake errors. required: false type: string default: modern...


[misspelling] ~89-~89: Possible spelling mistake found. (MORFOLOGIK_RULE_EN_US)
Context: ...lse type: string default: modern {% endconfiguration %} The sample below shows a configurat...


Line range hint 41-41: Start the sentence with an uppercase letter.

The sentence beginning with "Let you set a port to use." should start with an uppercase letter to maintain consistency and proper grammar in documentation.

- Let you set a port to use.
+ Let you set a port to use.
Tools
LanguageTool

[typographical] ~86-~86: This sentence does not start with an uppercase letter. (UPPERCASE_SENTENCE_START)
Context: ...rations causing SSL handshake errors. required: false type: string default: modern...


[misspelling] ~89-~89: Possible spelling mistake found. (MORFOLOGIK_RULE_EN_US)
Context: ...lse type: string default: modern {% endconfiguration %} The sample below shows a configurat...


Line range hint 45-45: Grammar improvement: Use gerund form with 'recommend'.

The phrase "We recommend to use the [NGINX add-on]" should use the gerund form 'using' to be grammatically correct.

- We recommend to use the [NGINX add-on]
+ We recommend using the [NGINX add-on]
Tools
LanguageTool

[typographical] ~86-~86: This sentence does not start with an uppercase letter. (UPPERCASE_SENTENCE_START)
Context: ...rations causing SSL handshake errors. required: false type: string default: modern...


[misspelling] ~89-~89: Possible spelling mistake found. (MORFOLOGIK_RULE_EN_US)
Context: ...lse type: string default: modern {% endconfiguration %} The sample below shows a configurat...


Line range hint 50-50: Start the sentence with an uppercase letter.

The description under ssl_key should start with an uppercase letter for consistency and readability.

- description: Path to your TLS/SSL key to serve Home Assistant over a secure connection.
+ Description: Path to your TLS/SSL key to serve Home Assistant over a secure connection.
Tools
LanguageTool

[typographical] ~86-~86: This sentence does not start with an uppercase letter. (UPPERCASE_SENTENCE_START)
Context: ...rations causing SSL handshake errors. required: false type: string default: modern...


[misspelling] ~89-~89: Possible spelling mistake found. (MORFOLOGIK_RULE_EN_US)
Context: ...lse type: string default: modern {% endconfiguration %} The sample below shows a configurat...


Line range hint 54-54: Start the sentence with an uppercase letter.

The description under cors_allowed_origins should start with an uppercase letter for consistency and readability.

- description: "A list of origin domain names to allow [CORS](https://en.wikipedia.org/wiki/Cross-origin_resource_sharing) requests from...
+ Description: "A list of origin domain names to allow [CORS](https://en.wikipedia.org/wiki/Cross-origin_resource_sharing) requests from...
Tools
LanguageTool

[typographical] ~86-~86: This sentence does not start with an uppercase letter. (UPPERCASE_SENTENCE_START)
Context: ...rations causing SSL handshake errors. required: false type: string default: modern...


[misspelling] ~89-~89: Possible spelling mistake found. (MORFOLOGIK_RULE_EN_US)
Context: ...lse type: string default: modern {% endconfiguration %} The sample below shows a configurat...


Line range hint 60-60: Remove unnecessary colon for grammatical correctness.

The description of use_x_forwarded_for ends with a colon before a series introduced by a preposition, which is grammatically incorrect.

- Enable parsing of the `X-Forwarded-For` header, passing on the client's correct IP address in proxied setups:
+ Enable parsing of the `X-Forwarded-For` header, passing on the client's correct IP address in proxied setups.
Tools
LanguageTool

[typographical] ~86-~86: This sentence does not start with an uppercase letter. (UPPERCASE_SENTENCE_START)
Context: ...rations causing SSL handshake errors. required: false type: string default: modern...


[misspelling] ~89-~89: Possible spelling mistake found. (MORFOLOGIK_RULE_EN_US)
Context: ...lse type: string default: modern {% endconfiguration %} The sample below shows a configurat...


Line range hint 71-71: Consider adding a comma for clarity.

The sentence "Therefore in a reverse proxy scenario, this option should be set with extreme care." might be clearer with a comma after "Therefore," to improve readability.

- Therefore in a reverse proxy scenario, this option should be set with extreme care.
+ Therefore, in a reverse proxy scenario, this option should be set with extreme care.
Tools
LanguageTool

[typographical] ~86-~86: This sentence does not start with an uppercase letter. (UPPERCASE_SENTENCE_START)
Context: ...rations causing SSL handshake errors. required: false type: string default: modern...


[misspelling] ~89-~89: Possible spelling mistake found. (MORFOLOGIK_RULE_EN_US)
Context: ...lse type: string default: modern {% endconfiguration %} The sample below shows a configurat...


Line range hint 76-76: Start the sentence with an uppercase letter.

The description under ip_ban_enabled should start with an uppercase letter for consistency and readability.

- description: Flag indicating whether additional IP filtering is enabled.
+ Description: Flag indicating whether additional IP filtering is enabled.
Tools
LanguageTool

[typographical] ~86-~86: This sentence does not start with an uppercase letter. (UPPERCASE_SENTENCE_START)
Context: ...rations causing SSL handshake errors. required: false type: string default: modern...


[misspelling] ~89-~89: Possible spelling mistake found. (MORFOLOGIK_RULE_EN_US)
Context: ...lse type: string default: modern {% endconfiguration %} The sample below shows a configurat...


Line range hint 80-80: Consider adding a comma for clarity.

The sentence "Number of failed login attempt from single IP after which it will be automatically banned if ip_ban_enabled is true." might be clearer with a comma after "IP," to improve readability.

- Number of failed login attempt from single IP after which it will be automatically banned if `ip_ban_enabled` is `true`.
+ Number of failed login attempt from single IP, after which it will be automatically banned if `ip_ban_enabled` is `true`.
Tools
LanguageTool

[typographical] ~86-~86: This sentence does not start with an uppercase letter. (UPPERCASE_SENTENCE_START)
Context: ...rations causing SSL handshake errors. required: false type: string default: modern...


[misspelling] ~89-~89: Possible spelling mistake found. (MORFOLOGIK_RULE_EN_US)
Context: ...lse type: string default: modern {% endconfiguration %} The sample below shows a configurat...


Line range hint 134-134: Use consistent strong style in Markdown.

The Markdown syntax for strong emphasis should be consistent. Replace asterisks with underscores for strong emphasis to align with the expected style.

- **User profile**
+ __User profile__
Tools
LanguageTool

[typographical] ~86-~86: This sentence does not start with an uppercase letter. (UPPERCASE_SENTENCE_START)
Context: ...rations causing SSL handshake errors. required: false type: string default: modern...


[misspelling] ~89-~89: Possible spelling mistake found. (MORFOLOGIK_RULE_EN_US)
Context: ...lse type: string default: modern {% endconfiguration %} The sample below shows a configurat...


Line range hint 147-147: Consider adding a comma for clarity.

The sentence "After a ban is added a Persistent Notification is populated to the Home Assistant frontend." might be clearer with a comma after "added," to improve readability.

- After a ban is added a Persistent Notification is populated to the Home Assistant frontend.
+ After a ban is added, a Persistent Notification is populated to the Home Assistant frontend.
Tools
LanguageTool

[typographical] ~86-~86: This sentence does not start with an uppercase letter. (UPPERCASE_SENTENCE_START)
Context: ...rations causing SSL handshake errors. required: false type: string default: modern...


[misspelling] ~89-~89: Possible spelling mistake found. (MORFOLOGIK_RULE_EN_US)
Context: ...lse type: string default: modern {% endconfiguration %} The sample below shows a configurat...


Line range hint 169-169: Consider adding a comma for clarity.

The sentence "After a restart of Home Assistant the sensor will be gone until it is triggered again." might be clearer with a comma after "Assistant," to improve readability.

- After a restart of Home Assistant the sensor will be gone until it is triggered again.
+ After a restart of Home Assistant, the sensor will be gone until it is triggered again.
Tools
LanguageTool

[typographical] ~86-~86: This sentence does not start with an uppercase letter. (UPPERCASE_SENTENCE_START)
Context: ...rations causing SSL handshake errors. required: false type: string default: modern...


[misspelling] ~89-~89: Possible spelling mistake found. (MORFOLOGIK_RULE_EN_US)
Context: ...lse type: string default: modern {% endconfiguration %} The sample below shows a configurat...


Line range hint 187-187: Consider adding a comma for clarity.

The sentence "For a quick test curl can be useful to 'simulate' a device." might be clearer with a comma after "test," to improve readability.

- For a quick test `curl` can be useful to "simulate" a device.
+ For a quick test, `curl` can be useful to "simulate" a device.
Tools
LanguageTool

[typographical] ~86-~86: This sentence does not start with an uppercase letter. (UPPERCASE_SENTENCE_START)
Context: ...rations causing SSL handshake errors. required: false type: string default: modern...


[misspelling] ~89-~89: Possible spelling mistake found. (MORFOLOGIK_RULE_EN_US)
Context: ...lse type: string default: modern {% endconfiguration %} The sample below shows a configurat...


Line range hint 222-222: Consider adding a comma for clarity.

The sentence "In this section you'll find some real-life examples of how to use this sensor, besides curl, which was shown earlier." might be clearer with a comma after "sensor," to improve readability.

- In this section you'll find some real-life examples of how to use this sensor, besides `curl`, which was shown earlier.
+ In this section, you'll find some real-life examples of how to use this sensor, besides `curl`, which was shown earlier.
Tools
LanguageTool

[typographical] ~86-~86: This sentence does not start with an uppercase letter. (UPPERCASE_SENTENCE_START)
Context: ...rations causing SSL handshake errors. required: false type: string default: modern...


[misspelling] ~89-~89: Possible spelling mistake found. (MORFOLOGIK_RULE_EN_US)
Context: ...lse type: string default: modern {% endconfiguration %} The sample below shows a configurat...


Line range hint 242-242: Start the sentence with an uppercase letter.

The description under the httpie example should start with an uppercase letter for consistency and readability.

- `httpie` is a user-friendly CLI HTTP client.
+ `httpie` is a user-friendly CLI HTTP client.
Tools
LanguageTool

[typographical] ~86-~86: This sentence does not start with an uppercase letter. (UPPERCASE_SENTENCE_START)
Context: ...rations causing SSL handshake errors. required: false type: string default: modern...


[misspelling] ~89-~89: Possible spelling mistake found. (MORFOLOGIK_RULE_EN_US)
Context: ...lse type: string default: modern {% endconfiguration %} The sample below shows a configurat...

source/_integrations/zha.markdown (2)

Line range hint 343-346: Markdown Linting Issues

There are several markdown linting issues related to unordered list indentation and trailing spaces that should be addressed to comply with best practices.

-  - Silicon Labs EmberZNet based radios using the EZSP protocol (via the [bellows](https://github.com/zigpy/bellows) library for zigpy)
+ - Silicon Labs EmberZNet based radios using the EZSP protocol (via the [bellows](https://github.com/zigpy/bellows) library for zigpy)
-  - Texas Instruments based radios (via the [zigpy-znp](https://github.com/zigpy/zigpy-znp) library for zigpy)
+ - Texas Instruments based radios (via the [zigpy-znp](https://github.com/zigpy/zigpy-znp) library for zigpy)
-    - [CC2652P/CC2652R/CC2652RB USB stick, module, or dev board hardware flashed with Z-Stack coordinator firmware](https://www.zigbee2mqtt.io/guide/adapters/)
+   - [CC2652P/CC2652R/CC2652RB USB stick, module, or dev board hardware flashed with Z-Stack coordinator firmware](https://www.zigbee2mqtt.io/guide/adapters/)
-    - [CC1352P/CC1352R USB stick, module, or dev board hardware flashed with Z-Stack coordinator firmware](https://www.zigbee2mqtt.io/guide/adapters/)
+   - [CC1352P/CC1352R USB stick, module, or dev board hardware flashed with Z-Stack coordinator firmware](https://www.zigbee2mqtt.io/guide/adapters/)
-  - dresden elektronik deCONZ based Zigbee radios (via the [zigpy-deconz](https://github.com/zigpy/zigpy-deconz) library for zigpy)
+ - dresden elektronik deCONZ based Zigbee radios (via the [zigpy-deconz](https://github.com/zigpy/zigpy-deconz) library for zigpy)

Also applies to: 534-535, 546-554, 638-638

Tools
Markdownlint

138-138: Element: div (MD033, no-inline-html)
Inline HTML


Line range hint 282-282: Inconsistent Emphasis Style

The document uses asterisks for emphasis instead of underscores, which is inconsistent with the expected markdown style. It's recommended to use underscores for emphasis to maintain consistency across the documentation.

- *text*
+ _text_

Also applies to: 393-393

Tools
Markdownlint

138-138: Element: div (MD033, no-inline-html)
Inline HTML

Comment thread source/_integrations/zha.markdown Outdated
#### Warning about Wi-Fi-based Zigbee-to-Serial bridges/gateways
#### Warning about using Zigbee Coordinator over Wi-Fi/WAN/VPN

<div class="note warning">
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Usage of Inline HTML

The use of inline HTML <div> tags is generally discouraged in markdown files as it can lead to issues with portability and rendering on different platforms. Consider using markdown syntax for notes and warnings instead.

- <div class="note warning">
+ **Warning:**
- </div>
+ _End of Warning_

Also applies to: 234-234, 340-340, 431-431

Tools
Markdownlint

138-138: Element: div (MD033, no-inline-html)
Inline HTML

@@ -86,11 +86,6 @@ ssl_profile:
required: false
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Start the sentence with an uppercase letter.

The description under ssl_profile should start with an uppercase letter for consistency and readability.

- description: The [Mozilla SSL profile](https://wiki.mozilla.org/Security/Server_Side_TLS) to use.
+ Description: The [Mozilla SSL profile](https://wiki.mozilla.org/Security/Server_Side_TLS) to use.

Committable suggestion was skipped due to low confidence.

Tools
LanguageTool

[typographical] ~86-~86: This sentence does not start with an uppercase letter. (UPPERCASE_SENTENCE_START)
Context: ...rations causing SSL handshake errors. required: false type: string default: modern...

@frenck frenck added the parent-merged The parent PR has been merged already label Jul 7, 2024
Copy link
Copy Markdown
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

Comment thread source/_integrations/madvr.markdown Outdated
Comment thread source/_integrations/madvr.markdown Outdated
Comment thread source/_integrations/madvr.markdown Outdated
Copy link
Copy Markdown
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: 2

Comment thread source/_integrations/madvr.markdown Outdated
Comment thread source/_integrations/madvr.markdown Outdated
@frenck
Copy link
Copy Markdown
Member

frenck commented Jul 8, 2024

Please revert the changes of other parent PRs, these will need their own separate PRs once this one is merged.

There are also unrelated changes in this PR that must be removed. This Pr should only cover the adding of the initial Core PR.

../Frenck

Copy link
Copy Markdown
Member

@frenck frenck left a comment

Choose a reason for hiding this comment

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

As per above.

@home-assistant home-assistant Bot marked this pull request as draft July 8, 2024 01:08
@home-assistant
Copy link
Copy Markdown

home-assistant Bot commented Jul 8, 2024

Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍

Learn more about our pull request process.

@iloveicedgreentea
Copy link
Copy Markdown
Contributor Author

I have no idea what happened here but this is a mess. Will close and open a new PR.

@home-assistant home-assistant Bot removed the parent-merged The parent PR has been merged already label Jul 8, 2024
@iloveicedgreentea
Copy link
Copy Markdown
Contributor Author

corrected PR #33626

@github-actions github-actions Bot locked and limited conversation to collaborators Jul 9, 2024
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 another repo next This PR goes into the next branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.