jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-10 02:46:53 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fix secure inclusion section. Source: AlCalzone (#30990)

Browse Source 
Co-authored-by: AlCalzone <dominic.griesel@nabucasa.com>
This commit is contained in:
c0ffeeca7 2024-01-24 09:04:17 +01:00 committed by GitHub
parent 55497fe8cd
commit 6ec05712cd
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 5 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
source/_integrations/zwave_js.markdown
View File

@ -845,11 +845,13 @@ Names set in Home Assistant will not import into Z-Wave JS UI.
### Should I use `Secure Inclusion`?
That depends. There are two generations of Z-Wave security, S0, and S2.
That depends. There are two generations of Z-Wave encryption, Security S0, and Security S2. Both provide encryption and allow detecting packet corruption.
S0 security imposes significant additional traffic on your mesh and is recommended only for devices that require security, such as door locks.
Security S0 imposes significant additional traffic on your mesh and is recommended only for older devices that do not support Security S2 but require encryption to work, such as door locks.
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.
Security S2 does not impose additional network traffic and provides additional benefits. For example, end devices using S2 require the hub to report whether it has received and understood their reports.
By default, Z-Wave prefers Security S2, if supported. Security S0 is used only when absolutely necessary.
### Where can I see the security keys in the Z-Wave JS add-on?