-
-
Notifications
You must be signed in to change notification settings - Fork 7.9k
Add info where to find security keys #26890
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
Add info where to find security keys #26890
Conversation
- as for a different server setup the location may be different.
Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍 |
Co-authored-by: Franck Nijhof <frenck@frenck.nl>
ah! that's how it is done. Thank you, @frenck ! |
@@ -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. |
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.
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.
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.
thank you, @AlCalzone 👍 . Updated section.
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.
Thanks, @c0ffeeca7 👍
../Frenck
Co-authored-by: Franck Nijhof <frenck@frenck.nl>
Co-authored-by: Franck Nijhof <frenck@frenck.nl>
Proposed change
Type of change
current
branch).current
branch).next
branch).next
branch).Additional information
Checklist
current
branch.next
branch.