Use library fork for ViCare integration

[CFenner]

Proposed change

This changes the API library used in ViCare integration to a new one created from a fork.

Over the last ~9 months I provided several PRs to the original library. Some of them got merged, others where not, and since December last year there was no new version release. I tried to reach the maintainers via PR comment and via Discord but got no response over the last months.

Now we have some kind of urgency as there is one bug in the library and mid of September some of the datapoints in the API will be deleted and replaced with others.

CFenner/PyViCare@2.32.0...v0.2.1

Changes:

• fix getter for dhw gas consumption
• expose hysteresis data points
• expose device ID of room sensors
• expose ventilation mode and preset on heat pumps
• switch deprecated data points for bufferCylinder and dhwCylinder
• handle TCU300 as gateway

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 Viessmann ViCare Integration: Missing device_class for energy sensors #122850
• 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.

[MartinHjelmare]

If you're not planning to contribute back changes to upstream you should ask GitHub to disconnect your fork from its upstream. That way it's clear to the community that it's a separate project going forward.

[MartinHjelmare]

Please add a description to the PR of the due diligence that has been done to continue working with upstream project before labeling the project as unmaintained.

[CFenner]

Please add a description to the PR of the due diligence that has been done

done, I hope that is enough.

[MartinHjelmare]

Thanks!

[CFenner]

Original owner of the lib just responded and agreed to transfer the repo to a dedicated org where we can share the ownership.
Hope it's not a big deal to change back once the repo is transferred, release is setup and the bugfixes are cherry-picked.

[MartinHjelmare]

That's fine. You can link to this discussion thread in the future PR that changes back the library.