O3 Edge BACnet Application Guide - Delta Controls Support

O3 EdgeBACnet Application GuideEdition 2.5

© 2022 Delta Controls. All rights reserved.

No part of this document may be reproduced, transmitted, transcribed, stored in a retrievalsystem, or translated into any language (natural or computer), in any form or by any means,without the prior written permission of Delta Controls.

Limited permission is granted to reproduce documents released in Adobe® Portable DocumentFormat (PDF) electronic format in paper format. Documents released in PDF electronic formatmay be printed by end-users for their own use using a printer such as an inkjet or laser device.Authorized distributors of Delta Controls products (Delta Partners) may print PDF documentsfor their own internal use or for use by their customers. Authorized Delta Partners may engagea printing or copying company to produce copies of released PDF documents with the priorwritten permission of Delta Controls.

Information in this document is subject to change without notice and does not represent acommitment to past versions of this document on the part of Delta Controls. Delta Controls maymake improvements and/or changes to this document at any time.

Document edition: 2.5

ContentsIntroduction 1

About the O3 Edge 1

BACnet Objects in the O3 2

Sensor Objects 2

Device Objects 5

How Occupancy Works 8

Light Ring Patterns 9

Default Sounds 10

Setting Up the O3 11

Security Settings 11

Changing the BLE PIN 11

Disabling Bluetooth 12

Enabling the Internal MQTT Broker 12

Changing the Internal MQTT Broker Password 12

Configuration Settings 12

Upgrading the Firmware 12

Calibrating the Occupant Temperature 13

Changing Network Settings 14

Disabling NTP 15

Enabling a Startup Sound 16

Custom Settings 17

Creating a Custom Light Ring Color 17

Loading Custom Sounds 18

Controlling Colors and Sounds Remotely 18

GCL+ Programming 19

Configuring the IR Blaster 19

Working with Metrics 21

Viewing Metrics 22

Forcing Updates 23

Deleting Metrics 23

Revision History 24

IntroductionThis guide describes the BACnet objects associated with O3 Edge series edge controllers. Theseobjects are used to represent sensor and device properties and can be accessed and configuredby BACnet front-end software.

The information in this guide applies to the following models:l O3-EDGE-02l O3-EDGE-O2-E8l O3-EDGE-O2-E9

About the O3 EdgeThe O3 Edge ("O3") is a ceiling-mounted multisensor device that integrates temperature,humidity, motion, sound, and light sensing. Using sensor fusion technology and machinelearning algorithms, the O3 delivers fast, accurate feedback on the monitored space.

The O3 supports BACnet, MQTT, EnOcean, and Bluetooth® Low Energy (BLE) protocols,allowing it to integrate with almost any system. It also comes with two universal I/O points forcontrolling or accepting inputs from nearby devices.

For more information about EnOcean, go to support.deltacontrols.com/Products/O3Edge

Other features of the O3 include:l dual Ethernet ports for daisy-chaining over large areasl pass-through communication during power lossl a full-color customizable LED light ringl user feedback via speakerl supports up to 32 EnOcean wireless devicesl an IR blaster for remote control of audio-visual equipmentl supports up to 32 EnOcean wireless devices

For more information about the O3, go to support.o3hub.com.

© 2022 Delta Controls Inc. 1

http://support.deltacontrols.com/Products/O3Edge

http://support.o3hub.com/

BACnet Objects in the O3BACnet objects are used to represent the O3's sensor and device properties. The objects can begrouped as follows.

Sensor Device

l Temperaturel Humidityl Occupancyl Environmentall I/O

l Light Ringl Soundsl Bluetoothl Firmwarel Otherl IR Blaster

The following tables list the default BACnet objects for the O3.

Sensor Objects

Name Instance Description

Occupant Temperature AI3 Temperature at 1 m (3 ft) above the floor. Thisis a composite value derived from the O3'sinternal temperature sensors and the IRtemperature sensor. Range: 0°C to 59°C (32°F to 138°F).

IR Temperature AI4 Average temperature of surfaces in the O3'sfield of view. Range: 0°C to 59°C(32°F to 138°F).

Internal Temperature AI5 Temperature at ceiling height.Range: 0°C to 59°C (32°F to 138°F).

Temperature Setpoint AV33 User-entered temperature from mobile app.Measured by user at occupant height.

