Skip to content
omnismith docs

Multi-Site Fleet Management with Home Assistant

Home Assistant is the gold standard for single-location local smart automation. However, when managing multiple properties (such as boutique hotels, short-term rentals, logistics warehouses, or server rooms), operators need centralized visibility, asset passports, and fleet-wide telemetry without compromising local offline autonomy.

Omnismith acts as the centralized Fleet Management & Data Hub for distributed Home Assistant instances.

Architecture Overview

Section titled “Architecture Overview”
 [Site A: Boutique Hotel]      [Site B: Warehouse]      [Site C: Residences]
  Local ESP32s & Sensors        Local ESP32s & Probes    Local Pumps & Sensors
            │                             │                         │
  Local Home Assistant          Local Home Assistant     Local Home Assistant
            │ (Buffered Metrics)          │ (Heartbeats)            │ (Asset State)
            └──────────────────────┬──────┴─────────────────────────┘
                                   │
                                   ▼
                       ┌───────────────────────┐
                       │ Omnismith Cloud Fleet │
                       │ • Multi-Site Passport │
                       │ • Telemetry Charts    │
                       │ • Maintenance Tickets │
                       │ • Granular Team RBAC  │
                       └───────────────────────┘
  1. Local-First Reliability: Lights, relays, climate schedules, and safety automations run locally inside Home Assistant at zero latency, completely offline.
  2. Centralized Cloud Fleet Hub: The Omnismith component buffers metric telemetry (power draw, temperature, humidity, water leak status) and streams it securely to cloud object cards.
  3. Asset Passport Meets Live Metrics: Each smart hardware record stores warranty dates, serial numbers, technician contacts, and repair history right alongside live telemetry charts.

1. Quick Start: Deploy the Blueprint

Section titled “1. Quick Start: Deploy the Blueprint”

The quickest way to configure your workspace is by deploying the Smart Facility Fleet blueprint from the Marketplace:

  1. Navigate to Marketplace → Search.
  2. Select Smart Facility Fleet and click Install Blueprint.
  3. Omnismith immediately instantiates the complete schema into your project:
    • Templates: Site / Facility, Smart Hub / Gateway, Smart Device / Node, Maintenance Ticket.
    • Attributes: Power (W), Energy (kWh), Temperature (°C), Humidity (%), RSSI (dBm), Battery (%), Hardware serials, and SLA tiers.
    • Demo Portfolio: Pre-seeded sites with 24-hour metric curves across distributed facilities.

2. Setting Up the Home Assistant Integration

Section titled “2. Setting Up the Home Assistant Integration”

Step 1: Generate an Access Token

Section titled “Step 1: Generate an Access Token”
  1. In Omnismith, open Project Settings → Access Tokens.
  2. Create a new token with write access for entities and metrics: 
    omni_live_secret_key_demo742918bc3a

Step 2: Configure Home Assistant

Section titled “Step 2: Configure Home Assistant”

In your Home Assistant instance:

  1. Open Settings → Devices & Services → Add Integration.
  2. Select Omnismith Fleet Sync.
  3. Enter your configuration:
    • API Endpoint: https://api.omnismith.io
    • API Token: omni_live_secret_key_demo742918bc3a
    • Site Name: Grand Vista Boutique Hotel
    • Flush Interval: 30 seconds (configurable from 5s to 300s)

3. How Auto-Discovery Works

Section titled “3. How Auto-Discovery Works”

You do not need to manually create entities in Omnismith for every connected sensor:

  1. Automatic Device Registration: The integration inspects Home Assistant’s device registry and automatically registers connected hardware (ESP32 controllers, Zigbee sensors, Shelly switches) into your Omnismith workspace.
  2. Standard Metric Mapping: Sensor categories (temperature, humidity, power, energy, battery) automatically map to canonical metric fields.
  3. Custom Hardware Support: If you deploy a custom ESP32 microcontroller with unique sensors, the integration dynamically synthesizes the corresponding attributes in Omnismith on the fly.

4. Telemetry Streaming API Reference

Section titled “4. Telemetry Streaming API Reference”

Behind the scenes, Home Assistant pushes batched telemetry to the Omnismith metric ingestion endpoint:

POST https://api.omnismith.io/v1/entities/01a02b42-0cd3-7100-8000-000000000021/metrics
Content-Type: application/json
Authorization: Bearer omni_live_secret_key_demo742918bc3a


{
  "metric_values": [
    { "attribute_slug": "power_consumption_w", "value": "1850.5", "updated_at": "2026-03-20T11:45:00Z" },
    { "attribute_slug": "temperature_c", "value": "21.8", "updated_at": "2026-03-20T11:45:00Z" },
    { "attribute_slug": "rssi_dbm", "value": "-58", "updated_at": "2026-03-20T11:45:00Z" }
  ]
}

5. Multi-Site Team Access & RBAC

Section titled “5. Multi-Site Team Access & RBAC”

With Omnismith’s role-based access control (RBAC):

  • Property Managers: View and manage tickets and occupancy climate presets for their assigned site only.
  • Field Technicians: Access equipment serial numbers, wiring notes, and live metric diagnostics on mobile devices.
  • Operations Executives: Monitor global portfolio health, cumulative energy consumption, and SLA compliance from a single dashboard.