Connectivity

Frequently asked questions regarding device connectivity issues.

Can I connect to the eGauge without a network?

You may also refer to the complete guide, Directly Connecting to the eGauge

Below are the recommended steps to establish communication with an eGauge when the HomePlug adapter or eGauge Ethernet port is directly connected to the Ethernet port of a computer, and the eGauge is configured for DHCP. Note that Ethernet to USB dongles may require additional configuration not covered here.

1. Configure the computer's Ethernet port to a static IP address of 192.168.1.11. The exact steps to do this vary, depending on the operating system of the computer. For Windows, this can be done by starting the "Control Panel", then selecting the "Network and Sharing Center". For Linux, this can be done by selecting "System", then "Administration", then "Network Tools". For Mac OS X, this can be done by clicking on the Apple Menu's "System Preferences", then on "Network Control Panels".

2. Power-cycle the eGauge main unit. To do this, turn off the breaker(s), wait for 5 seconds, then turn them back on.

3. EG30xx will have a Status LED blinking green/cyan or blue/cyan. EG4xxx will show an Ethernet icon on the LCD Display.

4. Open a browser on the computer and enter the address

http://192.168.1.88

into the browser's address bar (not the search bar), then press the Enter key.

5. At this point, you should be connected to the eGauge.

If the eGauge has a static IP address, modify the IP address set on the computer and the IP address used to access the eGauge in the steps above. For example, if an eGauge has been set to use a static IP of 10.1.10.50, the computer should be set to 10.1.10.11 and http://10.1.10.50 should be entered into the browser address bar.

 

How much data (bandwidth) does the eGauge use?

The eGauge meter stores all data locally on the device itself, meaning it does not need to be connected to the internet and the proxy server for functionality. Because of this, data is only transferred when a user visits the device interface, or if data sharing is enabled to push data to a third-party server. 

In most cases, any high-speed internet such as DSL, satellite, or cable is sufficient for networking multiple eGauge devices without any effect on other network traffic. Concerns may be raised on networks with limited data, such as cellular. In cases like this, if a browser window with the eGauge interface is left open, small amounts of data will be transferred indefinitely until the browser window is closed, and if data caps are exceeded, service may be disabled or overages charged. 

Put simply, every eGauge meter will use different amounts of data, depending on multiple factors.

