-
-
Notifications
You must be signed in to change notification settings - Fork 7.7k
Z-Wave update steps on adding controller #39483
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
Z-Wave update steps on adding controller #39483
Conversation
β Deploy Preview for home-assistant-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
π WalkthroughWalkthroughThe documentation for setting up the Z-Wave JS server in Home Assistant was updated to clarify the dongle recognition and installation steps, provide more detailed instructions, and adjust the language regarding network security key prompts. The troubleshooting note was reorganized under a new label. Changes
Sequence Diagram(s)sequenceDiagram
participant User
participant HomeAssistantUI
participant ZWaveDongle
participant ZWaveJSAddon
User->>HomeAssistantUI: Start Z-Wave JS server setup
HomeAssistantUI->>ZWaveDongle: Detect dongle
ZWaveDongle-->>HomeAssistantUI: Dongle recognized
HomeAssistantUI->>User: Prompt for "Recommended installation"
User->>HomeAssistantUI: Select "Recommended installation"
HomeAssistantUI->>ZWaveJSAddon: Install add-on
HomeAssistantUI->>User: Add device to area
User->>HomeAssistantUI: Select area and "Finish"
HomeAssistantUI->>User: (Optional) Prompt for network security keys
User->>HomeAssistantUI: Enter keys if prompted
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.
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 (1)
source/_integrations/zwave_js.markdown (1)
119-119
: Use consistent ordered-list prefixes to satisfy MD029The
4.
prefix on this list item triggers a markdownlint MD029 warning. To leverage automatic numbering and avoid linter errors, use1.
for every ordered item:- 4. Depending on your Home Assistant version, you may be prompted for network security keys. + 1. Depending on your Home Assistant version, you may be prompted for network security keys.π§° Tools
πͺ markdownlint-cli2 (0.17.2)
119-119: Ordered list item prefix
Expected: 2; Actual: 4; Style: 1/2/3(MD029, ol-prefix)
π 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
(2 hunks)
π§° Additional context used
πͺ markdownlint-cli2 (0.17.2)
source/_integrations/zwave_js.markdown
119-119: Ordered list item prefix
Expected: 2; Actual: 4; Style: 1/2/3
(MD029, ol-prefix)
β° Context from checks skipped due to timeout of 90000ms (4)
- GitHub Check: Redirect rules - home-assistant-docs
- GitHub Check: Header rules - home-assistant-docs
- GitHub Check: Pages changed - home-assistant-docs
- GitHub Check: Lint Text
π Additional comments (1)
source/_integrations/zwave_js.markdown (1)
98-102
: Inconsistent summary: troubleshooting note not promoted to a section headingThe AI summary states that the troubleshooting note was moved under a new "Troubleshooting" label, but here it remains a bolded bullet. Consider converting this into a proper subheading (e.g.,
#### Troubleshooting
) to match the documented intent and improve scan-ability.Likely an incorrect or invalid review comment.
Proposed change
Type of change
current
branch).current
branch).next
branch).next
branch).Additional information
Checklist
current
branch.next
branch.Summary by CodeRabbit