




An IoT camera can read a visible water meter dial remotely while the meter stays in service. We use NeoEyes NE101 to capture the register on a schedule and send images over MQTT or MQTTS. Your system can store the photos or run its own OCR. Where a project needs an OCR workflow, NeoMind can turn those images into numerical readings on a suitable local host.
A camera retrofit is useful when the register is visible, the meter needs to stay in place, and each scheduled read can stand on its own. Mount the NE101 with a fixed view of the register so each image shows the same digits at a usable size. For a building operator or utility integrator, the photo preserves the displayed total and gives the team something to check if a reading looks wrong.
A pulse output is worth using when the meter already provides one and the application needs frequent consumption increments. A camera is useful when the team needs the displayed total or a photograph for verification. These approaches depend on different things at the site.
| Retrofit Path | Data You Get | Site Requirement |
|---|---|---|
| Camera-based reading | A dated image of the register. OCR can extract the displayed total. | A clear view and a stable mount. Useful where the installation must leave the meter untouched. |
| Pulse or reed sensor | Consumption increments. A running total requires a starting reading and the meter’s pulse factor. | A compatible pulse output or sensor and permission to connect or attach it. |
Take a test photo from the proposed mounting position with the enclosure in its normal state. Check the full register, glare from its cover, and the legibility of each digit. Use the meter-reading lens guide to match working distance, focus and field of view to the size of the readout.
NeoEyes NE101 — compact form factor designed for tight meter enclosures
Typical deployment scenario: underground water meter pit, battery-powered camera with LTE uplink
Both approaches start with the same capture process. The split happens after the image reaches the broker. Assigning that handoff up front lets the integrator keep an existing OCR system or add recognition on a host while using the same field camera.
Set the interval around billing, reporting or inspection needs. A shorter interval creates more uploads and uses more energy, so size power and connectivity for the same schedule.
Use a stable viewpoint and check that the lens focuses at the actual mounting distance. Keep the full register in the frame and test glare and fill light with the meter enclosure closed as it will be in service.
NE101 reports the image and capture metadata to the configured MQTT or MQTTS broker. Wi-Fi, LTE Cat.1 and Wi-Fi HaLow are connectivity options. The broker is the point where the receiving workflow picks up the image.
Use your own broker when the receiving system can already store photos, route them for review, or run its own recognition. In the NexAscent deployment, our NE101 captures the existing water meter register on a schedule and uploads images over 4G. NexAscent owns the OCR, reading validation and reporting in MeterOCR. Its review screen keeps the source photo next to the reading, so an operator can inspect a result flagged for review. See the NexAscent water meter retrofit case study.
When your team needs an OCR layer, use NeoMind on an NG4500 or another suitable PC or Linux host. NE101 supplies the image and NeoMind runs recognition on the host. The receiving SCADA, BMS or IoT platform gets the processed reading through the configured integration. If the host is on-site and the image path stays on the local network, the workflow can run without a third-party cloud.
We recommend checking images from each representative meter style before evaluating OCR. Use a few captures under real lighting and confirm that the digits remain distinguishable on wet, reflective or worn registers. Then check how the receiving workflow flags readings that an operator needs to review. The NeoMind water meter OCR workflow shows how capture, recognition and reading validation fit together.
A bench prototype can establish that a register is readable. A field pilot adds the work of keeping that view stable, powering repeat captures and delivering each image to the receiving system. Compare the full installation and maintenance effort across representative meter locations before choosing how to build the capture node.
| Dimension | DIY ESP32 Camera Build | NeoEyes NE101 |
|---|---|---|
| Mount and enclosure | Source or design the housing and mount for the installation. | Start with an IP67-rated camera and choose a compatible mount for the position. |
| Capture and reporting | Implement or adapt scheduling, sleep behavior and image delivery. | Configure scheduled capture and MQTT/MQTTS image reporting in the Web UI. |
| Network and power | Qualify the radio, power budget and antenna for the meter location. | Evaluate a Wi-Fi, LTE Cat.1 or Wi-Fi HaLow configuration with the planned capture interval. |
| Project cost | Include enclosure design, assembly, field testing and service time alongside the board cost. | Include the selected camera, mount, network equipment and scheduled service visits. |
We recommend starting an NE101 evaluation on a representative meter before choosing a fleet configuration. The assembled camera lets you test optics, reporting and the installation with the same unit. The open firmware and mounting resources give your team a starting point when the standard setup needs adapting.
Test the link and image quality from the actual mounting position. A metal cabinet or closed pit cover can change both the light on the register and the radio link. Use the same capture settings and image size you plan to use in service.
The NE101 wakes, captures, transmits and returns to sleep between scheduled reads. Budget for the time spent uploading, including retries at weak-signal locations. Use the CamThink battery life calculator for the supported network modes, then check the estimate against the actual signal, temperature and fill-light use.
Start with the built-in fill light and check the image with the cover closed. The NE101 Web UI supports an automatic light threshold and a scheduled lighting window. Adjust the camera angle or light intensity when reflections obscure the digits. The low-light meter reading guide covers fill-light configuration and validation.
At an exposed outdoor meter, evaluate the NE101 with a weather shield. The shield provides added protection from rain and UV exposure and shades the camera window. The enclosure retains its IP67 rating. On LTE Cat.1 and Wi-Fi HaLow versions, the adjustable external antenna can be aimed independently of the camera. For a close-up register, check whether the 60° lens with a 15 cm focus distance fits the available mounting space.
Use Wi-Fi where the installed camera can reach an access point reliably. Evaluate LTE Cat.1 if the site has suitable cellular coverage and no local network. A private Wi-Fi HaLow network needs a compatible gateway and a backhaul path to the broker. Test with the cabinet or pit in its normal state before selecting hardware. See the LTE versus Wi-Fi HaLow guide for underground meters.
The camera captures the display, so the recognition task changes with the type of register. Start by identifying the value you need to recover from the image and the smallest detail that distinguishes one reading from another.
A mechanical water meter with a visible digit window is a practical starting point for OCR. Test partially rolled digits and condensation as well as clear reads. On backlit displays, check for glare and exposure changes at the times the camera will capture.
Digit-window gas meters can follow a similar capture workflow. Pointer dials require a model or calibration that maps position to a reading. On a pressure gauge, for example, the needle tip and scale markings both need to be clear enough for the receiving application to interpret.
Set up the data handoff according to what your platform needs to store. For direct image delivery, the NE101 Quick Start documents standard MQTT/MQTTS reporting. If your platform only accepts HTTPS, use an integration service to receive the MQTT image and forward it to the endpoint. Device-side HTTPS upload would require separate firmware work and validation.
For processed readings, configure the NeoMind integration for your receiving system. OpenAPI, Data Push and Webhook are available integration paths described in the engineering guide. When mapping your records, keep the meter identifier, capture time, value and unit together. Retain an image reference if someone needs to verify or correct the reading. This example shows a downstream record after OCR. The NE101 camera report contains the image and device metadata.
{
"device_id": "ne101-a3f2",
"timestamp": "2026-03-20T08:30:00Z",
"site": "building-b-level2",
"meter_id": "WM-045",
"image_url": "https://your-server/captures/ne101-a3f2-20260320-083000.jpg",
"ocr_value": "01027.8",
"unit": "m3",
"battery_pct": 84
}
Where coverage is intermittent, test a connection loss and recovery during the pilot. NE101 can store images locally using its MicroSD slot. Any automatic backfill to your platform depends on the workflow you configure and validate.
Start with NE101 for scheduled meter images. Add a host when the project needs OCR or centralized processing. NE301 fits projects that need a separate, supported on-camera vision task alongside meter image capture.
Start with a mounting position that reflects the actual installation. Verify the register in a scheduled photo, confirm delivery to the intended receiver, and check a reading against the source image. If the same site has different meter faces or weaker radio coverage, repeat the test at one of those points before ordering for the wider site.
After the first pilot, size the receiving system for the number of meters, the peak upload window and how long you need to retain images. The multi-site meter reading guide covers network and OCR host considerations for larger deployments.