Notifications

Notifications are used to send out a notification (sms, email, push notification) whenever a specific event occurs. For instance, you can subscribe to station disconnects, faults, etc., or drivers can receive a push notification when their electric vehicle reaches a specific battery percentage.

Topics in this document:

To access this section in EV Charge, from the Menu, select System configuration, and click Notifications.

Notifications

To access this section, click Notifications. A paginated list of all notifications is shown in a tabular format.


Four actions/subpages can be performed/viewed under this section, namely:

Create notification

Under notifications, to create a notification, click Create. Provide a name and code.

Publishers is used to configure what type of notification will be sent: SMS, push notification, URL, Email, and Log. It is also used to configure where the notification will be sent using Receivers.

List of applicable Receiver-value pairs for the publishing type:

  • Base: Notification targets plain destination contact data, depending on publisher type (email address, phone number or URL).

  • Customer: Notification targets to the destination of customer’s primary contact info, depending on publisher type (email address, phone number, URL, push notification), if action is related to the specific customer. Additionally, as a value, Customer Type group can be selected, meaning that notification will apply only if the customer belongs to the specific customer group.

To create a publisher, under Publishers, click Add publisher. The action and number of retries specify the type of notification that will be sent and how many times to resend in case of a failure—for instance, sending out an email that will resend three times, suppose it fails.

Under each publisher are Receivers. The Receivers refers to where the notification will be sent. It can be a URL or a customer (if it is an email or SMS).

The Scope typifies what will trigger the notification, which can be a change in the charging infrastructure or a change in the charging session.

Once a specific action from the scope occurs, you can add filtering options. To add a filter, under Filters, click Add filter.

Example of a notification

  • Scope: Charging sessions
  • Action: Battery percentage
  • Filter: Battery percentage equals 80% (Reached 80%)

Details notification page

Under notification, to see the full details of a notification, click Details. It contains the following information:

  • Name
  • Code
  • Action
  • Scope
  • Publishers
  • Filters (if any)

Update notification

Under notification, to update a notification, first, click Details; it shows the details of the notification. Then to update, click Update.

Delete notification

Under notification, to delete a notification, click Delete.

Notification scopes and actions

Notification scope defines the triggering event scope of EV charging related notifications.

There are currently two scopes of EV charging related notifications:

  • Charging infrastructure: Notification of charging infrastructure related operations. See Table 1 for applicable actions in the scope.
  • Charging sessions: Notification of charging session control related operations. See Table 2 for applicable actions in the scope.

Action nameDescription
Station connectedIndicates that the charging station has successfully established the connection with the central system of Tridens EV Charge.
Station bootedIndicates that the charging station has reported the boot event. It usually means that the successful boot has happened after the restart, but the boot event can also be triggered on demand.
Station disconnectedIndicates that the charging station has disconnected from the central system of Tridens EV Charge.
Station resetIndicates that the central system of Tridens EV Charge requested the charging station to reset.
Charger status changedIndicates that the charger’s status has been modified and reported to the central system of Tridens EV Charge.

E.g., status switched to available, unavailable, faulted, etc. Also contains additional reported status info, if provided by the charger manufacturer.
Connector status changedIndicates that the connector’s status has been modified and reported to the central system of Tridens EV Charge.

E.g., status switched to available, preparing, charging, suspended, unavailable, faulted, etc. Also contains additional reported status info, if provided by the charger manufacturer.
Connector unlocking requestedIndicates that the central system of Tridens EV Charge requested the connector to unlock from the mechanical electromagnetic lock.
Connector unlocking resultIndicates the result of connector unlocking (mechanical electromagnetic lock), reported by the charger to the central system of Tridens EV Charge.
Energy meter reportRepresents the general energy meter report in kWh reported by the charger to the central system of Tridens EV Charge.
Firmware update requestedIndicates that the central system of Tridens EV Charge requested the firmware upgrade on the charger.
Firmware statusIndicates firmware update status on the charger, as reported by the charger to the central system of Tridens EV Charge.

