Use hottubctl spas and hottubctl temp get before a write when the selected
spa, unit, or current state is unclear. Temperature writes require --yes; the
flag confirms intent, not physical safety.
hottubctl temp set VALUE --yes:
- loads the private account configuration;
- logs in through
python-smarttub; - selects an exact configured spa, or the account's only spa;
- converts Fahrenheit input to Celsius when needed;
- sends the target temperature;
- reads spa status again; and
- reports the target value returned by SmartTub.
The returned setpoint confirms cloud/API state, not current water temperature.
Use temp get and physical controls for follow-up verification.
Connectivity status and temperature telemetry can have different timestamps. When the spa is offline, temperatures may be last-known values. The CLI reports their available ages and adds an explicit freshness note instead of treating them as live.
Automated tests never log in or perform writes. Before a release that changes write behavior, validate a supervised read, a small safe setpoint change, the returned target, and a restore to the original target.