Custom Component: Hayward Aquarite

Awesome!!!

Is it under 0.3.4 version?

Regards

still testing, new release soon

1 Like

I can no longer update those values, does it work on your end with current release ?

{‘gateway’: ‘NODE_AWSxxxxx’, ‘poolId’: ‘05xxxxxxxxxx’, ‘operation’: ‘WRP’, ‘operationId’: None, ‘changes’: ‘{“modules”: {“ph”: {“current”: “785”, “tank”: 0, “al3”: 0, “pump_low_on”: 0, “status”: {“high_value”: 768, “low_value”: “650”}, “pump_high_on”: 0, “type”: “ACID”}}}’, ‘pool’: None, ‘source’: ‘web’}

No, it doesn´t.

You only can put 730, 735, 740, 745…so the step should be 0,05 points.

Regards

found it, I was loosing the pool because of the atmospheric situation and my network RSSI below expectation. Pool is distant and wifi is sometimes not at best.

Fixed, and new release available 0.3.5

Just downloaded, it works perfectly @fdebrus.

Once again, keep on pushing! Thanks for your effort.

By the way, cell time is something I do not understand at all.

the “off” here in the middle of the official web user interface is related to the PH Pump, so it’s used and should be updated accordingly.

Cell Time, still a mistery :slight_smile:

Future release will include a fix for Hydrolysis to be correctly reported in gram by hour and renamed to Electrolysis

Testing now…

image

I had a draft message just to ask for those 2 things !!!

Great!

Thanks @fdebrus

Hi @fdebrus

One last change I would propose would be to change the scale of the Electrolysis Setpoint to 0-22 instead of hundreds, wouldnt it?

This value is dynamic, my guess is that it is based on your model and the amount that can be produced by the cell.

int(dataservice.get_value(“hidro.maxAllowedValue”))/10

now, we are obviously not on the latest release, it shall report 22 not 220 :slight_smile:

Just running last version, it works perfectly!!!

I think we shall get rid of, it is useless

Useless at all.

If you are interested in available data points, I took the most obvious, more could be added as we see fit.

Available data points

Top-Level

  • id
  • present
  • company
  • updatedAt
  • createdAt
  • wifi
  • isAWS

modules.uv

  • modules.uv.status
  • modules.uv.total
  • modules.uv.partial

modules.rx

  • modules.rx.status.value
  • modules.rx.pump_status
  • modules.rx.tank
  • modules.rx.current

modules.ph

  • modules.ph.al3
  • modules.ph.pump_high_on
  • modules.ph.status.low_value
  • modules.ph.status.high_value
  • modules.ph.pump_low_on
  • modules.ph.current
  • modules.ph.tank
  • modules.ph.type

modules.io

  • modules.io.activation
  • modules.io.status
  • modules.io.level

modules.cl

  • modules.cl.status.value
  • modules.cl.pump_status
  • modules.cl.tank
  • modules.cl.current

modules.cd

  • modules.cd.status.value
  • modules.cd.current
  • modules.cd.tank

backwash

  • backwash.startAt
  • backwash.interval
  • backwash.status
  • backwash.frequency
  • backwash.mode
  • backwash.remainingTime

light

  • light.status
  • light.freq
  • light.to
  • light.mode
  • light.from

form

  • form.street
  • form.zipcode
  • form.country
  • form.lat
  • form.name
  • form.city
  • form.active
  • form.names (list of objects: name, user for each)
  • form.lng

relays.relay1.info

  • relays.relay1.name
  • relays.relay1.info.delay
  • relays.relay1.info.to2
  • relays.relay1.info.status
  • relays.relay1.info.freq
  • relays.relay1.info.onoff
  • relays.relay1.info.from
  • relays.relay1.info.tiempoOn
  • relays.relay1.info.manAutoTemp
  • relays.relay1.info.polarity
  • relays.relay1.info.from2
  • relays.relay1.info.to
  • relays.relay1.info.signal
  • relays.relay1.info.freq2
  • relays.relay1.info.key

Repeat similar structure for:

  • relays.relay2.info
  • relays.relay3.info
  • relays.relay4.info
  • (each has similar fields, but names and values can differ)

relays.ph.base

  • relays.ph.base.gpio
  • relays.ph.acid.gpio

relays.uv

  • relays.uv.gpio

relays.cd

  • relays.cd.gpio

relays.io

  • relays.io.gpio

relays.cl

  • relays.cl.gpio

relays.rx

  • relays.rx.gpio

relays.backwash

  • relays.backwash.gpio

relays.light

  • relays.light.gpio

relays.filtration.heating

  • relays.filtration.heating.status
  • relays.filtration.heating.gpio

relays.filtration

  • relays.filtration.gpio

main

  • main.hasLCD
  • main.localTime
  • main.hasLinked
  • main.hideFiltration
  • main.version
  • main.hasUV
  • main.hasIO
  • main.hideTemperature
  • main.LEDPulse
  • main.hasWifi
  • main.RSSI
  • main.hasCL
  • main.hasLinkedAuto
  • main.hasBackwash
  • main.hideLighting
  • main.FWU_enabled
  • main.hideRelays
  • main.hasPH
  • main.hasLED
  • main.hasCD
  • main.networkPresent
  • main.hasRX
  • main.hasHidro
  • main.wifiVersion
  • main.temperature

hidro

  • hidro.maxAllowedValue
  • hidro.measure
  • hidro.cellPartialTime
  • hidro.is_electrolysis
  • hidro.al4
  • hidro.temperature_enabled
  • hidro.temperature_value
  • hidro.cover
  • hidro.cloration_enabled
  • hidro.hasHidroControl
  • hidro.low
  • hidro.level
  • hidro.cellTotalTime
  • hidro.current
  • hidro.cover_enabled
  • hidro.control
  • hidro.reduction
  • hidro.fl2
  • hidro.fl1

filtration

  • filtration.hasSmart
  • filtration.intel.temp
  • filtration.intel.time
  • filtration.timerVel3
  • filtration.timerVel1
  • filtration.interval3.to
  • filtration.interval3.from
  • filtration.interval1.to
  • filtration.interval1.from
  • filtration.timerVel2
  • filtration.status
  • filtration.heating.temp
  • filtration.heating.tempHi
  • filtration.heating.clima
  • filtration.smart.tempMin
  • filtration.smart.freeze
  • filtration.smart.tempHigh
  • filtration.manVel
  • filtration.hasHeat
  • filtration.mode
  • filtration.pumpType
  • filtration.interval2.to
  • filtration.interval2.from

Just came accross the below

The Hayward wifi module talk to Amazon web services.
The user front end “web” and “mobile” talk to google cloud services.

No wonder why we have delay sometimes… :slight_smile:

Hi guys. v0.3.8 is great. Works perfect with the newest model (2025) of Aquarite Flo Advanced.

Thank you for your great work!

1 Like

Is it possible to act on modules.ph.al3 or is it just readonly?
I would like to reset the al3 alarm remotely.

You cannot reset the AL‑3 (pH timeout) error remotely through the Hayward mobile app. This type of alert, triggered when acid dosing takes too long, must be cleared locally at the control unit, after you’ve fixed the root cause.

so if the official app does not support ir, we can’t do it from the integration.

New release

Added

  • Home Assistant service to synchronize pool time with Home Assistant.