Stale-data handling
Solar readings older than the policy window can be treated as zero instead of driving new charging.
Safety & reliability
Charging control should be conservative, visible, and recoverable.
GlintEV is software that requests charging behavior. The vehicle, EVSE, electrical installation, and manufacturer safety systems remain the final safeguards.
Operating principles
Do less when data is stale. Show more when something is unclear.
Home energy automation should not pretend every device is always reachable or every third-party API will behave perfectly. GlintEV records failures and uses fallback behavior rather than hiding uncertainty.
Control checks before action
Conservative by default
Is the controller on time?Late or offline agents are shown clearly to observers.
Is the solar reading fresh?Stale data can be treated as zero before charging increases.
Is the target inside policy?Min amps, max amps, voltage, and step are applied before command.
Did the device respond?Accepted commands, provider errors, and measured values are recorded.
Dry-run testing
Test decisions and event recording before allowing live charging commands.
Clear event history
See command requests, measured values, provider errors, and controller health in one place.
What GlintEV does not replace
- Licensed electrical design, installation, or inspection.
- Vehicle, EVSE, breaker, panel, and wiring safety systems.
- Manufacturer requirements, utility requirements, or local electrical code.
- User responsibility to monitor early integrations before relying on them unattended.
Transparency
If a command is accepted but charging behaves differently, GlintEV should say so.
That is why the dashboard displays requested amps, measured amps where available, and recent controller decisions. Visibility is part of safety.
Service agreement