Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Z-Wave: set radio frequency region #39499

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: current
Choose a base branch
from

Conversation

c0ffeeca7
Copy link
Contributor

@c0ffeeca7 c0ffeeca7 commented Jun 12, 2025

Proposed change

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

  • Link to parent pull request in the codebase:
  • Link to parent pull request in the Brands repository:
  • This PR fixes or closes issue: fixes #

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 a new section with step-by-step instructions for setting the radio frequency region of the Z-Wave controller, including prerequisites and important notes about regional compliance.

@c0ffeeca7 c0ffeeca7 requested a review from a team as a code owner June 12, 2025 07:46
@home-assistant home-assistant bot added the current This PR goes into the current branch label Jun 12, 2025
Copy link

netlify bot commented Jun 12, 2025

Deploy Preview for home-assistant-docs ready!

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

coderabbitai bot commented Jun 12, 2025

📝 Walkthrough

Walkthrough

A new informational section was added to the Z-Wave JS integration documentation. This section details how to set or change the radio frequency region of the Z-Wave controller, explains regional compliance, and provides step-by-step instructions for updating the frequency region in the Z-Wave JS add-on settings.

Changes

File Change Summary
source/_integrations/zwave_js.markdown Added a section on setting and changing the controller's radio frequency region, with instructions.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Home Assistant UI
    participant Z-Wave JS Add-on

    User->>Home Assistant UI: Open Z-Wave JS Add-on configuration
    User->>Home Assistant UI: Select desired radio frequency region
    User->>Home Assistant UI: Save configuration changes
    Home Assistant UI->>Z-Wave JS Add-on: Apply new frequency region setting
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 f163086 and f38cbdb.

📒 Files selected for processing (1)
  • source/_integrations/zwave_js.markdown (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • source/_integrations/zwave_js.markdown

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 (2)
source/_integrations/zwave_js.markdown (2)

189-192: Improve grammar and clarity
A few sentences could be tightened for grammar and consistency. For example:

-The frequency used for Z-Wave depends on your region. For each country or region, the Z-Wave products has to apply the standard Z-Wave frequency used and approved in that region.
+Z-Wave operates on different frequencies depending on the region. Z-Wave products must comply with the frequency approved for their region.

-During onboarding of your controller, the region of your Home Assistant is used to determine the region in the Z-Wave JS add-on. If needed, you can change this radio frequency region for your controller. However, the region of the device cannot be changed. It only works in the frequency region it was specified for.
+When onboarding your controller, Home Assistant’s region is used to set the initial frequency in the Z-Wave JS add-on. You can later change your controller’s frequency region, but individual devices cannot be reprogrammed and only operate in the region they were manufactured for.

193-200: Align instruction heading and list style
Existing sections use gerund-based subheadings rather than “To …”. Please update the step heading and ensure the note under step 4 isn’t mistaken for a nested list:

-### To change the radio frequency region of your Z-Wave controller
+### Changing the radio frequency region of your Z-Wave controller

And consider formatting the final bullet as a standalone note:

4. To apply your changes, select **Save**.

   > Your Z-Wave controller is now ready to communicate with devices approved for that region.
📜 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 c736681 and b11ac50.

📒 Files selected for processing (1)
  • source/_integrations/zwave_js.markdown (1 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
🔇 Additional comments (1)
source/_integrations/zwave_js.markdown (1)

187-188: Heading Level and Placement
The new section is well-positioned immediately after the migration steps and correctly uses a level-2 heading to match other top-level sections.

Copy link
Contributor

@AlCalzone AlCalzone left a comment

Choose a reason for hiding this comment

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

I'm not sure if all the legal stuff is necessary. I'd just say end devices only work in the region they were made for.

@c0ffeeca7 c0ffeeca7 marked this pull request as draft June 12, 2025 10:41
@c0ffeeca7 c0ffeeca7 marked this pull request as ready for review June 12, 2025 11:55
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/zwave_js.markdown (1)

192-193: Clarify possessive phrasing.
Change "the country of your Home Assistant" to "Home Assistant's country" for readability:

- If you are using the Z-Wave JS add-on, the country of your Home Assistant is used to determine the radio frequency region.
+ If you are using the Z-Wave JS add-on, Home Assistant's country is used to determine the radio frequency region.
🧹 Nitpick comments (3)
source/_integrations/zwave_js.markdown (3)

187-188: Remove extra blank line.
There are two consecutive blank lines before the new section; reduce to a single blank line to satisfy markdown linting (MD012).

🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

187-187: Multiple consecutive blank lines
Expected: 1; Actual: 2

(MD012, no-multiple-blanks)


188-190: Simplify the heading.
Consider shortening to "Setting the radio frequency region in the Z-Wave JS add-on" to avoid redundant wording ("of the controller" is implied).


196-198: Use consistent terminology for device approval.
Replace "specified for that region" with "approved for that region" to match earlier phrasing:

- All your Z-Wave devices must be specified for that region
+ All your Z-Wave devices must be approved for that region
📜 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 cbe9452 and f163086.

📒 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

187-187: Multiple consecutive blank lines
Expected: 1; Actual: 2

(MD012, no-multiple-blanks)

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

202-205: Verify UI label accuracy.
Please confirm in the Z-Wave JS add-on UI that the setting is exactly labeled "Radio Frequency Region". If it differs (e.g., "RF Region"), update the docs accordingly.

Comment on lines +189 to +191
The frequency used by Z-Wave devices depends on your region. For each country or region, the Z-Wave product has to apply the standard Z-Wave frequency approved for that region. This means that when you buy a Z-Wave product, you need to make sure it is approved for your region.

If you are using the Z-Wave JS add-on, the country of your Home Assistant is used to determine the radio frequency region. If needed, you can change the radio frequency region for your controller. However, the region of end devices cannot be changed. They only work in the frequency region they were specified for.
Copy link
Contributor

Choose a reason for hiding this comment

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

Something about these two paragraph bugs me a bit. How about something in this direction?

Suggested change
The frequency used by Z-Wave devices depends on your region. For each country or region, the Z-Wave product has to apply the standard Z-Wave frequency approved for that region. This means that when you buy a Z-Wave product, you need to make sure it is approved for your region.
If you are using the Z-Wave JS add-on, the country of your Home Assistant is used to determine the radio frequency region. If needed, you can change the radio frequency region for your controller. However, the region of end devices cannot be changed. They only work in the frequency region they were specified for.
The frequency used by Z-Wave devices depends on your region. For 700 and 800 series controllers, this frequency can be changed. The frequency of end devices cannot, so you need to make sure to buy devices specific to your region.
If you are using the Z-Wave JS add-on, Home Assistant automatically changes the radio frequency region to match the region/country you're in. If needed, you can override this setting.


1. Go to {% my supervisor_addon addon="core_zwave_js" title="**Settings** > **Add-ons** > **Z-Wave JS**" %}.
2. Open the **Configuration** tab.
3. In the **Options** section, select the **Radio Frequency Region**.
Copy link
Contributor

Choose a reason for hiding this comment

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

AFAIK we have an "Automatic" option, which is the default. Should we mention this here?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
current This PR goes into the current branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants