Fix string typos and consistencies in nibe_heatpump (#81902)

* Fix typos and consistency

* Fix typos and consistency
This commit is contained in:
lunmay 2022-11-10 10:32:07 +01:00 committed by GitHub
parent 9ded232522
commit a954443795
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 13 additions and 13 deletions

View File

@ -6,7 +6,7 @@
"nibegw": "NibeGW", "nibegw": "NibeGW",
"modbus": "Modbus" "modbus": "Modbus"
}, },
"description": "Pick the connection method to your pump. In general, F-series pumps require a Nibe GW custom accessory, while an S-series pump has Modbus support built-in." "description": "Pick the connection method to your pump. In general, F-series pumps require a NibeGW custom accessory, while an S-series pump has Modbus support built-in."
}, },
"modbus": { "modbus": {
"data": { "data": {
@ -16,7 +16,7 @@
}, },
"data_description": { "data_description": {
"modbus_url": "Modbus URL that describes the connection to your Heat Pump or MODBUS40 unit. It should be on the form:\n - `tcp://[HOST]:[PORT]` for Modbus TCP connection\n - `serial://[LOCAL DEVICE]` for a local Modbus RTU connection\n - `rfc2217://[HOST]:[PORT]` for a remote telnet based Modbus RTU connection.", "modbus_url": "Modbus URL that describes the connection to your Heat Pump or MODBUS40 unit. It should be on the form:\n - `tcp://[HOST]:[PORT]` for Modbus TCP connection\n - `serial://[LOCAL DEVICE]` for a local Modbus RTU connection\n - `rfc2217://[HOST]:[PORT]` for a remote telnet based Modbus RTU connection.",
"modbus_unit": "Unit identification for you Heat Pump. Can usually be left at 0." "modbus_unit": "Unit identification for your Heat Pump. Can usually be left at 0."
} }
}, },
"nibegw": { "nibegw": {
@ -37,13 +37,13 @@
} }
}, },
"error": { "error": {
"write": "Error on write request to pump. Verify your `Remote write port` or `Remote IP address`.", "write": "Error on write request to pump. Verify your `Remote write port` or `Remote address`.",
"read": "Error on read request from pump. Verify your `Remote read port` or `Remote IP address`.", "read": "Error on read request from pump. Verify your `Remote read port` or `Remote address`.",
"address": "Invalid remote address specified. Address must be an IP address or a resolvable hostname.", "address": "Invalid remote address specified. Address must be an IP address or a resolvable hostname.",
"address_in_use": "The selected listening port is already in use on this system.", "address_in_use": "The selected listening port is already in use on this system.",
"model": "The model selected doesn't seem to support modbus40", "model": "The selected model doesn't seem to support MODBUS40",
"unknown": "[%key:common::config_flow::error::unknown%]", "unknown": "[%key:common::config_flow::error::unknown%]",
"url": "The url specified is not a well formed and supported url" "url": "The specified URL is not well formed nor supported"
} }
} }
} }

View File

@ -6,11 +6,11 @@
"error": { "error": {
"address": "Invalid remote address specified. Address must be an IP address or a resolvable hostname.", "address": "Invalid remote address specified. Address must be an IP address or a resolvable hostname.",
"address_in_use": "The selected listening port is already in use on this system.", "address_in_use": "The selected listening port is already in use on this system.",
"model": "The model selected doesn't seem to support modbus40", "model": "The selected model doesn't seem to support MODBUS40",
"read": "Error on read request from pump. Verify your `Remote read port` or `Remote IP address`.", "read": "Error on read request from pump. Verify your `Remote read port` or `Remote address`.",
"unknown": "Unexpected error", "unknown": "Unexpected error",
"url": "The url specified is not a well formed and supported url", "url": "The specified URL is not well formed nor supported",
"write": "Error on write request to pump. Verify your `Remote write port` or `Remote IP address`." "write": "Error on write request to pump. Verify your `Remote write port` or `Remote address`."
}, },
"step": { "step": {
"modbus": { "modbus": {
@ -20,7 +20,7 @@
"model": "Model of Heat Pump" "model": "Model of Heat Pump"
}, },
"data_description": { "data_description": {
"modbus_unit": "Unit identification for you Heat Pump. Can usually be left at 0.", "modbus_unit": "Unit identification for your Heat Pump. Can usually be left at 0.",
"modbus_url": "Modbus URL that describes the connection to your Heat Pump or MODBUS40 unit. It should be on the form:\n - `tcp://[HOST]:[PORT]` for Modbus TCP connection\n - `serial://[LOCAL DEVICE]` for a local Modbus RTU connection\n - `rfc2217://[HOST]:[PORT]` for a remote telnet based Modbus RTU connection." "modbus_url": "Modbus URL that describes the connection to your Heat Pump or MODBUS40 unit. It should be on the form:\n - `tcp://[HOST]:[PORT]` for Modbus TCP connection\n - `serial://[LOCAL DEVICE]` for a local Modbus RTU connection\n - `rfc2217://[HOST]:[PORT]` for a remote telnet based Modbus RTU connection."
} }
}, },
@ -53,7 +53,7 @@
"remote_read_port": "The port the NibeGW unit is listening for read requests on.", "remote_read_port": "The port the NibeGW unit is listening for read requests on.",
"remote_write_port": "The port the NibeGW unit is listening for write requests on." "remote_write_port": "The port the NibeGW unit is listening for write requests on."
}, },
"description": "Pick the connection method to your pump. In general, F-series pumps require a Nibe GW custom accessory, while an S-series pump has Modbus support built-in.", "description": "Pick the connection method to your pump. In general, F-series pumps require a NibeGW custom accessory, while an S-series pump has Modbus support built-in.",
"menu_options": { "menu_options": {
"modbus": "Modbus", "modbus": "Modbus",
"nibegw": "NibeGW" "nibegw": "NibeGW"