Celsius AIC1 Temperature unit of measurement.

Fahrenheit AIC2 Temperature unit of measurement.

TABLE 1: TEMPERATURE OBJECTS

2 O3 Edge BACnet Application GuideEdition 2.5

BACnet Objects in the O3


Occupant Humidity AI6 Humidity at 1 m (3 ft) above floor. This iscalculated from the occupant temperature andinternal humidity using psychrometrics.Range: 0% to 100%.

Internal Humidity AI7 Humidity at ceiling height. Range: 0% to 100%.

TABLE 2: HUMIDITY OBJECTS


Occupancy BI8 Combined (motion + sound) occupancy signal.Active state when motion and sound isdetected. See How Occupancy Works for moredetails.

Motion Sensor BI9 Motion occupancy signal. Active state whenmotion is detected.

Acoustic Activity Level AI10 Audio level after certain frequencies arefiltered out.

Acoustic Occupancy BI11 Acoustic occupancy signal. Active state whenacoustic activity level is above the internalacoustic occupancy threshold.

Motion Sensitivity AV23 Controls the sensitivity of the PIR sensor tochanges in movement levels within thedetection area. 100% = maximum sensitivity.

Occupancy AudioSensitivity

AV24 Controls the sensitivity of the acousticoccupancy sensor to changes in audio levelswithin the detection area. 100% = maximumsensitivity.

Occupancy Audio RetriggerPeriod

AV25 The amount of time (in seconds) that activitysounds can cause the O3 to remain in theoccupied state after motion is detected.Default value is 1200 seconds (20 minutes).Measured from most recent motion detectionevent.

Occupancy RemainingLatch Time

AV39 The amount of time (in seconds) remainingbefore the combined occupancy signal (BI8)deactivates. Read-only.

TABLE 3: OCCUPANCY OBJECTS





Light Level AI12 Brightness of ambient light (lx or ft-candle).

Color Temperature AI13 Color temperature of ambient light (K).

Light Sensor RedComponent

AI14 Red component of ambient light.Range: 0 to 65535.

Light Sensor GreenComponent

AI15 Green component of ambient light.Range: 0 to 65535.

Light Sensor BlueComponent

AI16 Blue component of ambient light.Range: 0 to 65535.

Sound Level AI17 Level of ambient noise (dB SPL). Unfilteredaudio level across the entire spectrum.

Light Level Setpoint AV34 (Optional) User-entered light level frommobile app. Records the light level read by theO3 (AI12) when the lighting in the space is setto the desired brightness. This setpoint can beretrieved later by the control system to set thefeedback loop, etc.

Lux AIC3 Light level unit of measurement.

Footcandles AIC4 Light level unit of measurement.

16bit Scale AIC5 Analog-to-digital unit of measurement.

Decibel AIC6 Sound level unit of measurement.

Kelvin AIC7 Color temperature unit of measurement.

TABLE 4: ENVIRONMENTAL OBJECTS


Universal IO Channel 1 AI AI1 Displays analog input value on I/O point xP1.

Universal IO Channel 1 BI BI1 Displays binary input value on I/O point xP1.

Universal IO Channel 1 AO AO1 Displays analog output value on I/O point xP1.

Universal IO Channel 1 BO BO1 Displays binary output value on I/O point xP1.

Universal IO Channel 2 AI AI2 Displays analog input value on I/O point xP2.

Universal IO Channel 2 BI BI2 Displays binary input value on I/O point xP2.

Universal IO Channel 2 AO AO2 Displays analog output value on I/O point xP2.

Universal IO Channel 2 BO BO2 Displays binary output value on I/O point xP2.

TABLE 5: I/O OBJECTS


Device Objects


Play Light Ring Pattern MV1 Plays light ring pattern (1-13). Default value is1 (Off). See Light Ring Patterns for moredetails.

Light Ring Pattern Repeats AV2 Sets number of times light ring patternrepeats.

Light Ring Custom ColorRed

AV3 Sets red component of light ring RGB value.Range: 0% to 100%. Only valid if BV7 is On.

Light Ring Custom ColorGreen

AV4 Sets green component of light ring RGB value.Range: 0% to 100%. Only valid if BV7 is On.

Light Ring Custom ColorBlue

