Skip to main content

Network Thermostat Module

The Network Thermostat module on Aida Controller brings Network Thermostat (NetX) BACnet/IP thermostats into your building as first-class HVAC devices. You can discover and adopt units on the LAN, poll live space temperature and humidity, and control setpoint, system mode, and fan from Control, Device Detail, schedules, and event redirection — using the same ControlEvent path as lights and shades (thermostat:* / fan:*).

:::info Version requirement Network Thermostat requires Aida Controller 2.0 v2.12.0 or later. :::

:::note Shared BACnet scan NetX and O3 Sense both use BACnet/IP discovery. NetX is adopted as HVAC; O3 stays a sensor. Reclaiming an IP that previously hosted an O3 (or emulator) clears leftover O3 identity so the thermostat is not mis-identified. :::

Overview​

This module provides:

  • Network discovery — find NetX thermostats on the LAN from Device Discovery (or identify/adopt by IP on the module page), then assign a group
  • Live poll — space temperature, optional humidity, heat/cool setpoints, mode, fan, and equipment status
  • Thermostat control — setpoint (C/F), heat / cool / auto / off, and fan on / off / auto via ControlEvents
  • Config templates — NETWORK_THERMOSTAT defaults and software HVAC policy (mot / vac / on / off / up / down / s1–s3)
  • Schedules & redirection — thermostat and fan action types (not lighting dim)
  • Resources & zones — whole-device hvac/thermostat plus discovered humidity as hvac/sensors/humidity for optional group overrides; facility HVAC zone type for climate areas

Operator work happens on the controller UI (Modules → Network Thermostat). Discovery runs from Commissioning → Device Discovery or the module’s identify/adopt flow.

How it works​

RoleWhoNotes
NetXBACnet server on the thermostatObject map for setpoints, mode, fan, sensors
Aida moduleBACnet clientWho-Is / identify, ReadProperty poll, WriteProperty for control
BACnet/IP Server moduleSeparate northbound server for lighting clustersDo not conflate with NetX client traffic

Prerequisites​

Before enabling Network Thermostat, ensure you have:

  • Aida Controller 2.0 v2.12.0+
  • At least one NetX thermostat (for example X5 / X7 Ethernet or Wi‑Fi) on BACnet/IP on the same subnet (or reachable via your BACnet routing design)
  • Groups (and optionally facility floors / HVAC zones) so adopted devices have a place in the building model
  • Operator access to enable modules, run discovery, and manage devices

:::tip UDP 47808 Confirm nothing blocks BACnet/IP (UDP 47808) between the controller and the thermostat. NetX is IP only for this module — not BACnet Ethernet L2. :::

Setup process​

Step 1: Enable the module​

  1. Open the controller UI and go to Modules.
  2. Open Network Thermostat.
  3. Toggle the module Enabled.

When the module is off, NetX poll and write workers stop. Existing state remains visible but goes stale until you turn it back on.

Step 2: Prepare the thermostat​

  1. Power the NetX and confirm it is on the building IP network.
  2. Confirm BACnet/IP is enabled on the device (vendor setup / BACnet tools as needed).
  3. Note the IP address if you plan to identify or adopt manually.

Step 3: Discover and adopt​

  1. Go to Commissioning → Device Discovery, or use identify/adopt on Modules → Network Thermostat.
  2. Run a BACnet scan (or enter a known address for identify).
  3. Review candidates tagged as Network Thermostat / NetX. O3 and other BACnet equipment are not auto-adopted into this module.
  4. Adopt each thermostat: clear name, optional serial / instance, and assign a group.

Step 4: Apply a configuration template (optional)​

  1. Under Commissioning → Configuration, create or edit a NETWORK_THERMOSTAT template.
  2. Set defaults.unit (C or F), default HVAC mode, fan, and setpoints.
  3. On the Policy tab, map mot / vac / on / off / up / down / s1–s3 rows to thermostat actions as needed.
  4. Assign the template to the device or its group and apply.

Software HVAC policy runs through the same ControlGateway path as Control Events (not a separate vendor fork).

Step 5: Verify​

  1. Open the device’s Detail page — confirm space temperature, setpoint, mode, fan, and humidity (when the thermostat reports it).
  2. Use the Thermostat widget to change setpoint or mode; confirm the device follows after the write.
  3. On Control, select the HVAC group — you should see the thermostat widget (not standard lighting events).
  4. Open Resources on the device to see hvac/thermostat and, when discovered, humidity for optional group assignment.
  5. Optionally create a facility zone with type HVAC and link climate devices for monitors / energy indoor temperature.

Using the module day to day​

Device Detail​

AreaWhat you see / do
StateSpace temp, setpoint, mode, fan, decoded equipment (idle / heating / cooling / fan / off), humidity when capable
ControlThermostat widget — level (C/F), mode, fan via /control/events
ResourcesThermostat resource; humidity peripheral when present
ConfigApplied template parameters and match status

Control, schedules, and redirection​

SurfaceBehavior
Operations → ControlThermostat section for HVAC targets; Policy Events when a template is applied
SchedulesThermostat setpoint, mode, fan, and composite thermostat actions
Event redirectionSame HVAC action types as schedule targets

Do not use lighting dim / light:level for thermostats.

Monitoring and troubleshooting​

Common issues​

Scan finds nothing

  • Confirm the Network Thermostat module is Enabled.
  • Confirm the unit is on BACnet/IP and reachable on UDP 47808.
  • Confirm the controller and thermostat are on the same subnet (or that BBMD / foreign-device settings match your design).

Adopted but values stay blank

  • Wait one poll interval, then use the module’s force read / poll if available.
  • Confirm the BACnet object map matches the thermostat model (X5 / X7 family).

Setpoint write does not stick

  • Confirm mode is not off if your site expects active heat/cool tracking.
  • Confirm the device accepts WriteProperty for the mapped setpoint objects.
  • Refresh Device Detail — presentation uses stored setpoint, not space temperature as a substitute.

Humidity missing

  • Not all NetX units expose humidity. When present, a successful poll discovers SENSOR_HUMIDITY and lists it under Resources.

Confused with O3 on the same IP

  • NetX reclaim clears stale O3 markers. Prefer adopting NetX after the previous device is gone; do not run an O3 emulator and a NetX emulator on the same address during lab tests.

Module disabled

  • Expected: NetX poll/write stops; ControlEvents for NetX capability are filtered or no-op. Re-enable under Modules → Network Thermostat.