Solar-aware charging
Use available production while preserving a house buffer and treating stale solar data as zero.
How it works
GlintEV decides how fast your EV should charge.
It reads fresh energy and charging data, applies the rules you set, then sends a charging request to the car or charger.
The simple version
The website stores your rules. The controller runs them at home.
Many inverters and chargers are only reachable on your home network. That is why GlintEV uses a local controller on a supported Mac, Windows, Android, or other always-on device. The website is where you configure the site and review history.
GlintEV has four jobs
- ReadGet fresh solar, charger, and vehicle status.
- DecideCalculate the target amps from your house buffer and limits.
- ControlTell the vehicle, EVSE, or OCPP charger what to do.
- ExplainShow requested amps, measured amps, and recent decisions.
Read
Decide
Control
Explain
Control paths
GlintEV can control charging from the car side or the charger side.
Some vehicles accept charging commands well. Some chargers are better control points. GlintEV keeps both paths available so the setup can match the hardware.
Charger control
Control compatible EVSEs directly when the charger can enforce the current limit better than the car.
Vehicle control
Read battery, limit, and charging status from supported vehicles and request charge changes when available.
Dashboard history
Track commands, measured amps, estimated solar-to-car energy, controller health, and recent errors.
Control loop
Every controller cycle follows the same sequence.
Read devices
The controller polls solar sources, chargers, and vehicle state from local and provider APIs.
Check freshness
If required data is stale, disconnected, or missing, the policy falls back to a safer target.
Calculate target
GlintEV applies house buffer, voltage, amp step, limits, battery state, and control mode.
Command and record
The controller sends the request, checks measured state where possible, and uploads one event.
Next
Choose the control path that fits the hardware.
Most sites start with solar-aware charging, EVSE control, or vehicle API control. The platform supports mixing those approaches when the hardware calls for it.