Connecting building sensors and IoT devices

Property Operations includes a vendor-neutral IoT primitive that lets you ingest sensor and device events from any building system into a unified Devices view at /property?tab=operations.

What's supported out of the box:
• **Mock devices** — for demo / dev / training; lets you add a fake fire panel, door system, leak sensor, or temperature sensor that emits realistic events on a schedule
• **BACnet adapter** — pulls from BACnet/IP building-automation networks (HVAC, fire panels, access control, lighting, energy meters)
• **Generic webhook ingestion** — any vendor that can POST JSON can call /api/property/iot/ingest with their event schema; we accept and normalize it

How to add a device:

1. Go to /property?tab=operations → click + Add Device.
2. Pick the vendor (Mock, BACnet, or Webhook).
3. For BACnet: paste the IP address of your building controller. For Webhook: copy the per-org ingestion URL and paste it into your vendor's webhook settings.
4. Devices report status, heartbeat, and events (alarm, fault, offline). Events route to:
• The Property Operations dashboard (live tiles)
• The /property/wall full-bleed mode for facilities-team monitoring
• Wally Insights when patterns emerge ("Boiler #3 has cycled 12 times in 4 hours — investigate")

Life-safety automation:
• Any "alarm" event from a device tagged as life-safety (fire, gas, intrusion) auto-creates a Field Service work order routed to your on-call rotation
• A hash-chained audit log records every event for after-action review and compliance audits

What this replaces:
Most building-automation vendors have proprietary apps that don't talk to each other. Centralizing on the Devices primitive lets you correlate (e.g., HVAC fault → temperature sensor reading → fire panel pre-alarm) in one timeline.