Device Identification

Last modified by Alexander Mott on 2026/11/18 00:12

All controlled hardware (ZUMNET/ZUMLINK devices, Cresnet devices, Touchpanels, DIN-CENCN-2, etc.) must be addressed according to the configuration in order for the ShowRunnerCLC™ program to control them as expected. Chief Integrations will provide an "SRTakeoff" Excel file indicating how devices are expected to be addressed as well as providing a means for the technician to record serial numbers, track online/configured status, and note any issues with device installation or functionality. This takeoff will be accurate to the initially provided configuration, but if things change during commissioning then it will not be accurate unless it is updated by the technician. Zūm autodiscovery jobs are shipped with a blank takeoff, as it is impossible to know how devices will be addressed until after they are pulled into ShowRunnerCLC™

In order to determine how a device should be addressed, you must identify which serial number is associated with that device and then set the device's CID or RFID according to the takeoff. In an ideal world, serial numbers and MAC addresses are recorded by the EC during hardware installation and provided prior to a technician's arrival on-site, allowing the technician to fill out the takeoff and get right to addressing and testing devices when they arrive on-site. In reality, this rarely happens and it is necessary to identify devices after they are installed.

The most surefire way to identify a device is by physically going to the device and recording its MAC address or serial number:

  • All Ethernet devices will give their Serial Number in the Device Summary generated from the Device Discovery tool in Toolbox
  • All Ethernet devices will give their MAC address with the ipconfig command in Text Console
  • All ZUMLINK/Cresnet devices will give their TSID from the ppndiscover command in Text Console
  • Some ZUMLINK/Cresnet devices will give their serial number in ppndiscover, and those that do not are able to be converted using the SN/TSID conversion tool in Toolbox under the "Utility" menu
  • All ZUMLINK/Cresnet devices will give both their TSID and serial number in Network Device Tree View if it is configured correctly
    The below table covers the location of the MAC address and serial number stickers for most devices as well as whether or not the serial number is displayed in Device Discovery Tool and/or PPN Discover:

MAC Address / Serial Number Label Location Table

The below table provides information about where on a device the MAC address and serial number are located, and whether or not the MAC address or serial number will appear for the device in Device Discovery or when running the ppndiscover command

DeviceMAC Address LocationMAC in Device Discovery?Serial Number LocationSN in ppndiscover?Notes
C2N-CBD Keypads--Front of keypadNo 
C2N-IO--Top side of deviceNo 
CAEN/CLX Module--Right side of module, center rearNo 
CAEN-BLOCK-CENCN-2-POEFront of device, leftNoFront of device, lower right- 
CEN-GW1Rear of deviceYesRear of device-Label is obscured by DIN rail bracket
CLW Keypads--Front of keypadNo 
CM2 Keypads--Front and rear of keypadNo 
CP3N / CP4NRear of deviceYesRear of device, right-"MAC" is for LAN, "MAC1" is for Control Subnet
DIN-AP3Right side of deviceYesTop side of device, right- 
DIN-AP4Right side of deviceYesLeft side of device- 
DIN-CENCN-2(-POE)Left side of deviceNoTop side of device, right- 
DIN-DALI-2Right side of deviceNoTop side of device, right- 
DIN-DLILeft side of moduleYesRight side of moduleYes 
GLPACs / GL-IPACsFront of moduleNoFront of module, lower rightNo 
GLS-ODT-C-CN--On front of device, underneath twist-off coverNo 
GLS-PART--Rear of deviceNo 
GLS-SIM--Top side of deviceNo 
GLXP/GLXX-CTRL Module--Left side of module, No 
HZ2-KPCN / EX Keypads--Front and rear of keypadNo 
HZ-KPCN / EX Keypads--Front and rear of keypadNo 
RMC3 / RMC4Rear of deviceYesRear of deviceYesLabel is obscured by DIN rail bracket
TSW-XXX TouchpanelsRear of deviceYesRear of device- 
ZUM-HUB4Rear of deviceYesRear of device, right-"MAC" is for LAN, "MAC1" is for control subnet
ZUMLINK Occupancy Sensors--On sensor base, underneath sensor headYes 
ZUMLINK-DIN-*--Left side of moduleYes 
ZUMLINK-JBOX-*--Underside of fold-out coverYes 
ZUMLINK-JBOX-IO--Bottom side of deviceYes 
ZUMLINK-KP--Right side of keypadYes 
ZUMNET-DIN-*Right side of moduleYesLeft side of moduleYes 
ZUMNET-GATEWAY / CEN-GWEXER / CEN-RFGW-EXRear of deviceNoRear of device-Label is obscured by DIN rail bracket
ZUMNET-JBOX-*Underside of fold-out coverYesUnderside of fold-out coverYes 

