mirror of
https://github.com/aljazceru/addons.git
synced 2025-12-18 13:44:20 +01:00
Add translation files to all add-ons (#2433)
* Add translation files to all add-ons * lint * Apply suggestions from code review Co-authored-by: Stefan Agner <stefan@agner.ch> * Adjust zwave docs * Adjust zwave_js docs * Adjust ada docs * Reorder ada * Reorder duckdns * Reorder git_pull * Reorder google_assistant * Reorder homematic * Reorder letsencrypt * Reorder mosquitto * Reorder nginx_proxy * Reorder samba * Reorder ssh * Lint Co-authored-by: Stefan Agner <stefan@agner.ch>
This commit is contained in:
@@ -26,14 +26,13 @@ change if other devices are added to the system.
|
||||
in order to connect securely to compatible devices. It is recommended
|
||||
that all four network keys are configured as some security enabled devices (locks, etc)
|
||||
may not function correctly if they are not added securely.
|
||||
* As a note, it is not recommended to securely connect *all* devices unless they support S2 security
|
||||
as the S0 security triples the amount of messages sent on the mesh.
|
||||
- As a note, it is not recommended to securely connect _all_ devices unless they support S2 security
|
||||
as the S0 security triples the amount of messages sent on the mesh.
|
||||
3. Click on "SAVE" to save the add-on configuration.
|
||||
4. Start the add-on.
|
||||
5. Add the Z-Wave JS integration to Home Assistant, see documentation:
|
||||
<https://www.home-assistant.io/integrations/zwave_js>
|
||||
|
||||
|
||||
## Configuration
|
||||
|
||||
Add-on configuration:
|
||||
@@ -48,7 +47,7 @@ s2_unauthenticated_key: CF338FE0CB99549F7C0EA96308E5A403
|
||||
|
||||
### Option `device`
|
||||
|
||||
The device address of your Z-Wave controller.
|
||||
The Z-Wave controller device.
|
||||
|
||||
If you're using Home Assistant you may find the correct value for this on the
|
||||
`Supervisor -> System -> Host system -> Hardware` page. It is recommended
|
||||
@@ -126,6 +125,7 @@ automatically on startup.
|
||||
### Option `log_level` (optional)
|
||||
|
||||
This option sets the log level of Z-Wave JS. Valid options are:
|
||||
|
||||
- silly
|
||||
- debug
|
||||
- verbose
|
||||
|
||||
@@ -25,8 +25,6 @@ options:
|
||||
s2_unauthenticated_key: ""
|
||||
ports:
|
||||
3000/tcp: null
|
||||
ports_description:
|
||||
3000/tcp: Z-Wave JS communication
|
||||
schema:
|
||||
device: device(subsystem=tty)
|
||||
emulate_hardware: bool?
|
||||
|
||||
41
zwave_js/translations/en.yaml
Normal file
41
zwave_js/translations/en.yaml
Normal file
@@ -0,0 +1,41 @@
|
||||
---
|
||||
configuration:
|
||||
device:
|
||||
name: Device
|
||||
description: The Z-Wave controller device.
|
||||
emulate_hardware:
|
||||
name: Enable Emulated Hardware
|
||||
description: >-
|
||||
If you don't have a USB stick, you can use a fake stick for testing
|
||||
purposes.
|
||||
log_level:
|
||||
name: Log Level
|
||||
description: This option sets the log level of Z-Wave JS.
|
||||
network_key:
|
||||
name: Network Key
|
||||
description: >-
|
||||
In previous versions of the addon, this was the only key that was needed.
|
||||
With the introduction of S2 security inclusion in zwave-js, this option
|
||||
has been deprecated.
|
||||
s0_legacy_key:
|
||||
name: S0 Legacy Key
|
||||
description: >-
|
||||
S0 Security Z-Wave devices require a network key before being added to the
|
||||
network.
|
||||
s2_access_control_key:
|
||||
name: S2 Access Control Key
|
||||
description: >-
|
||||
This must be provided in order to include devices with the S2 Access
|
||||
Control security class.
|
||||
s2_authenticated_key:
|
||||
name: S2 Authenticated Key
|
||||
description: >-
|
||||
This must be provided in order to include devices with the S2
|
||||
Authenticated security class.
|
||||
s2_unauthenticated_key:
|
||||
name: S2 Unauthenticated Key
|
||||
description: >-
|
||||
This must be provided in order to include devices with the S2
|
||||
Unauthenticated security class.
|
||||
network:
|
||||
3000/tcp: Z-Wave JS communication
|
||||
Reference in New Issue
Block a user