🚀 New features​

Payment Terminals​

New functionality to support payment terminals for chargers has been released. In the first phase of supporting different payment terminals we are bringing support to Siemens terminals supporting California Pricing Requirement protocol. In the future we will be supporting more methods with different terminal types.

🪄 Enhancements​

API​

• New payment terminal endpoints

🚀 New features​

New experience for using DLM​

We have been working hard on making the Dynamic Load Management easier to use in our platform and today we are launching the new DLM experience! Now DLM is more tightly connected to existing site structure and it has a new page for managing it built from the ground up. Enabling DLM for a site is now as easy as setting up the correct earthing system and the max current the fuses can handle and activating it. You can see real time statistics on how much amperage your site is using and how much individual sockets are using current. The support for external metering is also still there, so you can configure more complex setups and still have a good experience with the Dynamic Load Management.

🪄 Enhancements​

eMabler UI & API​

• We are preparing to launch a new way of managing PDF invoicing on our platform, so we are releasing some preparations for that. More information on this will be released later.

🐛 Bug fixes​

eMabler UI​

• Transaction details are now shown correctly
• Activating Utility Cloud integrations can now be done through the UI
• Other small bug fixes

API​

• Several bug fixes

🚀 New features​

Express with white-label support​

We are proud to release the new version of our ad hoc payment application, Express! New version of Express provides white label support, which allows modifying the look-and-feel (company logo and information) of the application to support your branding. You can update the branding settings under "Customer Details" page. Express can easily be taken into use by updating charger specific Express settings on the Charger page. Just provide the URL ending for the charger and setup your pricing scheme for the Express and you are ready to go!

We are preparing to launch a new version of Express, which allows white labeling the user interface to match your brand! To support this, we have released new settings in eMabler UI.

🚀 New features​

Express look-and-feel settings​

You can update look-and-feel of Express by updating "Branding details" under Customer details. These settings will be carried over to the new version of Express we will be launching shortly!

🪄 Enhancements​

eMabler UI​

• Express look-and-feel settings page under Customer details
• New field for socket details: "Name". Sockets can now be given names, which can be utilized in the new version of Express or in other ways through our APIs.

API​

• Get and update endpoints for chargers updated to support new "Name" field for socket

🚀 New features​

UtilityCloud integration​

eMabler platform now supports integrations with UtilityCloud! You can start syncing transaction data on driver level with this integration. Creating UtilityCloud integration happens from the same page as creating OCPI integrations.

Spot price support for tariffs​

Tariffs now support a new price element type: ENERGY_SPOT. With ENERGY_SPOT you can calculate the price for the charging session based on the spot prices in 15 minute segments.With ENERGY_SPOT the price of the energy is with the current spot price every 15 minutes. With the new price element type creating dynamic pricing is easier than ever!

🪄 Enhancements​

eMabler UI​

• New integration type: UtilityCloud
• New tariff price element type: ENERGY_SPOT
• New charging sessions details information, prices can be now seen in 15 minute intervals from the entire session
• Tariffs can now be deleted

API​

• New API endpoint to get transaction timeseries information /statistics/transaction/{transactionId}/timeseries
• New API endpoint to delete tariff /tariff/{tariffId}

🐛 Bug fixes​

eMabler UI​

• Prevent accidental duplicate integration creation
• Minor bug fixes

🐛 Bug fixes​

DLM​

• Minor bug and performance fixes

🪄 Enhancements​

eMabler UI​

• New SOCKET_COUNT tariff type, which allows creating tariffs that are based on the number of sockets.

Happy beginning of 2024 from all of us at eMabler! We have been working hard during the turn of the year to bring new quality of life enhancements to our platform and fix many bugs. The following features and fixes have been released for you to enjoy.

🪄 Enhancements​

eMabler UI​

• Add Excel export functionality for tables with export enabled
• Possibility to add tariff to site for CPO to invoice the site owner
• Performance enhancements for Operators list
• Site navigation uses URL to decide which site to show, so sites can more easily be shared with links
• Add option to change time format in Charging Statistics and CDRs
• Show charger sockets, events and configs even if there are no sockets available to help in troubleshooting

API​

• Added country code validations to site location update
• GetOperators API performance improvements
• Possibility to add tariff to site for CPO to invoice the site owner
• Updated API descriptions

🐛 Bug fixes​

• Charger configuration refresh button actually refreshes the configurations
• Make the aggregated sum values of Charging Statistics stick to the bottom of the table
• Fix tariff price element chart to support negative values and multiple of the same type of price element
• Allow navigation to integrations without a name
• Fix charging statistics and CDRs "Show last" filter not updating the time range correctly
• Fix the CDR translations
• Fix time format on Tariffs list
• Unrealistics transaction consumptions are excluded in dashboard
• Usability fixes for Charging Statistics and CDRs pages
• Usability fixes for Dashboard

API​

• If integration name is missing when creating a new one, default name is given
• Added country code validations to site location update
• When changing the home group of the charger the DLM and OCPI connection changes are handled properly
• Fix for removing empty locations from integrations
• Fix EvseId validation

A problem in our cloud environment regarding resourcing was causing problems accessing the eMabler UI and other eMabler services.

We investigated the root cause and were able to mitigate the problem. We will continue monitoring if the problem occurs again.

There was a problem with message handling inside Azure Platform and we managed to mitigate it. This problem might have caused problems with starting charging sessions this morning.

We will continue monitoring the situation closely and investigate the root cause and keep you updated on that!