Skip to content

Implement Frisquet Connect integration #144047

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 1 commit into
base: dev
Choose a base branch
from

Conversation

brunohead
Copy link

  • Added FrisquetConnectRepository for handling API interactions including authentication, site info retrieval, and temperature settings.
  • Introduced sensor entities for monitoring various parameters such as heating consumption, thermometer readings, and alarms.
  • Implemented system health checks to verify connectivity with the Frisquet Connect API.
  • Created utility functions for logging method calls and managing API requests.
  • Developed water heater entity to manage and monitor water heating operations.
  • Established comprehensive test suite covering configuration flow, component setup, and entity functionality.
  • Added translation files for multi-language support.

Breaking change

Proposed change

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:

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:

…n, site management, and various sensor entities

- Added FrisquetConnectRepository for handling API interactions including authentication, site info retrieval, and temperature settings.
- Introduced sensor entities for monitoring various parameters such as heating consumption, thermometer readings, and alarms.
- Implemented system health checks to verify connectivity with the Frisquet Connect API.
- Created utility functions for logging method calls and managing API requests.
- Developed water heater entity to manage and monitor water heating operations.
- Established comprehensive test suite covering configuration flow, component setup, and entity functionality.
- Added translation files for multi-language support.
Copy link

@home-assistant home-assistant bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @brunohead

It seems you haven't yet signed a CLA. Please do so here.

Once you do that we will be able to review and accept this pull request.

Thanks!

Copy link

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!

@github-actions github-actions bot added the stale label Jun 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant