Z-Wave JS: remove from Home Assistant #39475
Conversation
✅ Deploy Preview for home-assistant-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
📝 WalkthroughWalkthroughA new section has been added to the Z-Wave JS integration documentation in Home Assistant. This section provides detailed, step-by-step instructions for completely removing Z-Wave JS from a Home Assistant setup, including device exclusion, add-on uninstallation, integration deletion, and final confirmation steps. Changes
Sequence Diagram(s)sequenceDiagram
participant User
participant HomeAssistant_UI
participant Supervisor_Addon_Interface
participant ZWave_Network
User->>ZWave_Network: Exclude or factory reset each device
User->>HomeAssistant_UI: Delete Z-Wave JS integration
HomeAssistant_UI-->>User: Confirm removal
User->>Supervisor_Addon_Interface: Uninstall Z-Wave JS add-on
Supervisor_Addon_Interface-->>User: Option to delete or keep data
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (1)
✅ Files skipped from review due to trivial changes (1)
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. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed 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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (3)
source/_integrations/zwave_js.markdown (3)
1066-1070: Consistent section introduction tone
The phrase “Do this if you no longer want to use Z-Wave JS in your Home Assistant” feels informal compared to the passive/instructional voice used elsewhere. Consider rephrasing to:If you no longer want to use Z-Wave JS in Home Assistant, follow these steps:
1070-1076: Normalize nested list indentation
The nested bullets under step 1 are indented with three spaces. Standard Markdown lists use two spaces for nested items. For example:- - Do this for each device that is joined… + - Do this for each device that is joined…
1083-1083: Remove trailing whitespace
There’s an extra space at the end of this line (…{% icon "mdi:dots-vertical" %} menu.) which triggers markdownlint MD009. Please delete the trailing space after the period.🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
1083-1083: Trailing spaces
Expected: 0 or 2; Actual: 1(MD009, no-trailing-spaces)
📜 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
📒 Files selected for processing (1)
source/_integrations/zwave_js.markdown(1 hunks)
🧰 Additional context used
🪛 markdownlint-cli2 (0.17.2)
source/_integrations/zwave_js.markdown
1083-1083: Trailing spaces
Expected: 0 or 2; Actual: 1
(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
Proposed change
Type of change
currentbranch).currentbranch).nextbranch).nextbranch).Additional information
Checklist
currentbranch.nextbranch.Summary by CodeRabbit