ClimateFleet reference stack

Bench test

Primary path (P1 XY-MD02 + 4G DTU): bench tested. Other profiles: pending.

Fleet dashboard for temperature and humidity sensors. Device type: ht_sensor.

Dashboard notes: ClimateFleet (dashboard).

---

Telemetry contract

Key	Unit	Typical range (indoor)
temperature	°C	About 18–32 (comfort); alarms per profile
humidity	%RH	About 35–75

---

Reference sensor (bench tested — P1)

Item	Detail
Sensor	XY-MD02 RS485 Modbus temperature & humidity probe
Datasheet / map	Factory default 9600 8N1, slave ID often 1 — holding registers for temp/RH (see DR154 guide register table)
Environment	Indoor / duct mount per probe rating

---

Connectivity options

Profile	Guide	Status
P1 4G DTU	DR154 + XY-MD02	Bench tested
P2 ESP32 WiFi	ESP32 Modbus edge with XY-MD02 map	Pending bench test
P4 Native WiFi sensor	MQTT JSON with temperature / humidity	BYO

---

Wiring — P1

flowchart LR
  AC[Autoconnecto]
  GW[htgateway]
  DTU[4G DTU]
  XY[XY-MD02 RS485]
  AC --> GW
  GW <-->|MQTT| DTU
  DTU --> XY

RS485	Notes
Power	Per XY-MD02 manual (often 5–24 V DC)
A/B	To DTU; confirm polarity
Termination	120 Ω if long bus

---

Wiring — P2 (lab / office WiFi)

flowchart LR
  AC[Autoconnecto MQTT]
  ESP[ESP32 + MAX485]
  XY[XY-MD02]
  AC <--> ESP
  ESP --> XY

Use the same Modbus addresses as the DR154 child map; publish JSON to device token.

---

Autoconnecto checklist

• [ ] Create gateway + child devices linked with parentDeviceId (Sample On demos this topology)
• [ ] Child device type ht_sensor
• [ ] Child on Modbus gateway (P1) or direct MQTT device (P2/P4)
• [ ] Keys exactly temperature, humidity on the child
• [ ] Optional hub health: publish gateway.heartbeat on the gateway token (no childDeviceId)
• [ ] Gateway shows Active from hub heartbeat and/or any active child

---

Related

• Reference stacks
• Connectivity profiles