User config flow and custom panel for Dynalite integration

[ziv1234]

Breaking change

The change deprecates the YAML configuration. it imports it into the UI and adds a repair issue, so it won't break a user configuration or change the existing behavior, but since it adds a "deprecation" warning, better to be explicit

Proposed change

The Dynalite configuration process is done today via YAML which we want to deprecate. However, the configuration is complex since it involved several items (Dynalite has no ability to query, so config has to be set manually).
This adds a user config flow to setup the basics (host / port). After this, a panel appears that can configure the various config entries in a straightforward interactive way

A few example screenshots:

Viewing all defined DYNET areas:

Configuring the system global settings:

Editing a specific DYNET area:

Editing a DYNET channel:

Defining a new DYNET preset:

Switching between different systems (multiple config entries)

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)
• Deprecation (breaking change to happen in the future)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue:
• Link to documentation pull request:

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.
• For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
• Untested files have been added to .coveragerc.

The integration reached or maintains the following Integration Quality Scale:

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

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[github-actions]

There hasn't been any activity on this pull request recently. This pull request has been automatically marked as stale because of that and will be closed if no further activity occurs within 7 days.
Thank you for your contributions.

[ziv1234]

adding a comment so it does not auto close. nothing to add until it is reviewed :)

[ziv1234]

had a merge conflict in manifest.json from another PR when it was approved. now all good

[github-actions]

There hasn't been any activity on this pull request recently. This pull request has been automatically marked as stale because of that and will be closed if no further activity occurs within 7 days.
Thank you for your contributions.

[ziv1234]

hello. I rebased it again and fixed the conflicts. can someone please review this? it has been sitting for a very long time with no comments

[farmio]

I did only see some minor points, but I'm not very familiar with websockets and panels yet 😬

[home-assistant]

Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍

Learn more about our pull request process.

[farmio]

Oh, Is the yaml config not deprecated here? I guess it would make sense since when a user changes / reconfigures a bridge via the new panel, that is also configured via yaml it would not persist those changes, would it?

[ziv1234]

apologies. i have been out for a few weeks. will get on it quickly

[farmio]

Still not sure about this: #77181 (comment)
Is YAML still supported? Is it imported?

If imported and converted, I think it should be deprecated too, and a repair issue should be created for the user to remove stale yaml config then.

[ziv1234]

Still not sure about this: #77181 (comment) Is YAML still supported? Is it imported?

If imported and converted, I think it should be deprecated too, and a repair issue should be created for the user to remove stale yaml config then.

the yaml config is still imported and converted. I did this, so it would not be a breaking change. do you have an example of a depracation / repair issue? i will check in knx as well

[farmio]

Knx doesn't import yaml.
Have a look at any of the recent release notes. You'll find a section "configurable from UI". There you can find some integrations that did such conversion and also a standard text for that in their PR description.

[ziv1234]

Knx doesn't import yaml. Have a look at any of the recent release notes. You'll find a section "configurable from UI". There you can find some integrations that did such conversion and also a standard text for that in their PR description.

thanks. implemented per your suggestion from bratt...

[farmio]

Just a minor addition - not sure if this is required, but can't hurt.

[farmio]

post was duplicated

[ziv1234]

implemented the last change

[farmio]

This looks good to me! 👍
I have tested it locally to see the panel in action (mocking the config entry since not having Dynalite equipment) and it seems to work as intended.