Integrating Digi XBee Sensors with Schneider MPM via Zigbee PRO

Overview

Integrating Digi XBee wireless sensors with a Schneider Electric Multi-Purpose Manager (MPM) requires the XBee radio to be on the same Zigbee stack profile as the coordinator. The most common deployment failure is leaving the LTH (Light–Temperature–Humidity) sensor on the legacy Zigbee 2007 stack while the MPM runs Zigbee PRO—these profiles are not interoperable, so the sensor appears to join the PAN, fails association authentication, and silently drops off the network within 60–120 seconds.

This procedure forces both the MPM-attached XBee and the LTH sensor onto Zigbee PRO using a coordinator XBee in API mode, then registers the device with EcoStruxure Building Operation through a Zigbee Device Import File. The same workflow applies to other Schneider wireless coordinators such as the MPM-UN, MPM-VA, and the Wiser for KNX bridge when paired with a Digi XBee gateway.

Prerequisites

• Digi XBee ZB (S2C) or XBee ZB Pro module running firmware 2x6x, 2x7x, or 3x0x (XBee 802.15.4 firmware does not support the ZS parameter).
• XBee USB adapter or serial breakout board (Digi XBIB-U-DEV, SparkFun XBee Explorer USB, or compatible).
• Digi XCTU version 6.5.0 or newer for AT console access and firmware management.
• Schneider Electric MPM-UN or MPM-VA running EcoStruxure Building Operation 3.2 or newer with the Wireless Devices option licensed.
• Zigbee Device Import File (.zip container) matching the LTH sensor part number, downloaded from the Schneider BMS Applications portal.
• For data-center deployments: a Device Definition File authored per the Schneider AN_DDF_EN third-party DCIM integration guide.
• Stable 2.4 GHz RF environment—survey channel utilization with XCTU's Range Test before locking the channel.

Zigbee Stack Profile Selection (ZS Parameter)

The ZS (Zigbee Stack Profile) parameter selects which IEEE 802.15.4 mesh profile the XBee joins. The values supported on current Digi firmware are:

Coordinator Configuration

The Schneider MPM acts as the Zigbee trust center and PAN coordinator. The XBee attached to the MPM's USB/serial port (or the on-board radio of newer MPM-VA variants) must be configured as a coordinator before commissioning. Apply the following AT commands in XCTU's console or via the API frame equivalent:

ATRE              ; restore defaults
ATCE 1            ; Coordinator Enable = 1 (Coordinator)
ATZS 1            ; Zigbee Stack Profile = Zigbee PRO
ATID 0x1A2B      ; PAN ID = 0x1A2B (any 0x0000-0x3FFF; 0xFFFF = random)
ATCH 0x15         ; Channel 21 (0x0B-0x1A maps to channels 11-26; 0x00 = scan)
ATAP 1            ; API mode 1 (non-escaped); use AP 2 if the host may see 0x7E bytes
ATAO 1            ; API Options: indicate ZB reception with 0x91 frame
ATBD 3            ; Interface Data Rate 9600 bps if MPM serial port is fixed 9600
ATWR              ; write to non-volatile memory
ATFR              ; software reset, join occurs on reboot

After reset, verify with ATAI (Association Indication). A successful coordinator reports 0x00 (successful join—coordinator started). Common non-zero values include:

API Mode Setup for Reprovisioning the LTH Sensor

The LTH sensor ships in transparent AT mode (AP=0) with Zigbee 2007 stack profile. To force a stack-profile change without losing the sensor's calibration data, attach the sensor to a second XBee on a Windows or Linux host running XCTU and run:

