Appearance
SmartHomeFleet reference stack
Bench test
Pending bench test — Validation status.
Fleet dashboard for connected homes. Device type: smart_home.
Telemetry contract
| Key | Unit | Notes |
|---|---|---|
temperature | °C | Indoor ambient |
humidity | %RH | Indoor RH |
power_kw | kW | Whole-home or circuit power |
motion | boolean | Room / hall motion |
Reference hardware (pending bench test)
| Role | Class / example | Protocol |
|---|---|---|
| Climate | DHT22 / SHT3x / XY-MD02 | I²C / Modbus |
| Power | PZEM-004T / Shelly / CT energy monitor | UART Modbus / MQTT |
| Motion | PIR HC-SR501 or mmWave | GPIO |
| Hub | Zigbee/Z-Wave bridge (optional) | Hub → MQTT (P5) |
Status: Pending bench test — prefer native MQTT (P4) for consumer gear when available.
Connectivity options
| Profile | Edge | Link | Status |
|---|---|---|---|
| P4 | Shelly / Tasmota / SDK device | WiFi MQTT | Pending |
| P2 | ESP32 + DHT + PZEM + PIR | WiFi | Pending |
| P5 | Home hub relays rooms as children | WiFi / Ethernet | BYO |
| P1 | Rare — Modbus meters via 4G DTU | 4G | BYO |
| P6 | LoRaWAN sensors via ChirpStack | RF → webhook | Pending |
Wiring — P2 (ESP32 home kit)
mermaid
flowchart LR
AC[Autoconnecto]
ESP[ESP32]
SHT[Temp RH]
PZEM[Energy monitor]
PIR[Motion]
AC <-->|WiFi MQTT| ESP
ESP --> SHT
ESP --> PZEM
ESP --> PIRUse device token MQTT (Check connectivity). Publish temperature, humidity, power_kw, motion.
Wiring — P4 (native WiFi)
Configure the vendor MQTT client with Autoconnecto broker/token; map payload fields to Solution keys (Integration Hub if names differ).
Checklist
- [ ] Device type
smart_home - [ ] CT/power wiring by qualified person if mains-side
- [ ] Motion privacy expectations documented for occupants
