8000 Documentation for new Seko PoolDose integration by lmaertin · Pull Request #39581 · home-assistant/home-assistant.io · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Documentation for new Seko PoolDose integration #39581

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 236 commits into
base: next
Choose a base branch
from

Conversation

lmaertin
Copy link
@lmaertin lmaertin commented Jun 16, 2025

Proposed change

Documentation for a new integration for local polling of SEKO PoolDose devices. This integration enables cloudless monitoring and control of a PoolDose Dual/Double device for automatic dosing of Pools or Spas.

Brands also planned in PRs on the dedicated respo.

Type of change

  • Spelling, grammar or other readability improvements (current branch).
  • Adjusted missing or incorrect information in the current documentation (current branch).
  • Added documentation for a new integration I'm adding to Home Assistant (next branch).
  • Added documentation for a new feature I'm adding to Home Assistant (next branch).
  • Removed stale or deprecated documentation.

Additional information

Checklist

  • This PR uses the correct branch, based on one of the following:
    • I made a change to the existing documentation and used the current branch.
    • I made a change that is related to an upcoming version of Home Assistant and used the next branch.
  • The documentation follows the Home Assistant documentation standards.

Summary by CodeRabbit

  • New Features
    • Introduced the "Seko Pooldose" integration for local monitoring and control of pool water treatment systems with live sensor data, manual overrides, and configurable settings.
  • Documentation
    • Added comprehensive user guide with setup, configuration options, supported entities, and operational details for the Pooldose integration.

frenck and others added 30 commits May 26, 2025 20:48
…e-assistant#39258)

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
…e-assistant#39278)

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…t#39283)

Co-authored-by: Joost Lekkerkerker <joostlek@outlook.com>
…9302)

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…istant#39321)

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…39319)

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
@c0ffeeca7
Copy link
Contributor

Hi there, @lmaertin 👋 Thank you for contributing 💪

There are unrelated commits and changes in this PR, probably because it was based against the current branch. The easiest way to fix this, is to close this PR. The get the latest next branch and create a new PR based against the nextbranch.

@c0ffeeca7 c0ffeeca7 marked this pull request as draft July 2, 2025 06:29
@c0ffeeca7
Copy link
Contributor

I'm drafting this PR, as changes are needed. Please undraft it, once the changes have been implemented and the PR is ready for review again.

@lmaertin
Copy link
Author
lmaertin commented Jul 2, 2025

Hi there, @lmaertin 👋 Thank you for contributing 💪

There are unrelated commits and changes in this PR, probably because it was based against the current branch. The easiest way to fix this, is to close this PR. The get the latest next branch and create a new PR based against the nextbranch.

Thanks for your feedback. I'm working on parent core PR currently. After next update is done, I will proceed to update the documentation and re-create a next-based PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
has-parent This PR has a parent PR in a other repo in-progress This PR/Issue is currently being worked on next This PR goes into the next branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0