Easy BACnet- Home
- BACnet points lists
- Lutron
- Quantum BACnet Area Virtual Device
Lighting control system (BACnet IP area device) · BACnet points list
Lutron Quantum BACnet Area Virtual Device BACnet points list
Updated 29 October 2026
Quantum processors (Quantum Lighting Hubs) speak BACnet IP natively once a BACnet license is enabled. Each subsystem is a main BACnet device that routes to one virtual device per area (room). Every area device carries the same fixed objects for light level, scene, occupancy, daylighting, load shedding, Hyperion shades, power and device failures, plus one object per lighting zone, shade group, 3-wire motor zone and light sensor in that area.
This page lists 29 BACnet objects for the Lutron Quantum BACnet Area Virtual Device — 19 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 Area Virtual Device
- Equipment
- Lighting control system (BACnet IP area device)
- Equipment type
- Other equipment
- BACnet objects
- 29 (19 writable)
- Transport
- BACnet IP
- Firmware
- Quantum 2.6 (BACnet integration software 2.0)
- 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
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 Area Virtual Device
A Lutron service engineer enables the BACnet license and sets device IDs and network numbers. Each area then shows up as a virtual device behind the processor. Command the area light level (AV 2) or scene (MV 4), read occupancy (MV 8) and power (AV 18), and watch the failure counters.
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 |
|---|---|---|---|
| AV 2 | Lighting Level | Area light level command, 0-100 % | Write |
| MV 4 | Lighting Scene | Scene select; 1 = Off scene | Write |
| BV 3 | Lighting State | On if any light in the area is on | Write |
| MV 8 | Occupancy State | 1 Unocc, 2 Occ, 3 Inactive, 4 Unknown | Read |
| AV 18 | Total Power | Present lighting power, W | Read |
| AV 15 | Number of Lamp Failures | Count of failed lamps | Read |
| AV 16 | Number of Devices Not Responding | Count of offline lighting devices | Read |
Enable & remote start
BACnet is native to the Quantum processor but needs a BACnet software license per processor (QSW-BAC-PP-A covers 50 areas); a Lutron service representative enables it and sets the device IDs and network numbers. No separate BMS enable point exists.
Network setup
- BACnet IP (Annex J). The processor is a BACnet router: area virtual devices sit on a virtual network behind the subsystem device.
- Device ID = Base + System + 1; Base default 1760000, System 0-127. Agree device IDs and network numbers with the integrator first.
- Lutron advises at most 50 areas per subsystem; more areas means slower BACnet responses.
- The processor can register as a foreign device; give the BBMD address to the Lutron engineer if the BMS is on another subnet.
- Enable COV on the Lutron side before the BMS discovers the system.
Watch out for
- Lighting Level reports the brightest fixture in the area when fixtures differ.
- Lutron application notes say Schedule and Trend Log objects are not supported; trend and schedule from the BMS or the Quantum timeclock.
- Zone and shade object instances are assigned per area; read the object list of each area device.
Lutron Quantum BACnet Area Virtual Device 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 | |||||
|---|---|---|---|---|---|---|
| AVmin | 2 | Lighting Level | Highest light level in the area, 0-100 | % | Write | |
| BVmin | 3 | Lighting State | On if any light in the area is on | Write | 0=Off, 1=On | |
| MVmin | 4 | Lighting Scene | Active lighting scene; 1 = Off scene | Write | 1=Off scene; 2..n = scenes named in the Quantum project ({SceneName}) | |
| BV | 5 | Daylighting Enabled | Lets daylight sensors limit the area's light level | Write | 0=Disabled, 1=Enabled | |
| AV | 6 | Daylighting Level | Daylight target cap, 0-100 | % | Write | |
| BV | 7 | Disable Occupancy | True stops occupancy sensors affecting the lights | Write | 0=False, 1=True | |
| MVmin | 8 | Occupancy State | Occupancy of the whole area | Read | 1=Unoccupied, 2=Occupied, 3=Inactive, 4=Unknown | |
| AV | 9 | Unoccupied Level | Light level/scene used when the area goes unoccupied (0-216) | Write | 0=Off, 1-100=level %, 101=Unaffected, 102=Daylighting, 200=Off scene, 201-216=Scene 1-16 | |
| AV | 10 | Occupied Level | Light level/scene used when the area goes occupied (0-216) | Write | 0=Off, 1-100=level %, 101=Unaffected, 102=Daylighting, 200=Off scene, 201-216=Scene 1-16 | |
| AV | 11 | Additional Occupied Timeout | Extra wait after sensors go unoccupied, 0-300 | min | Write | |
| BV | 12 | Loadshed Allowed | Area takes part in load shedding | Write | 0=No, 1=Yes | |
| AV | 13 | Loadshed Goal | Light reduction when loadshed is on, 0-90 % | Write | ||
| MV | 14 | Occupancy Mode | How occupancy sensors control the lights | Write | 1=Inactive, 2=Automatic ON and Automatic OFF, 3=Manual ON and Automatic OFF, 4=Not Applicable | |
| AVmin | 15 | Number of Lamp Failures | Digital ballasts/drivers reporting lamp failure | Read | ||
| AVmin | 16 | Number of Devices Not Responding | Programmed devices not responding | Read | ||
| BV | 17 | Hyperion Enabled | Sun-tracking shade control for the area | Write | 0=Disabled, 1=Enabled | |
| AVmin | 18 | Total Power | Present lighting power in the area | watts | Read | |
| AV | 19 | Maximum Power | Connected lighting load of the area | watts | Read | |
| BV | 20 | Roof-Mount Cloudy Day Sensor: Area Status | Cloudy-day override for Hyperion shades | Write | 0=Dark, 1=Sunny | |
| BV | 21 | Radio Window Sensor State | Radio window sensor override of Hyperion | Write | 0=Disabled, 1=Enabled | |
| BV | 22 | Light Level Discrepancy | Photo sensor reading disagrees with timeclock state | Read | 0=False, 1=True | |
| AV | 23 | Number of Wireless Input Device Failures | Wireless keypads/sensors not communicating | Read | ||
| AV | 25 | Number of Loads with Lamps Nearing End of Life | Loads past their programmed lamp-hours | Read | ||
| AV | 1000 | {ZoneName} Level | Zone light level; one object per zone, instances 1000-1999 | % | Write | |
| AV | 2000 | {ShadeGroupName} Level | Shade group level, 100 = open; instances 2000-2999 | % | Write | |
| MV | 3000 | {ShadeGroupName} Preset | Shade group preset; instances 3000-3999 | Write | 1=Open, 2-30=user presets, 31=Closed, 32-33=not used, 34=Undefined | |
| MV | 4000 | {ShadeGroupName} Radio Window Sensor Shade Group Status | Window sensor state per shade group; instances 4000-4999 | Read | 1=Unknown, 2=Sunny, 3=Dark | |
| MV | 5000 | {3-Wire Motor Zone Name} | 3-wire motor output state; instances 5000-5999 | Write | 1=Stop, 2=Open, 3=Close | |
| AV | 6000 | Light Sensor Value | Light sensor reading per sensor; instances 6000-6999 | fc | Read |
No points match these filters.
Object ID lookup: Lutron Quantum BACnet Area Virtual Device point IDs by name
AV2Lighting LevelBV3Lighting StateMV4Lighting SceneBV5Daylighting EnabledAV6Daylighting LevelBV7Disable OccupancyMV8Occupancy StateAV9Unoccupied LevelAV10Occupied LevelAV11Additional Occupied TimeoutBV12Loadshed AllowedAV13Loadshed GoalMV14Occupancy ModeAV15Number of Lamp FailuresAV16Number of Devices Not RespondingBV17Hyperion EnabledAV18Total PowerAV19Maximum PowerBV20Roof-Mount Cloudy Day Sensor: Area StatusBV21Radio Window Sensor StateBV22Light Level DiscrepancyAV23Number of Wireless Input Device FailuresAV25Number of Loads with Lamps Nearing End of LifeAV1000{ZoneName} LevelAV2000{ShadeGroupName} LevelMV3000{ShadeGroupName} PresetMV4000{ShadeGroupName} Radio Window Sensor Shade Group StatusMV5000{3-Wire Motor Zone Name}AV6000Light Sensor Value
Integration notes
- Object names in braces ({ZoneName}, {ShadeGroupName}, {3-Wire Motor Zone Name}) take the names set in the Quantum project.
- Only the first instance of each repeating range is listed. The document gives each zone level object a unique instance from 1000 to 1999 and each shade group level a unique instance from 2000 to 2999; shade group presets use 3000-3999, shade group window sensor status 4000-4999, 3-wire motor zones 5000-5999 and light sensors 6000-6999.
- Instance 24 is not used in the document.
- Area device IDs are Base + System + 1, with Base set in the Quantum software (default 1760000) and System 0-127.
- Unoccupied Level and Occupied Level are numeric codes: 0 off, 1-100 percent, 101 unaffected, 102 daylighting, 200 off scene, 201-216 scenes 1-16.
- The document is Lutron 369696a (PIC statement for Quantum area virtual devices, Quantum 2.6).
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 Area Virtual Device 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 Area Virtual Device
How many BACnet points does the Lutron Quantum BACnet Area Virtual Device have?
This list has 29 BACnet objects: 15 analog values, 8 binary values, 6 multi-state values. The exact set on a given unit depends on its firmware, installed options and configuration.
Which Lutron Quantum BACnet Area Virtual Device BACnet points are writable?
19 of the 29 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 Area Virtual Device BACnet documentation?
The source is BACnet PIC Statement for Quantum Area Virtual Devices using Quantum Version 2.6 (369696a), revision 2013-08-12, published free by Lutron at https://assets.lutron.com/a/documents/369696.pdf.
What are the minimum BACnet points to integrate the Lutron Quantum BACnet Area Virtual Device?
Start with AV 2 Lighting Level (Area light level command, 0-100 %); MV 4 Lighting Scene (Scene select; 1 = Off scene); BV 3 Lighting State (On if any light in the area is on); MV 8 Occupancy State (1 Unocc, 2 Occ, 3 Inactive, 4 Unknown); AV 18 Total Power (Present lighting power, W); AV 15 Number of Lamp Failures (Count of failed lamps); AV 16 Number of Devices Not Responding (Count of offline lighting devices).
How do I enable BMS control of the Lutron Quantum BACnet Area Virtual Device?
BACnet is native to the Quantum processor but needs a BACnet software license per processor (QSW-BAC-PP-A covers 50 areas); a Lutron service representative enables it and sets the device IDs and network numbers. No separate BMS enable point exists.
How do I check these points on the real Quantum BACnet Area Virtual Device?
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 subsystem device)
Lutron Quantum BACnet Subsystem Device (Quantum 3.1)
Lutron Quantum lighting control systems (Quantum 3.1) with BACnet; one physical subsystem device per subsystem, typically one per floor.
Also known as: Lutron Quantum subsystem BACnet, Quantum main device BACnet, Quantum timeclock BACnet, 369997, Quantum BACnet integration subsystem - 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 Area Virtual Devices using Quantum Version 2.6 · 369696a · rev. 2013-08-12. Object names, instances and units are reproduced as published; descriptions are our own.