E.g., downloading, downloaded, installing, installed, failed, etc.
Diagnostics requestedIndicates that the central system of Tridens EV Charge requested the charger for diagnostics.
Diagnostic statusIndicates the status of diagnostics reporting by the charger. Reported by the charger to the central system of Tridens EV Charge.

E.g., uploading, uploaded, failed, etc.

Table 1. Charging infrastructure actions/events.


Action nameDescription
AuthorizationIndicates that the EV driver has attempted the charging session authorization by identification device (e.g. swiping an RFID) at the charger side and the attempt was forwarded to the central system of Tridens EV Charge. Not to be confused with the rating authorizations.
AuthorizedIndicates that the EV driver has successfully authorized for the charging session at the charger side with identification device (e.g. swiping an RFID), by authorization being accepted by the central system of Tridens EV Charge. Not to be confused with the rating authorizations.
StartedIndicates that the charging session has started on the charging infrastructure.
EndedIndicates that the session has ended and finally terminated. Status goes into ‘closed’. Includes the ending in park-time session termination mode.
Reservation createdIndicates that an instant reservation of the charging infrastructure has been made for the charging session.
Reservation canceledIndicates that the reservation of the charging infrastructure has been canceled.
Vehicle chargedIndicates that the vehicle has been fully charged. Threshold for the vehicle charged detection is 95%.

Conditionally works when the charger reports EV battery’s percentage state-of-charge.

Charging endRepresents the end of the charging in the scope of the session, as the charger reported the charging end event to the central system of Tridens EV Charge. The session may keep going on in the final park time, until the final termination.
Charging end by monetary limitIndicates that the charging of the session ended, as the central system of Tridens EV Charge detected breaching of the monetary limit, based on the Session Rating Settings.
Charging end by energy limitIndicates that the charging of the session ended, as the central system of Tridens EV Charge detected breaching of the energy limit, based on the Session Rating Settings.
Charging end by charge time limitIndicates that the charging of the session ended, as the central system of Tridens EV Charge detected breaching of the charge time limit, based on the Session Rating Settings.
Charging end by payment auth. failureIndicates that the charging of the session ended, as additional payment authorization on the central system of Tridens EV Charge did not succeed, based on the Session Rating Settings.
Charging end by auth. failureIndicates that the charging of the session ended, as additional customer resources authorization on the central system of Tridens EV Charge did not succeed, based on the Session Rating Settings.
Battery percentage limitIndicates that the EV battery’s percentage has breached the defined limit. Can be triggered once per session.

Mandatory to provide the ‘State of charge limit’ notification filter, e.g. 80%.

Conditionally works when the charger reports EV battery’s percentage state-of-charge.

Energy limitIndicates that the charging session’s notification energy limit in kWh has been breached.

Mandatory to provide the ‘Energy limit’ notification filter, e.g. 60kWh.

Charge time limitIndicates that the charging session’s notification charge time limit in seconds has been breached.

Mandatory to provide the ‘Charge time limit’ notification filter, e.g. 3600 seconds (1 hour).

Park time limitIndicates that the charging session’s notification park time limit in seconds has been breached. Useful to notify customers that their vehicle is not charging.

Mandatory to provide the ‘Park time limit’ notification filter, e.g. 900 seconds (15 minutes).

Park time rating threshold breachedIndicates that the session’s park time duration rating threshold has been breached, based on the Session Rating Settings. Since this point, parking is charged to the driver.
Fault time limitIndicates that the charging session’s notification fault time limit in seconds has been breached.

Mandatory to provide the ‘Fault time limit’ notification filter, e.g. 300 seconds (5 minutes).

Monetary limitIndicates that the monetary limit (in Site’s default currency) has been breached for the charging session. Can be triggered once per session.

Mandatory to provide the ‘Monetary limit’ notification filter, e.g. 40€.

Monetary limit intervalIndicates that the monetary limit interval (in Site environment’s default currency) has been breached for the charging session. Can be triggered once per session.

Mandatory to provide the ‘Monetary limit’ notification filter, e.g. 5€.

Example for limit of 5 EUR: Notification is triggered when used amount of session breach is made first time over 5 EUR, then 10 EUR, then 15 EUR, …

