Reference stacks

A reference stack is a complete field path for a Solution: sensor or controller → edge connectivity → Autoconnecto device/gateway → telemetry keys the dashboard expects.

Solutions share one UX spine (Solution dashboard template). Reference stacks add variety without forking dashboards.

Bench test tracker (what is proven today): Validation status — EnergyFleet and ClimateFleet primary P1 paths are bench tested; Phase 1 fleets are documented and pending bench test until lab/field runs complete.

How to read the matrix

Status	Meaning
Bench tested	End-to-end on Autoconnecto with the named hardware path (see validation status).
Pending bench test	Datasheet-aligned wiring and register/key mapping documented; not yet fully exercised on our hardware.
BYO device	Publish the listed keys (any profile) — widgets work without a named SKU.

Connectivity profile IDs (P1–P6) are defined in Connectivity profiles.

Catalog matrix

Solution	Device type	Stack doc	Bench test (primary path)
EnergyFleet	energy_meter	EnergyFleet	Tested — P1 AVH-14-M1 + 4G DTU
ClimateFleet	ht_sensor	ClimateFleet	Tested — P1 XY-MD02 + 4G DTU
FuelFleet	fuel_tank	FuelFleet	Pending — P1 / P2 ultrasonic Modbus
WaterFleet	water_meter	WaterFleet	Pending — P1 / P2 EM flow + pressure
GeneratorFleet	generator	GeneratorFleet	Pending — controller Modbus
AirQualityFleet	air_quality	Air quality	Pending — P2 / P4 IAQ
ColdChainFleet	cold_chain	Cold chain	Pending — probe + door

Phase 2 (index)

Solution	Device type	Stack doc	Bench test
SmartOfficeFleet	smart_office	smart-office-fleet	Pending
SmartRetailFleet	smart_retail	smart-retail-fleet	Pending
SmartHomeFleet	smart_home	smart-home-fleet	Pending
SiteTrackingFleet	site_tracker	site-tracking-fleet	Pending
AssistedLivingFleet	assisted_living	assisted-living-fleet	Pending
WasteManagementFleet	waste_bin	waste-management-fleet	Pending
SmartIrrigationFleet	irrigation_zone	smart-irrigation-fleet	Pending

Phase 3 (index)

Solution	Device type	Stack doc	Bench test
PoolScadaFleet	pool_controller	pool-scada-fleet	Pending
OilGasDrillingFleet	drilling_rig	oil-gas-drilling-fleet	Pending
EntityManagementFleet	managed_entity	entity-management-fleet	Pending
EnergyScadaFleet	energy_scada	energy-scada-fleet	Pending

Phase 4 + Analytics (index)

Solution	Device type	Stack doc	Bench test
PumpStationFleet	pump_station	pump-station-fleet	Pending
SolarInverterFleet	solar_inverter	solar-inverter-fleet	Pending
UpsBatteryFleet	ups	ups-battery-fleet	Pending
HvacChillerFleet	chiller	hvac-chiller-fleet	Pending
ColdChainVehicleFleet	reefer_vehicle	cold-chain-vehicle-fleet	Pending
EnergyAnalytics	energy_meter	energy-analytics	Pending
FleetHealthAnalytics	ht_sensor	fleet-health-analytics	Pending
UtilizationAnalytics	generator	utilization-analytics	Pending

Phase 5 — Analytics B (index)

Solution	Device type	Stack doc	Bench test
PumpAnalytics	pump_station	pump-analytics	Pending
SolarAnalytics	solar_inverter	solar-analytics	Pending
UpsAnalytics	ups	ups-analytics	Pending
ChillerAnalytics	chiller	chiller-analytics	Pending
WaterAnalytics	water_meter	water-analytics	Pending
FuelAnalytics	fuel_tank	fuel-analytics	Pending

Phase 6 — Analytics C (index)

Solution	Device type	Stack doc	Bench test
ColdChainAnalytics	cold_chain	cold-chain-analytics	Pending
AirQualityAnalytics	air_quality	air-quality-analytics	Pending
IrrigationAnalytics	irrigation_zone	irrigation-analytics	Pending
WasteAnalytics	waste_bin	waste-analytics	Pending
AlarmNoiseOps	ht_sensor	alarm-noise-ops	Pending

Telemetry contract rule

All profiles for a Solution must publish the same key names (units documented per stack). If your hardware uses different names, map them in a rule chain or integration before the dashboard sees data.

Related

• Connectivity profiles
• Solutions roadmap
• USR-DR154 — P1 example (not the only edge option)
• ESP32 Modbus edge — P2 WiFi example