Skip to main content

Obvius AcquiSuite (Leviton Energy Management Hub)

Updated yesterday

Obvius is a legacy integration. This document provides assistance for existing integrations only.

Obvius was acquired by a company called Leviton, and the AcquiSuite device was rebranded as the Leviton Energy Management Hub (EMH). Functionally, the EMH and the AcquiSuite are identical—aside from differences in name and physical appearance. All procedures in this guide apply equally to both versions.

👍 This article will help you:

  • Understand installation and connectivity requirements and data flow

  • Configure Obvius AcquiSuite (a.k.a. Leviton Energy Management Hub (EMH)) devices for data sharing with Atrius

  • Set up integration points and mapping in Atrius

  • Troubleshoot your Obvius integration

To view your current Obvius integration details in Atrius, go to Settings on the left side menu, select Integrations, then select Obvius.

Overview

An Obvius AcquiSuite is a piece of hardware that sits on an Energy Management System (EMS), Building Automation System (BAS), or Building Management System (BMS) network and pushes real-time Modbus, Pulse, or BACnet data to Atrius.

An Obvius Data Logger is used when existing BACnet points are present on a BMS, BAS, or EMS system in order to push data to Atrius. It is able to push data from a large number of points to Atrius, depending on the setup of your BACnet system.

The BACnet compatible point(s) measures the resource and submits that value over BACnet to the Obvius Data Logger. The Obvius Data Logger pushes that value and timestamp to Atrius via a CSV driver installed on the device. The interval of data, also known as resolution, is determined by the point.

Integration Type: Obvius formatted text file push via HTTP/HTTPS POST
​Data Push Endpoints:

  • Standard: http://obvius.buildingdashboard.net/csv/obvius/acquisuite/

  • SSL: https://obvius.buildingos.com/csv/obvius/acquisuite/

Prerequisites

Before beginning the installation, ensure you have:

  • Access to Obvius UI (local or remote)

  • Admin access to Atrius

  • Obvius device configured with real-time measurements

  • Internet access for outbound HTTP or HTTPS traffic

  • Network connectivity between Obvius and BACnet devices

  • Static IP or DHCP reservation recommended

Responsibilities

Customer Responsibilities

Customer Support Responsibilities

BAS/BMS/EMS: Ensure point(s) are properly calibrated and configured.

Configure Atrius: Open up a gateway to receive point data.

Confirm connectivity: Confirm connectivity between point and controls system with correct Modbus/BACnet IDs, values, etc.

Provide useful tools: Collect, store, and display point data.

AcquiSuite installation: Ensure the gateway is installed correctly, has power, and has an ethernet connection.

Verify data mapping: Ensure the customer provided the correct Obvius Data Logger mapping with necessary point details.

Allow outbound communication: Confirm networking details with IT to allow Obvius Data Logger outbound communication to Atrius servers over the correct port.

Installation and Setup

Hardware Installation

  1. Mount the Obvius gateway securely in a panel or control enclosure

  2. Connect power to the device according to manufacturer specifications

  3. Connect ethernet to local network with outbound internet access

  4. Verify network connectivity and note the assigned IP address

Initial Obvius Configuration

  1. Access the Obvius web interface:

    • Use default IP, DHCP-assigned IP, or static IP address

    • Customer IT may require specific IP configuration

  2. Initial login and setup:

    • Log in using default credentials or existing account

    • For newer AcquiSuite devices, you may be required to create a new password

Data Upload Configuration

  1. Navigate to data upload settings:

    • Go to: Log File Data → Setup Data Upload

  2. Choose upload method (Standard HTTP or SSL): Standard Upload (HTTP):

    • Navigate to: Log File Data → Setup / Upload

    • Set scheduled upload time to every 15 minutes (recommended)

    • Configure Number of times to retry to 3 times (recommended)

    • In Upload Channel #2, select protocol: Obvius Building Manager Online™ (default)

    • Enter Push URL: http://obvius.buildingdashboard.net/csv/obvius/acquisuite/

    • Select Save and Apply settings

    SSL Standard Upload (HTTPS - Recommended):

    • Navigate to: Log File Data → Setup / Upload

    • Set scheduled upload time to every 15 minutes (recommended)

    • Configure Number of times to retry to 3 times (recommended)

    • In Upload Channel #3, select protocol: BMO over SSL/TLS

    • Enter Push URL: https://obvius.buildingos.com/csv/obvius/acquisuite/

    • Select Save and Apply settings

    ⚠️ Important: The upload schedule controls how often data is sent to Atrius (recommended: 15 minutes). This does NOT control data resolution—that is controlled by the Data Logging Period.

BACnet Device Integration

  1. Network connectivity:

    • Connect BACnet IP-enabled power meter and Obvius AcquiSuite to the same network

    • Ensure both devices can ping each other and are on correct IP subnet

  2. BACnet gateway configuration:

    • Navigate to: BACnet → Gateway

    • To set a fixed BACnet ID, select discover (in line with BACnet base object ID field)

    • Wait for devices to appear in the discovered devices list

    • Enter BACnet device instance ID or IP address if the list is too large

  3. Add devices:

    • Press Add Device for each discovered device

    • Navigate to Device List to verify devices were added

    • Select create configuration to configure port (default: 47808)

    • Change port number if different from default

    • Repeat for all AcquiSuite devices needed

  4. Save and test:

    • Save the configuration

    • Test device communication to confirm successful polling

Data Logging Configuration

  1. Set data logging period:

    • Navigate to: Devices → Logging → Data Logging period

    • Set Data Logging Period to 5-15 minutes (must be less than upload period)

    • This setting dictates the resolution of your data in Atrius

  2. Test device communication:

    • Select: Testing/Diags → Connection Test → Begin Test

    • Review any failures and resolve using Obvius resource guides

    • MAC address (found at top left of navigation panel, begins with 001) will be used for device identification

