Config flow for elkm1

[bdraco]

Breaking change

• 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.

Proposed change

• 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.

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Example entry for configuration.yaml:

# Example configuration.yaml

Additional information

• This PR fixes or closes issue: fixes Elk M1 integration problems #31776
• This PR is related to issue:
• Link to documentation pull request: Elkm1 config flow home-assistant.io#12521

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• The code has been formatted using Black (black --fast homeassistant tests)
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• Untested files have been added to .coveragerc.

The integration reached or maintains the following Integration Quality Scale:

• No score or internal
• 🥈 Silver
• 🥇 Gold
• 🏆 Platinum

[bdraco]

@gjbadros If you have a spare moment, would you give this a spin?

[gjbadros]

At least in my use case, I wanted to be able to specify an abbreviation (e.g., "gh" for guest house, "ph" for pool house, or whatever) explicitly.

…

On Fri, Mar 27, 2020 at 9:29 AM Robert Svensson ***@***.***> wrote: ***@***.**** commented on this pull request. ------------------------------ In homeassistant/components/elkm1/config_flow.py <#33297 (comment)>: > + if "base" not in errors: + await self.async_set_unique_id(user_input[CONF_PREFIX]) + self._abort_if_unique_id_configured() + + if self.importing: + return self.async_create_entry(title=info["title"], data=user_input) + + return self.async_create_entry( + title=info["title"], + data={ + CONF_HOST: info[CONF_HOST], + CONF_USERNAME: user_input[CONF_USERNAME], + CONF_PASSWORD: user_input[CONF_PASSWORD], + CONF_AUTO_CONFIGURE: True, + CONF_TEMPERATURE_UNIT: user_input[CONF_TEMPERATURE_UNIT], + CONF_PREFIX: info[CONF_PREFIX], Can the prefix be automatically selected instead? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#33297 (review)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AALOHTLBUTSKE5MRFURAFGDRJTH5VANCNFSM4LUVGIJQ> .