Water

NeoPool

neopool

Built inLocal pollingPlatinum

The NeoPool integration integrates pool controllers built around the NeoPool control system (originally developed by Sugar Valley, acquired by Hayward in 2016) with Home Assistant. It communicates entirely locally over Modbus TCP, providing real-time monitoring of water chemistry, filtration, and hydrolysis without any cloud dependency.

Documentation Source code

In Apple Home through HomeKit Bridge

What HomeKit Bridge makes of each kind of entity this integration creates, read from its source code. A device only gets the ones that apply to it.

Entity	Shows up as	Note
`light`	Light
`switch`	Switch or outlet
`binary_sensor`	Sensor (contact)
`sensor`	Sensor (temperature)
`button`	Button (as a switch)
`select`	Mode picker (as switches)

What people report

NeoPool pool controllers are polled locally over Modbus TCP via a gateway; manual setup only, with direct serial added Oct 2026.

Works8

Device	In Home Assistant	What they said	Source
Hayward Aquarite (NeoPool option)	Works Local	Modbus TCP; manual setup, no discovery Saved copy Supported devices: Hayward: Aquarite (with NeoPool option), Hidroniser, UVScenic, Station; Sugar Valley: Hidrolife, Aquascenic, Oxilife, Bionet. Limitations: Discovery is not supported. Modbus TCP gateways do not expose a standard discovery protocol that uniquely identifies a NeoPool controller behind the gateway, so the integration must be configured manually. One controller per config entry. Multiple physical controllers are supported, but each one needs its own config entry. Authentication is not used. Modbus TCP itself has no authentication mechanism; the integration relies on network … Excerpt saved from home-assistant.io on 2026-10-23.	Docs
Hayward Hidroniser	Works Local	Listed as supported in the docs Saved copy Supported devices: Hayward: Aquarite (with NeoPool option), Hidroniser, UVScenic, Station; Sugar Valley: Hidrolife, Aquascenic, Oxilife, Bionet. Limitations: Discovery is not supported. Modbus TCP gateways do not expose a standard discovery protocol that uniquely identifies a NeoPool controller behind the gateway, so the integration must be configured manually. One controller per config entry. Multiple physical controllers are supported, but each one needs its own config entry. Authentication is not used. Modbus TCP itself has no authentication mechanism; the integration relies on network … Excerpt saved from home-assistant.io on 2026-10-23.	Docs
Hayward Station	Works Local	Listed as supported in the docs Saved copy Supported devices: Hayward: Aquarite (with NeoPool option), Hidroniser, UVScenic, Station; Sugar Valley: Hidrolife, Aquascenic, Oxilife, Bionet. Limitations: Discovery is not supported. Modbus TCP gateways do not expose a standard discovery protocol that uniquely identifies a NeoPool controller behind the gateway, so the integration must be configured manually. One controller per config entry. Multiple physical controllers are supported, but each one needs its own config entry. Authentication is not used. Modbus TCP itself has no authentication mechanism; the integration relies on network … Excerpt saved from home-assistant.io on 2026-10-23.	Docs
Hayward UVScenic	Works Local	Listed as supported in the docs Saved copy Supported devices: Hayward: Aquarite (with NeoPool option), Hidroniser, UVScenic, Station; Sugar Valley: Hidrolife, Aquascenic, Oxilife, Bionet. Limitations: Discovery is not supported. Modbus TCP gateways do not expose a standard discovery protocol that uniquely identifies a NeoPool controller behind the gateway, so the integration must be configured manually. One controller per config entry. Multiple physical controllers are supported, but each one needs its own config entry. Authentication is not used. Modbus TCP itself has no authentication mechanism; the integration relies on network … Excerpt saved from home-assistant.io on 2026-10-23.	Docs
Sugar Valley Aquascenic	Works Local	Listed as supported in the docs Saved copy Supported devices: Hayward: Aquarite (with NeoPool option), Hidroniser, UVScenic, Station; Sugar Valley: Hidrolife, Aquascenic, Oxilife, Bionet. Limitations: Discovery is not supported. Modbus TCP gateways do not expose a standard discovery protocol that uniquely identifies a NeoPool controller behind the gateway, so the integration must be configured manually. One controller per config entry. Multiple physical controllers are supported, but each one needs its own config entry. Authentication is not used. Modbus TCP itself has no authentication mechanism; the integration relies on network … Excerpt saved from home-assistant.io on 2026-10-23.	Docs
Sugar Valley Bionet	Works Local	Listed as supported in the docs Saved copy Supported devices: Hayward: Aquarite (with NeoPool option), Hidroniser, UVScenic, Station; Sugar Valley: Hidrolife, Aquascenic, Oxilife, Bionet. Limitations: Discovery is not supported. Modbus TCP gateways do not expose a standard discovery protocol that uniquely identifies a NeoPool controller behind the gateway, so the integration must be configured manually. One controller per config entry. Multiple physical controllers are supported, but each one needs its own config entry. Authentication is not used. Modbus TCP itself has no authentication mechanism; the integration relies on network … Excerpt saved from home-assistant.io on 2026-10-23.	Docs
Sugar Valley Hidrolife	Works Local	Listed as supported in the docs Saved copy Supported devices: Hayward: Aquarite (with NeoPool option), Hidroniser, UVScenic, Station; Sugar Valley: Hidrolife, Aquascenic, Oxilife, Bionet. Limitations: Discovery is not supported. Modbus TCP gateways do not expose a standard discovery protocol that uniquely identifies a NeoPool controller behind the gateway, so the integration must be configured manually. One controller per config entry. Multiple physical controllers are supported, but each one needs its own config entry. Authentication is not used. Modbus TCP itself has no authentication mechanism; the integration relies on network … Excerpt saved from home-assistant.io on 2026-10-23.	Docs
Sugar Valley Oxilife	Works Local	Listed as supported in the docs Saved copy Supported devices: Hayward: Aquarite (with NeoPool option), Hidroniser, UVScenic, Station; Sugar Valley: Hidrolife, Aquascenic, Oxilife, Bionet. Limitations: Discovery is not supported. Modbus TCP gateways do not expose a standard discovery protocol that uniquely identifies a NeoPool controller behind the gateway, so the integration must be configured manually. One controller per config entry. Multiple physical controllers are supported, but each one needs its own config entry. Authentication is not used. Modbus TCP itself has no authentication mechanism; the integration relies on network … Excerpt saved from home-assistant.io on 2026-10-23.	Docs

