Easy BACnet
  1. Home
  2. BACnet points lists
  3. Lutron
  4. myRoom BACnet Area Virtual Device (myRoom 3.3)

Hospitality lighting and HVAC control system (BACnet IP area device) · BACnet points list

Lutron myRoom BACnet Area Virtual Device (myRoom 3.3) BACnet points list

Updated 4 November 2026

Short answer

A myRoom processor speaks BACnet IP and routes to one virtual device per guestroom area. Each area device has fixed objects for light level, lighting state, scene, occupancy, power and failure counters, plus HVAC zone objects (temperature, mode, fan, setpoint, drift) and one object per lighting zone, shade group, 3-wire motor zone, temperature sensor and keypad.

This page lists 30 BACnet objects for the Lutron myRoom BACnet Area Virtual Device (myRoom 3.3) — 23 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
myRoom BACnet Area Virtual Device (myRoom 3.3)
Equipment
Hospitality lighting and HVAC control system (BACnet IP area device)
Equipment type
Other equipment
BACnet objects
30 (23 writable)
Transport
BACnet IP
Firmware
myRoom 3.3
Default device instance
Base + System + 1 (Base default 1760000)
Also known as
Lutron myRoom BACnet, myRoom guestroom BACnet, myRoom area device, 3691087, Lutron hotel guestroom control BACnet
Source document
BACnet PIC Statement for myRoom Virtual Devices Using Version 3.3 · 3691087c · rev. 2024-09-20
Download CSV 30 rows Download EDE B.I.G.-EU JSON Manufacturer PDF ↗ Compare with your scan Download Easy BACnet Mobile App Google Play

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 myRoom BACnet Area Virtual Device (myRoom 3.3)

Integration in brief

The BACnet base and system numbers are set in the myRoom configuration software; each guestroom then shows up as a virtual device behind the myRoom processor. Read occupancy (MV 8) and lighting power, command scenes (MV 4) or level (AV 2), and use the HVAC zone objects for mode, setpoint and fan. If the room's HVAC unit is on BACnet, the BMS must write temperature, operating state and fan state to the 71xx objects.

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.

ObjectNameWhyAccess
MV 4Lighting SceneScene select; 1 = Off sceneWrite
MV 7106{HVACZoneName} Operating ModeHVAC mode: 1 Off/Protect, 4 AutoWrite
MV 7108{HVACZoneName} Fan ModeFan mode: Auto, High, Medium, LowWrite
AV 2Lighting LevelArea light level command, 0-100 %Write
AV 7114{HVACZoneName} Single Setpoint CelsiusZone setpoint, °CWrite
AV 7100{HVACZoneName} Temperature CelsiusZone temperature; BMS writes it if HVAC is on BACnetWrite
MV 7107{HVACZoneName} Operating StateHVAC stage; BMS writes it if HVAC is on BACnetWrite
MV 8Occupancy State1 Unoccupied, 2 Occupied, 4 UnknownRead
AV 18Total Lighting PowerPresent lighting power, WRead
MV 7111{HVACZoneName} HVAC Fault Status2 = generic HVAC faultWrite

Enable & remote start

BACnet integration is a licensed feature set up in the myRoom configuration software; there is no BMS enable point.

Sensors & values from the BMS

When the HVAC unit is connected over BACnet rather than the thermostat's Modbus link, the zone temperature (AV 7100/7103), operating state (MV 7107) and fan state (MV 7109) must be written by the HVAC side so the thermostat can display them and energy reports work.

Network setup

Watch out for

Lutron myRoom BACnet Area Virtual Device (myRoom 3.3) 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.

