Skip to content

Z-Wave controllers: rename to adapter #39806

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
Jul 3, 2025
Merged

Conversation

c0ffeeca7
Copy link
Contributor

@c0ffeeca7 c0ffeeca7 commented Jul 2, 2025

Proposed 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
    • Updated terminology in Z-Wave documentation to use "adapter" instead of "controller" or "stick" for improved consistency.
    • Renamed sections and refined recommendations to emphasize 800-series adapters as the preferred hardware.
    • Clarified wording and updated notes for better user guidance without altering technical instructions.

@Copilot Copilot AI review requested due to automatic review settings July 2, 2025 09:15
@home-assistant
Copy link

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

@home-assistant home-assistant bot added 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 2, 2025
Copy link

netlify bot commented Jul 2, 2025

Deploy Preview for home-assistant-docs ready!

Name Link
🔨 Latest commit c2671b6
🔍 Latest deploy log https://app.netlify.com/projects/home-assistant-docs/deploys/6866158d2010220008c44846
😎 Deploy Preview https://deploy-preview-39806--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

This PR renames references from “Z-Wave controllers” to “Z-Wave adapters” in the documentation, updating titles, headings, and content to reflect the new terminology.

  • Updated the frontmatter title and main headings to use “adapters” instead of “controllers”
  • Replaced all inline mentions of “controllers” with “adapters” in lists and paragraphs
  • Adjusted the “Stick alternatives” section header to “Stick or module alternatives” and the “Controller notes” section to “Adapter notes”
Comments suppressed due to low confidence (2)

source/_docs/z-wave/controllers.markdown:76

  • This line was converted from a list item to a paragraph when renaming controllers to adapters. Consider restoring the leading "- " so it remains part of the bullet list.
If you are just starting out, we recommend that you purchase a 700 series adapter or a Raspberry Pi module. The 700 series adapters are the more recent version (when compared to the 500 series). The 700 series adapters support SmartStart, which allows you to add a device by scanning a QR code.

source/_docs/z-wave/controllers.markdown:1

  • Since the document now refers to "adapters" throughout, consider renaming the file from controllers.markdown to adapters.markdown for consistency.
---

Copy link
Contributor

coderabbitai bot commented Jul 2, 2025

📝 Walkthrough

"""

Walkthrough

The documentation for Z-Wave hardware was updated to consistently use the term "adapter" instead of "controller" or "stick." This includes changes to titles, section headers, warnings, notes, and device lists. The recommended starting hardware was updated to emphasize 800-series adapters with firmware version 7.23.2 or higher. No technical instructions, upgrade procedures, or device lists beyond terminology and recommendations were changed.

Changes

File(s) Change Summary
source/_docs/z-wave/controllers.markdown Replaced "controller," "stick," and "module" with "adapter" throughout; updated titles, headers, warnings, notes, and recommendations to emphasize 800-series adapters (firmware ≥ 7.23.2) and clarify fallback options with third-party hubs.

Sequence Diagram(s)

No sequence diagram generated as the changes are limited to documentation terminology updates.
"""


📜 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 af709a1 and c2671b6.

