Ask Flux
Help Center
How can we help?
All Categories
Assets
Commissioning locations and charge stations in Mobi.E ecosystem

Commissioning locations and charge stations in Mobi.E ecosystem

Last updated on December 11, 2025

Table of contents

 

Intro

This article provides a step by step into what is required to commission a charger to GreenFlux backend, which belongs to Mobi.E ecosystem.

Detailed step by step

Step A1: Create Location (through EV Portal)

Besides the normal information that should be filled in while creating a location (Location creation), there are certain fields that are mandatory for Mobi.E integration:

  1. You MUST chose a CPO with Mobi.E exclusive hub - your CSM should have created one for you. You can check if a CPO contains Mobi.E exclusive hub by checking its details --> Exclusive hub field must be 'MobiE'
  1. You must create the location with Publish = TRUE, as follows:
  1. Location object as per Mobi.E integration has 3 additional properties that must be filled in:
    1. mobie_voltage_level - can be one of three options:
      1. BTN
      2. BTE
      3. MT
    2. mobie_CPE - MUST be an alphanumeric with all uppercase, containing precisely 20 characters.
  1. mobie_access_type - In order to define this value (which can theoretically be 'Public' or 'Private', the Restricted Access flag must be set to False, as follows:, as we do not support chargers with private access, only Public.

Once you save the location after its creation, the system should automatically proceed with step B1.

Step A2: Verify that Mobi.E Location ID is populated

As per Mobi.E integration each location (and associated charge station, only one) will have an ID which is defined by Mobi.E.

When step B1 was successfully done, then this ID should be populated in the external ID property, as follows:

Step A3.n: Do while ext. ID is empty, --> then update location details

If for some reason the external ID remains empty, then check the diagnostics of the OCPI (tool) connection with Mobi.E to see if they provide a hint on what could be wrong. Or otherwise review the location data and resave it again. Every time you save a location and if step B2.n has not been completed successfully, step B2.n is repeated.

ℹ️

How to check the OCPI tool's diagnostics:

1. On EvPortal letf pane, go to CPO (section) --> Roaming --> and click 'OCPI Subscriptions'

2. Then click on the subscription '[Self-M-Roam] <Operator> CPO - MOBI.E eMSP Hub (OCPI 2.2)'

3. Then click on diagnostics tab

4. Use the available filters to easily locate the diagnostic messages of interest (e.g. if you want to look for a POST Location message, select MODULE 'Locations' and METHOD 'POST'

Note: this tool provides only information from approximately the last 2 weeks, after which data gets erased.

At this stage, once the POST location has been successful, it is possible to set the location Publish = False, if that is intended (e.g. the CPO doesn't want this location displayed in maps yet)

Step A4: Create a charge station

Besides the normal information that should be filled in while creating a charge station Charge Station Creation, there are certain fields that are mandatory for Mobi.E integration:

  1. The charge station external ID must be the same as the Mobi.E location ID. In step A3 before, it is MOBI-LSB-00834
  1. You must select a tariff that is suited for Mobi.E ecosystem. All tariffs that belong to Mobi.E ecosystem must have one of the following prefixes:
      • '<operator>-continente-'
      • '<operator>-madeira-'
      • '<operator>-acores-'
      • below an example with a 0 cost tariff (...)A0,
      • Obviously, chargers in Portugal mainland MUST only be assigned wholesale tariff codes which start with 'EDP-continente', charger in Madeira islands MUST ... and chargers in The Azores (acores) islands MUST ...

Step A5: Verify in OCPI Tool that PUT Location was successful

Check the OCPI Tool (see how in step A3.n above) --> diagnostics --> filter per modules 'Location' method 'PUT'. Confirm that location has been correctly created towards Mobi.E (when that is the case the column Level provides a blue tag displaying 'Info'). If the blue tag displays an error, click on see details to check if there is some hint about the problem.

Step A6: Do While PUT is not successful, then --> update charger (or location) data and resave

If for some reason the PUT Location provides an error, review the charge station (or location) data, fix it and resave it again. Every time you save a charge station, step B4 is repeated.

ℹ️

Once all the above steps are completed, then you are ready to establish the connection between the charge station and GreenFlux backend. You should follow this article: Charge station First connection

 

Further details

The above process depicts how it should be done to create a location through GreenFlux platform. Please note that it is only possible to manually create location using the front-end, i.e. one by one through EV Portal.

Further details GFX technical solution for this Mobi.E extra-OCPI requirement:

  • We added in GFX data model an additional filed in the location object, called 'external ID'
  • Operationally:
    • In the interface with Mobi.E (OCPI 2.2), in all relevant data exchanges, we will pass the external_id in the location ID (e.g. in the put location we will map the external_id in the id field)
    • EDP will be able to see the external_id of the location in EV Portal
    • All systems within GreenFlux domain will keep their modus operandi as per the Location ID = <GUID>. Some examples:
      • Platform API:
        • Get a Location by ID (greenflux.com), the input parameter here being still the GUID
      • CA API:
        • All data provided by charge assist related end-points will be based on the GUID, as it currently is, so for chargers mapped in our back-end, the Location ID for CA end-points will be nl-gfx-<GUID of the location>, whereas for chargers in Mobi.E platform, it will be pt-mob-<Mobi.E Location ID>
 
Did this answer your question?
😞
😐
🤩
Submit a ticket