Main device interface
The eGauge meter will use internet bandwidth when the eGauge main graph interface is viewed through our proxy server (ie, http://DEVNAME.d.egauge.net/ or http://DEVNAME.egaug.es/). If the eGauge is viewed locally (ie, http://DEVNAME/ on Windows, http://DEVNAME.local/ on Mac or Linux, or the local IP address), this will only use internal network bandwidth, not external internet bandwidth. On limited bandwidth internet connections such as cellular, accessing locally will reduce data usage. 

When the main graph page of the eGauge is requested, it may load between 200 to 250 KB of data. Depending on how many registers are being loaded and the time period displayed in the graph, the eGauge may load an additional 10KB to several hundred KB. After the initial load, the eGauge will need to send instantaneous (second by second) data which may range from 0.5KB to 10KB per request. These numbers represent one browser window viewing the main graph page; additional browsers viewing the graph will each use this amount of data. 

Pushed data
The eGauge has the ability to push stored data to a third party service. Push data usage is influenced by the number of registers, push interval, and any push options (such as totals or compression). As a rule, the smaller the interval, the more data is used. Depending on the configuration, push data usage can vary from a few megabytes to over a gigabyte per month. Beginning with firmware v2.03, push options gzip and deflate are available to compress the pushed data. This can significantly reduce the amount of data usage required for pushing data. 

Testing/tracking data usage
Data usage varies widely based on a number of factors, each eGauge will use different amounts of data. Also, data usage will not necessarily remain constant from month to month. To see data usage on the main interface, you can use a browser such as Google Chrome, open the developer console (usually CTRL+SHIFT+J or F12), click the "Network" tab, and open a device interface. Every page request and its size will be visible in the Network tab. 

You can get an idea of how much data will be used by uncompressed pushes (or polls) by making CGI calls to egauge-show, specifying different options such as interval. For example,

http://DEVNAME.egaug.es/cgi-bin/egauge-show?m&n=360

will represent a single push from a device set to push every 6 hours with no options. Similarly, 

http://DEVNAME.egaug.es/cgi-bin/egauge-show?m&n=15&a

will represent one data push from an eGauge set to push every 15 minutes with totals as an option. For full details and parameters available, please see the eGauge XML API document.

How do I configure a static IP address?

If in doubt, a static IP address is most likely not required. eGauge support can assist with setting a static IP address, but cannot guarantee that the values used in that address are correct for the network. Please refer to the document below for additional information and step by step instructions.        

The eGauge by default comes configured for DHCP. If the eGauge is unable to obtain a DHCP address from the network, it will default to 192.168.1.88. Thus, it is possible to connect to the eGauge directly from a laptop or computer. To do this, connect a computer to the eGauge via HomePlug or direct Ethernet, configure the computer with an IP address of 192.168.1.11, and direct a browser to http://192.168.1.88 to access the eGauge interface. More information on connecting directly is available here.  

Warnings

Configuration

A static IP address may be configured in Settings -> Network Settings. Default password information can be found in this knowledgebase article. The following example shows a device configured with an IP of 10.1.10.23:

Every entry needs to be entered correctly for network functionality. Any Incorrect setting can disrupt all network traffic and make the eGauge inaccessible remotely and locally.

Other services such as BACnet can be disrupted if certain values such as the Broadcast address is incorrect.

The Network and broadcast address values can be calculated from the IP address and netmask, using a subnet calculator tool.

 

How does proxy server connectivity work?

For more information about the proxy server see this article. Information about all network connections may be found here.

The eGauge proxy server is a free, best effort service provided by eGauge to allow easy access to the eGauge interface from anywhere on the internet.

The proxy server allows easy access to an eGauge behind a firewall and obfuscates the IP address and location of the eGauge meter. When a client browser views an eGauge over the proxy server, they only see the IP address of the proxy server, no IP or network location information of the eGauge is transmitted through the proxy to the client browser.

The eGauge proxy server is located at d.egauge.net, and devices can be accessed at:

http://DEVNAME.d.egauge.net or http://DEVNAME.egaug.es where DEVNAME is the device name of the eGauge. For example, eGauge12345 could be accessed on the eGauge proxy server at http://egauge12345.d.egauge.net or http://egauge12345.egaug.es (note that this is not a real device name, so the link will not work).

The eGauge meter will make an outbound connection to TCP port 8082 (for plain HTTP) and TCP port 8084 (secured HTTPS, EG4xxx only). No incoming firewall access is necessary.

The proxy-server address is configured in Settings -> General Settings in the "Proxy-server hostname" field. If this field is changed to something else besides d.egauge.net, the eGauge will not be accessible at http://DEVNAME.d.egauge.net or http://DEVNAME.egaug.es/. If the hostname of the eGauge is changed without requesting it through eGauge support, the proxy-server URL will not work either.

To prevent unwanted access to your eGauge on the proxy server, you can configure a site-wide password which will require credentials to view any eGauge data. This can be configured in Settings -> Access Control. Proxy server access can also be fully disabled by changing the "Proxy-server hostname" field under Settings -> General Settings to 0 (zero). Note that this will prevent eGauge support from accessing your meter (for example, if requesting a password reset).

 

What data export and data import options does the eGauge support?

Most users will probably access data on an eGauge meter via the classic interface or mobile-friendly interface. These interfaces are designed for ease of use and accessibility. However, advanced users may also be interested in other options to read data form (or into) the eGauge meter.

eGauge meters feature a variety of communications options. These can be used to read data from third party devices into the meter, or make data available for third party devices to read from the meter. These communication options are briefly summarized below. Click on the links in the table for additional information.

The following tables apply to EG4xxx meters only. EG30xx and older meters cannot use any option requiring a serial to USB adapter.

 

Data export (read data from the meter)

Modbus TCP Function Code 4
Modbus RTU Function Code 4, serial to USB adapter required, EG4xxx only
BACnet IP  
BACnet MS/TP serial to USB adapter required, EG4xxx only
XML API  
Remote eGauge  
USB Export Can be scripted to run automatically, EG4xxx only

 

Data import (read data into the meter)

Modbus TCP Function code 1, 2, 3, and 4
Modbus RTU Function code 1, 2, 3, and 4, serial to USB adapter required
Remote eGauge