AV5 Sets blue component of light ring RGB value.Range: 0% to 100%. Only valid if BV7 is On.

Light Ring Brightness AV6 Sets overall brightness of light ring.Range: 0% to 100%. Default value is 50%.

Light Ring Activate CustomColors

BV7 Activates custom light ring color defined byLight Ring Custom Color Red (AV3), Light RingCustom Color Green (AV4), and Light RingCustom Color Blue (AV5). When set to On, itoverrides Play Light Ring Pattern (MV1).

Power On Self Test Enable BV8 Activates power-on self-test (POST), whichtests sensor, Bluetooth, and Ethernetfunctionality. POST status is indicated by thefollowing colors: green = OK, red = sensorproblem, blue = Bluetooth problem, andyellow = Ethernet problem.

Light Ring Patterns MIC1 Contains 12 light ring patterns. See Light RingPatterns for more details.

TABLE 6: LIGHT RING OBJECTS





Play Sound MV28 Plays a sound. There are 25 default sounds,contained in MIC2. You can also create up to25 custom sounds. See Loading CustomSounds for more details.

Sound Repeats AV29 Sets the number of times a sound is played.

Sound Volume AV30 Sets the speaker volume in the range 0% to100%. Default value is 75%.

Startup Sound Enable BV44 Enables "Power On" sound to play when theO3 restarts. Default value is Off.

Default Sounds MIC2 Contains 25 default sounds (FIL101 to FIL125).These sounds cannot be overwritten.

TABLE 7: SOUND OBJECTS


Enable BLE BV31 Enables Bluetooth LE communication.

Bluetooth Beacon MACAddress

CSV32 Displays MAC address of Bluetooth LE beacon.

BLE PIN CSV45 Sets the 6-digit authentication code forread/write access via Bluetooth. Default valueis 000000.

TABLE 8: BLUETOOTH OBJECTS


Firmware Upgrade CSV43 Initiates a firmware upgrade. See Upgradingthe Firmware for more details.

TABLE 9: FIRMWARE OBJECT



NTP Enable BV42 Sets time to Coordinated Universal Time(UTC) when connected to the internet. SeeDisabling NTP for more details.

MQTT Password CSV46 Sets the internal MQTT broker password. SeeChanging the MQTT Broker Password formore details.

Internal MQTT BrokerEnable

BV48 Enables external access to the O3's internalMQTT broker. See Enabling the InternalMQTT Broker for more details.

TABLE 10: OTHER DEVICE OBJECTS


Send IR Code MV9 Sends IR code (1-12). Default value is 1. SeeConfiguring the IR Blaster for more details.

IR Code Repeats AV10 Sets number of times IR code is sent pertransmission. By default, code is sent once pertransmission.

IR Code 1 CSV11 Sets IR code. Must be in Pronto hex format.












IR Codes MIC3 Contains 12 IR codes (CSV11 to CSV22).

TABLE 11: IR BLASTER OBJECTS




How Occupancy WorksA state change from unoccupied to occupied is triggered when a combination of motion andsound is detected in the room. Sound by itself does not trigger a state change.

The occupied state is extended when additional motion or sound is detected in the room. Theambient sound level must be above the baseline audio level that the O3 has previouslyestablished. Activity sounds detected after the Occupancy Audio Retrigger Period (AV25) do notextend the occupied state. This reduces artificial extension of the occupied state by backgroundnoise.


Light Ring PatternsThe following light ring patterns are defined by the MIC1 (Light Ring Patterns) object. The statesare supplied to the MV1 (Play Light Ring Pattern) object.

State Name Description Color

1 Idle (Off) No pattern is displayed. None

2 Blue Swirl Light circles ring once, followed by two shortflashes, followed by long flash.

Blue

3 Fast BlueSwirl

Same as above but faster. Blue

4 Power On Light circles ring three times. Green

5 OccupancyActive

Light circles ring three times. White

6 Got Request Three short flashes. Green

7 Heating Active Light ring fades in and out. Red

8 Cooling Active Light ring fades in and out. Blue

9 Don'tUnderstand

Four short flashes, followed by long flash. Yellow

10 Error Eight short flashes. Red

11 Alarm Sixteen short flashes on alternating sides of ring. Red

12 Christmas Sixteen short flashes in alternating colors. Red andgreen

13 Awake andWaiting