📒 Files selected for processing (1)
  • source/_docs/z-wave/controllers.markdown (4 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • source/_docs/z-wave/controllers.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: 0

🧹 Nitpick comments (4)
source/_docs/z-wave/controllers.markdown (4)

3-3: Fix grammatical issue in the description sentence
“Extended instructions how to setup Z-Wave.” is ungrammatical. Use “Extended instructions on how to set up Z-Wave.”

-description: "Extended instructions how to setup Z-Wave."
+description: "Extended instructions on how to set up Z-Wave."

15-16: Use uncountable noun “firmware”
“Firmwares” is not standard English; “firmware versions” or just “firmware” is preferred.

-The firmwares of 700 and 800 series Z-Wave adapters have several bugs
+The firmware of 700 and 800-series Z-Wave adapters has several bugs

35-36: Minor wording tweak for clarity
Consider inserting “to” for smoother reading.

-You should upgrade the firmware on all 700 and 800 series adapters to a recommended version.
+You should upgrade the firmware on all 700 and 800-series adapters to a recommended version.

84-85: Reduce repetition of “support(s)”
The sentence repeats “support(s)” twice.

-The alternative to a stick or module is a hub that supports Z-Wave. Home Assistant supports the following hubs with Z-Wave support:
+Instead of a stick or module, you can use a hub with built-in Z-Wave. Home Assistant supports the following hubs:
📜 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 c523e14 and 3669a29.

📒 Files selected for processing (1)
  • source/_docs/z-wave/controllers.markdown (4 hunks)
⏰ 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

@@ -73,32 +73,32 @@ Firmware can be upgraded using the below directions:
- Z-Wave.Me Razberry 2 (500 series)
- Z-Wave.Me Razberry 1 (300 series)

If you are just starting out, we recommend that you purchase a 700 series controller or a Raspberry Pi module. The 700 series controllers are the more recent version (when compared to the 500 series). The 700 series controllers support SmartStart, which allows you to add a device by scanning a QR code.
If you are just starting out, we recommend that you purchase a 700 series adapter or a Raspberry Pi module. The 700 series adapters are the more recent version (when compared to the 500 series). The 700 series adapters support SmartStart, which allows you to add a device by scanning a QR code.
Copy link
Contributor

Choose a reason for hiding this comment

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

Actually, I think this entire sentence needs to be reworked:

  • We recommend starting with 800 series now, especially in EU because of the upcoming Long Range support
  • 700 series only supports Long Range in US (with one exception)
  • 700 and 800 series (and some recent 500 series firmwares) support SmartStart

But this is too complex to explain here, so we should just say that 800 series is the most future proof and has the best RF performance.


### 800 Series Controllers
### 800 Series Adapters

Z-Wave JS does not support Z-Wave Long Range yet.
Copy link
Contributor

Choose a reason for hiding this comment

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

This is no longer true.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thank you for the catch. Removed!

Co-authored-by: AlCalzone <dominic.griesel@nabucasa.com>
@c0ffeeca7 c0ffeeca7 marked this pull request as draft July 2, 2025 09:43
@c0ffeeca7 c0ffeeca7 added this to the 2025.7 milestone Jul 2, 2025
@c0ffeeca7 c0ffeeca7 marked this pull request as ready for review July 2, 2025 11:23
@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 2, 2025
@home-assistant home-assistant bot added the has-parent This PR has a parent PR in another repo label Jul 2, 2025
@c0ffeeca7 c0ffeeca7 marked this pull request as draft July 2, 2025 12:52
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 (1)
source/_docs/z-wave/controllers.markdown (1)

82-86: Minor style polish for hub paragraph (optional)
Flow reads more naturally with the adverbial clause at the end.

-For best experience, it is recommended to use an adapter directly with Home Assistant. If this doesn't work for you, you can use a hub that supports Z-Wave.
+For the best experience, use an adapter directly with Home Assistant. If that is not possible, you can fall back to a hub that supports Z-Wave.
📜 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 599e17f and 496c5f5.

📒 Files selected for processing (1)
  • source/_docs/z-wave/controllers.markdown (4 hunks)
🧰 Additional context used
🪛 LanguageTool
source/_docs/z-wave/controllers.markdown

[misspelling] ~76-~76: Use “an” instead of ‘a’ if the following word starts with a vowel sound, e.g. ‘an article’, ‘an hour’.
Context: ...ing out, we recommend that you purchase a 800-series controller (with firmware up...

(EN_A_VS_AN)


[misspelling] ~76-~76: This word is normally spelled with a hyphen.
Context: ...). The 800-series adapters are the most future proof and have the best RF performance. {% t...

(EN_COMPOUNDS_FUTURE_PROOF)

🔇 Additional comments (1)
source/_docs/z-wave/controllers.markdown (1)

74-78: Review controllers.markdown for remaining “controller” & “stick” references
Our grep on source/_docs/z-wave/controllers.markdown found additional occurrences:

• The original purchase recommendation (lines 74–78) still uses “controller”
• A generic USB “stick” reference
• Numerous product names (e.g. “Z-Stick”, “USB Stick”)—verify which should stay as branded names

Suggested updates for the generic lines:

--- source/_docs/z-wave/controllers.markdown
@@ -74,4 +74,4 @@
-If you are just starting out, we recommend that you purchase a 800-series controller (with firmware updated to >=7.23.2). The 800-series adapters are the most future proof and have the best RF performance.
+If you are just starting out, we recommend that you purchase an 800-series adapter (with firmware updated to ≥ 7.23.2). The 800-series adapters are the most future-proof and offer the best RF performance.

-It's recommended to use a USB stick, not a module. Passing a module through Docker is more complicated than passing a USB stick through.
+It's recommended to use a USB adapter, not a module. Passing a module through Docker is more complicated than passing a USB adapter through.

Please audit the remaining branded “Stick” product names and remove or update any other generic “controller”/“stick” references as needed.

@c0ffeeca7
Copy link
Contributor Author

In that case, should the other 3 headlines instead be "XXX series USB adapters"?

good point. In that case, "modules": are they always hats/shields? would they then be shield adapters?

@AlCalzone
Copy link
Contributor

I've seen 3 form factors so far:

  • Connected via USB, either via cable or as a USB stick
  • GPIO hats/modules/..., essentially what you put on a Raspberry Pi
  • Very rarely: PCIe cards, essentially like GPIO, but for "real" servers.

I would ignore the latter.

@c0ffeeca7 c0ffeeca7 marked this pull request as ready for review July 2, 2025 14:09
@c0ffeeca7
Copy link
Contributor Author

I've seen 3 form factors so far:

  • Connected via USB, either via cable or as a USB stick
  • GPIO hats/modules/..., essentially what you put on a Raspberry Pi
  • Very rarely: PCIe cards, essentially like GPIO, but for "real" servers.

I would ignore the latter.

thx! I called it hat adapter, to have the form factor in the title. WDYT?

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 (1)
source/_docs/z-wave/controllers.markdown (1)

47-75: Minor consistency polish for list headings
The bullet labels mix “USB adapters” with “hat adapters”, and “hat” is usually capitalised as the trademark “HAT”. Consider tightening the wording for uniformity:

-800 series USB adapters
-700 series USB adapters
-500 series USB adapters
-Raspberry Pi hat adapters
+800-series USB adapters
+700-series USB adapters
+500-series USB adapters
+Raspberry Pi HAT adapters

This keeps the form-factor qualifier last and uses hyphens consistently in the series designations.

📜 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 496c5f5 and 46dcb1d.

📒 Files selected for processing (1)
  • source/_docs/z-wave/controllers.markdown (4 hunks)
🧰 Additional context used
🪛 LanguageTool
source/_docs/z-wave/controllers.markdown

[misspelling] ~76-~76: Use “an” instead of ‘a’ if the following word starts with a vowel sound, e.g. ‘an article’, ‘an hour’.
Context: ...ing out, we recommend that you purchase a 800-series controller (with firmware up...

(EN_A_VS_AN)


[misspelling] ~76-~76: This word is normally spelled with a hyphen.
Context: ...). The 800-series adapters are the most future proof and have the best RF performance. {% t...

(EN_COMPOUNDS_FUTURE_PROOF)

@c0ffeeca7 c0ffeeca7 added the parent-merged The parent PR has been merged already label Jul 2, 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

🧹 Nitpick comments (5)
source/_docs/z-wave/controllers.markdown (5)

15-16: Prefer “firmware versions” over plural “firmwares”

“Firmware” is normally treated as an uncountable noun; “firmware versions” reads more naturally and avoids style debates.

-The firmwares of 700 and 800 series Z-Wave adapters have several bugs which impact the stability of the mesh and can cause the adapter to become unresponsive. Because there is no known firmware version that is completely fixed, it is recommended to choose a firmware based on the following criteria:
+The firmware versions for 700- and 800-series Z-Wave adapters have several bugs that affect mesh stability and can cause the adapter to become unresponsive. Because no version is completely bug-free, choose a version based on the following criteria:

47-59: Hyphenate “800-series”, “700-series”, “500-series” for consistency

Elsewhere (line 76) you use the hyphenated form “800-series adapter”. Keeping the adjectival compound consistently hyphenated improves readability.

-800 series USB adapters
+800-series USB adapters-700 series USB adapters
+700-series USB adapters-500 series USB adapters
+500-series USB adapters

69-75: Capitalize “HAT” in Raspberry Pi HAT adapters

“HAT” is the official Raspberry Pi term; capitalizing avoids ambiguity with the common noun “hat”.

-Raspberry Pi hat adapters
+Raspberry Pi HAT adapters

76-79: Use ASCII “>=” and tighten wording

Unicode ≥ can render inconsistently in some terminals; ASCII “>=” is safer. Minor wording tweaks drop an extra article and keep the sentence tight.

-If you are just starting out, we recommend that you purchase an 800-series adapter (with firmware updated to ≥ 7.23.2). The 800-series adapters are the most future-proof and offer the best RF performance.
+If you are just starting out, we recommend purchasing an 800-series adapter (with firmware updated to >= 7.23.2). 800-series adapters are the most future-proof and offer the best RF performance.

81-84: Add missing article “the”

Standard English calls for “the best experience”.

-For best experience, it is recommended to use an adapter directly with Home Assistant.
+For the best experience, use an adapter directly with Home Assistant.
📜 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 46dcb1d and e174381.

📒 Files selected for processing (1)
  • source/_docs/z-wave/controllers.markdown (4 hunks)
🧰 Additional context used
🪛 LanguageTool
source/_docs/z-wave/controllers.markdown

[uncategorized] ~83-~83: You might be missing the article “the” here.
Context: ... {% endtip %} ## Third-party hubs For best experience, it is recommended to use an...

(AI_EN_LECTOR_MISSING_DETERMINER_THE)

⏰ 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

@frenck frenck merged commit bba763e into next Jul 3, 2025
9 checks passed
@home-assistant home-assistant bot removed the in-progress This PR/Issue is currently being worked on label Jul 3, 2025
@frenck frenck deleted the z-wave-controllers-rename-to-adapter branch July 3, 2025 06:53
@home-assistant home-assistant bot removed the parent-merged The parent PR has been merged already label Jul 3, 2025
@c0ffeeca7 c0ffeeca7 restored the z-wave-controllers-rename-to-adapter branch July 3, 2025 07:34
@github-actions github-actions bot locked and limited conversation to collaborators Jul 4, 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 another repo next This PR goes into the next branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants