Add Config Flow to EmonCMS

[ArnyminerZ]

Breaking change

Existing YAML configuration must be migrated to config flow.

Proposed change

Add config flow functionality to EmonCMS, and also group entities by its server.

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
• I have followed the perfect PR recommendations
• 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.

To help with the load of incoming pull requests:

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

[home-assistant]

Hey there @borpin, mind taking a look at this pull request as it has been labeled with an integration (emoncms) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of emoncms can trigger bot actions by commenting:

• @home-assistant close Closes the pull request.
• @home-assistant rename Awesome new title Renames the pull request.
• @home-assistant reopen Reopen the pull request.
• @home-assistant unassign emoncms Removes the current integration label and assignees on the pull request, add the integration domain after the command.

[epenet]

This PR is way bigger than it needs to be, and will be very difficult to review as it is.
It is missing tests - tests are compulsory for config flow.
It also seems to be missing the migration/deprecation from YAML.

I suggest that you keep this in draft and create preliminary PR for all refactoring that is not directly linked to the config flow.

[waako]

Can't comment on the python code I'm afraid, but looks promising.
Just confused about the change to cloud_polling.

There does appear to be overlap with #86840 but assume this PR supersedes anything in that one ?

[waako]

That is only relevant if using emoncms.org.
Majority of users interface with a local instance, it does not require internet access.

[waako]

Same query as in the manifest.json.
By default EmonCMS would be used with local hardware/server, so local_polling.
Similar to MQTT, which mostly is local, but can be used with a cloud service.

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

[borpin]

Hopefully soon.

[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.
If you are the author of this PR, please leave a comment if you want to keep it open. Also, please rebase your PR onto the latest dev branch to ensure that it's up to date with the latest changes.
Thank you for your contribution!