Skip to main content

O3 Sense Module

The O3 Sense module on Aida Controller brings Delta O3 Sense / O3 Sensor Hub ceiling multisensors into your building: temperature, humidity, light level, sound, occupancy, and people count. Readings appear on the module dashboard, on each device’s detail page, and on facility floor plans — and they can feed Aida’s northbound BACnet points for the BMS.

:::info Version requirement O3 Sense requires Aida Controller 2.0 v0.80.0 or later. Update the host controller (appliance install / self-update) to 0.80.0+ before enabling the module — that release also adds the host privileges needed for optional BACnet Ethernet discovery. :::

:::note Not ozone O3 here means the Delta O3 Sense product family. It is an occupancy and environment sensor — not an ozone-gas detector. :::

Overview​

This module provides:

  • Network discovery — find O3 sensors on the LAN (BACnet/IP or BACnet Ethernet) from Device Discovery, then adopt them into a cluster
  • Live dashboard — site-wide averages for temperature, humidity, lux, sound, occupancy, and people count
  • History chart — recent trends; click a device in the list to focus the chart on that sensor
  • Per-device management — add by IP, edit, remove, poll now, and control the sensor light ring
  • MQTT fallback — support sensors still commissioned the Controller 1.0 way (per-device MQTT), with an option to re-commission to BACnet/IP
  • Building surfaces — same live values on device detail and facility floors; occupancy / lux / temperature / sound can roll into Aida cluster BACnet aggregates when that server is enabled

Operator work happens on the controller UI (Modules → O3 Sense). Discovery runs from Commissioning → Device Discovery.

How it works​

ConnectionBest forWhat you do
BACnet/IP (recommended)Most sites; sensors that can talk over the IP networkEnable BACnet/IP on the sensor, then scan on Device Discovery
BACnet EthernetFactory-default sensors that still speak MAC-level BACnet on the same switch/LAN segmentScan with BACnet Ethernet (O3) on Device Discovery (same L2 as the controller)
MQTTOlder Controller 1.0 installs, or sensors already set up with MQTTAdd the device by IP and MQTT credentials, or import from a 1.0-style list

Once adopted, the controller polls BACnet sensors on a short interval (typically about every 15–30 seconds). MQTT sensors push updates when they publish. Either way, the latest values show up in the same places in the UI.

Prerequisites​

Before enabling O3 Sense, ensure you have:

  • Aida Controller 2.0 v0.80.0+, with the host controller updated to 0.80.0+ (appliance self-update or reinstall)
  • At least one Delta O3 Sense / Sensor Hub on the same network path you plan to use (IP subnet and/or same Ethernet segment)
  • Clusters (and optionally facility floors/zones) so adopted sensors have a place in the building model
  • Operator access to enable modules, run discovery, and manage devices

:::tip Factory-default sensors Many O3 units ship speaking BACnet Ethernet, not BACnet/IP. For IP discovery, switch the sensor to BACnet/IP with the Delta O3 Setup app (Bluetooth) or vendor tools (for example NP6 / enteliWEB). If you cannot change that yet, use BACnet Ethernet discovery on the same LAN segment instead. :::

Setup process​

Step 1: Enable the module​

  1. Open the controller UI and go to Modules.
  2. Open O3 Sense.
  3. Toggle the module Enabled.

When the module is off, discovery and polling stop. Existing readings remain visible but go stale until you turn it back on.

Step 2: Prepare the sensor (BACnet/IP path)​

  1. Power the O3 and confirm it is on the building network.
  2. If you want BACnet/IP discovery:
    • Open the O3 Setup mobile app (or vendor BACnet tools).
    • Enable BACnet/IP on the device.
  3. Note the sensor’s IP address if you plan to add it manually.

Step 3: Discover and adopt​

  1. Go to Commissioning → Device Discovery (linked from the O3 Sense page).
  2. Select BACnet/IP (O3) and/or BACnet Ethernet (O3), then start a scan.
  3. Review candidates. Only O3-class sensors are offered for this module — other BACnet equipment is ignored.
  4. Adopt each sensor: give it a clear name and assign a cluster.

