Upload third-party meter readings into a utility's IEEE 2030.5 server using MirrorUsagePoint resources
domain: sunspec.org · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
POST a MirrorUsagePoint resource describing the meter and reading type to the utility server's mirror endpoint
Create a MirrorMeterReading tied to that MirrorUsagePoint
Push interval readings via MirrorReadingSet/IntervalBlock objects on the schedule the utility server expects
Check the server's response for accepted versus rejected reading submissions
Register the mirror relationship in the end device's FunctionSetAssignmentsList
Known gotchas
Metering mirroring is a one-way telemetry upload (device pushes readings to the server) and is entirely separate from the DER and DRLC control function sets — implementing DER control does not give you metering upload for free
Reading type fields (uom, powerOfTenMultiplier) must match exactly what the utility server expects, or readings are silently rejected without a clear error
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?