Supported devices

Built for mixed home energy hardware.

GlintEV is designed to support solar inverters, batteries, smart chargers, OCPP EVSEs, and vehicle APIs through a consistent site model.

Device categories

Support grows by device type, not by one-off dashboards.

Each integration should answer a simple question: can GlintEV read useful state, control charging safely, or both?

Site device model Read, control, measure
EnergySolar and batteriesProduction, site power, storage state, freshness checks.
EVSEChargersLocal vitals, current limits, OCPP profiles, measured kW.
VehicleCars and APIsBattery, limit, connected state, provider command result.
AgentControllerRuns near LAN devices and uploads one event per cycle.
FroniusLocal inverter readings for PV watts using LAN APIs where available.
EnphasePlanned energy-system support for solar, battery, and site readings.
SolarEdgePlanned inverter and site production support.
Tesla EnergyPlanned support for Powerwall and energy product state where APIs allow it.
RivianVehicle state and charging commands through supported account sessions.
Tesla vehiclesPlanned Fleet API support after app registration and OAuth approval.
Tesla Wall ConnectorLocal EVSE status and measured charging where the device exposes it.
OCPP EVSEsCommand queues and smart charging profiles for compatible OCPP gateways.

Integration levels

  • Read onlyGlintEV can display status and use readings in policy, but cannot command the device.
  • Control capableGlintEV can request a charging target, pause, resume, or OCPP profile.
  • Measured feedbackGlintEV can compare requested current against measured current or power.

Compatibility note

Exact support depends on firmware, API access, and network reachability.

Many useful devices live only on the home LAN. That is why GlintEV uses a local controller instead of asking the server to reach private IP addresses.