Custom Component: Hayward Aquarite

Share your Projects! Custom Integrations
123

your version “version”: 1027 is more advanced than mine, could explain why I’m missing some options.

could you tell me your exact Aquarite model ?

124

its a Oxilife , not Aquarite, the app is “Vistapool”

125

New release 1.2.0, be aware of BREAKING CHANGES see below or release notes, I’m preparing the custom_component for official integration submission, so I do have to follow some HA guidelines and standards that will rename some entities…

New Features

  • Filtration schedule control — Filtration interval start/end times are now editable time entities with native time pickers (previously read-only sensors)
  • Timer speed control — Filtration timer speeds 1-3 are now select entities with Slow/Medium/High dropdowns (previously read-only sensors)
  • Per-mode temperature settings — Intel, Heat, and Smart mode temperatures exposed as adjustable number entities with sliders
  • Smart mode controls — Freeze protection toggle and min/max temperature setpoints
  • Heating mode controls — Min/max temperature setpoints and climate toggle
  • LED pulse button — Advances pool LED to next color (gated behind hasLED hardware flag)
  • Options flow — Configurable health check interval (60–3600s) via Settings → Configure
  • Expanded binary sensors — pH base pump, chlorine pump status, Rx pump status, acid tank level

Bug Fixes

  • Fix time sync service — Now writes Unix timestamp to main.localTime (previously wrote to non-existent main.time path with no effect)
  • Fix time sync timezone — Add UTC offset so controller receives local time instead of UTC
  • Fix LED pulse button — Write to light.status with off-delay-on cycle for proper color advance
  • Fix config flow error handling — Proper handling of auth errors, subscription race conditions, and reauth UX

Quality Improvements

  • Options flow for runtime configuration
  • Standardized unique_id delimiters — all entities now use consistent hyphen delimiter
  • Complete translation coverage — strings.json, icons.json, and all translation files (en, nl, da) fully synced with 70 entity keys
  • Manifest updates — added button/time to supported platforms, homeassistant version constraint (2024.1.0), issue_tracker URL
  • Test suite — 22+ tests covering value conversions, data navigation, config flow, coordinator, and options flow
  • GitHub Actions CI — automated test runs on push and PRs (Python 3.12/3.13)
  • Updated example dashboard YAML with new entity types and interactive controls

:warning: Breaking Changes

After upgrading, you will need to remove stale entities from the entity registry and reload the integration for the following changes:

Old Entity New Entity
sensor.pool_filtration_interval_* time.pool_filtration_interval_*
sensor.pool_filtration_timer_speed_* select.pool_filtration_timer_speed_*
sensor.pool_filtration_intel_temperature number.pool_intel_mode_temperature
sensor.pool_filtration_smart_min_temp number.pool_smart_mode_min_temperature
sensor.pool_filtration_smart_high_temp number.pool_smart_mode_max_temperature
binary_sensor.pool_filtration_smart_freeze switch.pool_smart_mode_freeze_protection

Additionally:

  • Unique ID format changed for switch, select, light, and button entities — existing entities will need to be removed and re-registered
  • LED pulse button now only appears when controller reports hasLED=1
  • Automations and dashboard cards referencing old entity IDs will need to be updated (see updated aquarite_dashboard.yaml for reference)
1 Like
127

The Hayward AquaRite custom integration is going official as Vistapool: Vistapool - Home Assistant

I'm starting with sensors only. Additional PRs into the official channel will bring the current custom integration and the future official one up to parity in terms of functionality. Once that's done, the custom integration will no longer be supported.

Monitor this space for updates.

128

Awesome job.

I forgot to tell you that now I created a full local-only custom integration (the package version is deprecated):

Time to update the OP with both your Vistapool official integration and my local-only custom integration. :slight_smile:

Thanks for inspiring me to create it...

129

@fdebrus maybe a little too off-topic of a question but since you are working on control integrations related to automations for pools wondering what you and others here think about this feature request idea of adding a pool cleaner entity domain for pool cleaning devices (forking the existing vacuum entity domain?

Not sure which API they use today but I at least know that they are a few Hayward-branded pool cleaner robots but it might still be relevant in the future if extend support to pool cleaner robots. everyone here can feel free to post feedback/input comments there in tnag upstream feature request.

130

@alexdelprete well done, I like your local integration very much ! always a source of inspiration.

@Gamester17 I guess this is a total different platform, do you have a website where you connect to manage your pool robots ?

1 Like
131

Question to all, if you have a Wifi module connected to your system, how does it names ? do you all have "SugarWifi" as hostname in your DHCP ?

132

Hi @fdebrus ,

First of all, thanks for all the work and the time spent developing this integration (now Official!) for Home Assistant. I just installed it and it's working great! I'm so thankful.

My only question is if you know, approx, when will we be able to control the pool options, like filtration, redox target, pH target, filtration mode, light, and AUX relays. I don't know if you have any plan adding this or not.

Again, very thankful for the official integration!

133

Thanks so much, appreciate it! :folded_hands:

Good news: control of those features (filtration, redox and pH targets, filtration mode, light, and the AUX relays) is exactly what's being worked on right now. It's all moving through review rather than waiting to be started.

The best way to follow progress is to keep an eye on the open Pull Requests for Vistapool. The HA Core team is doing an incredible job reviewing everything, fine-tuning it, and aligning it with Home Assistant's standards and they're doing this across thousands of contributions project-wide.

Vistapool alone represents 16 Pull Requests in total (around 10 still open) along with all their reviews, so they're putting serious care into making sure what lands in HA Core is solid and robust. Worth the wait!

You can track them all here: Pull requests · home-assistant/core