Identifying Ethernet Devices

Ethernet devices must be online with a compatible network configuration (either DHCP or static) before they can be identified and configured over the network

Ethernet devices typically require physical access to the device in order to determine their MAC address and serial number, with two exceptions:

  • ZUMNET, GLPAC, and GL-IPAC devices are also load controllers, and can be identified by flashing their loads or putting their load controller into identification mode as described in the next section
  • The identity of CENCN-2, ZUMNET, gateways, or any other Ethernet device hosting ZUMLINK/Cresnet/wireless devices can be inferred if the serial number of a hosted device is known: if that serial number or the associated TSID appears when you run ppndiscover / reportnetdev command, then you will be able to know what device you are connected to

All Ethernet devices will have serial number and MAC address labels somewhere on the device. Record the serial number and  the MAC address and use them to identify the device in a Device Summary report generated from the Device Discovery tool in Toolbox. Once identified, set the IP-ID and then record or set the IP address and hostname of the device so that it can be easily identified in the future. See our network setup pages for device-specific configuration instructions

Not all devices show their MAC address in a Device Summary report, so if you are trying to identify one of these devices but all you have is the MAC address, then you will need to connect to it and run the ipconfig command to see the MAC address.

Identifying ZUMLINK / Cresnet / RF Devices

ZUMLINK / Cresnet / RF devices must be online and connected/acquired to their host with a unique CID / RFID before they can be identified and configured

Hosted ZUMLINK, Cresnet, and wireless devices are able to be put into an "identify" mode,  where the device itself will make a visible indication that it is in identify mode. ZUMNET load controllers and GLPACs can also be put into identify mode, since the load controller component is treated like a built-in ZUMLINK/Cresnet device.

Most devices will blink an LED in a steady pattern, with load controllers additionally flashing their connected loads and (for some models) producing a beeping or alarm noise. 

Network Device Tree View

Using Network Device Tree View to identify devices connected to a processor will cause the program to stop and restart each time a device is put into / taken out of identify mode. It is recommended to run the Text Console command stopprog -p:01 before identifying devices directly from a processor to temporarily stop the ShowRunnerCLC™. Once identification is complete, run progreset or reboot the processor to start up ShowRunnerCLC™ again.

Network Device Tree View is the easiest way to put a device into identification mode for most people, though it can sometimes be slow.

To identify devices through Network Device Tree View:

  • Connect to the device hosting the devices you want to identify (e.g. the processor, ZUMNET-JBOX, CEN-GW1, etc.) in Network Device Tree View
    • It is a good idea to configure Network Device Tree View to show the ID, serial number, and TSID of devices at the top level
    • For DIN-CENCN-2, you should also enable "Show by Device Connection" so that you know which branch a device is connected to
  • Right click a device in the tree and click "Identify this Device"
    • Note: only top level devices can be identified; ZUMMESH devices connected to a ZUM-NETBRIDGE cannot be identified, only the ZUM-NETBRIDGE itself can be identified
  • Look for the device or the flashing loads in the field and note the location
  • Return to your computer and record the TSID / serial number associated with that device and set the CID/RFID according to the ShowRunnerCLC™ configuration
  • Once the device is identified, take it out of identification by clicking the "Cancel" button
    • Most keypads can be taken out of identify mode by pressing any button
  • Repeat until all devices are identified and configured

Text Console

