Consistent spelling of IT abbreviations / protocol / format names (#45913)
parent
44914c01ac
commit
5a0715d388
|
@ -3,7 +3,7 @@
|
|||
"step": {
|
||||
"auth": {
|
||||
"title": "Authenticate Ambiclimate",
|
||||
"description": "Please follow this [link]({authorization_url}) and **Allow** access to your Ambiclimate account, then come back and press **Submit** below.\n(Make sure the specified callback url is {cb_url})"
|
||||
"description": "Please follow this [link]({authorization_url}) and **Allow** access to your Ambiclimate account, then come back and press **Submit** below.\n(Make sure the specified callback URL is {cb_url})"
|
||||
}
|
||||
},
|
||||
"create_entry": {
|
||||
|
|
|
@ -5,7 +5,7 @@ show_lovelace_view:
|
|||
description: Media Player entity to show the Lovelace view on.
|
||||
example: "media_player.kitchen"
|
||||
dashboard_path:
|
||||
description: The url path of the Lovelace dashboard to show.
|
||||
description: The URL path of the Lovelace dashboard to show.
|
||||
example: lovelace-cast
|
||||
view_path:
|
||||
description: The path of the Lovelace view to show.
|
||||
|
|
|
@ -1,5 +1,5 @@
|
|||
turn_on:
|
||||
description: Set the light RGB to the predominant color found in the image provided by url or file path.
|
||||
description: Set the light RGB to the predominant color found in the image provided by URL or file path.
|
||||
fields:
|
||||
color_extract_url:
|
||||
description: The URL of the image we want to extract RGB values from. Must be allowed in allowlist_external_urls.
|
||||
|
|
|
@ -11,7 +11,7 @@ configure:
|
|||
entity (when entity is specified).
|
||||
example: '"/lights/1/state" or "/state"'
|
||||
data:
|
||||
description: Data is a json object with what data you want to alter.
|
||||
description: Data is a JSON object with what data you want to alter.
|
||||
example: '{"on": true}'
|
||||
bridgeid:
|
||||
description: (Optional) Bridgeid is a string unique for each deCONZ hardware. It can be found as part of the integration name.
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
# Describes the format for available webostv services
|
||||
|
||||
get_command:
|
||||
description: "Send a generic http get command."
|
||||
description: "Send a generic HTTP get command."
|
||||
fields:
|
||||
entity_id:
|
||||
description: Name(s) of the denonavr entities where to run the API method.
|
||||
|
|
|
@ -11,4 +11,4 @@ set_theme:
|
|||
example: "dark"
|
||||
|
||||
reload_themes:
|
||||
description: Reload themes from yaml configuration.
|
||||
description: Reload themes from YAML configuration.
|
||||
|
|
|
@ -3,7 +3,7 @@
|
|||
"step": {
|
||||
"user": {
|
||||
"title": "Goal Zero Yeti",
|
||||
"description": "First, you need to download the Goal Zero app: https://www.goalzero.com/product-features/yeti-app/\n\nFollow the instructions to connect your Yeti to your Wifi network. Then get the host ip from your router. DHCP must be set up in your router settings for the device to ensure the host ip does not change. Refer to your router's user manual.",
|
||||
"description": "First, you need to download the Goal Zero app: https://www.goalzero.com/product-features/yeti-app/\n\nFollow the instructions to connect your Yeti to your Wifi network. Then get the host IP from your router. DHCP must be set up in your router settings for the device to ensure the host IP does not change. Refer to your router's user manual.",
|
||||
"data": {
|
||||
"host": "[%key:common::config_flow::data::host%]",
|
||||
"name": "[%key:common::config_flow::data::name%]"
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
# Describes the format for Habitica service
|
||||
api_call:
|
||||
description: Call Habitica api
|
||||
description: Call Habitica API
|
||||
fields:
|
||||
name:
|
||||
description: Habitica's username to call for
|
||||
|
@ -9,5 +9,5 @@ api_call:
|
|||
description: "Items from API URL in form of an array with method attached at the end. Consult https://habitica.com/apidoc/. Example uses https://habitica.com/apidoc/#api-Task-CreateUserTasks"
|
||||
example: '["tasks", "user", "post"]'
|
||||
args:
|
||||
description: Any additional json or url parameter arguments. See apidoc mentioned for path. Example uses same api endpoint
|
||||
description: Any additional JSON or URL parameter arguments. See apidoc mentioned for path. Example uses same API endpoint
|
||||
example: '{"text": "Use API from Home Assistant", "type": "todo"}'
|
||||
|
|
|
@ -4,7 +4,7 @@ start:
|
|||
description: Starts the HomeKit driver.
|
||||
|
||||
reload:
|
||||
description: Reload homekit and re-process yaml configuration.
|
||||
description: Reload homekit and re-process YAML configuration.
|
||||
|
||||
reset_accessory:
|
||||
description: Reset a HomeKit accessory. This can be useful when changing a media_player’s device class to tv, linking a battery, or whenever Home Assistant adds support for new HomeKit features to existing entities.
|
||||
|
|
|
@ -99,7 +99,7 @@
|
|||
}
|
||||
},
|
||||
"error": {
|
||||
"bad_host": "Invalid Override API host url"
|
||||
"bad_host": "Invalid Override API host URL"
|
||||
},
|
||||
"abort": {
|
||||
"not_konn_panel": "Not a recognized Konnected.io device"
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
# Describes the format for available lovelace services
|
||||
|
||||
reload_resources:
|
||||
description: Reload Lovelace resources from yaml configuration.
|
||||
description: Reload Lovelace resources from YAML configuration.
|
||||
|
|
|
@ -8,7 +8,7 @@
|
|||
},
|
||||
"user": {
|
||||
"title": "Automaticlly connect to the bridge",
|
||||
"description": "Enter the ip address of the device.",
|
||||
"description": "Enter the IP address of the device.",
|
||||
"data": {
|
||||
"host": "[%key:common::config_flow::data::host%]"
|
||||
}
|
||||
|
|
|
@ -1,5 +1,5 @@
|
|||
play_media:
|
||||
description: Downloads file from given url.
|
||||
description: Downloads file from given URL.
|
||||
fields:
|
||||
entity_id:
|
||||
description: Name(s) of entities to play media on.
|
||||
|
|
|
@ -37,4 +37,4 @@ dump:
|
|||
default: 5
|
||||
|
||||
reload:
|
||||
description: Reload all mqtt entities from yaml.
|
||||
description: Reload all MQTT entities from YAML.
|
||||
|
|
|
@ -2,7 +2,7 @@
|
|||
"config": {
|
||||
"abort": {
|
||||
"already_setup": "You can only configure one Soma account.",
|
||||
"authorize_url_timeout": "Timeout generating authorize url.",
|
||||
"authorize_url_timeout": "Timeout generating authorize URL.",
|
||||
"missing_configuration": "The Soma component is not configured. Please follow the documentation.",
|
||||
"result_error": "SOMA Connect responded with error status.",
|
||||
"connection_error": "Failed to connect to SOMA Connect."
|
||||
|
|
|
@ -10,7 +10,7 @@
|
|||
}
|
||||
},
|
||||
"abort": {
|
||||
"authorize_url_timeout": "Timeout generating authorize url.",
|
||||
"authorize_url_timeout": "Timeout generating authorize URL.",
|
||||
"no_url_available": "[%key:common::config_flow::abort::oauth2_no_url_available%]",
|
||||
"missing_configuration": "The Spotify integration is not configured. Please follow the documentation.",
|
||||
"reauth_account_mismatch": "The Spotify account authenticated with, does not match the account needed re-authentication."
|
||||
|
|
|
@ -11,7 +11,7 @@
|
|||
"webhook_not_internet_accessible": "[%key:common::config_flow::abort::webhook_not_internet_accessible%]"
|
||||
},
|
||||
"create_entry": {
|
||||
"default": "To send events to Home Assistant, you will need to setup the webhook feature in Traccar.\n\nUse the following url: `{webhook_url}`\n\nSee [the documentation]({docs_url}) for further details."
|
||||
"default": "To send events to Home Assistant, you will need to setup the webhook feature in Traccar.\n\nUse the following URL: `{webhook_url}`\n\nSee [the documentation]({docs_url}) for further details."
|
||||
}
|
||||
}
|
||||
}
|
||||
|
|
|
@ -1,12 +1,12 @@
|
|||
{
|
||||
"config": {
|
||||
"abort": {
|
||||
"cannot_connect": "Could not connect to controller with url {base_url}"
|
||||
"cannot_connect": "Could not connect to controller with URL {base_url}"
|
||||
},
|
||||
"step": {
|
||||
"user": {
|
||||
"title": "Setup Vera controller",
|
||||
"description": "Provide a Vera controller url below. It should look like this: http://192.168.1.161:3480.",
|
||||
"description": "Provide a Vera controller URL below. It should look like this: http://192.168.1.161:3480.",
|
||||
"data": {
|
||||
"vera_controller_url": "Controller URL",
|
||||
"lights": "Vera switch device ids to treat as lights in Home Assistant.",
|
||||
|
|
|
@ -4,7 +4,7 @@
|
|||
"step": {
|
||||
"user": {
|
||||
"title": "Xiaomi Aqara Gateway",
|
||||
"description": "Connect to your Xiaomi Aqara Gateway, if the IP and mac addresses are left empty, auto-discovery is used",
|
||||
"description": "Connect to your Xiaomi Aqara Gateway, if the IP and MAC addresses are left empty, auto-discovery is used",
|
||||
"data": {
|
||||
"interface": "The network interface to use",
|
||||
"host": "[%key:common::config_flow::data::ip%] (optional)",
|
||||
|
@ -21,7 +21,7 @@
|
|||
},
|
||||
"select": {
|
||||
"title": "Select the Xiaomi Aqara Gateway that you wish to connect",
|
||||
"description": "Run the setup again if you want to connect aditional gateways",
|
||||
"description": "Run the setup again if you want to connect additional gateways",
|
||||
"data": {
|
||||
"select_ip": "[%key:common::config_flow::data::ip%]"
|
||||
}
|
||||
|
|
|
@ -71,7 +71,7 @@
|
|||
"oauth2_authorize_url_timeout": "Timeout generating authorize URL.",
|
||||
"oauth2_no_url_available": "No URL available. For information about this error, [check the help section]({docs_url})",
|
||||
"reauth_successful": "Re-authentication was successful",
|
||||
"unknown_authorize_url_generation": "Unknown error generating an authorize url."
|
||||
"unknown_authorize_url_generation": "Unknown error generating an authorize URL."
|
||||
}
|
||||
}
|
||||
}
|
||||
|
|
Loading…
Reference in New Issue