Atrius Integration Setup

  1. Access Atrius:

  2. Register device:

    • Enter the MAC address of the Obvius device (found in UI or device label)

    • Atrius will associate incoming payloads with this MAC address

Integration Configuration in Atrius

Platform Access & Point Mapping

  1. Access Point Discovery:

  2. Wait for data points:

    • Allow 5–15 minutes for points to appear based on incoming payloads

    • Refresh browser if data is not immediately visible

  3. Connect and configure points:

    • Click Connect next to each desired point (e.g., kW, kWh)

    • Name each point per your naming convention

  4. Set point metadata:

    • Meter name (e.g., "Main Electrical Panel")

    • Building name associated with the meter

    • Keep Hidden: No

    • Point type: Electricity

    • Source Units (e.g., kWh)

    • Display Units (e.g., kW)

    • Offline threshold

  5. Save configuration:

    • Save all point mappings

    • Allow 5-15 minutes for data transmission

Data Validation

  1. Verify data transmission:

    • Wait for scheduled data push from Obvius (within 5–15 minutes)

    • Navigate to: Points (https://buildingos.com/meters/)

    • Search for newly enrolled points and click meter link

  2. Validate data accuracy:

    • Confirm values match expected readings from source devices

    • Hover over data points to verify timestamp and unit alignment

    • Check data appears at expected intervals

  3. Use Obvius diagnostics:

    • In Obvius UI: Diagnostics → Upload Status to confirm successful transmission

    • Verify MAC address matches registration in Atrius

Best Practices

  • Use HTTPS push method when SSL firmware is available

  • Reserve a static IP for the Obvius device on your network

  • Back up Obvius configuration regularly

  • Review point mappings in Atrius after firmware updates

  • Set Data Logging Period less than upload schedule for optimal data resolution

  • Keep firmware updated with weekly automatic checks enabled

Troubleshooting

Review common troubleshooting steps that may restore communication between an offline Obvius gateway and Atrius.

If all Obvius points are offline:

  1. Physically reboot the Obvius device

  2. Verify network connectivity:

    • Ensure Obvius device has outbound connection to IP range: 20.59.7.16/29 via http (port 80) or https (port 443)

    • Check if recent network/firewall changes impacted communication

If partial list of Obvius points are offline:

  1. Verify individual metering hardware:

    • Confirm devices at offline locations are reporting expected values

    • Check individual device communication to Obvius gateway

  2. Check network connectivity:

    • For devices not directly wired to Obvius gateway, verify local connectivity

    • Confirm Modbus TCP Port 502 and/or BACnet UDP Port 47808 access

    • Verify no recent network changes have occurred

Common Issues and Solutions:

No Data Appearing in Atrius:

  • Confirm upload status shows success in Obvius diagnostics

  • Validate MAC address registration in Atrius gateway creation

  • Confirm outbound HTTP/HTTPS access is allowed

  • Standard Upload test: Look for success message: "Success: Channel X's Uploader was able to contact, authenticate with and receive a reply from http://obvius.buildingosdashboard.net/csv/obvius/acquisuite/."

  • SSL Upload test: Confirm HTTPS outbound access with connection test

Unexpected or Missing Points:

  • Re-check BACnet point mappings in Obvius UI

  • Verify time synchronization between BACnet device and gateway

  • In Atrius: Navigate to Settings → Integrations → Obvius → Gateway ID → Convert Time to UTC (try toggling YES/NO)

  • In Obvius: Check Systems → Date and Time settings

Payload Not Received:

  • Check for typos in Push URL configuration

  • Verify DNS server settings (try Google: 8.8.8.8/8.8.4.4 or Cloudflare: 1.1.1.1)

  • Update Obvius firmware:

    • Navigate to: Devices → System → Firmware Version

    • Enable Check for and Install Firmware updates weekly

    • Install available updates

Connection Issues:

  • Verify stable ethernet connection

  • Check DHCP lease status (consider static IP)

  • Test ping connectivity between Obvius and BACnet devices

  • Confirm port accessibility (BACnet: 47808, Modbus: 502)

Remote Access Setup

If remote access to Obvius device is needed:

Web UI Method:

  1. Log into AcquiSuite Web UI

  2. Navigate to: Networking → Setup

  3. Select "Allow Remote Access"

  4. Apply settings

  5. Record Serial Number and RA Pin

LCD Screen Method:

  1. From LCD screen: Menu → TCP/IP Config

  2. Select RAccess On/Off → Enable

  3. Record Serial Number and RA Pin

Try Troubleshooting your Obvius integration with a decision tree

Open the interactive Decision Tree tool below to diagnose problems with your Obvius integration, or scroll down the page for instructions and additional resources.

Launch Decision Tree tool in a new window ↗

Decision Tree

Additional Resources

Device Support:

  • A Facilities or Controls point of contact can determine if the Obvius device has lost power or network connectivity and perform physical reboots if necessary

  • A Network or IT point of contact can determine if the Obvius device is impacted by recent network/firewall changes or network hardware changes

Technical Resources:

🚧 Forward this information to your points of contact

Please forward this information to any additional Facilities, Controls, Network, or IT points of contact at your organization for on-site support.

📘 Contact Customer Support

For additional questions regarding your integration with Atrius, please contact Customer Support.

Related Articles
eGauge
Kodaro Niagara CSV
EC-Net Facilities / Niagara 4
Data recovery options
Atrius Energy & Sustainability Standard Integrations
Did this answer your question?