Skip to content

Conversation

c0ffeeca7
Copy link
Contributor

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.

@home-assistant home-assistant bot added the current This PR goes into the current branch label Apr 6, 2023
- as for a different server setup the location may be different.
@c0ffeeca7 c0ffeeca7 marked this pull request as ready for review April 6, 2023 06:39
@c0ffeeca7 c0ffeeca7 requested a review from a team as a code owner April 6, 2023 06:39
@home-assistant
Copy link

home-assistant bot commented Apr 6, 2023

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.

@home-assistant home-assistant bot marked this pull request as draft April 6, 2023 07:01
Co-authored-by: Franck Nijhof <frenck@frenck.nl>
@c0ffeeca7
Copy link
Contributor Author

ah! that's how it is done. Thank you, @frenck !

@c0ffeeca7 c0ffeeca7 marked this pull request as ready for review April 6, 2023 07:09
@home-assistant home-assistant bot requested a review from frenck April 6, 2023 07:09
@@ -771,6 +771,10 @@ S0 security imposes significant additional traffic on your mesh and is recommend

S2 security does not impose additional network traffic and provides additional benefits, such as detecting packet corruption. By default, Z-Wave attempts S2 security during inclusion if supported, falling back to S0 security only when necessary.

#### Where can I see the security keys in the Z-Wave JS add-on?

After the initial setup of the Z-Wave controller, you can view the security keys in the Z-Wave JS add-on. Go to {% my supervisor_addon addon="core_zwave_js" title="**Settings > **Add-ons** > **Z-Wave JS**" %} and open the **Configuration** tab. You can now see the network security key and the S0 and S2 security keys.
Copy link
Contributor

Choose a reason for hiding this comment

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

Only 4 keys are relevant, the 3 S2 keys and the S0 key.
"Network key" is a legacy config setting, identical to the S0 key.

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, @AlCalzone 👍 . Updated section.

Copy link
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.

Thanks, @c0ffeeca7 👍

../Frenck

@frenck frenck merged commit ce5e548 into home-assistant:current Apr 11, 2023
eifinger pushed a commit to eifinger/home-assistant.io that referenced this pull request Apr 11, 2023
Co-authored-by: Franck Nijhof <frenck@frenck.nl>
regevbr pushed a commit to regevbr/home-assistant.io that referenced this pull request Apr 11, 2023
Co-authored-by: Franck Nijhof <frenck@frenck.nl>
@c0ffeeca7 c0ffeeca7 deleted the add-info-where-to-find-security-keys branch April 11, 2023 20:37
@github-actions github-actions bot locked and limited conversation to collaborators Apr 12, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
current This PR goes into the current branch
Projects
No open projects
Archived in project
Development

Successfully merging this pull request may close these issues.

3 participants