Skip to main content

What settings should I avoid changing?

The eGauge has a number of settings which can be modified by the end user. Some of these are relatively benign, while others can impact accuracy or even break network connectivity outright. This article is intended to provide first-time users with a brief overview of which settings can be experimented with and which settings should be left alone, along with sample consequences for changing these settings. Note that this list is not exhaustive - only the most serious examples are included here (changes that will ruin meter data, break connectivity, or cause similar major problems).

Settings under Settings -> Preferences are generally related to appearance, and can be safely modified. However, it's prudent to make a backup (screenshot) of this page before making major changes.


Settings that can cause accuracy issues:

Changing anything under Settings -> Installation can cause massive accuracy issues. Most of these changes will cause incorrect readings from the time they are applied moving forward. Generally, these settings should be properly configured when the eGauge is first installed and then left alone. Incorrectly recorded data cannot be adjusted or recovered.

Changing the "Date & Time" under Settings -> Date & Time will cause data to be recorded with incorrect timestamps. Depending on the change, it may cause the eGauge to "roll back" and write over data which has already been recorded. This setting should be automatically managed if the eGauge is connected to an NTP server.


Settings that can cause connectivity issues:

Changing "Proxy server hostname" under Settings -> General Settings or any setting under Settings -> Network Settings can cause a loss of communication. This can be limited to the proxy server connection (meaning the meter would still be accessible over the local network) or can also impact the local connection (eg, invalid static IP addressing) making the meter inaccessible over the local network as well.

Pairing the eGauge with the wrong HomePlug adapter under Settings -> HomePlug can completely break HomePlug (powerline) communication. If in doubt, it's usually not necessary to pair the eGauge with a HomePlug.

Making changes to Settings -> BACnet or Settings -> Modbus Server can break communication with remote devices which read data from the eGauge. The effects of this might not be noticeable through the eGauge UI itself.


Settings that can cause other issues:

Modifying alerts under Settings -> Alerts can break expected alert behavior. For example, adding a new alert with a higher priority level can prevent lower priority alerts from sending a notification in a timely manner. However, these settings can be safely experimented with if a copy (screenshot) of the original settings is made, as they have no impact on communication or stored data.

Changing the "System Language" setting under Settings -> General Settings can be annoying if a language is selected which is not understood by the user, but has no major impact on device functionality.

Changing the "Min. interval for public usage data" under Settings -> General Settings will cause the Channel Checker to display no values and may cause the graph to look "choppy" unless valid credentials are used to log in to the eGauge meter. This is the intended behavior of this setting. The stored data on the meter is not affected by this change, and it can always be turned off if desired.