DLM now shows properly the used amperage for multilevel DLM setups. Now parent sites show the used amperage of the subsites to make it easier to understand how the current is flowing on the whole site structure.
New tariff engine improvement has been released which will streamline tariff handling between OCPI and regular charging sessions and will add support for all price elements for both charging session types. Invoicing related price elements will still be handled separately. This improvement will change the way spot prices are handled internally and from this release forward the sites that have spot price tariff connected will need to have timezone set under "Location". No other changes are required.
Please add the "timezone" information to sites that have a spot price tariff connected to them. Without it, the spot prices will stop working after this release.
If you need help with this, please contact our customer support and we will happily help you with the process!
We have launched a new version of our OCPP handler in production.
It has been taken in use for OCPP 2.0.1 chargers at the endpoint wss://ocpp2.emabler.io/ocpp/.
This also introduces the capability to see raw OCPP messages on eMabler UI.
We will be migrating OCPP 1.6 chargers to this new OCPP handler soon as well, so stay tuned!
We at eMabler want to wish all of you Happy Holidays and Merry Christmas! Due to the holiday season we will be introducing a brief production deployment freeze to mitigate possibilities for incidents during the holidays. The production deployment freeze will take place between 20th of December 2024 and 3th of January 2025. During this freeze we won't be introducing new features to our production environments.
We have a lot of interesting things under development and we cannot wait to bring these to you during the year 2025. Until that we wish you a Merry Christmas and a Happy New Years!
Receipt is now downloadable after the session has finished! In case you have forgotten to give your email address during the charging session you can still retrieve the receipt manually after the session from Express.
In our previous OCPI implementation, we utilized routing headers introduced in OCPI version 2.2 whenever they were provided. However, to address compatibility issues with certain partner integrations, we have updated our implementation.
When using OCPI 2.1.1, the following routing headers will now be ignored:
It has come to our attention that some third-party QR code readers redirect users to malicious websites after scanning the QR code. We recommend avoiding the use of any 3rd party QR code readers and only trusting the device's native QR code scanning features, such as ones built in to the device's own camera app. These 3rd party QR code readers might show ads in a misleading way that will make the user click on the ad instead of the actual link or redirect users to wrong websites.
Our payment solution Express never asks for payment details before it has verified that the charger has been properly connected to your vehicle.
Read more from here: Avoid the use of 3rd party QR code readers
/authorise/user/external/:externalId endpoint not responding with proper values for IntegratedExternalIds fields.