GlintEV

EVSE / OCPP control

Control the charger when the charger is the better control point.

Some vehicles accept charging commands inconsistently. GlintEV can target compatible EVSEs instead, letting the charger enforce the current limit while the vehicle remains ready to charge.

Charger-first control

For predictable current limiting, the EVSE often has the final word.

GlintEV models chargers as first-class devices. A controller can read vitals from a local EVSE, receive OCPP command queues, and record measured charging so the dashboard shows what was requested and what actually happened.

Charger control path Requested and measured
PolicySolar or schedule decides target amps.
ControllerSends EVSE API or OCPP command.
ChargerLimits pilot current at the wall.
FeedbackUploads measured amps and kW.
Requested
32 A
Measured
31.4 A
AC

Local EVSE APIs

For chargers that expose local status and control, the controller can stay on the LAN and avoid unnecessary server load.

OP

OCPP smart charging

Compatible gateways can deliver charging profiles and command responses for OCPP 1.6 style deployments.

KW

Measured charging

When the EVSE reports current and power, GlintEV can display requested amps, measured amps, and measured kW.

Where EVSE control shines

  • Vehicles that do not expose a reliable current-control API.
  • Sites with more than one charger or a limited electrical panel.
  • Installations where measured charger current is more useful than vehicle-reported status.
  • Commercial or managed chargers that already support OCPP.

Open protocol path

OCPP gives GlintEV a standard way to talk to many chargers.

OCPP is not required for every home, but it gives installers and managed sites a more durable path than one-off charger integrations. GlintEV can use OCPP where it exists and local APIs where they are more practical.

What is OCPP?