Vehicle API control
Vehicle-aware charging for supported EVs.
For supported providers, GlintEV can read battery state, charging status, charge limits, and request charging changes through the vehicle account.
Vehicle intelligence
Charging control works better when GlintEV knows what the vehicle is doing.
Vehicle APIs can reveal whether a car is connected, charging, stopped, near its limit, or refusing a command. GlintEV records that state with every control cycle so a user can see whether the command path is working.
When vehicle APIs are limited, GlintEV can move the control target to the EVSE while still using vehicle state for visibility where possible.
Vehicle-aware command
Provider session active
81% battery / 85% limit
Connected, below limit, ready for a charging request.
Requested18 AVehicle or EVSE target
Command resultAcceptedRecorded in event history
When the vehicle API is limitedGlintEV can use vehicle state for visibility and move active control to the charger.
Design principle
Vehicles are separate from provider accounts, chargers, and sites.
That matters when a household adds a second EV, changes a charger, or mixes vehicle brands. GlintEV keeps the model clean so the dashboard can grow with the home.
1 userCan belong to one or more sites.
1 siteCan have energy sources, chargers, and vehicles.
Many vehiclesEach vehicle can point to a provider account.
Many chargersEach charger can be measured or controlled independently.