CLIMATE · geyser

Geyser

Water heater with temperature and energy telemetry.

3 capabilitiesREST + secure WebSocketProduction schema

OVERVIEW

Built from capabilities, not assumptions.

Geyser is a canonical HomeAutoPro climate template. The same production capability schema drives validation, controls, reported state, telemetry, scenes and automations. Undeclared keys are rejected.

WRITABLE CAPABILITIES

Controls

ControlTypeRange / valuesDescription

PowerpowerbooleanON / OFFWritable through validated owner commands and automations.

DEVICE → HOMEAUTOPRO

Feedback / state

Every connected device also reports online state and last-seen time. Applied values remain distinct from requested values until the device acknowledges them.

Powerpower

boolean. Report the value actually applied after each command.

Water Temperaturetemperature

number · °C. Read-only device feedback.

Energyenergy_kwh

number · kWh. Read-only device feedback.

TIME-SERIES VALUES

Telemetry

Water Temperaturetemperature

Validated number in °C, 0–100. Publish in a telemetry message.

Energyenergy_kwh

Validated number in kWh, 0–100000. Publish in a telemetry message.

CAPABILITY-AWARE WORKFLOWS

Automations

Triggers

State/telemetry changes for power, temperature, energy_kwh, plus online and offline events.

Actions

Validated commands for power. Applied state is reported as ACK.

ACTUAL PRODUCTION PROTOCOL

Payloads and acknowledgement

Dashboard/API→HomeAutoPro→Device→Applied-state ACK

Authenticate

{"type":"auth","device_secret":"YOUR_DEVICE_SECRET"}

Command

{
  "event": "command",
  "state": {
    "power": true
  }
}

State ACK

{
  "state": {
    "power": true
  },
  "type": "state"
}

Telemetry

{
  "telemetry": {
    "energy_kwh": 50000.0,
    "temperature": 50.0
  },
  "type": "telemetry"
}

CAPABILITY-GENERATED EXAMPLES

Sample code

Choose one platform. All examples use the production protocol and placeholders; no stored secret is retrieved.

#include <ESP8266WiFi.h>
#include <ArduinoJson.h>
#include <WebSocketsClient.h>

const char* DEVICE_CODE = "YOUR_DEVICE_ID";
const char* DEVICE_SECRET = "YOUR_DEVICE_SECRET";
WebSocketsClient socket;

// Handle only: power
// Connect: socket.beginSSL("api.homeautopro.in", 443, path);
// First message: {"type":"auth","device_secret":DEVICE_SECRET}
// After a command, publish {"type":"state","state":applied}.

#include <WiFi.h>
#include <ArduinoJson.h>
#include <WebSocketsClient.h>

const char* DEVICE_CODE = "YOUR_DEVICE_ID";
const char* DEVICE_SECRET = "YOUR_DEVICE_SECRET";
// Use TLS port 443 and the same authenticated command/state ACK lifecycle.
// Generate handlers only for: power

import requests

url = "https://homeautopro.in/api/device-ingest/DEVICE_CODE/telemetry"
headers = {"X-Device-Secret": "YOUR_DEVICE_SECRET"}
payload = {"telemetry": {"energy_kwh": 50000.0, "temperature": 50.0}}
response = requests.post(url, headers=headers, json=payload, timeout=10)
response.raise_for_status()

const response = await fetch(
  "https://homeautopro.in/api/device-ingest/DEVICE_CODE/telemetry",
  { method: "POST", headers: { "X-Device-Secret": "YOUR_DEVICE_SECRET", "Content-Type": "application/json" },
    body: JSON.stringify({"telemetry": {"energy_kwh": 50000.0, "temperature": 50.0}}) }
);
if (!response.ok) throw new Error(`HomeAutoPro ${response.status}`);

curl --fail-with-body -X POST \
  -H "X-Device-Secret: YOUR_DEVICE_SECRET" \
  -H "Content-Type: application/json" \
  -d '{"telemetry": {"energy_kwh": 50000.0, "temperature": 50.0}}' \
  https://homeautopro.in/api/device-ingest/DEVICE_CODE/telemetry

SAFE DIAGNOSTICS

Troubleshooting

401 authentication

Use the current Device Secret locally. Rotate it in Device Details if it was lost.

422 validation

Compare every key, type and range with the capability schema above.

No command ACK

Publish the value actually applied after handling event=command.