Gathered from GitHub issues, pull requests, discussions and docs, and from r/homeassistant. These are individual reports, so check the linked thread and the date before you buy.

How it connects

Local polling

Talks to the device on your network, asking it for updates every so often.

Details

Installs (analytics)	2
Quality scale	Platinum
Added in	Home Assistant 2026.8
Set up in the UI	Yes
Maintainers	@svasek

Devices listed in its documentation

Hayward: Aquarite (with NeoPool option), Hidroniser, UVScenic, Station
Sugar Valley: Hidrolife, Aquascenic, Oxilife, Bionet

Limitations from the docs

Discovery is not supported. Modbus TCP gateways do not expose a standard discovery protocol that uniquely identifies a NeoPool controller behind the gateway, so the integration must be configured manually.
One controller per config entry. Multiple physical controllers are supported, but each one needs its own config entry.
Authentication is not used. Modbus TCP itself has no authentication mechanism; the integration relies on network isolation between Home Assistant and the gateway. The gateway should not be exposed to untrusted networks.
The DISPLAY connector is reserved. The NeoPool controller exposes the same protocol on its DISPLAY connector as on WIFI / EXTERNAL, but the built-in LCD usually occupies it. Connecting to DISPLAY while the LCD is attached will result in collisions.
Variable-speed pump support depends on the controller firmware. The Filtration speed entity is registered only when the controller reports a variable-speed pump.
The pool light entity is opt-in. The controller does not report whether a physical light is wired to its lighting relay, so the entity is only registered after you enable it in the integration options.
The pool light cannot be controlled while its timer is in an automatic mode. Set the light timer to a manual mode first to turn the light on or off from Home Assistant.
The auxiliary relay and cover reduction switches are opt-in. The controller does not report what is wired to each auxiliary relay or whether a cover sensor is present, so these switches are only registered after you enable them in the integration options.
Filtration and auxiliary relays can only be switched in a manual mode. Set the controller or the relay timer to a manual mode first. When it is in an automatic mode, Home Assistant shows an error rather than overriding the schedule.

In ReReHome

Whatever HomeKit Bridge shares reaches Apple Home as normal HomeKit accessories behind your Home Assistant bridge, so ReReHome shows and controls them like any other.

Bridges get their own settings page listing the accessories behind them.