App is Showing Different Water Consumption Than Expected

Last updated
Save as PDF

There are times when you are expecting different water consumption results than what the App reports. This article will help you troubleshoot why this occurs.

Customers May See:

The App shows water flow when there isn't any. They may be constant GPM spikes or data in the usage graphs when there is no water running.

Users may also see that there is a large discrepancy between their Flo's water reports and their utility's water bill.

.Troubleshooting

Potential Cause	Description	Solution
Loose Toilet Flapper	Running Toilets caused by loose toilet flappers are the most common cause of consumption discrepancies. A loose flapper causes water to leak between the toilet tank and toilet bowl and subsequently down the drain. This water consumption will often look uneven as the flapper may let more or less water through at different times. It may even stop running completely for some time. The Flo is sensitive enough to catch this water flow below an audible level and since the water is going down the toilet and not leaking out, it can only be found by isolating the toilet(s).	If the flow rate is constant then start closing the toilet valves while monitoring the app's flow rate. If the flow stops after a specific toilet (or any other fixture) is closed then that is the culprit.
Back Flow	Turbulence or "back flow"; among the most frequent causes of consumption discrepancies. If the home's water supply has uneven pressure, then there may be small spikes of water flow being picked up. If you rule out any real drips or leaks in the system, this will point to turbulence, a phenomenon where water "bounces" in the home's plumbing at very small flow rates often below 0.3 GPM. Unlike a typical water meter that the city might use, the Flo's flow sensor (turbine) is not able to differentiate between water moving backwards or forwards. The back and forth movement of water (or "bounce") is picked up by the Flo as a constant jump in flow rate.	To verify that the plumbing has turbulence, close the Flo valve. Check to see if the pressure in the system starts to fall. Falling pressure will indicate an actual leak. However, if the spikes in flow rate stop AND there is no pressure loss then the issue is turbulence. Contact us if you need assistance corroborating back flow.

Potential Cause

Description

Solution

Loose Toilet Flapper

Running Toilets caused by loose toilet flappers are the most common cause of consumption discrepancies. A loose flapper causes water to leak between the toilet tank and toilet bowl and subsequently down the drain.

This water consumption will often look uneven as the flapper may let more or less water through at different times. It may even stop running completely for some time. The Flo is sensitive enough to catch this water flow below an audible level and since the water is going down the toilet and not leaking out, it can only be found by isolating the toilet(s).

If the flow rate is constant then start closing the toilet valves while monitoring the app's flow rate.

If the flow stops after a specific toilet (or any other fixture) is closed then that is the culprit.

Back Flow

Turbulence or "back flow"; among the most frequent causes of consumption discrepancies. If the home's water supply has uneven pressure, then there may be small spikes of water flow being picked up.

If you rule out any real drips or leaks in the system, this will point to turbulence, a phenomenon where water "bounces" in the home's plumbing at very small flow rates often below 0.3 GPM.

Unlike a typical water meter that the city might use, the Flo's flow sensor (turbine) is not able to differentiate between water moving backwards or forwards. The back and forth movement of water (or "bounce") is picked up by the Flo as a constant jump in flow rate.

To verify that the plumbing has turbulence, close the Flo valve.

Check to see if the pressure in the system starts to fall.

Falling pressure will indicate an actual leak. However, if the spikes in flow rate stop AND there is no pressure loss then the issue is turbulence.

The App is showing LESS water than expected or none at all

See the article Low Water Pressure.