Faster integration
Implement one documented adapter boundary instead of coupling every product screen to the device SDK.
Hardware ecosystem
WaterPesa for meter OEMs & AMI vendors
A device-neutral adapter contract that helps meters participate in a broader water-accountability platform without forcing the utility into one permanent software stack.
AdaptersLoRaWANNB-IoTInteroperability
Answer first
What this means in practice
WaterPesa answer
WaterPesa integrates meters through adapter contracts for payload decoding, normalization, status, sequence validation and declared capabilities. Application screens read the canonical model rather than an OEM-specific package.
Outcomes
Why this matters
Clear capability contract
Declare what the device supports: volume, flow, tamper, battery, valve, pressure, firmware and more.
Customer data portability
Preserve raw payload and canonical IDs so meter replacement does not erase historical truth.
Capabilities
What the workflow includes
Raw + normalized storage
Keep append-only raw payload separate from decoder-versioned normalized readings.
Capability registry
Feature-gate commands and UI based on real device capabilities.
Command audit
Log safe command creation and acknowledgements with permissions and correlation IDs.
Compatibility testing
Use fixtures and contract tests before certifying an adapter for production.
“For every cubic metre entering the system: where did it go, what happened commercially, what action was taken, and what measurable result followed?”WaterPesa product invariant · derived from the connected Notion product specification
FAQ
Questions this page should answer
Does WaterPesa manufacture meters?
No. The strategy is to integrate compatible devices and preserve a long-lived data model above replaceable hardware.
Can OEM-specific data still be retained?
Yes. Raw payload and external references can be preserved while WaterPesa exposes normalized fields to the rest of the application.
Can an OEM lock WaterPesa to one protocol?
The product design deliberately keeps protocol and decoder logic behind adapter boundaries to reduce that dependency.
Keep exploring