Drivers who start a session on a roaming-enabled charger and are authorised by eMabler are now priced with their own driver or site tariff. Roaming partners that pull CDRs no longer miss a CDR released after review, a partner sending a large number of token updates no longer slows down other roaming requests, and consumption reporting to UtilityCloud is more reliable.
Driver tariff on roaming-enabled chargers
A known eMabler driver authorised by eMabler on a roaming-enabled charger is priced with their own tariff.
On a charger that also takes roaming sessions, a session authorised locally by eMabler for a known eMabler driver is now priced with the driver's tariff group or the site tariff. Before, such a session could be priced with the roaming tariff. Sessions started through a roaming partner are priced as before.
Other features released
-
Roaming partners that page through CDRs no longer miss a CDR that is released from review while they are reading. CDRs are now returned in the order they were last updated, so a newly released CDR always appears on the last page.
-
Token updates from roaming partners are handled faster, and a token that has not changed is not written again. A partner sending a large number of token updates at once no longer slows down other roaming requests such as remote start.
-
Consumption sent to UtilityCloud is more reliable. Hours are no longer counted twice when several sessions of a driver stop close together, a session is sent only once all its energy data has been processed, and a driver linked to more than one UtilityCloud integration has the session sent to each of them.
-
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