Skip to main content

Another app is controlling your car: why smart charging looks broken

If a second app or an in-car timer can also start and stop charging, VOOL's schedule appears to be ignored. How to spot it and how to test.

J
Written by Juhan Harm

If charging starts and stops at times you did not ask for, or your car sits connected without taking power while VOOL says it is offering current, the most common cause is not a fault in VOOL. It is that something else is also controlling the car.

Why two controllers cause this

A charging session is a negotiation between the charger and the vehicle. If a second system is issuing its own start and stop commands to the same vehicle, the two decisions collide: one asks the car to charge, the other asks it to stop, and the result looks exactly like a schedule being ignored.

The usual candidates:

  • Another energy-optimisation app linked to your car — Gridio and similar services can start and stop charging on their own price logic.

  • A charging schedule set inside the car itself. Most EVs have their own departure time or charge timer, and the car will honour its own timer regardless of what the charger offers.

  • A charge limit set in the car — if the car is already at its own target state of charge, it will decline power.

How to test it in one session

  1. Check whether your car is linked to any other app that can control charging, and turn that control off.

  2. Check the car's own charging schedule and departure timer, and clear them.

  3. Check the car's charge limit — if it is set to 80% and the battery is at 80%, nothing will happen.

  4. Run one charging session with VOOL as the only controller and see whether it behaves as expected.

If that session works, you have found it. Pick one system to manage charging and let the other observe.

Which one should be in charge?

If your charger is a VOOL charger, let VOOL control it. VOOL sets the charging current at the charger, which works for every vehicle — including models where remote start and stop commands are unreliable or unsupported. Controlling the car directly through a vehicle API depends on what each manufacturer allows, and is the less predictable of the two.

If it still misbehaves

Write to us at [email protected] with the charger serial number, which charging mode you selected, when the unexpected session happened, and confirmation that no other app or in-car timer is active. That last line saves a day of back-and-forth.

Did this answer your question?