Entities¶

Pool Manager creates a device for each configured pool, with the following entities attached to it. All entity IDs follow the pattern {domain}.{pool_name}_{key}, where {pool_name} is derived from the pool name you set during configuration.

Sensors¶

The integration creates 22 sensor entities:

Reading sensors¶

These sensors mirror your source sensor values, giving you a unified view under the Pool Manager device.

Computed sensors¶

These sensors are calculated by Pool Manager from your readings.

Recommendations sensor attributes¶

The recommendations sensor exposes additional detail through its state attributes:

These attributes can be used in automations, templates, or Lovelace cards to display detailed recommendation information.

Chemistry actions sensor attributes¶

The chemistry_actions sensor exposes chemistry-related recommendations (chemical treatments and alerts, excluding filtration) through its state attributes:

When measuring spoon sizes are configured, each action object also includes:

See Spoon Equivalents for details on how spoon counts are calculated.

Actions are classified as either suggestions (optional improvements) or requirements (needed to keep the pool safe). See Action Kind for details.

Chemistry status sensors¶

These sensors provide a quick good / warning / bad status for each chemistry parameter. See Water Chemistry -- Chemistry Status for how the status is determined.

Each status sensor exposes additional detail through its state attributes:

Active treatments sensor attributes¶

The active_treatments sensor exposes additional detail through its state attributes:

Activation step sensor¶

The activation_step sensor tracks progress through the Activation Wizard. It shows the next pending step when the pool is in Activating mode, or has no state when the pool is in any other mode.

Activation step sensor attributes¶

These attributes are empty when the pool is not in activating mode. The checklist state persists across Home Assistant restarts via the RestoreEntity mechanism.

Binary Sensors¶

The integration creates 3 binary sensor entities for quick status checks:

Event Entities¶

The integration creates 18 event entities, one per chemical product, to track treatment applications. Each entity fires an applied event when a treatment is recorded via the poolman.add_treatment service.

Treatment-specific products (e.g., bromine_tablet) are disabled by default when the pool's configured treatment type doesn't match. Universal products (e.g., ph_minus, flocculant) are always enabled.

See Chemistry Tracking for the full list of products, safety profiles, and usage details.

Select¶

The integration creates select entities to control operational settings:

Changing the mode immediately triggers a data refresh and recalculation of all computed values.

Filtration Control Entities¶

When a pump switch entity is configured in the integration, additional entities are created for automatic pump scheduling. These entities are conditional -- they only appear when a pump entity is set.

See Filtration Control for full details on scheduling behavior, cross-midnight support, and automation examples.

Switch¶

Duration Mode Select¶

Time¶

Number¶

Event¶

Filtration Boost¶

See Filtration Control -- Filtration Boost for full details on boost behavior, persistence, and automation examples.

Events¶

Pool Manager fires poolman_event events on the Home Assistant event bus whenever a status transition is detected between two consecutive data updates. These events can be used to trigger automations (e.g. send a notification when pH becomes bad).

Chemistry status changed¶

Fired when an individual chemistry parameter transitions between good, warning, and bad, or becomes available/unavailable.

Water status changed¶

Fired when the overall water quality flips between OK and not OK (based on whether high/critical recommendations exist).

automation:
  - alias: "Notify when pH goes bad"
    trigger:
      - platform: event
        event_type: poolman_event
        event_data:
          type: chemistry_status_changed
          parameter: ph
          status: bad
    action:
      - service: notify.mobile_app
        data:
          title: "Pool Alert"
          message: "pH has gone out of range!"