This release lets you put your own logo, a QR code and a price on the screen of DEFA chargers. The Push API has three new events, including the running cost of a session and its final cost breakdown. The AC/DC charger filter now works for most of your fleet, and the sockets list shows AC or DC per socket. Tariff price elements can be named, tariffs can be duplicated, and configuration templates can target AC or DC chargers. A few API endpoints also behave differently, listed under API changes.
Logo, QR code and price on DEFA charger screens
Show your own logo, a start-charging QR code and the price on a DEFA charger's idle screen.
DEFA chargers on OCPP 2.0.1 have a new Manufacturer tab on the charger page. It has three cards:
-
Logo: a PNG image, shown in its normal size or full screen.
-
QR code: usually a link, at most 152 characters. Shorter links give a larger code that is easier to scan.
-
Price: the price per kWh with its currency, and optional extra lines such as "incl VAT". A price of 0 hides it.
Each card is sent to the charger on its own with Send to charger, so changing the QR code leaves the logo as it is. Remove takes the item off the screen. The charger must be online. Connect cannot read back what the charger currently shows, so the forms start empty.
DEFA shows these items only when authorization is on, unless the charger's CustomizationRequiresAuthEnabled setting is turned off.
Sending needs the Operate chargers, Site admin or organization admin permission. In the API, use PUT /v2/chargers/{chargerId}/display-customization with the items inside defa. An item you leave out is not changed, and null removes it.
Session cost and CDRs in the Push API
Follow a session's cost while it charges, get its final cost breakdown, and receive roaming CDRs through your Push API integration.
Push API integrations can now subscribe to three new events. Select them under Events to send on the integration.
-
OngoingTransactionCost: the running cost of a session, sent after each cost update while it charges.
-
TransactionProcessed: the final cost breakdown, sent once the session stop has been processed and the session used energy. Delivery is best effort and the same session can occasionally be sent twice, so de-duplicate on
transactionId. -
CdrReady: the roaming CDR in OCPI format, sent when the CDR is completed.
The charging session messages also carry the site's utilityMeteringPointId when one is set.
AC/DC filter and sockets column
The charger type filter on the chargers, site chargers and configuration template pages now uses the charger model's type, so it works for chargers whose sockets have no power type set. The filter offers AC, DC, AC + DC and Unknown. Automation triggers use the same values and select the same chargers.
The sockets page has a new AC/DC column. In the API, GET /v2/sockets rows carry a new powerType field (AC, DC or null), and chargerType on GET /v2/chargers and GET /v2/sockets accepts AC, DC, MIXED and UNKNOWN. Other still works and means MIXED or UNKNOWN.
Name tariff price elements and duplicate tariffs
Each price element in a tariff can now have a name, for example "Spot price", "Grid fee" or "Electricity tax", instead of several identical "Energy consumption" lines. The name shows on the price element cards, in the week view, in the energy chart and in the "What the driver pays" preview. Roaming partners still see only the element type. In the API, price components take an optional label of up to 100 characters.
Tariff details also has a new Duplicate button, which creates a copy of the tariff to edit.
Configuration templates by charger type
A configuration template implementation can now be limited to AC, DC or Any type chargers, next to manufacturer, model and firmware. The implementations table shows the type, and the apply dialog previews the chargers that will actually match.
This also fixes AC chargers not matching implementations set to AC.
API changes
-
Statistics endpoints return
400for invalid query parameters. A malformedsocketIds,siteIds,from,toorincludeSubsiteson the aggregated success rate, utilization rate and transaction success rate overview endpoints used to return500or be silently ignored. -
GET /v2/charger-eventslimits very large results instead of failing with500.
Other features released
-
The availability view in Data Insights no longer shows chargers as offline after a short connection break when the charger does not resend its status. Some chargers showed far lower uptime than they had.
-
An OCPI connection whose country code and party ID are the same as your organization's is now saved as having no override. This fixes roaming partners being rejected and new connections being refused for your own identity.
-
Roaming locations with a charger that has a parking restriction failed to reach the roaming partner, and the partner's location and CDR requests could fail for the whole page. Fixed.
-
For OCPP 2.0.1 chargers, a session ended by a remote stop or a reset no longer gets an authorization status in the reply.
-
A remote-started session is no longer reported as started from the local whitelist when the charger sends an extra authorization after the remote start.
-
A site's UtilityCloud settings now include the utility metering point ID.
-
Charger health export and the spacing of the Data Insights charts are fixed.
-
Other small bug fixes.
If you have any questions regarding these changes, feel free to contact us at our Service Desk or at support@emabler.com