Light circles ring once, followed by long flash. Blue




Default SoundsThe following default sounds are defined by the MIC2 (Default Sounds) object. The states aresupplied to the MV28 (Play Sounds) object. States 2 to 26 correspond to FIL101 to FIL125.

1. Idle (Off)2. Power On3. Acknowledge4. Chime Confirm5. Ding6. Reminder7. Occupancy 018. Occupancy 029. Cooling10. Heating11. Alarm12. Critical Alarm13. Error

14. Alert15. Security Alarm16. Notification17. Prompt18. Question19. Done20. Short Cancel21. Short Confirm Yes22. Short Off23. Short On24. TNG Door25. Scanning26. Ambient Alert

Setting Up the O3This section is divided into three parts:

l Security Settings contains instructions for enabling the internal MQTT broker, changing theinternal MQTT broker password, changing the BLE PIN, and disabling Bluetooth to protectthe O3 against unauthorized writes.

l Configuration Settings contains instructions for upgrading firmware, calibrating theoccupant temperature, changing the network settings, disabling NTP time syncs, andenabling a startup sound.

l Custom Settings contains instructions for creating custom light ring colors and loadingcustom sounds. It also describes GCL+ programs that you can use with the O3.

Security Settings

Changing the BLE PINThe BLE PIN is a 6-digit code used to authenticate Bluetooth-enabled mobile devices. To securewrites to the O3 via Bluetooth, you must change the BLE PIN after the initial configuration withthe O3 Setup app is complete.

The BLE PIN must consist of digits between 0 and 9 and must be exactly 6 digits in length. Thenew PIN cannot be 000000.

To change the PIN:

1. Create object CSV45 with the name "BLE PIN."2. Command the object to manual mode and enter the new PIN as the object value.3. Restart the O3. If you're using enteliWEB, on the object list page, click Device Actions >

Reset.

The CSV45 object value should clear after the new PIN is entered. If it doesn't clear,the PIN was not accepted. Check the PIN length and try again.


Setting Up the O3


Disabling BluetoothAnother way to secure writes to the O3 via Bluetooth is to disable Bluetooth LE communication.

To disable Bluetooth:

1. Command object BV31 (Enable BLE) to manual mode and set the object value to Off.2. Restart the O3. If you're using enteliWEB, on the object list page, click Device Actions >

Reset.

Enabling the Internal MQTT BrokerThe O3 has an internal MQTT broker that allows you to write directly to the device'sconfiguration file. The broker is disabled by default.

To enable the internal MQTT broker:l Command object BV48 (Internal MQTT Broker Enable) to manual mode and set the object

value to On, then click Save.

Changing the Internal MQTT Broker PasswordThe default username/password to access the internal MQTT broker is user/admin. To securewrites to the broker, you must change this password.

The MQTT broker password is case-sensitive and must be 5 to 31 characters in length. Specialcharacters are allowed.

To change the password:

1. Create object CSV46 with the name "MQTT Password".2. Command the object to manual mode and enter the new password as the object value.3. Restart the O3. If you're using enteliWEB, on the object list page, click Device Actions >

Reset.

The CSV46 object value should clear after the new password is entered. If it doesn'tclear, the password was not accepted. Check the password length and try again.

Configuration Settings

Upgrading the FirmwareIf the O3 has an active internet connection, you can get firmware updates from the default URL.

Setting Up the O3

The O3 must have the correct time for the firmware upgrade to work. Beforecontinuing, make sure object BV42 (NTP Enable) is set to On.

To upgrade a single O3:

1. Create object CSV43 with the name "Firmware Upgrade."2. Command the object to manual mode and enter the firmware version as the object value.

Use the following JSON format: {"version": "FIRMWARE_VERSION"}

To batch upgrade multiple O3s using enteliWEB:

1. Create object CSV43 with the name "Firmware Upgrade."2. In the left pane, hold down the Shift key and select up to 8 O3s that you want to update.3. Filter on CSV43.4. Select the checkbox at the top left to select all the objects.5. Click Command > Manual Value, then enter the firmware version as the object value. Use

the following JSON format: {"version": "FIRMWARE_VERSION"}

6. Click Save.

