What it connects
One device talks to the equipment already installed at a site. Solar inverters (the units that turn panel power into household power) and batteries often use different interfaces, which are the ways a device shares data and accepts commands. The Energy Router connects through the interfaces that its drivers support. A driver is the software that lets the Energy Router talk to one family of equipment, such as one maker's inverters.
How it works
Follow what happened at your site, from the first reading to the result. Every dispatch carries a record of the command, the acknowledgement, and the outcome.
Read the equipment.
Set the intended action and the limits.
Send the instruction.
Keep the response and the outcome.
Interfaces
The Energy Router connects through Modbus RTU, Modbus TCP, Wi-Fi, Matter, local APIs and local MQTT. Modbus RTU and Modbus TCP are two common ways equipment shares data, over a serial line or a network. An API is a defined way for software to request data or send a command, and MQTT is a lightweight messaging method.
One local connection to each device.
How it compares with other systems
An Energy Router is one layer in a larger system. People often compare it with gateways, building management systems, microgrid controllers and DERMS, which is software that manages many devices at once.
Common questions.
How do we confirm it works at our site?
Start a pilot. We test discovery, telemetry, and control on your sites and review what the equipment did.
What sets the revenue from a program?
Revenue comes from the grid program you join. See What is dispatchable revenue?.
What does the Energy Router do without an internet connection?
It keeps operating on site without an internet connection. New commands from the platform reach it once the connection returns.
What does it cost?
We set pricing with you. Tell us the equipment, market, and deployment scope to start.