Loading Guide

Preparing HPzenAi content

Skip to main content

Water Meters

Troubleshooting

Diagnosing and resolving common HPzenAi water meter issues — readings, connectivity, valve, and communication.

Water Meter Not Showing Readings

Cause: Most commonly caused by reversed RS485 A/B wiring or missing 12V power to the meter.

How to Fix

  • Verify RS485 A and B wires are not swapped — reversed polarity is the single most common cause.
  • Confirm the meter has 12V DC power (check the LED or pulse indicator if present).
  • Check that the RS485 bus address is unique and matches the configuration in the gateway.
  • In the HPzenAi app, go to Gateway → RS485 Scan to manually trigger a device search.
  • Inspect the RS485 cable for damage or loose connections at both the meter and gateway ends.

Water Meter Appears Offline

Cause: The gateway has lost connectivity to the meter or to the cloud, or the meter power supply has failed.

How to Fix

  • Confirm the HPzenAi gateway is powered on and connected to the internet.
  • Verify RS485 cable continuity between the meter and the gateway terminal block.
  • Check that the meter power supply is delivering 12V DC.
  • Open the HPzenAi app, go to Gateway, and check the gateway online status.
  • Restart the gateway from the app: Gateway → Settings → Restart.
  • If the meter was recently moved or reinstalled, re-link it via Gateway → Link Devices.

Reading Not Updating

Cause: Data polling may be interrupted by a communication error, address mismatch, or temporary gateway outage.

How to Fix

  • Check that the RS485 address configured on the meter matches the gateway configuration.
  • Verify the RS485 bus cable is within the maximum length of 1000 m.
  • Confirm no other device on the RS485 bus shares the same address.
  • Check for loose connections at the gateway terminal block.
  • Trigger a manual refresh: open the Water Meter tile in the app and tap Refresh.

Gateway Cannot Detect the Water Meter

Cause: RS485 wiring errors or an incorrect Modbus address prevent the gateway from finding the meter during scan.

How to Fix

  • Double-check wire colour mapping — Yellow to RS485 A (+), Green to RS485 B (−).
  • Confirm the meter has a unique Modbus address (factory default is typically 1).
  • Ensure only one RS485 segment is connected to the gateway during the initial scan.
  • Use a short test cable to isolate whether the issue is with the cable run or the meter itself.
  • Run a fresh RS485 scan from the app to re-detect the meter.

Guided Help Center

Step 1 / 8
9:41
1

Open the HPzenAi app.

Step 1 / 8

Incorrect or Unexpected Readings

Cause: Air in the pipeline, incorrect installation orientation, or upstream turbulence causes measurement errors.

How to Fix

  • Bleed the pipeline to remove trapped air before the meter — air causes erratic or inflated readings.
  • Confirm the flow direction arrow on the meter body matches the actual direction of water flow.
  • Ensure sufficient straight pipe lengths — 10× DN upstream and 5× DN downstream of the meter.
  • Check for partial blockage at the inline strainer or filter installed upstream of the meter.
  • Inspect for downstream leaks that could cause the meter to register higher-than-expected usage.

Zero Reading Despite Water Usage

Cause: The meter is not registering flow due to incorrect orientation, an air lock, or the meter being bypassed.

How to Fix

  • Verify the meter is installed horizontally with the register facing upward.
  • Confirm the flow direction arrow aligns with the actual direction water travels through the pipe.
  • Open a tap downstream to flush air from the pipeline and re-establish steady flow.
  • Confirm the meter isolation valves are fully open and the meter is not bypassed.
  • Inspect for a partial blockage at the meter inlet strainer that may be restricting flow.

Water Leakage Around the Meter

Cause: Leaks typically originate from improper coupling torque, worn or reused gaskets, or damaged pipe threads.

How to Fix

  • Isolate the water supply and inspect all coupling joints, gaskets, and mating surfaces.
  • Replace gaskets — reused gaskets are a common source of leaks after reinstallation.
  • Tighten couplings only until the leak stops — over-tightening cracks the meter body.
  • Do not use PTFE / Teflon tape or thread sealant compound on meter threads.
  • If the meter body itself is leaking, the unit must be replaced — do not attempt to repair internally.

Communication Failure Between Gateway and Meter

Cause: Long cable runs, electrical interference, or shared RS485 address conflicts interrupt data communication.

How to Fix

  • Verify the RS485 cable length does not exceed 1000 m for reliable communication.
  • Route RS485 signal cables separately from mains power cables, inverters, and variable-frequency drives.
  • Confirm each device on the RS485 bus has a unique address — duplicate addresses cause data corruption.
  • Ensure terminal screws are fully tightened at both the gateway and the meter ends.
  • Test with a short direct cable run to isolate whether the issue is the cable, environment, or device.

Meter Linked to Wrong Gateway

Cause: During installation the meter was paired to a different gateway than intended.

How to Fix

  • Open the HPzenAi app and navigate to the gateway the meter is currently linked to.
  • Go to Gateway → Linked Devices and select the water meter.
  • Tap Unlink Device and confirm the action.
  • Navigate to the correct gateway and link the meter again via Link Devices.

Guided Help Center

Step 1 / 9
9:41
1

Open the HPzenAi app.

Step 1 / 9

Device Online but No Consumption Data

Cause: The meter is communicating with the gateway but data is not being logged, usually due to a configuration or polling issue.

How to Fix

  • Confirm the meter register is mechanically advancing when water flows — check the physical display on the meter.
  • In the app, verify the data logging interval is configured: Water Meter → Settings → Polling Interval.
  • Check the cloud dashboard — data may be arriving but hidden by the current date range filter.
  • Confirm the gateway firmware is up to date: Gateway → Settings → Firmware Update.
  • If data logging stopped recently, check whether the gateway experienced an internet outage during that period.