Overview
This article explains how to check for excess and remove it if needed. If you do not know what excess is, click here to learn more.
Prerequisites
- Firmware v3.01 or greater to clear excess.
Instructions
Step 1: Go to http://DEVNAME.egaug.es/cgi-bin/egauge?teamstat Where DEVNAME is the device name of the master eGauge. Any value other than 0 in the <excess> tags indicates an accumulation of excess for that register. Local registers, such as power calculations, will always have an excess value of zero.
Information
- Meters sold after January 1, 2024 may show this information at: https://DEVNAME.egauge.io/cgi-bin/egauge?teamstat
Step 2:
Warning
- This command will immediately release excess in the form of a spike on the graph. Cumulative values (like energy/kWh) will now match between the master eGauge and remote devices. The resulting spike will be proportional to the missing kWh, and since it will be recorded in a one-minute granular entry, it will appear to be erroneously high. However, looking at the time from from when the remote device was lost, to the point of the spike or later, both cumulative (kWh/energy) and instantaneous averages (kW/power) values are correct.
Excess will naturally decrease as the instantaneous values are adjusted +/- 10% until it reaches zero. If it is undesirable to allow the excess to decrease naturally, excess can be cleared immediately by visiting http://DEVNAME.egaug.es/cgi-bin/protected/egauge-cfg?clearexcess where DEVNAME is the name of your eGauge. This may be the case if there was an unreasonably long loss of a remote device, such as several months.
Step 3: If cumulative values on the master eGauge are unimportant and the spike is undesired (for example, if excess was generated as part of the initial configuration process), you may see our tutorial on clearing spikes for information on how to clear this data from the device. Keep in mind, the spike and excess essentially contain the data that would have been written to the register over time, so erasing excess or spikes will invalidate data used for billing and other purposes.
Additional Resources