Protocol deep dives, integration guides, and lessons from the field.
Without a shared abstraction layer, every new DER hardware vendor means a new bespoke integration that consumes weeks of engineering time. A unified API schema changes that — one data model for every device type, regardless of manufacturer.
Read more
OCPP 2.0 is more than a version bump — it introduces mandatory TLS security profiles, a hierarchical device model, and a revised transaction lifecycle that breaks code ported directly from 1.6. Here is what changed and where teams get stuck.
Read more
OpenADR's VEN/VTN message model, registration flow, event lifecycle, and telemetry reporting requirements — explained for developers building demand response software from scratch.
Read more
SolarEdge and Enphase use different auth models, different field names for the same measurements, and different rate limit structures. Here is what those differences cost in engineering time and how normalization eliminates the divergence.
Read more
Integration maintenance consumes 30 to 50 percent of engineering capacity at typical DER software companies. This is what that looks like in dollar terms over a three-year product horizon, and what it costs in forgone features.
Read more
IEEE 2030.5 is the protocol for utility-grade solar and storage integration, mandated under various state grid interconnection rules and increasingly required by demand response programs. This is the resource model, the discovery flow, and the certificate requirements explained practically.
Read more
DER control APIs give software real-time command over physical grid-connected hardware. The threat model for those credentials is not like typical web API keys — here is the vault architecture and security boundaries that match the risk profile.
Read more
WebSocket lifecycle management, transaction state durability, smart charging gaps between spec and hardware, and why MeterValues configuration matters more than most teams realize — real lessons from OCPP production integrations.
Read more
Demand response dispatch requires low-latency fan-out to thousands of devices simultaneously. The architecture patterns that work — event-driven pipelines, pre-computed command templates, event-sourced enrollment state — and the failure modes they prevent.
Read more
You cannot iterate against real solar arrays or live demand response programs during development. A well-designed DER sandbox simulates device state machines, injects failure scenarios, and runs throughout the development lifecycle — not just at prototype time.
Read more
The integration trap starts with a rational first decision and compounds into an architectural constraint that costs a year of engineering velocity to escape. Here is how to recognize it before the third integration, and how to get out if you are already in it.
Read more