mirror of
https://github.com/elisspace/core.git
synced 2026-10-09 02:21:08 +00:00
J. Nick Koston
18a4829314
* Config flow for elkm1 * As entity ids can now be changed, the “alarm_control_panel” attribute “changed_by_entity_id” is now “changed_by_keypad” and will show the name of the Elk keypad instead of the entity id. * An auto configure mode has been introduced which avoids the need to setup the complex include and exclude filters. This functionality still exists when configuring from yaml for power users who want more control over which entities elkm1 generates. * restore _has_all_unique_prefixes * preserve legacy behavior of creating alarm_control_panels that have no linked keypads when auto_configure is False * unroll loop
28 lines
1.2 KiB
JSON
28 lines
1.2 KiB
JSON
{
|
|
"config": {
|
|
"title": "Elk-M1 Control",
|
|
"step": {
|
|
"user": {
|
|
"title": "Connect to Elk-M1 Control",
|
|
"description": "The address string must be in the form 'address[:port]' for 'secure' and 'non-secure'. Example: '192.168.1.1'. The port is optional and defaults to 2101 for 'non-secure' and 2601 for 'secure'. For the serial protocol, the address must be in the form 'tty[:baud]'. Example: '/dev/ttyS1'. The baud is optional and defaults to 115200.",
|
|
"data": {
|
|
"protocol": "Protocol",
|
|
"address": "The IP address or domain or serial port if connecting via serial.",
|
|
"username": "Username (secure only).",
|
|
"password": "Password (secure only).",
|
|
"prefix": "A unique prefix (leave blank if you only have one ElkM1).",
|
|
"temperature_unit": "The temperature unit ElkM1 uses."
|
|
}
|
|
}
|
|
},
|
|
"error": {
|
|
"cannot_connect": "Failed to connect, please try again",
|
|
"invalid_auth": "Invalid authentication",
|
|
"unknown": "Unexpected error"
|
|
},
|
|
"abort": {
|
|
"already_configured": "An ElkM1 with this prefix is already configured",
|
|
"address_already_configured": "An ElkM1 with this address is already configured"
|
|
}
|
|
}
|
|
} |