You may use the complete guide, Tutorial 6: Directly Connecting to the eGauge
Here are the recommended steps to establish communication with an eGauge when the HomePlug adapter or eGauge Ethernet port is directly connected into the Ethernet port of a computer, and the eGauge is configured for DHCP:
1. Configure the computer's Ethernet-port to a static IP address of 192.168.1.11. The exact steps to do this vary with the operating system of the computer. For Mac OS X, this can be done by clicking on the Apple Menu's "System Preferences", then on "Network Control Panels". 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".
2. Power-cycle the eGauge main unit (turn off the breakers it is wired to, wait for 5 seconds, then turn them back on).
3. If you can see the Status LED of the eGauge, it should be blinking green/cyan or blue/cyan (cyan- light blue) now.
4. Open a browser on the computer, then type the address
http://192.168.1.88into the browser's address bar (not the search bar), then press the Enter key.
5. At this point, you should be connected to the device.
http://dev-name/cgi-bin/egauge-show?m&n=360will represent a single push from a device set to push every 6 hours with no options. Similarly,
http://dev-name/cgi-bin/egauge-show?m&n=15&awill 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.
This answer applies only when a Netgear HomePlug 1.0 adapter is in use! With Actiontec adapters (or any Turbo-mode HomePlug adapter), there is no issue connecting to Cisco Catalyst switches. Also, this question only applies to professional-grade Catalyst Cisco products, not to Cisco home routers or switches.
Jan 6 19:41:46 192.168.1.15 1041767: 1041766: Jan 6 19:41:46.038 MST: %ETHCNTR-3-HALF_DUX_COLLISION_EXCEED_THRESHOLD: Collisions at FastEthernet0/14 exceed threshold. Considered as loop-back. Jan 6 19:41:46 192.168.1.15 1041768: 1041767: Jan 6 19:41:46.038 MST: %PM-4-ERR_DISABLE: loopback error detected on Fa0/14, putting Fa0/14 in err-disable stateTo work around this issue, change the switch configuration to force full-duplex mode on the port. That is, turn off auto-negotiation and force the port into full-duplex mode, even though the HomePlug adapter advertises itself as a half-duplex device only. Alternatively, replace the HomePlug adapter with a Turbo-mode adapter (85Mbps).
|HomePlug AV PWR500/PWR200|
|HomePlug AV PWR500/PWR200||LED Label||Function||Typical Behavior||Other Behavior|
|PWR||Indicates the adapter has power||Green light||No LED - no Ethernet communication for too long or not receiving power|
|LK||Indicates a connection with the eGauge or another HomePlug AV adapter||Blinking red light when communicating with the eGauge||Blinking orange or green - possible connection with another HomePlug AV device
Off - no connection to any HomePlug AV devices
|ETH||Indicates an Ethernet line connection||Blinking green light when transmitting data||Off - may indicate an issue with network connectivity or a damaged Ethernet cable|
|HomePlug AV TL-PA2010|
|HomePlug AV TL-PA2010||LED Label||Function||Typical Behavior||Other Behavior|
|Indicates the adapter has power||Green light||No LED - no Ethernet communication for too long or not receiving power|
|Indicates a connection with the eGauge or another HomePlug AV adapter||Blinking green when communicating with the eGauge||Off - no connection to any HomePlug AV devices|
|Indicates an Ethernet line connection||Blinking green light when transmitting data||Off - may indicate an issue with network connectivity or a damaged Ethernet cable|
|HomePlug 1.0 HPE100T|
|HomePlug 1.0 HPE100T||LED Label||Function||Typical Behavior||Other Behavior|
|Power||Adapter has power and is connected to the eGauge or another HomePlug 1.0 device||Green light when active, blinking green light when transmitting data||Off - adapter is not receiving power, or cannot communicate to the eGauge|
|Link||Indicates an Ethernet line connection||Green when active, blinking green when transmitting data||Off - issue with network connectivity or a damaged Ethernet cable|
The pairing button on the TP-Link adapter will either put it in "pair mode" (where it looks for and connects to other devices also in pair mode) or "leave mode" (where it randomizes its encryption key, preventing it from pairing with another HomePlug device). If either state was triggered, it means the HomePlug adapter will no longer communicate with an eGauge using the default encryption key. You will need to use TP Link's configuration utility to reset the TP Link adapter to the default encryption key and enable it to communicate with the eGauge again. Note that this utility is developed and supported by TP Link, so eGauge cannot offer much in the way of troubleshooting assistance for the utility itself.
|Register||Which register should appear in the defined style|
|Color||Color for the chosen register|
|Line||Line style and thickness|
|Sign||Whether to style the line for positive, negative, or both sign|
The eGauge has the ability to back up data recorded on the device, and restore it to any eGauge device with the same register configuration.
For saving data to a spreadsheet, please see our video tutorial on exporting data to CSV here
The backup function is found in Tools --> Backup. From here, you can choose whether to perform a full backup, or partial backup. If performing a partial backup, choose the time range for the data to be backed up from. The backup file will be named backup-DEVNAME.bin where DEVNAME is your device name. This file is only used for restoring data to the eGauge; it cannot be processed or modified.
To restore a backup file, navigate to Tools --> Restore. From here, you can choose a full restore (all data in the backup file is restored), or only a range. Note when choosing full restore, all data in the backup file will overwrite data on the device. This means if the backup file contains data from when the eGauge recorded no values, this blank data will overwrite any data in the same time period on the device.
If uncertain about how much data is in the backup file, only restore the range of data necessary.
If restoring fails or hangs, please attempt the restore from the same LAN the eGauge resides on. This is done by using a computer at the same network as the eGauge, and clicking on LAN Access in the upper right-hand link menu before performing the restore.
[MFG] [MODEL] [SIZE_MM]/[SIZE_IN] [AMPERAGE]
|[MFG]||2-letter manufacturer code (see below table)|
|[MODEL]||Model of the CT (see below table)|
|[SIZE_MM]||CT inner-diameter in millimeters|
|[SIZE_IN]||CT inner-diameter in inches||[AMPERAGE]||CT amperage rating|
|JD||J&D||CC||Continental Control Systems|
|RCT||Rogowski coil (rope CT)|
|JS||Split-core CT||JRFS||Rogowski coil (rope CT)|
|ACT||High-accuracy split-core CT|
|RCT||Rogowski coil (rope CT)|
|CR||Solid-core DC CT|
|CRS||Split-core DC CT|
A physical register is a reserved section of memory that stores values associated with one point of measurement. Physical registers can store a variety of measurement types, such as voltage, current, kVA, and others depending on how the eGauge is configured. Note that there is not necessarily a correlation between the number of CTs installed and the number of physical registers used. For example, using one CT to monitor a 120V split-phase load or using three CTs to monitor a three phase load would both require one register.
The primary difference between the 16 register and 64 register eGauge is the granularity of the stored data.
Thus, the trade-off is between number of points (registers) that can be monitored and the granularity of the stored data.
Provided you are connected to the device directly through your LAN (not through egauge.net) you can enter username "owner"' and password "default''. You can ensure that you're directly connected to the device by clicking the "LAN Access'' link at the top right of the device web pages.
In some instances (including upgrading from a firmware version older than 2.15) the eGauge interface may not load correctly. Should this happen, the first troubleshooting step is clearing browser cache. Browser cache is data stored by the web browser to increase the loading speed of a webpage. However, this can have the effect of forcing the browser to use older data, which can cause issues with the eGauge interface.
Most modern browsers will attempt to store website credentials. If credentials that do not have the authorization to make changes are stored, the eGauge interface will show the error "Sorry, you are not authorized to make this change." instead of prompting for a username and password. To resolve this, the credentials must be cleared from browser memory.
To clear browser cache and/or stored credentials:
Note that some browsers (for example, mobile browsers) may have a different process. It may be necessary to search for browser-specific instructions if the steps above do not work. There is a Wikipedia article with more information available here.
Each eGauge meter has a unique device name (also referred to as hostname) that identifies the meter to the egauge.net proxy server. You will need this name to access your eGauge. The device name is printed in a number of locations:
If you are viewing the eGauge via the web interface, you can also find the device name by:
If you are unsure of the name of an eGauge that is connected to your network, you can open your router's configuration page and look for a list of active DHCP leases. Assuming the eGauge is connected using DHCP, it should have an entry in this table containing the hostname, current IP address, and MAC address (always starts with F8 2F 5B with the exception of some eGauge2 models, which may start with 00 50 C2). Because of the number of routers available, we cannot offer specific steps to find this information through the router interface; you should contact your router manufacturer or Internet Service Provider for additional support.
The eGauge has two MAC addresses. The first address is for Ethernet network communication (through the router or local area network). The second MAC address is associated with HomePlug power-line communication.
The Ethernet MAC address (for EG30xx) may be found:
The HomePlug MAC address (for EG301x) may be found:
Either MAC address may be used for device registration or verification of ownership.
The graph on the main page of the eGauge has a limited horizontal resolution, based on the size of the window and the horizontal resolution of the screen the eGauge is being viewed on. This means that only a limited number of data points can be present on the screen at a given time. On a longer view period, the eGauge will automatically average out several data points so the entire data range can be presented. This has the effect of "flattening" peaks and valleys on the graph. This effect becomes more noticeable the longer the view period. In order to see the data represented at maximum granularity, zoom in on a particular section (for example, a given monthly billing period). Note that this scaling behavior does not modify the stored data.
In your breaker-panel, locate the breaker to which the eGauge is wired. This breaker should be labelled "eGauge Disconnect" or something similar. Once you locate the breaker, trip it so power is off, wait 5 seconds, then turn it back on. Normally, there is a single multi-pole breaker for eGauge, but in some cases there may be two or three separate breakers (one per phase/leg). In the latter case, turn off all eGauge breakers, leave them off for 5 seconds, then turn them all back on.
First, power-cycle the eGauge. See the answer to the question "How do I power-cycle the eGauge?" for details on how to do this. Second, try unplugging the HomePlug adapter and then plugging it back in. This retrains the HomePlug-adapter and will often bring the device back.
Third, let's find out if the device can be accessed locally. We will use DEVNAME as a stand-in for the name of your device (e.g., for eGauge9999 or whatever the real name of your device is). Using a computer that is connected to the same LAN as the eGauge, open a browser and open one of the following two URLs, depending on the type of your computer:
If this URL loads and you get a graph that's updating, the eGauge is working fine and accessible through your LAN. If the URL does not load, check the following:
Fourth, let's find out whether the eGauge is connected to the server at egauge.net. Open a browser on a computer and try to load this URL:
If the page loads fine and results in a graph that's updating, your eGauge is fully operational. If the page does not load, it indicates a problem in your LAN environment. For example, the DHCP server on your LAN may be handing out incorrect Internet information. If possible, power cycle the router and/or modem as applicable and repeat the steps above. This can sometimes resolve connectivity issues that are not related to security settings. If this does not resolve the issue, please consult an IT professional for further help.
When contacting eGauge support, please provide the following details:
In addition, if eGauge2, or EG301x with HomePlug:
In addition, if EG30xx with hardwired Ethernet:
Almost all will cause issues, but will not necessarily prevent communication. A standard outlet can be installed; however this may not be allowed by code.
Some arc-fault breakers will trip when the HomePlug is connected. As of right now, eGauge Systems has no data on which models have this issue. If you come across a model that causes issues, please contact the support department
Outlet-style and strip-style both cause significant issues with HomePlug communication by filtering out the HomePlug signal. More information is available here.
The eGauge communicates with the HomePlug over the phase connected to L1. If the HomePlug is installed on the phase connected to L2, this will result in significant communication issues. For more information, refer to the phasing document available here.
In almost all cases, transformers will completely filter the HomePlug signal, resulting in a total loss of communication.
The effective range of HomePlug communications is approximately 50-100ft. Note that this distance refers to the length of wire in the walls, not a straight line between the eGauge and HomePlug. Longer wire runs will cause communication problems.
Depending on the model, the eGauge either uses the HomePlug AV or HomePlug 1.0 communication protocol. Other devices using the same protocol can cause communication issues. Note that devices using the 1.0 protocol will not interfere with devices using the AV protocol, and vice versa. Pairing the eGauge and HomePlug together can often resolve these issues. Information on pairing the eGauge and HomePlug can be found here.
The color and pattern of the LEDs on the eGauge and HomePlug can help troubleshoot communication issues. A guide to the HomePlug LED codes can be found here. A guide to the eGauge LED codes can be found here.
There are certain types of communication issues associated with older firmware versions. Keeping the eGauge firmware up to date is recommended. If you are unsure about the firmware version your device is using, refer to the instructions on checking firmware version located here.
While every browser might render things a bit differently, we strive to make sure the browsers listed are usable and all functionality is available. If you are having a problem with a particular supported browser and can not reproduce it in another, please share this information eGauge support, along with the exact version(s) affected, so we can get a fix in the works!
Please ensure your browser is up-to-date. Browser versions unsupported by the designer may not function with the eGauge interface.