Meter values reportedIndicates that the charger has reported meter values to the central system of Tridens EV Charge. Usually consists of energy (kWh), power (kW), amperage (A), voltage (V) reports.
Session refusedIndicates that the session has been refused. Customer is known to the central system of Tridens EV Charge, but initial resource authorization did not succeed.

Table 2. Charging session control events/actions.

Platforms

To access this section, click Platforms.

Platforms entail configuring third-party services to enable notifications. It includes Twilio for text messages and Firebase for push notifications.

To enable Firebase for push notifications in EV Charge, see Firebase Configuration.

Firebase configuration

Requirements and process outline

  1. A Google account is required in order to set up Firebase.
  2. You configure Firebase for EV Charge.
  3. Tridens provides either:
    • App - Apple ID
    • App - Android Package Name
  4. You configure iOS or Android apps on Firebase.
  5. You provide either:
    • GoogleService-Info.plist file (iOS platform)
    • google-services.json file (Android platform)

Firebase configuration for EV Charge

Visit your Firebase portal at https://firebase.google.com/ and click Get started or Go to console.

Firebase portal

Figure 1: Firebase portal

Create a new project on Firebase

Create a new project by clicking Create a project.

Create a project

Figure 2: Create a project

Follow the steps to create a new project.

Create a project - step 1

Figure 3: Create a project - step 1

Create a project - step 2

Figure 4: Create a project - step 2

Create a project - step 3

Figure 5: Create a project - step 3

Configure Firebase credentials in EV Charge

After returning to the Project Dashboard, click Project settings.

Settings

Figure 6: Project settings

Go to Service accounts and click Generate new private key.

Generate new private key

Figure 7: Generate new private key

After confirming key generation, a JSON file will be downloaded to your computer.

Confirm key generation

Figure 8: Confirm key generation

The JSON file from the previous step contains your Firebase private key credentials—it can be opened in a text editor.

Private key JSON file contents

Figure 9: Private key JSON file contents

Next, visit EV Charge, navigate to System configuration Notifications Platforms. Click Firebase (FCM), then enter the credentials (which are: client ID, client email, project ID, private key ID, and private key) into the form. Finish by clicking Submit.

Firebase configuration on EV Charge - Web

Figure 10: Firebase configuration on EV Charge

You have successfully configured Firebase for EV Charge.

Create a Firebase mobile app configuration - iOS

Go to the Project Dashboard on Firebase and enter the Project settings.

Project settings

Figure 11: Project settings

Under the General tab, scroll to Your apps and select the iOS platform.

Add iOS app configuration

Figure 12: Add iOS app configuration

In the first step, enter the Apple ID (provided by Tridens) and click Register app.

iOS app configuration - Step 1

Figure 13: iOS app configuration - Step 1

In the second step, download the GoogleService-Info.plist config file and provide it to Tridens to include it in your app build, then click Next.

iOS app configuration - Step 2

Figure 14: iOS app configuration - Step 2

Click Next on steps 3 and 4, then Continue on step 5. This will return you to the Project Settings page, where your iOS app configuration will be visible. You can also re-download the GoogleServiceInfo.plist file here.

iOS app configuration - finished

Figure 15: iOS app configuration - finished

Create a Firebase mobile app configuration - Android

Go to the Project Dashboard on Firebase and enter the Project settings.

Project settings

Figure 16: Project settings

Under the General tab, scroll to Your apps and select the Android platform.

Add Android app configuration

Figure 17: Add Android app configuration

In the first step, enter the Android package name (provided by Tridens) and click Register app.

Android app configuration - Step 1

Figure 18: Android app configuration - Step 1

In the second step, download the google-services.json config file and provide it to Tridens to include it in your app build, then click Next.

Android app configuration - Step 2

Figure 19: Android app configuration - Step 2

Click Next on step 3 and Continue on step 4. This will return you to the Project Settings page, where your Android app configuration will be visible. You can also re-download the googleservices.json file here.

Android app configuration - finished

Figure 20: Android app configuration - finished