When the O3 receives the upgrade command, it validates the server URL and firmware buildbefore proceeding. If the validation check fails, the light ring flashes red 8 times. If thevalidation check is successful, the light ring turns orange to indicate that the upgrade is inprogress. The upgrade may take several minutes. If the firmware upgrade fails for any reason,the light ring flashes red 8 times.

If the upgrade command is sent simultaneously to multiple O3s in a daisy chain, somedownstream devices may fail to upgrade if there are interruptions in the network. Open theDEV object, and check that the Application Version shows the correct firmware version.

Once the upgrade process is complete, verify that CSV43 has cleared its value.

Calibrating the Occupant TemperatureThe O3 models the room temperature at occupant height using its internal temperature sensorsand IR temperature sensor. Because each room is different (due to air flow, heating sources,height of the ceiling, etc.), the O3's initial prediction is likely to be slightly off. This differencecan be calibrated out by measuring the current room temperature and sending that value to theO3. The offset is calculated automatically.

For best results, observe the following guidelines:l Try to get the room temperature as close to your setpoint as reasonably possible. The

calibration should hold within ± 5°C, but the closer you are to the control point the better itwill be.


Setting Up the O3


l Make sure the temperature in the space has been reasonably stable for at least 15minutes. That is, don’t go from 10°C to 20°C and then calibrate the reading as soon as youreach 20°C. Hold at approximately 20°C for 15 minutes and then calibrate.

l Try to calibrate within the O3’s IR envelope, but also make sure it isn’t directly next to aheating or cooling source.

l Calibrate at approximately 1 m (3 ft) off the floor.

Normally, the occupant temperature is calibrated using the O3 Setup mobile app. However, youcan also update the calibration value over BACnet.

To update the calibration value:

1. Open object AI3 (Occupant Temperature).2. Set the object to manual mode.3. Enter the new calibration value in the Calibration field and save your changes.

If AI3 is not set to manual mode, the entered value will be discarded and the previouscalibration value will be shown after a refresh.

Changing Network SettingsThe O3 supports both BACnet over Ethernet (BACnet/Ethernet) and BACnet over UDP/IP (BACnet/IP). By default, the BACnet protocol type is set to BACnet/Ethernet. To change theprotocol type, connect to the device over BACnet/Ethernet and configure the BACnet/IP settings.

To configure BACnet/IP settings in enteliWEB:

1. Open object NP6 (Ethernet1 - IP1).2. Clear the Out Of Service checkbox.3. Leave the UDP Port number as the default value (47808) unless you want to create

independent groups of BACnet devices on the same IP subnet.4. Set IP Mode to Foreign if you want the O3 to join a BACnet/IP network with a different IP

subnet address. Otherwise, leave it as Normal.5. If IP Mode is set to Foreign, in the BBMD Address field, enter the IP address of the BACnet

Broadcast Management Device (BBMD) that you want to register with, then enter theSubscription Lifetime (Time-To-Live) value. This is the interval at which the O3 must re-register with the BBMD to keep participating on the BACnet/IP network.

6. Click Save. The message "Changes Pending" appears at the top of the page.7. Return to the object list page and click Device Actions > Activate Network Change.8. Open object NP5 (Ethernet1 - BACnet) and select the Out of Service checkbox to disable

BACnet/Ethernet.

Setting Up the O3

The O3 does not route and cannot function as a BBMD.

Disabling NTPNetwork Time Protocol (NTP) service is enabled by default, which allows the O3 to synchronizewith Coordinated Universal Time (UTC) time when connected to the internet.

Time zone offsets are not currently supported by the firmware. If you are usingenteliWEB, you cannot enable the time zone setting in the DEV object.

If you want the O3 to get its time from another BACnet device or from enteliWEB, you mustdisable the NTP service.


Setting Up the O3


To disable NTP:l Command object BV42 (NTP Enable) to manual mode and set the object value to Off.

Enabling a Startup SoundYou can enable the "Power On" startup sound to play when the O3 is restarted. By default, thisoption is disabled.

To enable the startup sound:

1. Command object BV44 (Startup Sound Enable) to manual mode and set the object value toOn.

2. Restart the O3 to verify that the sound plays. If you're using enteliWEB, on the object listpage, click Device Actions > Reset.

Setting Up the O3

Custom Settings

Creating a Custom Light Ring ColorThe light ring consists of red, green, and blue LEDs. You can create custom colors by adjustingthe intensity of the component LEDs.

