Pull circuit-level usage data from an Emporia Vue energy monitor using the unofficial PyEmVue-style API
domain: github.com/magico13/PyEmVue · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Confirm Emporia does not offer an official public API; plan on relying on community-maintained clients such as PyEmVue (Python), emporia-api-go (Go), or emporia-vue-lib (TypeScript)
Authenticate against Emporia's AWS-based backend to obtain an authtoken, which is passed via a header rather than a standard OAuth bearer token
Call device/customer-detail endpoints to enumerate Vue monitors, outlets, and EV chargers on the account
Call usage-data endpoints to pull historical or interval energy usage per monitored circuit
Track the community library's documentation/changelog for breaking changes, since there is no vendor-guaranteed API contract
Known gotchas
There is no officially supported API; Emporia has stated an official API is only a long-term goal, so any integration can break without notice
Authentication flows through AWS rather than a documented OAuth flow, and has required workarounds like the Warrant library in community clients
Because this is reverse-engineered, endpoint behavior (rate limits, field meanings) is only as reliable as the community documentation, which is itself unofficial
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?