Question: Is /v2/spa/temperature working for you?

[jolexa]

Hello,
I'm not using your package and I have my own REST automations. I found that PUT /v2/spa/temperature responds with a 200 but doesn't actually change my setpoint. This behavior was confirmed on https://api.myarcticspa.com/docs as well. Are you experiencing the same thing? Thanks

[jensenbox]

Thanks for the detailed report. I just tested PUT /v2/spa/temperature with {"setpointF": N} against my own spa via the same v2 API — it changed my setpoint from 98→97 (and back), returning 200 with an empty [] body each time. So the documented endpoint does apply on my account, and that's exactly the call this integration makes.

Since it's a no-op for you but works here, it looks spa- or firmware-specific rather than a universal API problem. A few things that would help narrow it down:

• What spa model / firmware are you on?
• Does the setpoint change show in the myarcticspa.com web UI, or only fail via the API?
• Can you confirm the X-API-KEY is for the same spa you're reading /status from?

One thing worth flagging: the PUT returns 200 with an empty [] body even on success, so a 200 by itself isn't a reliable 'it applied' signal — the only sure check is re-reading /status afterward (which is what the integration does on its next poll). Happy to dig in further with those details.