Heating and spa
The controller heats the pool and the spa to separate target temperatures using whichever heat sources are selected: a pool heater, a spa heater (or one combined heater) and solar. Which heat source runs at a given moment is the controller’s decision; the API sets the targets and the selection.
Read targets and heater state
Section titled “Read targets and heater state”GET…/temperatureInfo
{ "status": "SUCCESS", "data": { "temperatureInfo": { "temperature": [ { "category": "pool", "solar_temp": 2450, "water_temp": 265, "target_temp": 28, "is_solar_heater_selected": false, "is_pool_heater_selected": true, "is_spa_heater_selected": false, "is_solar_heater_on": false, "is_pool_heater_on": true, "is_spa_heater_on": false }, { "category": "spa", "solar_temp": 2450, "water_temp": 265, "target_temp": 38, "is_solar_heater_selected": false, "is_pool_heater_selected": true, "is_spa_heater_selected": false, "is_solar_heater_on": false, "is_pool_heater_on": true, "is_spa_heater_on": false } ], "is_mp_en": true, "temp2_ch": 0, "temp3_ch": 0 } }}| Field | Meaning |
|---|---|
category |
pool or spa. Only target_temp differs between the two entries; the readings and the selection are shared |
target_temp |
Target temperature for that category, whole °C |
water_temp |
Current water temperature, °C × 10 |
solar_temp |
Roof or air sensor, °C × 100 |
is_*_selected |
The heat sources the controller may use |
is_*_on |
The heat source outputs energised right now. is_pool_heater_on and is_spa_heater_on are both true when a combined pool and spa heater is on |
is_mp_en, temp2_ch, temp3_ch |
Sensor configuration set at commissioning: whether the chemistry probe is enabled and which input each extra temperature sensor uses. Read-only in practice; see below |
This read is cached like the others (see How reads work). The cached copy expires after 10 minutes.
Set targets and heater selection
Section titled “Set targets and heater selection”POST…/setTemperatureInfo
{ "desire_pool_temp": 28, "desire_spa_temp": 38, "is_solar_heater_selected": false, "is_pool_heater_selected": true, "is_spa_heater_selected": false}| Field | Type | Range | Meaning |
|---|---|---|---|
desire_pool_temp |
int | 0 to 40 | Pool target, whole °C |
desire_spa_temp |
int | 0 to 40 | Spa target, whole °C |
is_solar_heater_selected |
bool | Allow solar heating | |
is_pool_heater_selected |
bool | Allow the pool heater | |
is_spa_heater_selected |
bool | Allow the spa heater |
The controller replaces all five values with what you send and any field you omit becomes 0 or false, so read temperatureInfo first and send the complete set. Values outside the range return 400 with a message such as desire_pool_temp must be 0-40 (got 45). The API carries the controller’s sensor configuration (temp2_ch, temp3_ch) across unchanged; do not send those fields unless SplashMe support asks you to.
Response: 200 with data.message holding the controller’s acknowledgement string. The write waits up to 3 seconds and clears the cached temperatureInfo and dashboardInfo. Changing the selection while the pump is running takes effect at once; otherwise it applies when the pump next runs.
Spa mode
Section titled “Spa mode”Spa mode is not a setting: it is the state of the spa actuator outputs. Switch any spa actuator slot (type 20, 21, 33 or 34, listed in auxInfo.spa) with manualSet and the controller moves all of them together, starts the main pump at the spa speed and heats towards desire_spa_temp with the spa heater. Switching any of them off ends spa mode and clears the pump override that spa mode held. auxInfo shows the actuators’ aux_status and dashboardInfo.spa_heater_state shows whether the spa heater is on.
Heater cool-down after a spa or heating session is described under Manual overrides.