To create a custom light ring color:

1. Command object BV7 (Light Ring Activate Custom Colors) to manual mode and set theobject value to On.

2. Open one or more of the following objects: AV3 (Light Ring Custom Color Red), AV4 (LightRing Custom Color Green), or AV5 (Light Ring Custom Color Blue).

3. Set the object(s) to manual mode.4. For each object, enter an object value between 0 (Off) and 100 (full intensity) and save your

changes.

Possible light ring color settings include the following:

Color AV3 (Red)

AV4 (Green) AV5 (Blue)

Red 100 0 0

Green 0 100 0

Blue 0 0 100

Cool White 100 100 50

Yellow 100 50 0

Orange 100 25 0

Pink 100 0 25

Teal 0 100 50

The light ring displays the custom color until object BV7 is set to Off.

Light ring commands are processed in the following order: Device status display BV8(highest priority) > Light ring brightness AV6 > Activate custom light ring color BV7 >Play light ring pattern MV1 (lowest priority).


Setting Up the O3


Loading Custom SoundsYou can load up to 25 custom sounds, saved as WAV files, to the O3. Each sound file should notexceed 1 MB. The total number and size of custom sounds supported will depend on the amountof remaining free space in the system.

To load custom sounds to the O3:

1. Create a FIL object for each audio file, with instances between 126 and 150.2. Open each FIL object and upload the audio file that you want to associate with that FIL.3. Update the existing MIC2 object and add states 26 to xx for the custom sounds (FIL126 to

FIL1xx).

To play a sound, command object MV28 (Play Sound) to manual mode and set the object value tothe sound you want to play. For example, "1. Power On".

Controlling Colors and Sounds RemotelyYou can control the device's light ring and/or sounds remotely using GCL+ code executed on aBACnet system controller.

For example, you could write a program to activate the light ring and play a sound when motionis detected. If the O3 has a BACnet Device_Instance property (Device Number or Device ID) of1503, the GCL+ code on the system controller might look something like this:

//play light ring and sound on motion detectionIfOnce 1503.BI9 Then1503.MV1 = 5 //play "occupancy active" light ring1503.MV28 = 7 //play "occupancy sound"End If

Setting Up the O3

GCL+ ProgrammingGCL+ programming language makes it easier to develop application control logic in a simplifiedway.

Use Program (PG) objects to develop, validate, download, and debug GCL+ programs. You cancreate up to five PG objects, PG1–PG5, in one device. You can also copy PG objects betweenvarious V4 devices. For more information about using GCL+, see help.deltacontrols.com

You need enteliWEB 4.20, or enteliWEB 4.19 with the patch to use GCL+.If you don't have enteliWEB or enteliCLOUD, you can contact Delta ProfessionalDevelopment Services to develop your GCL+.

You can write GCL+ code directly into the device to write application control logic, such ascontrolling the local I/O, reading values from other devices, writing values to other devices, etc.

Additionally, you can use existing code available in other Delta products to write GCL+ code.

GCL+ does not replace Node-RED; Node-RED can still be used for IoT integrations. ContactDelta Professional Development Services to create your Node-RED flows.

Configuring the IR BlasterSet up the O3 to transmit infrared remote control signals using enteliWEB or MQTT.

To configure the IR blaster using enteliWEB:

1. Obtain the remote control codes specific to your appliance brand and model in Pronto hexformat (4-digit hexadecimal values separated by spaces). Remote control codes areavailable online on websites such as remotecentral.com.

2. Specify the CSV object (there are 12 default CSV objects per O3) with specific instances aslisted in the IR Blaster table, command it to manual mode, then enter the remote controlcode as the Value property.

3. Specify how many times you want to repeat the code in the AV10 object. By default, code issent once per transmission.

4. In the MV9 (Send IR Code) object, command the object value (select one of 12 optionsavailable) to the state corresponding to the remote control signal that you want totransmit.

To configure the IR blaster over MQTT:

1. Publish the remote control code using the format {"data": "IRCODE"} tocommands/object/irCode


https://help.deltacontrols.com/

http://www.remotecentral.com/

Setting Up the O3


