EMH Data Collection Methods

This article provides details on methods of collecting data from the Leviton Energy Monitoring Hub.

Notes:

• Upload features listed here are available on the Energy Monitoring Hub EMB A8810, Energy Monitoring Hub A8812, and HubLite EMB A7810
• Processing the data for billing reports, summaries, analysis, and other data processing concepts are beyond the scope of this document.

EMH data collection can be divided into Push or Pull methods:
Push Pull
• HTTP(S) POST to BMO • HTTP(S) GET CSV files from EMH web interface
• HTTP(S) POST to your server • HTTP(S) GET live data in XML from EMH web UI
• HTTP POST XML to your server • FTP client download from EMH
• FTP push to your server

HTTP or HTTPS POST to BMO

• EMH sends data to the Leviton Building Manager Online software service BMO at https://levitonbmo.com/
• Annual paid service with tools for data graphing, analysis, and reports
• Different tiers of service depending on feature needs and number of datapoints
• Removes any need for software development of your own data solution
• Data is hosted and backed up on the Amazon AWS cloud

HTTP POST, HTTPS POST, or XML format HTTP POST push directly to your server

• EMH uploads data directly to your webserver
• You must create a script to handle the protocol and process the incoming data
• Typically requires webserver, scripting, and database expertise
• Protocol of choice for enterprise level deployments and companies looking to create a SaaS offering with the data collected from our devices.
• XML has greater overhead but may be easier to process
• No HTTPS option for XML
• Additional protocol documentation and sample scripts are available for these methods

FTP push

• CSV files are uploaded automatically to your configured FTP URL
• Expect one CSV file, per device, per configured data upload interval
• Files and data will need to be processed regularly

FTP pull

• EMH retains CSV log files in tar.gz format on internal memory
• If data is not collected/removed and internal memory becomes full, oldest log files are purged when the EMH flash memory is full
• Your computer must call each EMH to collect the data.
• Appropriate inbound network ports must be opened for an FTP client to reach the EMH
• Log files are in /mnt/main/log/modbusHTTP GET of XML formatted live data
• Each GET request initiates an immediate polling for new data from that device to present
• Slightly older data may be provided with an age (in seconds)
• Best for applications in which a small number of data points needs to be pulled with near real-time updates.
• Refresh rate will depend on overall system hardware and configuration

Example URLs of where live XML information can be accessed:
http://username:password@192.168.40.50/setup/devicexml.cgi?ADDRESS=006&TYPE=DATA
http://username:password@192.168.40.50/setup/devlist.cgi?GATEWAY=127.0.0.1&SETUP=XML

HTTP GET from the EMH Web Interface

The EMH allows for download of log files from your web browser. Log into the EMH and navigate to Log File Data > Log File Export. There it will provide options to download the log file for a device on that EMH’s device list.

It is possible to automate this process using a direct URL. An example of this is below:
http://username:password@192.168.40.50/setup/logexport.cgi?MB=0