Use pyephember2 library in ephember

[Zaduvalo]

Breaking change

Proposed change

New pyephember library support.
New devices support added.
Multiple home support

New library diff - https://github.com/ttroy50/pyephember/pull/19/files
Library github link - https://github.com/roberty99/pyephember2

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:
• Link to developer documentation pull request:
• Link to frontend 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 Ruff (ruff format 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.

To help with the load of incoming pull requests:

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

[home-assistant]

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

Code owner commands

Code owners of ephember 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 ephember Removes the current integration label and assignees on the pull request, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the pull request.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the pull request.

[Zaduvalo]

New pypyember version supported
ttroy50/pyephember#17 (comment)

https://pypi.org/project/pyephember2/0.4.10/

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

[Zaduvalo]

Hi @MartinHjelmare , @frenck, is anything needed to complete PR?

[MartinHjelmare]

CI need to pass. Every time you merge dev or rebase on dev the CI result is lost and we need to run CI again. Unless the feature branch needs something from dev or there's a merge conflict you generally don't need to merge dev or rebase.

[MartinHjelmare]

Please add a link to the new library GitHub repo in the PR description.

[Zaduvalo]

Please add a link to the new library GitHub repo in the PR description.

Github link added. No more branch updates.

[MartinHjelmare]

Thanks!

Comment addressed

[joostlek]

Mind sending me a message on discord so we can add you to the relevant channels?