Poolside for Home Assistant

Home Assistant integration for Poolside Tech Attendant pool and spa controllers.

Communication is entirely local: the integration discovers the controller on your network via zeroconf and talks to it over an encrypted websocket session (Noise Protocol Framework) with pushed status updates — no cloud, no polling.

Features

• climate — heater/chiller control per body of water
• fan — variable-speed pumps and water features
• light — underwater/landscape lights, including effects and brightness where supported
• switch — single-speed pumps and other on/off controls
• select — heating/cooling mode selection
• sensor — water temperature, body-of-water state, site mode, and optional read-only pool device telemetry

Requirements

• Poolside Tech Attendant software 2.7.0 or later
• Administrator access to the controller (to approve the pairing request)
• The controller must be reachable on your local network

Installation

HACS (recommended)

1. In HACS, choose Custom repositories from the overflow menu, add https://github.com/PoolsideStan/poolside-official-integration with type Integration.
2. Search for Poolside in HACS and download it.
3. Restart Home Assistant.

Manual

Copy custom_components/poolside into your Home Assistant config/custom_components directory and restart Home Assistant.

Configuration

Configuration is via the UI. If the controller is on the same network, it is discovered automatically (Settings → Devices & Services). Otherwise choose Add Integration → Poolside and enter the controller's host and port.

Pairing is a one-time step: the flow shows a key fingerprint and the request must be approved on the Attendant controller itself. Administrator access to the controller is required.

Options (Settings → Devices & Services → Poolside → Configure):

• Expose pool devices — create read-only telemetry sensors for the physical equipment (pumps, heaters, actuators, ...) the controller operates.

Relationship to Home Assistant Core

This integration has been submitted for inclusion in Home Assistant Core. This repository distributes the same integration via HACS in the meantime. The protocol client lives in the separate aiopoolside library (PyPI).

Because the domain is poolside in both, your configuration and entities will carry over when the core version ships — at that point, remove this custom component and restart (an installed custom integration always overrides the core one).

Issues

Please report problems at github.com/PoolsideStan/poolside-official-integration/issues.

License

MIT