<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>SplashMe Open API changelog</title><description>Changes to the SplashMe Open API and its documentation that affect integrators.</description><link>https://developers.splashmepool.com.au</link><language>en-au</language><item><title>Heating on Device API v1 · Schedule writes validated</title><link>https://developers.splashmepool.com.au/reference/changelog/#2026-10-14</link><guid isPermaLink="true">https://developers.splashmepool.com.au/reference/changelog/#2026-10-14</guid><pubDate>Wed, 14 Oct 2026 00:00:00 GMT</pubDate><content:encoded>&lt;ul&gt;&lt;li&gt;&lt;strong&gt;Heating on Device API v1.&lt;/strong&gt; New &lt;a href=&quot;https://developers.splashmepool.com.au/device-api-v1/heating/&quot;&gt;&lt;code&gt;temperatureInfo&lt;/code&gt; and &lt;code&gt;setTemperatureInfo&lt;/code&gt;&lt;/a&gt; endpoints read and set the pool and spa targets and the heater selection; the same page explains spa mode through &lt;code&gt;manualSet&lt;/code&gt;.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Schedule writes validated.&lt;/strong&gt; &lt;code&gt;createSchedule&lt;/code&gt; and &lt;code&gt;updateSchedule&lt;/code&gt; now return &lt;code&gt;400&lt;/code&gt; when a main-pump schedule has no &lt;code&gt;pump_speed&lt;/code&gt; in 40 to 100, and &lt;code&gt;422&lt;/code&gt; when the controller refuses a schedule, instead of &lt;code&gt;200&lt;/code&gt; with an error inside &lt;code&gt;data.message&lt;/code&gt;. See &lt;a href=&quot;https://developers.splashmepool.com.au/device-api-v1/overview/#status-codes&quot;&gt;Status codes&lt;/a&gt;.&lt;/li&gt;&lt;/ul&gt;</content:encoded></item><item><title>Device API v1 pages re-checked against the controller firmware · Client signature samples and test vector · Private integrations need no client</title><link>https://developers.splashmepool.com.au/reference/changelog/#2026-10-12</link><guid isPermaLink="true">https://developers.splashmepool.com.au/reference/changelog/#2026-10-12</guid><pubDate>Mon, 12 Oct 2026 00:00:00 GMT</pubDate><content:encoded>&lt;ul&gt;&lt;li&gt;&lt;strong&gt;Device API v1 pages re-checked against the controller firmware.&lt;/strong&gt; Corrections across &lt;a href=&quot;https://developers.splashmepool.com.au/device-api-v1/reading-state/&quot;&gt;Reading state&lt;/a&gt;, &lt;a href=&quot;https://developers.splashmepool.com.au/device-api-v1/chemistry/&quot;&gt;Chemistry&lt;/a&gt;, &lt;a href=&quot;https://developers.splashmepool.com.au/device-api-v1/equipment/&quot;&gt;Pump and equipment control&lt;/a&gt;, &lt;a href=&quot;https://developers.splashmepool.com.au/device-api-v1/schedules/&quot;&gt;Schedules&lt;/a&gt; and &lt;a href=&quot;https://developers.splashmepool.com.au/device-api-v1/equipment-types/&quot;&gt;Equipment types&lt;/a&gt;: &lt;code&gt;schedule_num&lt;/code&gt; is 0 to 19; &lt;code&gt;dry_run_status&lt;/code&gt; codes; &lt;code&gt;water_temp&lt;/code&gt; on the dashboard is °C × 10; &lt;code&gt;pump_type&lt;/code&gt; strings; &lt;code&gt;main_pump_status&lt;/code&gt; semantics; units for dose times, intervals and rates; &lt;code&gt;reset_*_volume&lt;/code&gt; behaviour; the 37-slot &lt;code&gt;auxAssign&lt;/code&gt; arrays and &lt;code&gt;equipment&lt;/code&gt; labels; &lt;code&gt;pool_volume&lt;/code&gt; is ignored and &lt;code&gt;turn_over&lt;/code&gt; never set through the API; schedule writes auto-enable and controller refusals come back as &lt;code&gt;200&lt;/code&gt;; &lt;code&gt;scheduleInfo&lt;/code&gt; never returns &lt;code&gt;503&lt;/code&gt;; 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: &lt;code&gt;setChlorineSettings&lt;/code&gt; now forwards &lt;code&gt;mineral_max_duration_preday&lt;/code&gt; instead of zeroing it on every write, and &lt;code&gt;chemistryCard.auxAssign.equipment&lt;/code&gt; labels and &lt;code&gt;brand&lt;/code&gt; now use the real equipment type names.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Client signature samples and test vector.&lt;/strong&gt; &lt;a href=&quot;https://developers.splashmepool.com.au/authentication/client-signature/&quot;&gt;Client signature&lt;/a&gt; now has a fixed test vector to check your implementation against, and signing code in Python, Node.js, Go, Java, C#, PHP and shell.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Private integrations need no client.&lt;/strong&gt; &lt;a href=&quot;https://developers.splashmepool.com.au/getting-started/register-client/&quot;&gt;Get client credentials&lt;/a&gt; now says up front that software acting only on your own account can use &lt;a href=&quot;https://developers.splashmepool.com.au/authentication/direct-login/&quot;&gt;Direct sign-in&lt;/a&gt; instead of requesting a client.&lt;/li&gt;&lt;/ul&gt;</content:encoded></item><item><title>Staged availability documented</title><link>https://developers.splashmepool.com.au/reference/changelog/#2026-10-09</link><guid isPermaLink="true">https://developers.splashmepool.com.au/reference/changelog/#2026-10-09</guid><pubDate>Fri, 09 Oct 2026 00:00:00 GMT</pubDate><content:encoded>&lt;ul&gt;&lt;li&gt;&lt;strong&gt;Staged availability documented.&lt;/strong&gt; &lt;a href=&quot;https://developers.splashmepool.com.au/overview/availability/&quot;&gt;What is available today&lt;/a&gt; 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.&lt;/li&gt;&lt;/ul&gt;</content:encoded></item><item><title>Audit events are now collected on request · Device API v2 · Command Protocol v2 · Per-controller throttling now returns `429` with a `retry after Ns` hint instead of timing out</title><link>https://developers.splashmepool.com.au/reference/changelog/#2026-09</link><guid isPermaLink="true">https://developers.splashmepool.com.au/reference/changelog/#2026-09</guid><pubDate>Tue, 01 Sep 2026 00:00:00 GMT</pubDate><content:encoded>&lt;ul&gt;&lt;li&gt;&lt;strong&gt;Audit events are now collected on request.&lt;/strong&gt; 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 &lt;code&gt;POST …/events/pull&lt;/code&gt; endpoint. &lt;code&gt;POST …/events/rewind&lt;/code&gt; now moves the controller&apos;s marker and starts a collection.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Device API v2&lt;/strong&gt; published under &lt;code&gt;/api-gateway/v2&lt;/code&gt; for 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.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Command Protocol v2&lt;/strong&gt; documented for direct implementation, including LAN access on port 8080 and mDNS discovery.&lt;/li&gt;&lt;li&gt;Per-controller throttling now returns &lt;code&gt;429&lt;/code&gt; with a &lt;code&gt;retry after Ns&lt;/code&gt; hint instead of timing out.&lt;/li&gt;&lt;/ul&gt;</content:encoded></item><item><title>OAuth2 API gateway launched</title><link>https://developers.splashmepool.com.au/reference/changelog/#2026-08</link><guid isPermaLink="true">https://developers.splashmepool.com.au/reference/changelog/#2026-08</guid><pubDate>Sat, 01 Aug 2026 00:00:00 GMT</pubDate><content:encoded>&lt;ul&gt;&lt;li&gt;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.&lt;/li&gt;&lt;/ul&gt;</content:encoded></item></channel></rss>