Frequently Asked Questions

1. Is it OK to plug the HomePlug adapter into a power-strip?
   We recommend plugging the HomePlug adapter directly into a wall-outlet. However, if that is not an option, it is possible to plug it into a power-strip provided the power-strip has no surge-suppressor built in. Most power-strips designed for computers do have surge-suppressors built in, so they are not suitable. Low-cost power-strips available at the local hardware store generally will work fine, however.
2. How do I compare eGauge data with my utility bill?
   On the eGauge home screen, click on the link after the "Time range:" label. The link will turn into four text-boxes which can be used to enter the time range that should be displayed. In the left-most box, enter or select the date at which the meter was read in the previous month. In the third text box from the left, enter the date at which the meter was read in the current month. Click on "Set". The graph will be updated to display the chosen date-range and the summary behind the time range will display the amount of energy produced (green) and consumed (red), as well as the net energy used or produced during that time-period (black). The utility bill's kWh-figure should correspond to the net energy displayed.
3. How secure is eGauge?
   Please click here for a white paper on eGauge security considerations.
4. I can't connect to my device anymore, what should I do?
   First, 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 eGauge345 or whatever the real name of your device is). Using a computer that is conneced 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:

   http://DEVNAME/	(use this on Windows-computers)
   http://DEVNAME.local/	(use this on any other type of computer, e.g., Mac or Linux)

   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:

   • Verify that the HomePlug adapter is plugged into a wall-outlet and that all LEDs are (mostly) green. If you have a Netgear adapter, all three LEDs should be a steady green, except that the bottom LED may be flickering from time to time, indicating network traffic. If you have an Actiontec adapter, both the Power and Link LEDs should be mostly green, except for the occasional flicker, indicating traffic on the powerline or the LAN, respectively.
   • Check the Status LED on the eGauge. It should be green. If it is blue, it may indicate the the HomePlug speed is too low or the HomePlug link is interrupted. You can use the software on the CD that came with the HomePlug adapter to further diagnose the problem. If the Status LED is any color other than green or blue, contact eGauge support.

   Second, 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:

   http://DEVNAME.d.egauge.net/

   If the page loads fine and results an a graph that's updating, your eGauge is fully operation. If the page does not load, it indicates a problem in your LAN environment. For example, the DCHP server on your LAN may be handing out incorrect Internet information. Please consult an IT professional for further help.

5. How do I power-cycle eGauge?
   Locate the breaker in your break-panel to which the eGauge is wired to. 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.
6. My HomePlug adapter is connected to a Cisco Catalyst switch and it stopped working. What do I do?
   This answer applies only when a Netgear HomePlug 1.0 adapter is in use. With the Actiontec adapters eGauge is being shipped now, there is no issue connecting to Cisco Catalyst switches. Also, this question only applies to Catalyst Cisco products.

   Certain Cisco Catalyst switches detect excessive numbers of collisions on the port with a Netgear HomePlug 1.0 adapter and end up shutting down the port. When this happens, the bottom LED on the Netgear HomePlug adapter will go dark. Also, the switch's log file may contain error messages of the form:

   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 state
   

   To 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.