GlintEV

Controller setup

One always-on controller keeps the site connected.

The GlintEV controller runs near the hardware so it can reach local inverters, EVSEs, and vehicle sessions while the website remains light.

Recommended setup

Use a device that can stay powered, stay online, and reach the home LAN.

A Mac, Windows PC, Android device, or small local computer can run the controller. iPhone, iPad, and Apple Watch are best as observers because mobile operating systems can suspend background work.

Local-first controller loop One event upload
DashboardStores site config, policy, and device inventory.
ControllerDownloads config and runs the local cycle.
Home LANReads inverter, EVSE, and vehicle state.
EventUploads readings, command, errors, and measurements.
Why local?The cloud cannot reach private LAN addresses, and the controller keeps polling burden off the server.
1

Create account

Register, choose a plan, and open the dashboard.

2

Add devices

Add energy sources, chargers, vehicles, and provider credentials.

3

Set controller

Mark the supported device as the controller in the app or dashboard.

4

Watch events

Confirm solar readings, charging requests, and measured status in the dashboard.

Controller responsibilities

  • Download the latest site configuration after login and after changes.
  • Poll local solar and EVSE devices on the configured interval.
  • Authenticate to supported vehicle providers when required.
  • Calculate and send the charging command.
  • Upload one event containing the readings, command, and measured result.

Server burden

The server should coordinate, not poll every home LAN.

Keeping the control loop local reduces server load and avoids impossible private-IP access from the cloud. That is the architecture GlintEV is built around.