This Q&A provides an overview of key topics related to cloud balancing.
What is cloud balancing?
Cloud balancing enables dynamic load balancing across multiple circuits by moving the balancing logic from local hardware (Wi-Fi and Equalizer) to the cloud. This significantly increases installation flexibility, reduces infrastructure costs, and supports large-scale deployments in multi-dwelling units (MDUs), commercial sites, and workplace charging setups.
With cloud balancing, balancing can be performed across chargers connected via different Wi-Fi networks and/or 4G, with or without an Equalizer. Cloud balancing supports two configurations: one with an Equalizer and one without.
In installations without an Equalizer, all master chargers share a fixed e-mobility capacity. To enable dynamic load balancing that also accounts for unknown building load, an Equalizer is required.
What problem does cloud balancing solve?
Cloud balancing removes the requirement for all chargers to be on the same, local Wi-Fi-network, allowing chargers on 4G or different Wi-Fi networks to work together, reducing installation complexity and cost in large commercial and MDU sites.
Does cloud balancing replace existing functionality?
No. Cloud balancing builds on existing load balancing functionality and provides the same core features, with increased flexibility. Especially useful where Wi-Fi infrastructure is limited or costly.
What’s the impact on installation time and cost?
Cloud balancing can reduce installation time and cost by removing the need for local Wi-Fi between master chargers. Wi-Fi may still be required for general connectivity, especially in underground parking garages.
Is new hardware needed?
No. Cloud balancing works with existing Easee commercial chargers. No additional hardware is required. An Equalizer is still required if load balancing against unknown load is needed (main fuse protection).
What types of installations benefit most from cloud balancing?
Cloud balancing is especially valuable for:
- MDU (multi-dwelling unit) installations
- Commercial sites with multiple circuits
- Sites where Wi-Fi is limited, expensive, or difficult to extend
- Outdoor installations
What’s required for cloud balancing to work?
- Each master charger must have a stable cloud connection (Wi-Fi or 4G)
- Activated during installation via the Installer App
- Can also be enabled later via Easee Control
Is there any cost for using cloud balancing?
No. Cloud balancing is included in the standard product offering for large sites.
Will all installations be able to activate cloud balancing?
No, cloud balancing is only available for commercial and MDU installations.
Will local Wi-Fi load balancing be phased out?
No. Local load balancing remains valuable, as it continues to function without cloud connectivity.
Does cloud balancing work between the master and Secondary units?
No. Cloud balancing manages master-to-master load balancing across circuits. Communication between master and Secondary units still relies on Easee Link for local communication.
Is cloud balancing secure and reliable?
Yes. All communication is encrypted and continuously monitored. Cloud balancing is built on Easee’s cloud infrastructure and meets high safety and reliability requirements.
Will cloud balancing work with third-party load management products?
No.
Is cloud balancing possible without an Equalizer?
Yes.
Example:
- Main fuse: 100 A
- Circuit A fuse: 80 A
- Circuit B fuse: 80 A
With cloud balancing and no Equalizer, the sum of circuit fuse values can exceed the main fuse as long as total site load is managed.
What happens if customers choose Direct OCPP?
Direct OCPP is not supported with cloud balancing.
What is the expected response time?
Typical response time after a vehicle connects:
- Minimum: approximately 2 seconds.
- Maximum: approximately 15 seconds.
Can cloud balancing be enabled per circuit?
No. Cloud balancing is activated at site level only..
What happens if chargers disconnect and reconnect to the cloud?
Offline masters use fallback limits. When reconnecting, updated limits are applied automatically.