Easy BACnet- Home
- BACnet points lists
- Lutron
- Quantum BACnet Subsystem Device (Quantum 3.1)
Lighting control system (BACnet IP subsystem device) · BACnet points list
Lutron Quantum BACnet Subsystem Device (Quantum 3.1) BACnet points list
Updated 4 November 2026
Each Quantum subsystem is a physical BACnet IP device that routes to the area virtual devices (listed separately). The subsystem device holds the subsystem-wide objects: master load shed, master Hyperion shade control, the roof-mount cloudy-day sensor, and one set of objects per timeclock, timeclock event and state variable.
This page lists 9 BACnet objects for the Lutron Quantum BACnet Subsystem Device (Quantum 3.1) — 9 of them writable — with each object’s type, instance number, name, engineering units and access. It is re-typed from Lutron’s own free documentation, linked below.
- Manufacturer
- Lutron
- Model
- Quantum BACnet Subsystem Device (Quantum 3.1)
- Equipment
- Lighting control system (BACnet IP subsystem device)
- Equipment type
- Other equipment
- BACnet objects
- 9 (9 writable)
- Transport
- BACnet IP
- Firmware
- Quantum 3.1 (BACnet integration software 2.0)
- Default device instance
- Base + System + 1 (Base default 1760000)
- Also known as
- Lutron Quantum subsystem BACnet, Quantum main device BACnet, Quantum timeclock BACnet, 369997, Quantum BACnet integration subsystem
Reference only, provided as-is: verify against Lutron’s current documentation and the live device before use. Not official Lutron information. Terms of use.
BMS integration notes: Lutron Quantum BACnet Subsystem Device (Quantum 3.1)
Use the subsystem device for building-wide actions: master load shed (BV 2), Hyperion shade control (BV 3) and timeclock enable/disable (MV 2000 range). Area lighting itself is read and commanded on the area virtual devices.
Minimum points to map
The short list most integrators start with — enough to run the unit from a BMS. Map more as the job needs.
| Object | Name | Why | Access |
|---|---|---|---|
| BV 2 | Master Loadshed Enabled | Turns load shedding on for the subsystem | Write |
| MV 2000 | {TimeclockName} Enable Command | Enable or disable a timeclock schedule | Write |
| BV 3 | Master Hyperion Enabled | Turns automatic sun-tracking shades on/off | Write |
| BV 4 | Roof-Mount Cloudy Day Sensor: Subsystem Status | Cloudy-day input: 0 Dark, 1 Sunny | Write |
Enable & remote start
BACnet IP is built into the Quantum processor as a licensed software option; device IDs come from the Base and System numbers set in the Quantum configuration software. No separate BMS enable point exists.
Sensors & values from the BMS
A BMS sensor can stand in for the roof-mounted cloudy-day sensor by writing BV 4 (Dark overrides Hyperion shades to open).
Network setup
- BACnet IP; the subsystem device is the router for its area virtual devices.
- Device ID = Base + System + 1; Base default 1760000, System 0-127, set in the Quantum software.
Watch out for
- Writing 1 (Disable Permanently) to a timeclock enable command stops that timeclock until it is enabled again.
- Enable With Catch Up replays missed events from up to the last seven days.
- Load shed only dims areas that have load shed allowed on their area device.
Lutron Quantum BACnet Subsystem Device (Quantum 3.1) BACnet objects
Type: AI, AO, AV, BI, BO, BV, MI/MO/MV (multi-state) · Access: Read read-only, Write writable, Command writable with a priority array.
| Description | States | |||||
|---|---|---|---|---|---|---|
| BVmin | 2 | Master Loadshed Enabled | Load shed for all areas in the subsystem | Write | 0=Disabled, 1=Enabled | |
| BVmin | 3 | Master Hyperion Enabled | Sun-tracking shade control for the subsystem | Write | 0=Disabled, 1=Enabled | |
| BVmin | 4 | Roof-Mount Cloudy Day Sensor: Subsystem Status | Cloudy-day override for Hyperion shades | Write | 0=Dark, 1=Sunny | |
| BV | 1000 | {TimeclockName} Enabled | Enable/disable a timeclock; instances 1000-1999 | Write | 0=Disabled, 1=Enabled | |
| MVmin | 2000 | {TimeclockName} Enable Command | Timeclock enable command; instances 2000-2999 | Write | 1=Disable Permanently, 2=Disable Until End of Day Without Catch Up, 3=Disable Until End of Day With Catch Up, 4=Enable Without Catch Up, 5=Enable With Catch Up, 6=Enable and Run Previous Event Only | |
| MV | 4000 | {VariableName} Current Variable State | State variable value; instances 4000-4999 | Write | 1..n = {StateName} set in the Quantum software | |
| BV | 5000 | {Timeclock Name} / {Timeclock Event} Enabled | Enable/disable a timeclock event; instances 5000-5999 | Write | 0=Disabled, 1=Enabled | |
| AV | 6000 | {Timeclock Name} / {Timeclock Event} Hour | Event hour, 0-23; instances 6000-6999 | h | Write | |
| AV | 7000 | {Timeclock Name} / {Timeclock Event} Minute | Event minute, 0-59; instances 7000-7999 | min | Write |
No points match these filters.
Object ID lookup: Lutron Quantum BACnet Subsystem Device point IDs by name
BV2Master Loadshed EnabledBV3Master Hyperion EnabledBV4Roof-Mount Cloudy Day Sensor: Subsystem StatusBV1000{TimeclockName} EnabledMV2000{TimeclockName} Enable CommandMV4000{VariableName} Current Variable StateBV5000{Timeclock Name} / {Timeclock Event} EnabledAV6000{Timeclock Name} / {Timeclock Event} HourAV7000{Timeclock Name} / {Timeclock Event} Minute
Integration notes
- Area-level objects (light level, scenes, occupancy, power) are on the area virtual devices; see the Quantum BACnet Area Virtual Device list.
- Only the first instance of each range is listed: timeclock enabled 1000-1999, timeclock enable command 2000-2999, state variables 4000-4999, timeclock event enabled 5000-5999, event hour 6000-6999, event minute 7000-7999.
- Timeclock objects in 1000-1999 and 2000-2999 pair by offset; event enabled, hour and minute pair by the last three digits.
- A timeclock appears on every subsystem device; write the same instance on each subsystem to change it everywhere.
- Source: Lutron PIC statement 369997a (05.24.16).
Check it against the live device. A points list tells you what the controller can expose; the unit in front of you may differ by firmware or installed options. This list is provided as-is for reference only and may contain mistakes — confirming it before you write, map or commission anything is up to you (terms). Easy BACnet scans a network for BACnet IP devices from an Android phone, reads every object on the Quantum BACnet Subsystem Device (Quantum 3.1) and exports what it actually has to Excel — free. New to BACnet? Start with what a BACnet points list is and what the object types mean.
Questions about the Lutron Quantum BACnet Subsystem Device (Quantum 3.1)
How many BACnet points does the Lutron Quantum BACnet Subsystem Device (Quantum 3.1) have?
This list has 9 BACnet objects: 2 analog values, 5 binary values, 2 multi-state values. The exact set on a given unit depends on its firmware, installed options and configuration.
Which Lutron Quantum BACnet Subsystem Device (Quantum 3.1) BACnet points are writable?
9 of the 9 objects accept a write. Points marked Command have a priority array: a write holds until it is released, so release it back to automatic when you are done.
Where is the official Lutron Quantum BACnet Subsystem Device (Quantum 3.1) BACnet documentation?
The source is BACnet PIC Statement for Quantum Subsystem Physical Devices using Quantum Version 3.1 (369997a), revision 2016-05-24, published free by Lutron at https://assets.lutron.com/a/documents/369997.pdf.
What are the minimum BACnet points to integrate the Lutron Quantum BACnet Subsystem Device (Quantum 3.1)?
Start with BV 2 Master Loadshed Enabled (Turns load shedding on for the subsystem); MV 2000 {TimeclockName} Enable Command (Enable or disable a timeclock schedule); BV 3 Master Hyperion Enabled (Turns automatic sun-tracking shades on/off); BV 4 Roof-Mount Cloudy Day Sensor: Subsystem Status (Cloudy-day input: 0 Dark, 1 Sunny).
How do I enable BMS control of the Lutron Quantum BACnet Subsystem Device (Quantum 3.1)?
BACnet IP is built into the Quantum processor as a licensed software option; device IDs come from the Base and System numbers set in the Quantum configuration software. No separate BMS enable point exists.
Can the BMS supply sensor values to the Lutron Quantum BACnet Subsystem Device (Quantum 3.1)?
A BMS sensor can stand in for the roof-mounted cloudy-day sensor by writing BV 4 (Dark overrides Hyperion shades to open).
How do I check these points on the real Quantum BACnet Subsystem Device (Quantum 3.1)?
Scan the network with a BACnet IP browser such as Easy BACnet, open the device and compare its object list with this table. Anything missing is usually an option that isn't installed or a point that is disabled in the controller's configuration.
More Lutron BACnet points lists
- Hospitality lighting and HVAC control system (BACnet IP area device)
Lutron myRoom BACnet Area Virtual Device (myRoom 3.3)
Lutron myRoom hospitality guestroom control systems (software 3.3) with BACnet integration; each guestroom area is its own virtual BACnet device.
Also known as: Lutron myRoom BACnet, myRoom guestroom BACnet, myRoom area device, 3691087, Lutron hotel guestroom control BACnet - Hospitality lighting and HVAC control system (BACnet IP)
Lutron myRoom XC BACnet (system and area devices)
Lutron myRoom XC hospitality guestroom systems with BACnet integration (Lutron Designer projects); one system device plus one virtual device per area.
Also known as: Lutron myRoom XC BACnet, myRoom XC processor, 3691271, Lutron Palladiom thermostat BACnet, Lutron guestroom BACnet XC - Lighting control system (BACnet IP area device)
Lutron Quantum BACnet Area Virtual Device
Lutron Quantum lighting control systems with the BACnet license; each programmed area appears as its own virtual BACnet device.
Also known as: Lutron Quantum BACnet, Quantum area device, Quantum BACnet integration, QSW-BAC-PP-A, 369696, Lutron lighting BACnet points, Quantum Lighting Hub BACnet - Lighting control system (BACnet IP)
Lutron Vive BACnet (hub and area devices)
Lutron Vive wireless lighting control systems with BACnet IP on the Vive hub (Vive 1.07); one hub device plus one virtual device per area.
Also known as: Lutron Vive, Vive hub, Vive BACnet Integration, 369996, Vive 1.07
Source: BACnet PIC Statement for Quantum Subsystem Physical Devices using Quantum Version 3.1 · 369997a · rev. 2016-05-24. Object names, instances and units are reproduced as published; descriptions are our own.