For: Operators (CPOs) and installers whose energy-managed location does not behave as expected
This article lists the checks for the most common energy management problems in the Hub. Each section covers one problem. Work through the checks in order, starting with the most common. Checks marked Needs Monta cannot be fixed in the Hub.
This article does not explain how energy management works. For fuse limit, buffer, phases, and charge intent order, see How does energy management work in the Hub?
Where do I find these settings in the Hub?
Go to CPO / Network → Energy management and open the Locations tab. Open a location. The header shows an Active or Inactive badge.
A location has four tabs: Location overview, Topology, Details, and Setup.
Setup has seven sections: Location configuration, Nodes, EVSEs, Meters, Solar panels, Charge intents, and Change log.
Details has four sub-tabs: Meter values, Charges, Logs, and EVSE state history. The live node cards on Details appear after you pick a node in Select node or EVSE.
Why is my old load management setup gone, or why does my location show Inactive?
The Hub moved load management groups from the old Hub to energy management as locations. They arrive Inactive. The old group keeps running until you activate the location.
Activating the location switches the old group off. Only one of the two can control the EVSEs at a time.
Activate a moved location before you change anything else. While it is Inactive, the Hub rejects changes to nodes, EVSEs, and meters. The message says the location was imported and must be activated first ("Activate before making changes").
To activate a moved location, follow these steps in order:
Do not change the old load management group, and do not change the nodes, EVSEs, or meters of the location. Activation fails with a "Drift detected…" message when the location no longer matches the old group.
Check that no EVSE of the location is also in another old load balancing group. If one is, remove it from that group first. Open the location's own page, then go to Settings → Load balancing → Open portal. Otherwise activation fails.
Activate the location. Go to Setup → Location configuration → Danger zone → Location active status. Confirm Activate. Activation switches off the old group of the location automatically.
Set the Electricity price area in Setup → Location configuration. Moved locations arrive without one, and Price optimize needs it.
Check the comment of the location. If it says "!! WARNING !! - external meter not imported…", add the external meter again in Setup → Meters.
Check the Phase setup of each EVSE in Setup → EVSEs. The Hub converted it from the settings of the old group.
For the full setup, see How do I set up energy management for a location in the Hub?
Find the location. Go to CPO / Network → Energy management → Locations. You can also open the location's own page and select the Energy management tab.
-
The location is Inactive. This is expected for a moved group.
Check: the header badge or the Status column in the Locations list says Inactive.
Fix: activate the location. See section "Why aren't my EVSEs being controlled?", check 1.
-
Activation fails with a "Drift detected…" message. The location no longer matches the old group, for example, because a meter was added or the group was changed after the move.
Needs Monta: contact Monta to bring the location in line with the old group.
-
Energy management is not in your menu. Your user or account may not have access.
Needs Monta: contact Monta to check your access.
Why is charging slower than expected, stuck at 6 A, or paused?
-
The node's capacity is used up. Charging stays within the fuse limit minus the buffer on every phase, and within the power limit.
Check: On Location overview, the node card turns amber at 80% and red above 100%. It shows the free amps. You can also open Details, pick the node, and look at the Node limits card.
Fix: In Edit node, check that Fuse limit, Buffer, and Power limit match the installation.
-
A power limit schedule is active.
Check: Setup → Nodes, column Power limit schedule.
Note: The card on Location overview compares against the fixed power limit only. It can show free capacity while a schedule limits charging.
Fix: select ⋮ → Power limit schedule.
-
An external limit is active. An external limit of 0 kW stops all charging on the node.
Check: Setup → Nodes, column External limit. It shows "Active limit…" and "Until…".
Fix: select ⋮ → External power limit → Clear limit.
-
The building uses more than usual, or the meter is offline. When the meter stops reporting, the node assumes its Max expected residual instead.
Check: Details → pick the node → the Residual power and External meter cards.
Fix: restore the meter, or adjust Max expected residual in Edit node.
Other EVSEs use the capacity. EVSEs set to Meter only, and EVSEs that are not on the energy location, still count against the node. See the section "Why aren't my EVSEs being controlled?", checks 3 and 4.
-
The EVSE's own settings limit it. The default minimum for AC is 6 A.
With Allow zero current/power on, the EVSE can pause at 0 A when there is no room for the minimum. With it off, the EVSE stays at the minimum.
Max. current or Max. power may also be set too low.
Check: Setup → EVSEs. Allow zero current/power is only visible inside Edit EVSE.
Fix: select Edit EVSE and change the values.
-
The phase setup is wrong. An example is AC Phase 1 on a three-phase EVSE.
Check: Setup → EVSEs, column Phase setup. The table shows codes like AC_123. The dialog shows "AC 1-2-3".
Fix: select Edit EVSE and correct the Phase setup.
-
The charge has a lower priority. When capacity is short, higher-priority charges get power first.
Check: the charge intent card on Location overview shows the priority.
Fix: change the priority of the intent. For a charge that is running now, select Set manual charge intent on the intent card.
-
Price optimize is waiting for cheaper hours. The EVSE gets 0 now. This is expected.
Check: the intent card says Price optimize, and the power schedule of the EVSE shows charging later.
-
The target is reached. If the vehicle does not report its battery level (SoC), the Hub estimates the target from Default battery capacity.
Check: the target and progress on the EVSE card. Default battery capacity is in Setup → Location configuration → Advanced settings.
-
Ramp-up protection holds the charge back. It limits the first part of a charge.
Check: Details → EVSE state history shows "Ramping up". The setting is in Setup → Location configuration.
-
The vehicle limits itself. This is common and expected.
Check: the status in Topology says Suspended (vehicle).
When a vehicle takes less than it is given, energy management lowers the allocation of that EVSE towards what the vehicle uses. It gives the rest to other EVSEs. It raises the allocation again when the vehicle takes more.
The charging station limits itself. Many charging limit questions turn out to be a limit outside Monta. Check the maximum current of the charging station, and any power limit or load management in the manufacturer's app or cloud. Also check any local energy management system on site. Monta cannot charge faster than the charging station allows.
-
A DC EVSE delivers less than the setpoint. The Hub scales DC setpoints by DC charging efficiency (%).
Check: Setup → Location configuration → Advanced settings.
-
A setting has a typo. Support has seen a buffer of 160 A instead of 16 A. Support has also seen a Max expected residual of 0, which leaves no room for charging.
Check: the values in Edit node.
Why can't I add an EVSE to a location?
-
The EVSE has no serial number or OCPP identity. The Add EVSE picker shows "No serial number, so it can't be attached".
Fix: set up OCPP (Open Charge Point Protocol) on the charging station first.
-
The EVSE is already on another energy location. The picker shows "Attached to {location}". An EVSE can be on only one location.
Fix: remove the EVSE from the other location first.
-
The EVSE is not in the account you are searching. The picker starts with the account of the location.
Fix: select Search all accounts to include the operator and its sub-operators.
-
The model does not support load management, or the EVSE is set up as the wrong model.
Needs Monta: contact Monta to check the model and its integration.
EVSEs owned by a Private account can be added like any other. Private here means the account type, not the Private access setting. For the difference, see How does energy management work in the Hub? You must operate them, and the model must support load management.
Why aren't my EVSEs being controlled?
-
The location is Inactive. While a location is inactive, the Hub sends nothing to the EVSEs, so they charge without limits.
Check: the header badge says Inactive, or the Status column in the Locations list does.
Note: an inactive location still shows a plan, such as "alloc X A", a schedule, or "Updated…". This makes it look managed. The Hub never sends that plan to the EVSEs.
Fix: go to Setup → Location configuration → Danger zone → Location active status. Confirm Activate.
-
Activation fails. The message says "Failed to activate location", followed by text such as "EVSE … is on an OCPP load balancing group…". The EVSE is still in load balancing in the old Hub.
Fix: remove the EVSE from the old group, then activate again. The old setting is on the own page of the location: Settings → Load balancing → Open portal.
Needs Monta: if you cannot remove the EVSE from the old group, contact Monta. Locations moved from an old group can also fail with "Drift detected…". Contact Monta in that case too.
-
An EVSE is set to Meter only. It sends meter values, but the Hub never controls it.
Check: Setup → EVSEs, column Load management. The column is hidden by default. Turn it on in the column options. Topology → Data grid also shows it.
Fix: select ⋮ → Edit EVSE and turn off Disable load management.
-
An EVSE at the location is not on the energy location, or has no OCPP connection.
Check: Setup → Location configuration → Linked location. It shows messages such as "EVSEs not attached", "…isn't on the site because it has no OCPP integration", or "…managed by another energy site".
Fix: select Sync, or go to EVSEs → Add EVSE. EVSEs without OCPP need OCPP set up first.
-
The node has no limit. Then there is nothing to balance against.
Check: the node card on Location overview says No limit set.
Fix: go to Setup → Nodes → ⋮ → Edit node. Select Set fuse limit, Set power limit, or both.
-
Energy management is not turned on for the location.
Check: the Energy management tab on the own page of the location says "Energy management not enabled".
Fix: select Enable energy management, then activate the location (check 1).
-
The EVSE does not follow the limits it receives. Possible causes are that it is offline, does not support smart charging, or has a firmware problem.
Check: the live power of the EVSE stays above "alloc X A". Details → Logs, filtered on Error, may show errors.
Needs Monta: contact Monta or the vendor of the charging station.
Why does a node show over 100%, or why does the fuse trip?
-
The percentage is measured against the fuse limit minus the buffer, not the breaker rating. A node can show red while still under the real fuse.
Check: Details → Meter values shows both Fuse limit and Effective limit.
Some load is not controlled. Causes are an inactive location, EVSEs set to Meter only, EVSEs that are not on the energy location, and EVSEs that do not follow limits. See the section "Why aren't my EVSEs being controlled?"
-
The meter is offline, and Max expected residual is not set. The Hub then counts the building load as 0, so charging can exceed the real limit.
Check: the External meter card says "Meter not receiving data". A meter that stopped reporting can keep showing its last values with only a timestamp. Check that time.
Fix: restore the meter. In Edit node, set Max expected residual for current per phase and for power.
The phase setup is wrong. The per-phase numbers (L1, L2, L3) are then wrong. See the section "Why is charging slower than expected, stuck at 6 A, or paused?" and check 7.
-
The grid connection type is wrong. The conversion between A and kW is then off.
Check: Setup → Location configuration → Grid connection type.
-
The meter is on the wrong node, or measures the wrong circuit.
Check: Setup → Meters shows the node path.
Fix: select ⋮ → Move meter.
-
The fuse limit is higher than the real breaker.
Check: Setup → Nodes. Change log shows who changed what and when.
-
Several vehicles start at the same time. Without Ramp-up protection, the first moments of several charges can spike the load.
Fix: turn on Ramp-up protection in Setup → Location configuration. Do this for locations with tight fuses.
The overview card and the chart on Details show different limits. The card uses the fixed power limit only. The chart also follows power limit schedules. Neither shows an external limit.
Why isn't Price optimize working?
-
No Electricity price area is set. Without it, no prices are loaded.
Check: Setup → Location configuration → Electricity price area says "None (load balancing only)". The Energy prices chart on Location overview is also missing.
Fix: pick the area, for example DK1.
-
A price area is set, but the Energy prices chart is still missing. The prices could not be loaded.
Needs Monta: contact Monta.
-
Another charge intent applied.
Check: the charge intent card on Location overview shows the type (Charge now or Price optimize) and the source (Smart charge, RFID, User, Account, Vehicle, EVSE, Location default, Manual override). Setup → Charge intents shows the order: "The first matching source is applied…".
Fix: edit the intent that matched.
-
The driver set a smart charge in the Monta app. It outranks all location settings.
Check: the source shows Smart Charge.
Fix: the driver changes it in the app. You can override a single charge (next check).
-
The intent was changed after the charge started. The intent is chosen once, when the charge starts, so later changes only affect new charges.
Fix: click the intent card → Set manual charge intent. It takes effect immediately. Price optimize needs a Departure time.
The departure time or time zone is wrong. The departure time is in the Timezone of the location (Setup → Location configuration). It means the next time that clock time comes around.
-
The target is too big for the time left, or the node has too little capacity, so the charge has to use more expensive hours as well.
Check: compare the power schedule with the price chart.
The vehicle does not report its battery level (SoC). The energy needed is then estimated from the battery capacity (Default battery capacity, or the capacity of the vehicle).
The location is Inactive. A plan is shown, but nothing is sent to the EVSEs. See the section "Why aren't my EVSEs being controlled?", check 1.
Reading the price chart. "High" and "Low" mean the top and bottom 20% of the prices in the window shown, not fixed price levels.
What should I have ready before I contact Monta?
Monta support asks for these details every time.
The charge session ID(s) that show the problem
The EVSE ID or serial, and a link to the energy location
The main fuse or site limit, and what other loads share it
Whether there is an external meter: which brand, and whether it is online in its own app
Whether the charge shows Suspended (vehicle) or a suspension from the charging station
Whether a limit or load management is also set on the charging station itself, in its manufacturer's app, or by a local energy management system
When should I contact Monta?
Activation fails with "Drift detected…".
An EVSE keeps ignoring its limits.
The Energy prices chart is missing even though a price area is set.
An external meter needs MQTT credentials.