+++                ; enter command mode (guard time 1 s)
ATRE              ; restore defaults
ATZS 1            ; switch to Zigbee PRO
ATAP 2            ; API mode 2 (escaped) so the sensor can be re-issued API frames
ATID 0x1A2B      ; match coordinator PAN ID
ATCH 0x15         ; match coordinator channel
ATJV 0            ; join attempts disable (we'll force via API)
ATJN 1            ; join notification enabled
ATD0 2            ; DIO0 = AD0 (light) for LTH variant
ATD1 2            ; DIO1 = AD1 (temperature)
ATD2 2            ; DIO2 = AD2 (humidity)
ATIR 0x1388       ; sample rate = 5000 ms (5 s)
ATWR
ATCN              ; exit command mode

Power-cycle the sensor. It will perform an active scan on channel 0x15 and send an Association Request. The coordinator MPM logs the new short address (16-bit, e.g. 0x7A12) in the EcoStruxure Workstation event stream.

Channel and PAN ID Planning

Wi-Fi coexistence is the dominant cause of dropped XBee links in commercial buildings. Apply the following planning rules before locking CH:

1. Run XCTU Range Test for 10 minutes on each candidate channel and plot the RSSI histogram.
2. Re-run at the same hours the sensor will report peak data (HVAC load shift, occupancy peaks).
3. Avoid channels within ±5 of the strongest Wi-Fi channel. Wi-Fi ch 1 = 2412 MHz → avoid Zigbee ch 11–14; Wi-Fi ch 6 = 2437 MHz → avoid Zigbee ch 17–19; Wi-Fi ch 11 = 2462 MHz → avoid Zigbee ch 22–24.
4. Set CH to the cleanest non-overlapping channel—commonly ch 15, 20, or 25 in office deployments.
5. Lock the PAN ID (ID) to a non-default value (e.g. 0x1A2B) to prevent joining a neighbouring building's PAN during commissioning.

EcoStruxure Building Operation Integration via Zigbee Device Import File

Once the sensor has joined and the MPM coordinator logs a ZB Device Join event, the third-party device must be registered so EcoStruxure Workstation can map Zigbee cluster attributes to BMS points. Schneider supplies this mapping as a Zigbee Device Import File (ZD) on the BMS Applications portal.

Import procedure:

1. Download the .zip ZD package that matches the sensor PN and firmware major version (e.g. XBee-LTH-v3.0.zd).
2. Open EcoStruxure Building Operation Workstation → System → Device Import.
3. Click Import, select the .zip, and confirm the SHA-256 checksum matches the value published on the BMS portal.
4. Assign the imported device template to the MPM's wireless port; Workstation will display the discovered XBee 64-bit extended address (e.g. 0013A200.4175B7C2) in the discovery tree.
5. Drag the device onto the floor plan; the LTH temperature, humidity, and illuminance points become available under the Analog Inputs folder with engineering units pre-scaled (°C, %RH, lux).

If the BMS Applications portal does not list a ZD for the exact sensor firmware, build a custom ZD using the Device Definition Editor. Each Zigbee cluster attribute must be mapped to an ECO point, and the polling interval should match ATIR (default 5 s).

DCIM Monitoring Integration

For data-center deployments where LTH readings must be exported to StruxureWare Data Center Expert or EcoStruxure IT Advisor, follow the third-party device policy described in the AN_DDF_EN application note:

1. Author a Device Definition File (DDF) that declares the XBee device as an SNMP-proxy target.
2. Configure the MPM's northbound interface to forward LTH points as BACnet/IP objects or Modbus TCP registers (default mapping: AV0 = temperature, AV1 = humidity, AV2 = illuminance).
3. Submit the DDF and a sample MIB extension to Schneider for certification before production rollout—uncertified DDFs are accepted by IT Advisor but flagged as unverified.

Verification Procedure

End-to-end verification confirms the sensor is on the correct stack profile, joined the right PAN, and that EcoStruxure is polling live values:

1. Coordinator XBee: ATAI must read 0x00; ATOP (Operating PAN ID) must match ATID.
2. Sensor XBee: ATAI must read 0x00; ATMY (16-bit short address) must be non-zero; ATZS must read 1.
3. EcoStruxure Workstation: open the device's Analog Inputs folder and confirm the three values update within two polling cycles.
4. Force a value change (cup-warm the LTH sensor) and verify the temperature point rises by ≥ 0.5 °C within 30 s.
5. Power-cycle the sensor and confirm it rejoins the same PAN (ATOP) within 30 s—failure to rejoin indicates JV1 is not set.

Troubleshooting Matrix

Field-Proven Caveats

• XBee ZB modules with firmware older than 2x6x do not expose ZS in the parameter list; flash to a current firmware image first.
• The MPM serial port defaults to 9600 8N1. If you set BD=7 (115200) without matching the MPM port configuration, the coordinator XBee will be invisible to EcoStruxure even though ATAI reads 0x00.
• Enabling AO=1 (Zigbee Receive API indicator) on the coordinator makes troubleshooting far easier—each sensor transmission prints a 0x91 frame on the serial console.
• When migrating a deployed LTH sensor from ZS=0 to ZS=1, plan a 5-minute outage. The radio performs a full rejoin and the MPM logs a Device Removed → Device Added pair that may trigger spurious alarms if not suppressed.
• For multi-floor deployments, give each floor a distinct PAN ID (ID) and channel (CH) pair to limit broadcast storm radius.

FAQ