Power Strip
Multi-outlet power control.
Built from capabilities, not assumptions.
Power Strip is a canonical HomeAutoPro energy template. The same production capability schema drives validation, controls, reported state, telemetry, scenes and automations. Undeclared keys are rejected.
Controls
outlet_1booleanON / OFFWritable through validated owner commands and automations.outlet_2booleanON / OFFWritable through validated owner commands and automations.outlet_3booleanON / OFFWritable through validated owner commands and automations.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.
outlet_1boolean. Report the value actually applied after each command.
outlet_2boolean. Report the value actually applied after each command.
outlet_3boolean. Report the value actually applied after each command.
power_wnumber · W. Read-only device feedback.
Telemetry
power_wValidated number in W, 0–10000. Publish in a telemetry message.
Automations
State/telemetry changes for outlet_1, outlet_2, outlet_3, power_w, plus online and offline events.
Validated commands for outlet_1, outlet_2, outlet_3. Applied state is reported as ACK.
Payloads and acknowledgement
Authenticate
{"type":"auth","device_secret":"YOUR_DEVICE_SECRET"}Command
{
"event": "command",
"state": {
"outlet_1": true,
"outlet_2": true,
"outlet_3": true
}
}State ACK
{
"state": {
"outlet_1": true,
"outlet_2": true,
"outlet_3": true
},
"type": "state"
}Telemetry
{
"telemetry": {
"power_w": 5000.0
},
"type": "telemetry"
}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: outlet_1, outlet_2, outlet_3
// 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: outlet_1, outlet_2, outlet_3import requests
url = "https://homeautopro.in/api/device-ingest/DEVICE_CODE/telemetry"
headers = {"X-Device-Secret": "YOUR_DEVICE_SECRET"}
payload = {"telemetry": {"power_w": 5000.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": {"power_w": 5000.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": {"power_w": 5000.0}}' \
https://homeautopro.in/api/device-ingest/DEVICE_CODE/telemetryTroubleshooting
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.