For example, the following code {"data": "0000 006d 0022 0003 00a9 00a8 0015003f 0015 003f 0015 003f 0015 0015 0015 0015 0015 0015 0015 0015 00150015 0015 003f 0015 003f 0015 003f 0015 0015 0015 0015 0015 0015 00150015 0015 0015 0015 003f 0015 003f 0015 003f 0015 0015 0015 0015 00150015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 003f 0015003f 0015 003f 0015 003f 0015 003f 0015 0702 00a9 00a8 0015 0015 00150e6e"} can be published to commands/object/irCode1

2. To send the IR code, publish {"data":IR CODE INDEX} to commands/object/irPattern.

IR CODE INDEX specifies the index of the IR code you want to send. Allowable index valuesrange from 1 to 13. 1 is Idle so the IR code index must start at 2 for irCode1, 3 forirCode2, 4 for irCode3, and so on.

For example, {"data":2}

Working with MetricsEdge analytics collected on the O3 are known as metrics.

Metrics are computed using a rolling database of archived sensor information, providingimmediate insight into room conditions without the need for post-processing.

The O3 archives temperature, humidity, light level, sound level, and occupancy data every timethere is a change of value. This archived data is then analyzed hourly to compute the followingmetrics:

l min/mean/max occupant temperaturel min/mean/max occupant humidityl min/mean/max light levell min/mean/max sound levell occupancy utilization

Once the metrics have been computed, the raw sensor data is purged. The metrics are kept for30 days. This 30-day history is available as a data dump via MQTT. See the O3 Edge MQTTAPI Reference Guide for more details.

You can set up Trend Log (TL) objects to monitor the metrics and collect sample data.This allows you to visualize the metrics on a line chart or in a table, or archive them ifyou'd like to report on them historically.


Working with Metrics


Viewing MetricsTo view metrics over BACnet, manually create the following objects.


Metrics - OccupantTemperature - mean

AV201 Average occupant temperature duringprevious hour.

Metrics - OccupantTemperature - min

AV202 Lowest occupant temperature during previoushour.

Metrics - OccupantTemperature - max

AV203 Highest occupant temperature during previoushour.

Metrics - OccupantHumidity - mean

AV211 Average occupant humidity during previoushour.

Metrics - OccupantHumidity - min

AV212 Lowest occupant humidity during previoushour.

Metrics - OccupantHumidity - max

AV213 Highest occupant humidity during previoushour

Metrics - Light Level -mean

AV221 Average light level during previous hour.

Metrics - Light Level - min AV222 Lowest light level during previous hour.

Metrics - Light Level - max AV223 Highest light level during previous hour.

Metrics - Sound Level -mean

AV231 Average sound level during previous hour.

Metrics - Sound Level -min

AV232 Lowest sound level during previous hour.

Metrics - Sound Level -max

AV233 Highest sound level during previous hour.

Metrics - OccupancyUtilization

AV241 Percentage of time the space was occupiedduring previous hour.

TABLE 1: READ-ONLY METRICS OBJECTS

Working with Metrics

Forcing UpdatesMetrics are normally computed at the beginning of every hour (12:00, 1:00, 2:00, etc.). However,you can force a metrics update at any time.

To force a metrics update:

1. Create object BV292 with the name "Compute Metrics."2. Command the object to manual mode and set the object value to On.

Deleting MetricsMetrics are archived for 30 days. However, you can delete all metrics from the database at anytime. Normally, this is done during commissioning to clear any metrics acquired during theinstallation and setup of the O3.

To delete all metrics:

1. Create object BV291 with the name "Clear Metrics Database."2. Command the object to manual mode and set the object value to On.


Revision HistoryEdition Date Description

1.0 February 9, 2021 New document.

2.0 May 12, 2021 Removed unsupported BACnet objects(AI18, AV27, AV38, CSV41) and addedsection on metrics.

2.1 June 14, 2021 Removed BACnet objects (MV40 andMIC4). Updated firmware upgradeinstructions. Added BV48 object.

2.2 June 29, 2021 Changed document formatting.

2.3 July 8, 2021 Added procedure to enable the internalMQTT broker.

2.4 September 8, 2021 Added 'GCL+ Programming' section.Updated introduction to include O3Edge support for EnOcean.

2.5 February 3, 2022 Added IR blaster feature.


Date post:	26-Apr-2023
Category:	Documents
Upload:	khangminh22
View:	0 times
Download:	0 times