The necessary commands differ between wired hosts (DIN-CENCN-2, ZUMNET, processors, etc.) and wireless gateways (ZUMNET-GATEWAY, CEN-GWEXER, etc.). Commands are provided in the form [wired command] / [wireless command].
Variable parameters for each command are shown in [square brackets]: replace these with the necessary values, and do not include the square brackets themselves.

Network Device Tree View can be slow sometimes, so it is often quicker (especially if only identifying a handful of devices) to use Text Console instead.

To put a device into identification mode through Text Console, use the lightbyppn / lightbytsid command:

  • Connect to the device hosting the devices you want to identify (e.g. the processor, ZUMNET-JBOX, CEN-GW1, etc.) in Text Console
  • Run the ppndiscover / reportnetdev command to get the 8-digit TSID for each hosted device
  • Run the lightbyppn [branch] [8-digit TSID] / lightbytsid [8-digit TSID] command to put a single device into identification mode
    • Running the command with no parameters or with a TSID of all will put all devices on that branch or on that device into identification mode
    • Zūm Wired devices always have a branch of 1, while processors should leave out the branch entirely
    • Run the command multiple times with different TSID to identify multiple devices at once
  • Look for the device or the flashing loads in the field and note the location
  • Return to your computer and record the TSID / serial number associated with that device and set the CID/RFID according to the ShowRunnerCLC™ configuration
  • Once the device is identified, take it out of identification with the stoplightbyppn [branch] [8-digit TSID] / stoplightbytsid [8-digit TSID] command
    • Running the command with no parameters or with a TSID of all will put take all devices on that branch or on that device out of identification mode
    • Most keypads can be taken out of identify mode by pressing any button
  • Repeat until all devices are identified and configured

Tips, Tricks, and Device-Specific Methods

Here are some additional tips and device-specific identification methods that may prove useful in certain situations:

  • If you have only two unidentified devices of any given model connected to a host, you only really need to identify one of them 
    • E.g., in a ZUMNET room with one keypad, one ZUMLINK-JBOX, and two occupancy sensors, you only need to identify one sensor: the second sensor can be identified by process of elimination while all other devices are the only device of their model on the ZUMNET
  • You can identify multiple keypads by identifying all of them simultaneously and then pressing them in a known order
    • In Network Device Tree View, this is done by right clicking the window and selecting "Show by Category", right clicking the Keypads section, and then clicking "Identify all keypads"
      • When pressed, a keypad's status goes from "active" to "pressed"
    • In text console, either identify specific TSIDs or simply identify all devices and then press the keypads in a known order
      • When a keypad is pressed, it will print a message to the console even if it does not take itself out of identify mode
  • For ZUMLINK / Cresnet devices, it is often useful to identify devices one cable at a time by unplugging all but one cable
    • This reduces the area you have to search for devices in identify mode once you know what general area that cable goes to
    • This also helps narrow down where a potential wiring issue may be, since a wiring issue anywhere on the ZUMLINK / Cresnet bus will affect all devices on that bus
  • Any load controller can be identified by manually toggling the loads, either through the buttons on the front of the device or by temporarily setting it to an ID in the ShowRunnerCLC™ configuration and using the ShowRunnerCLC™ UI
    • If you are temporarily setting the controller to an ID in the ShowRunnerCLC™ configuration, you can also use the "Identify" function from the load control setup menu in ShowRunnerCLC™ to silently flash the load without the beeping sound that comes with identification through console commands or Network Device Tree View
  • GLS-ODT-C-CN sensors and GLPP controllers can be directly addressed using their corresponding remotes, allowing you to set their correct ID right away and then recording their serial numbers once all devices have been addressed
  • GLXP and GLXX controllers can be directly addressed using buttons on the front of the module
  • TSW touchpanels can be configured and their MAC addresses viewed directly from the setup menu on the panel by pressing five fingers to the screen for approximately 10 seconds and inputting the credentials when prompted
  • If the lights on a 0-10V ZUMNET controller are on, the controller can be identified by rebooting them, as the reboot process will cause them to briefly flash their lights off. This is useful if you already need to reboot the controller for some other reason (e.g. to change primary/secondary or Zum/CNET mode)