:::note Where discovery lives There is no separate Scan tab on the O3 Sense module page. Use Device Discovery so all protocol scans stay in one place. :::

Step 4: Or add a device manually​

On Modules → O3 Sense → Devices:

  1. Add a device with name, IP address, and transport (BACnet/IP or MQTT).
  2. For MQTT, enter the broker username and password used on the sensor (often the defaults from your site’s commissioning notes).
  3. Assign a cluster and save.

Use manual add when discovery cannot see the unit (different subnet without BBMD, MQTT-only install, or known IP).

Step 5: Verify readings​

  1. Open Modules → O3 Sense → Dashboard.
  2. Confirm metric cards show temperature, humidity, lux, sound, occupancy, and people count (values appear after the first successful poll or MQTT message).
  3. Click Poll now if you just adopted a BACnet sensor and want an immediate refresh.
  4. Open Devices and confirm each row shows a recent update time and the correct connection type (BACnet/IP, BACnet Ethernet, or MQTT).
  5. Open a device’s detail page and a facility floor plan — the same environment and occupancy values should appear there.

Using the module day to day​

Dashboard​

ControlWhat it does
Metric cardsSite averages across adopted O3 devices (or the filtered device — see below)
History chartRecent trend for the selected metric
Device listClick a device to filter the chart to that sensor; use Show all to return to the site average
Poll nowTrigger an immediate BACnet read for adopted IP/Ethernet devices

Devices​

ActionWhen to use
AddKnown IP; MQTT-only; discovery not available
Edit / removeRename, change cluster, or retire a sensor
Light ringSet the sensor’s RGB indicator (BACnet or MQTT, depending on how the device is connected)
Re-commission to BACnet/IPMigrate an MQTT device after you have enabled BACnet/IP on the hardware

Where else readings appear​

PlaceWhat you see
Device detailTemperature, humidity, lux, sound, occupancy, people count, and connection type
Facility floorsLive labels on O3 pins (for example humidity and people count)
Aida BACnet/IP Server (if enabled)Occupancy, lux, temperature, and sound can contribute to cluster-level BMS points — humidity and people count stay in the Aida UI until dedicated BMS objects are added

MQTT and upgrading from Controller 1.0​

Controller 1.0 commissioned O3 sensors with MQTT only (no network discovery). On Controller 2.0 you can:

  1. Keep MQTT: add or import devices with IP and credentials; the module subscribes and updates live state.
  2. Move to BACnet/IP when ready: enable BACnet/IP on the sensor, then use Re-commission to BACnet/IP on the device row (or discover and adopt fresh).

Prefer BACnet/IP for new sites — discovery and polling are simpler to operate than per-device MQTT brokers.

Monitoring and troubleshooting​

Common issues​

Scan finds nothing (BACnet/IP)

  • Confirm the O3 module is Enabled.
  • Confirm the sensor is on BACnet/IP, not only BACnet Ethernet.
  • Confirm the controller and sensor are on the same subnet (or that BBMD / foreign-device settings match your network design).
  • Confirm nothing else is blocking UDP 47808 between them.

Scan finds nothing (BACnet Ethernet)

  • Sensor and controller must be on the same Layer‑2 segment (Ethernet does not route across IP routers).
  • Your appliance/deployment must allow raw Ethernet capture for this path (site installers typically enable this when Ethernet discovery is required).

Device adopted but values stay blank

  • Wait one poll interval, then click Poll now.
  • Check the Devices tab for errors or a stale “last updated” time.
  • For MQTT: confirm IP, port 1883, username/password, and that the sensor is publishing.

Dashboard averages look wrong

  • Click Show all on the chart if you previously filtered to one device.
  • Remove or fix offline devices so they do not pull the average down after timeouts.

Light ring does not change

  • Confirm the module is enabled and the device row shows the expected connection type.
  • For BACnet, the sensor must accept writes for the light-ring controls; for MQTT, the sensor must accept command topics.

Module disabled

  • Expected: polling and MQTT clients stop; APIs that change O3 config are blocked. Turn the module back on under Modules → O3 Sense.