30 of 30 shown
Type
AnalogBinaryMulti-state
Access
Show
Lutron myRoom BACnet Area Virtual Device (myRoom 3.3) BACnet Points List
DescriptionStates
AVmin2Lighting LevelHighest light level in the area, 0-100%Write
BV3Lighting StateOn if any light in the area is onWrite0=Off, 1=On
MVmin4Lighting SceneActive scene; 1 = Off sceneWrite1=Off scene; other states = scenes named in the myRoom project ({SceneName})
MVmin8Occupancy StateOccupancy from the room's sensorsRead1=Unoccupied, 2=Occupied, 4=Unknown
AV15Number of Lamp FailuresDigital ballasts/drivers reporting lamp failureRead
AV16Number of Devices Not RespondingProgrammed devices not respondingRead
AVmin18Total Lighting PowerPresent lighting power in the areaWRead
AV19Maximum Lighting PowerConnected lighting load of the areaWRead
AV23Number of Wireless Input Device FailuresWireless inputs not communicatingRead
AV1000{ZoneName} LevelZone light level; one object per zone, instances 1000-1099%Write
AV2000{ShadeGroupName} LevelShade group level, 100 = open; instances 2000-2999%Write
MV3000{ShadeGroupName} PresetShade group preset; instances 3000-3999Write1=Open, 2-30=user presets, 31=Closed, 32-33=not used, 34=Undefined
MV5000{3-WireMotorZoneName}3-wire motor output state; instances 5000-5099Write1=Stop, 2=Open, 3=Close
AVmin7100{HVACZoneName} Temperature CelsiusHVAC zone display temperature°CWrite
AV7103{HVACZoneName} Temperature FahrenheitHVAC zone display temperature°FWrite
MVmin7106{HVACZoneName} Operating ModeCommanded HVAC modeWrite1=Off/Protect, 4=Auto, 256=Unknown
MVmin7107{HVACZoneName} Operating StateReported HVAC stageWrite1=None, Heat Last; 2=Heat 1; 3=Heat 1+2; 4=Heat 1+2+3; 5=Heat 3; 6=None, Cool Last; 7=Cool 1; 8=Cool 1+2; 9=Off; 10=Emergency Heat; 11=Dry; 256=Unknown
MVmin7108{HVACZoneName} Fan ModeCommanded fan modeWrite1=Auto, 4=No Fan, 5=High, 6=Medium, 7=Low, 256=Unknown
MV7109{HVACZoneName} Fan StateReported fan speedWrite1=Unknown, 2=Off, 3=High/On, 4=Medium, 5=Low, 256=Unknown
MVmin7111{HVACZoneName} HVAC Fault StatusHVAC fault indicationWrite1=Unknown, 2=Generic Fault(s), 3=No Fault
AV7113{HVACZoneName} HVAC PowerCalculated HVAC zone powerWRead
AVmin7114{HVACZoneName} Single Setpoint CelsiusZone setpoint, 0-100°CWrite
AV7115{HVACZoneName} Single Setpoint FahrenheitZone setpoint, 32-212°FWrite
AV7116{HVACZoneName} Negative Drift CelsiusAllowed drift below setpoint, 0-8°CWrite
AV7117{HVACZoneName} Positive Drift CelsiusAllowed drift above setpoint, 0-8°CWrite
AV7118{HVACZoneName} Negative Drift FahrenheitAllowed drift below setpoint, 0-15°FWrite
AV7119{HVACZoneName} Positive Drift FahrenheitAllowed drift above setpoint, 0-15°FWrite
AV7300{TemperatureSensorName} Temperature CelsiusOptional FCU supply air sensor; instances 7300-7399°CWrite
AV7400{TemperatureSensorName} Temperature FahrenheitOptional FCU supply air sensor; instances 7400-7499°FWrite
BV8000{KeypadName} StateEnables or disables a keypad; instances 8000-8999Write0=Disabled, 1=Enabled
Object ID lookup: Lutron myRoom BACnet Area Virtual Device point IDs by name

Integration notes

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 myRoom BACnet Area Virtual Device (myRoom 3.3) 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 myRoom BACnet Area Virtual Device (myRoom 3.3)

How many BACnet points does the Lutron myRoom BACnet Area Virtual Device (myRoom 3.3) have?

This list has 30 BACnet objects: 19 analog values, 2 binary values, 9 multi-state values. The exact set on a given unit depends on its firmware, installed options and configuration.

Which Lutron myRoom BACnet Area Virtual Device (myRoom 3.3) BACnet points are writable?

23 of the 30 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 myRoom BACnet Area Virtual Device (myRoom 3.3) BACnet documentation?

The source is BACnet PIC Statement for myRoom Virtual Devices Using Version 3.3 (3691087c), revision 2024-09-20, published free by Lutron at https://assets.lutron.com/a/documents/3691087.pdf.

What are the minimum BACnet points to integrate the Lutron myRoom BACnet Area Virtual Device (myRoom 3.3)?

Start with MV 4 Lighting Scene (Scene select; 1 = Off scene); MV 7106 {HVACZoneName} Operating Mode (HVAC mode: 1 Off/Protect, 4 Auto); MV 7108 {HVACZoneName} Fan Mode (Fan mode: Auto, High, Medium, Low); AV 2 Lighting Level (Area light level command, 0-100 %); AV 7114 {HVACZoneName} Single Setpoint Celsius (Zone setpoint, °C); AV 7100 {HVACZoneName} Temperature Celsius (Zone temperature; BMS writes it if HVAC is on BACnet); MV 7107 {HVACZoneName} Operating State (HVAC stage; BMS writes it if HVAC is on BACnet); MV 8 Occupancy State (1 Unoccupied, 2 Occupied, 4 Unknown); AV 18 Total Lighting Power (Present lighting power, W); MV 7111 {HVACZoneName} HVAC Fault Status (2 = generic HVAC fault).

How do I enable BMS control of the Lutron myRoom BACnet Area Virtual Device (myRoom 3.3)?

BACnet integration is a licensed feature set up in the myRoom configuration software; there is no BMS enable point.

Can the BMS supply sensor values to the Lutron myRoom BACnet Area Virtual Device (myRoom 3.3)?

When the HVAC unit is connected over BACnet rather than the thermostat's Modbus link, the zone temperature (AV 7100/7103), operating state (MV 7107) and fan state (MV 7109) must be written by the HVAC side so the thermostat can display them and energy reports work.

How do I check these points on the real myRoom BACnet Area Virtual Device (myRoom 3.3)?

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

Source: BACnet PIC Statement for myRoom Virtual Devices Using Version 3.3 · 3691087c · rev. 2024-09-20. Object names, instances and units are reproduced as published; descriptions are our own.