Switch to PyEzvizApi

[RenierM26]

Proposed change

Need to update the library from pyezviz to pyezvizapi. The original owner hasn't been available for a long time, and I publish updates to pypi due to email address validation requirements.

I have decided to create a new pypi package with github repository to keep things neat and tidy.

Old github compare (just to make things easier)
BaQs/pyEzviz@0.2.2.4...1.0.0.6

New library:
https://github.com/RenierM26/pyEzvizApi/releases
RenierM26/pyEzvizApi@1.0.0.0...1.0.0.7

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 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 @BaQs, mind taking a look at this pull request as it has been labeled with an integration (ezviz) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of ezviz 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 ezviz 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.

[joostlek]

One thing I am concerned about is that paho-mqtt is pinned to 2.1.0 in the requirements, but HA ships with 1.6, so I am wondering if someone can use this library if they use the MQTT integration

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

[RenierM26]

The MQTT functionality in this library isn't used yet. I can change the pinned version to 1.6 if that's an issue?

[joostlek]

Like I am assuming 1.6 -> is a breaking change, so I think its better to downgrade it to 1.6, but it should all keep working of course :)

[RenierM26]

Pinned paho-mqtt==1.6.1 and bumped the pyezvizapi library version.

Also tested locally, no issues.

[frenck]

Not sure if it matters... but looking at the discussion above, the library doesn't pin anything in the package:

The requirements does... but that isn't used for the package distribution 🤷

[srescio]

btw, given this library change is made necessary to swap one of the current codeowners, I'd suggest to include in the PR amending this aspect too, since the bot will keep raising PRs to them otherwise

[dotlambda]

One thing I am concerned about is that paho-mqtt is pinned to 2.1.0 in the requirements, but HA ships with 1.6

#136130 has been merged

[srescio]

@frenck @joostlek I think both points raised have been addressed, any further actions required for approval? should we assign someone to the PR (asking cause now @RenierM26 is only owner so does not have a peer pal to cover this)