Changelog
Get these entries by email, or subscribe with any RSS reader at /changelog.xml. The latest entry is also shown at the top of every page.
2026-10-14
Section titled “2026-10-14”- Heating on Device API v1. New
temperatureInfoandsetTemperatureInfoendpoints read and set the pool and spa targets and the heater selection; the same page explains spa mode throughmanualSet. - Schedule writes validated.
createScheduleandupdateSchedulenow return400when a main-pump schedule has nopump_speedin 40 to 100, and422when the controller refuses a schedule, instead of200with an error insidedata.message. See Status codes.
2026-10-12
Section titled “2026-10-12”- Device API v1 pages re-checked against the controller firmware. Corrections across Reading state, Chemistry, Pump and equipment control, Schedules and Equipment types:
schedule_numis 0 to 19;dry_run_statuscodes;water_tempon the dashboard is °C × 10;pump_typestrings;main_pump_statussemantics; units for dose times, intervals and rates;reset_*_volumebehaviour; the 37-slotauxAssignarrays andequipmentlabels;pool_volumeis ignored andturn_overnever set through the API; schedule writes auto-enable and controller refusals come back as200;scheduleInfonever returns503; manual overrides, heater cool-down, interlocks and speed priorities are now described as the controller implements them; codes 35 to 38 added. Two API fixes shipped with this:setChlorineSettingsnow forwardsmineral_max_duration_predayinstead of zeroing it on every write, andchemistryCard.auxAssign.equipmentlabels andbrandnow use the real equipment type names. - Client signature samples and test vector. Client signature now has a fixed test vector to check your implementation against, and signing code in Python, Node.js, Go, Java, C#, PHP and shell.
- Private integrations need no client. Get client credentials now says up front that software acting only on your own account can use Direct sign-in instead of requesting a client.
2026-10-09
Section titled “2026-10-09”- Staged availability documented. What is available today now states which parts of the API third-party clients can use: authentication and the user and site endpoints are available; Device API v1 is enabled per client on request; Device API v2 in the cloud is internal to the SplashMe development team; Command Protocol v2 on the LAN is open for testing. Nothing in the API itself changed.
2026-09
Section titled “2026-09”-
Audit events are now collected on request. Controllers on firmware 2.5.46 and later no longer upload events on their own; the cloud asks when a controller comes online, every few minutes, and through the new
POST …/events/pullendpoint.POST …/events/rewindnow moves the controller’s marker and starts a collection. -
Device API v2 published under
/api-gateway/v2for controllers on firmware 2.5.46 or later: merged state document, on-demand refresh, per-device envelope key, signed queries and actions, audit events with rewind. -
Command Protocol v2 documented for direct implementation, including LAN access on port 8080 and mDNS discovery.
-
Per-controller throttling now returns
429with aretry after Nshint instead of timing out.
2026-08
Section titled “2026-08”- OAuth2 API gateway launched: authorization code flow with PKCE, refresh tokens, password grant for approved clients, client credentials issued on request, and the curated Device API v1 surface.

