Meter and source compatibility
Different meters need different connection routes. Tell us the make, model and how you currently get the readings. We’ll check the fit before you buy hardware or agree to setup.
An existing vendor connector brings supported Riecktron readings into the workspace.
We still check account access, available meters, units and reading history for your site. An installed connector does not guarantee that every account or model is compatible.
An MQTT integration is implemented, but live MQTT intake is not enabled on the current service. Connecting a device needs a managed setup and validation first.
A device labelled “MQTT” is not automatically compatible. Its topic, payload, units and timestamps must match, and broker access must be configured.
Have a CSV export, manual readings or another vendor’s portal? We can assess a sample format and an operator-assisted reporting route.
There is no general self-service CSV importer or automatic connector for every vendor. Any extra integration work needs a separate agreement.
Start with a description. Send credentials and private records only through the private route agreed for your workspace.
GridEvidence reads bills and prepaid receipts with OCR, then helps a person review the facts against the original.
A purchased prepaid unit is not a measured consumption reading. Document facts stay separate from device telemetry; automatic transfer between these products is not part of the current workflow.
See the report you could start with →Only after its connection has been checked. The current integration uses a registered device, a device-specific publish topic and credentials. It recognizes electricity values such as energy, power, voltage and current. A gateway may need to translate the manufacturer’s message into the expected format.
Before relying on a reading, we check its source, units, time, meter mapping and whether the energy value is cumulative or interval-based. We do not advertise untested meter models as supported.
Check my meter setup