A water-monitoring dashboard is useful when its readings are interpreted correctly. But what should a facility team do when a number looks wrong, one tank stops updating or several towers suddenly show no fresh data?
The first task is to distinguish a water-system condition from a measurement or communication condition. A tank may genuinely be rising or falling. Alternatively, a reading may be stale, the sensor may need inspection or a communication path may have stopped delivering data. Treating these situations as interchangeable can send the team in the wrong direction.
This guide offers a structured way to turn unexpected readings into a focused investigation, using timestamps, tank patterns, topology and independent checks to narrow the problem.
Start with the reading timestamp
Before interpreting an unexpected level, check when it was measured or last received. A displayed value from an earlier period is a historical observation, not confirmation of the tank's present condition.
TownEve can alert the responsible team when its software stops receiving input for a configured period. That telemetry-freshness condition is separate from a low-level or high-level water alert.
If a current physical level is operationally important, use the property's approved independent verification procedure. Do not wait for a communication problem to be resolved before carrying out a necessary safe site check.
Check whether the issue affects one tank or several
The pattern of affected readings helps organize the investigation.
If one sensor's readings appear inconsistent while nearby monitored tanks continue reporting, investigate that tank's measurement conditions and local connections first. If readings from several tanks associated with one tower become stale, investigate the tower's shared equipment and communication path. If many towers stop updating together, investigate shared components such as the society-level master, its power and its internet connection.
These are starting points, not confirmed diagnoses. Multiple faults can coexist, and a common symptom can have more than one cause. Preserve the affected tank IDs, last-reading timestamps and alert history before changing settings or restarting equipment.
TownEve's current architecture uses tank sensors connected through tower-level slave modules, RF communication to one society-level master and an internet path from the master to the application backend. Knowing the installed topology helps the technician decide which layer to inspect.
When a level suddenly jumps
An abrupt displayed change can be real, particularly when water is being transferred. It can also warrant checking the measurement setup.
Compare the reading with the recent historical trend, other relevant tanks and any independently observed operating event. Confirm that the tank identity is correct and that the reading is fresh. For a structured interpretation method, see how to read a water-tank level graph.
If the change does not fit the site's observations, arrange a qualified inspection of the sensor's mounting and measurement environment. The appropriate checks depend on the sensor specification and the tank installation. Do not assume that a sudden change proves either a water-system failure or a defective sensor.
A top-mounted ultrasonic sensor measures distance to the water surface. Its reported level depends on the configured reference and the suitability of the measurement path. Changes to mounting or configuration can affect the interpretation of the distance reading.
When a level appears stuck
A nearly constant level is not automatically a fault. A tank may be stable because inflow and outflow are approximately balanced, because little water is moving or because the operating pattern has changed.
First verify that new readings are actually arriving. A fresh series of similar measurements is different from an old value that has stopped updating.
Next compare the observation with the tank's expected use and any safe independent check. If the reported level remains inconsistent with verified physical conditions, ask the technical team to inspect the sensor, mounting reference and local measurement path.
Do not infer zero consumption from a flat tank-level trend. Simultaneous inflow and outflow can keep stored volume approximately unchanged while water continues to move.
When estimated litres look wrong
A plausible water-depth reading can still produce an inaccurate estimated volume if the tank geometry is configured incorrectly.
For a regular rectangular tank, stored volume depends on internal length, width and measured water depth. A vertical cylindrical tank uses its circular cross-section and water depth. Irregular tanks may require a more detailed level-to-volume relationship.
Check the recorded internal dimensions, zero reference, maximum operating level and whether the model matches the physical tank. A configuration error can affect the estimated litres without necessarily indicating a sensor failure.
Estimated stored volume is also not the same as measured consumption. When inflow and outflow occur together, the net change in stored water cannot separately identify both flows.
When several towers stop reporting
In TownEve's multi-tower design, a shared interruption may affect the route from the society-level master to the backend. The technician should inspect the actual installation's approved power and connectivity checks.
A loss of internet connectivity is one possible cause. It is not the only one. RF communication, master equipment, power or another issue may also interrupt telemetry.
If a current tank level is needed during the interruption, follow the site's independent verification process. TownEve hardware can retain up to 150 readings locally and upload retained readings after connectivity returns; the reporting interval determines the time window represented by that buffer. A full buffer represents up to approximately 75 minutes at the fixed cadence, provided the hardware remains powered and all 150 entries are retained.
When one tower stops reporting
If readings from a single tower become stale while other towers remain current, the facility team can focus its initial investigation on the affected tower's local power, slave module, sensor connections and RF path to the master.
Actual RF performance depends on equipment placement and site conditions. A technician may need to inspect the installed communication path and any site-specific signal-boosting arrangement.
Do not reposition powered equipment or modify electrical wiring without following the property's approved procedure and using qualified personnel where required.
When a level alert seems unexpected
An alert can be technically consistent with its configured threshold even if the recipient did not expect it. Review the tank identity, threshold, reading time and recent trend.
A low-level alert means the configured monitored condition was reached. It does not independently prove a pump failure or predict exactly when a resident will lose supply. A high-level alert does not by itself prove physical overflow.
If the alert repeatedly triggers during normal operation, the facility team should review the threshold against the tank's role and observed cycle. Avoid simply disabling alerts to reduce email volume without assessing the underlying operating risk.
Separate diagnosis from corrective action
Monitoring data helps frame questions. It does not authorize every corrective action.
For a water-supply issue, qualified personnel should follow the property's approved mechanical and electrical procedures. For a monitoring issue, the responsible technical team should investigate the sensor, power and communication path. Keep the two workstreams distinct in the incident record.
Tank-level monitoring helps narrow the investigation, while direct pump-state monitoring and remote pump operation are being developed as separate layers for equipment-specific context and control.
Record what was verified
A useful troubleshooting record contains the tank identifier, observation time, last fresh reading, affected equipment scope, independent checks, action taken and result.
Separate observations from conclusions. “Three tower feeds stopped updating at 14:10” is an observation. “The internet failed” is a diagnosis that should be recorded only after the team verifies it.
This discipline makes recurring issues easier to review and prevents an assumption made during one incident from becoming an untested explanation for the next.
Build a simple escalation path
The facility team should know whom to contact for a physical water-system problem, whom to contact for monitoring equipment and whom to contact for connectivity. These may be different people.
Maintain the tank inventory, installed system diagram and support details as part of the handover record. When staff or committee members change, confirm that alert recipients and escalation contacts remain current.
The objective is not to make every resident or committee member a technician. It is to ensure that an abnormal reading reaches the person able to investigate it safely.
Where TownEve fits
TownEve provides contactless monitoring for suitable overhead and underground tanks, historical readings, configured email alerts and telemetry-freshness monitoring. Its tower-to-master RF architecture allows multiple tank locations to be viewed through the application.
A deployment-specific troubleshooting procedure should reflect the actual equipment locations, communication paths, support scope and operating responsibilities. The dashboard supplies evidence; the facility and technical teams verify the cause.
FAQ
Why is my water-tank reading not updating?
Possible causes include sensor, power, local communication, RF, master or internet issues. Check the last reading time and investigate the actual installation path rather than assuming one cause.
Does a missing reading mean the tank is empty?
No. Missing telemetry is a monitoring-data condition. The last displayed level does not establish the current physical level.
Why does the tank show the same level for a long time?
The level may genuinely be stable, or the data may be stale. Check the timestamp first, then compare with the tank's expected operation and independent observations.
Can a level chart prove that a pump has failed?
No. Tank-level trends can prompt investigation but cannot independently establish the pump's electrical state or root cause.
Why might the litres estimate disagree with the physical tank?
The configured geometry, measurement reference or tank shape may need review. Estimated litres depend on both the level measurement and the tank model.
Will data automatically reappear after an internet outage?
TownEve hardware can retain up to 150 readings during a connectivity interruption and upload retained readings after connectivity returns. The fixed 30-second hardware reporting cadence determines how much time the retained data represents.
Who should investigate a suspected sensor problem?
Follow the site's agreed support and maintenance process. Qualified personnel should handle any electrical or physical intervention requiring their expertise.