How to configure sending OEM data to Wialon using flespi

This guide describes how to configure sending data from the original equipment manufacturer (OEM) devices to Wialon using dedicated protocols on flespi. This integration is possible for the devices of the following OEM:

• Fleetboard (Daimler)
• Scania FMS
• General Motors OnStar
• Invers CloudBoxx

The configuration process consists of the following stages:

1. Preparing OEM devices for streaming. This process varies depending on OEM:
   • Preparing Fleetboard devices for streaming
   • Preparing Scania FMS devices for streaming
   • Preparing General Motors OnStar devices for streaming
   • Preparing Invers CloudBoxx devices for streaming
2. Creating devices on flespi
3. Configuring data streaming to Wialon
4. Configuring a unit and security settings in Wialon
5. Verifying data reception in Wialon

Before you get started with the configuration process, register at https://flespi.io if you don’t have a flespi account yet.

For Fleetboard devices, you need to create a channel on flespi and follow the general workflow for other OEM devices.

1. Go to https://flespi.io/#/ and log in to your account.

2. In the Telematics Hub, select Channels.

   

3. Click the button .

4. Enter the channel name. For example, Fleetboard devices.

5. From the Protocol id dropdown list, select fleetboard.

   

6. In the configuration section, specify the Fleet Name, User Name, and Password that you use within Fleetboard.

7. Click Save.

After you create the channel, it will have a unique URI (host:port) that you can use to send data from your Fleetboard platform.

The configuration process consists of the following stages:

1. Getting credentials from Scania Developer Portal
2. Creating a channel with scania-fms protocol

These stages are described below.

Before you can integrate Scania vehicles with flespi, you need to obtain API credentials:

1. Open Scania Developer Portal.
2. In the Login As dropdown, select Scania Data Access User.
3. Enter your User ID and Password, then log in.
4. Open the My Application tab.
5. Click the Create Application button.
6. Enter an application name and description (for example, flespi integration).
7. Click Save.
8. Copy the generated Client ID and Secret Key strings. You will need these for your flespi channel configuration.

• Scania vehicles only send data to their servers when the engine is running or ignition is ON.
• The frequency of position updates depends on your service package: 1, 5, or 10 minutes.

1. On flespi, go to the Telematics Hub and select Channels.

2. Click the button .

3. Enter the channel name (for example, Scania FMS devices).

4. From the Protocol id dropdown list, select scania-fms.

   

5. In the configuration section, paste the Client ID and Secret Key you obtained from the Scania Developer Portal.

6. Click Save.

After creating the channel, check the Logs & Messages tab to verify that messages are arriving from the Scania API. If you see any errors, refer to the Scania API documentation for error code explanations.

The configuration process consists of the following stages:

1. Getting credentials from General Motors
2. Whitelisting flespi IP addresses with General Motors
3. Creating a channel with general-motors-onstar protocol
4. Provisioning devices for data services

These stages are described below.

Before you can integrate GM OnStar vehicles with flespi, you need to obtain the following credentials:

1. Contact your GM manager and request credentials for:
   • Pulsar client connection (to consume data)
   • API access for sending commands
2. You will receive the following credentials:
   • Owner Client ID
   • Owner Secret
   • Application Client ID
   • Application Secret
   • (Optional): FAN (Fleet Account Number)
   • Pulsar broker configuration (topic, subscription, client credentials, CA certificate)

Before your channel can communicate with GM OnStar API:

1. Provide GM with the flespi outbound IP addresses: 185.213.2.0/24
2. Request that GM whitelist these IP addresses for inbound requests from flespi to GM. This step is essential for the integration to work properly.

1. In the Telematics Hub, select Channels.

2. Click the button .

3. Enter the channel name (for example, GM OnStar devices).

   

4. From the Protocol id drop-down list, select general-motors-onstar.

5. Check the box in the Credentials section and enter the following information:

   • Owner Client ID
   • Owner Secret
   • Application Client ID
   • Application Secret
   • FAN (if provided)

6. Check the box in the Pulsar section and configure:

   • Topic (provided by GM)
   • Subscription (provided by GM)
   • Client ID (for Pulsar)
   • Client Secret (for Pulsar)
   • CA certificate (paste the certificate content)
   • SSL hostname (if required)

7. Click Save+Open to proceed with configuration.

After configuration, check the Logs & Messages tab to verify that the channel is connecting to GM’s Pulsar broker successfully.

For commands to General Motors OnStar devices to work correctly, there must be only one general-motors-onstar channel in your flespi account.

After creating devices, you need to provision each device to opt in for data services:

1. Open the device you just created.
2. Go to the Commands & Settings tab.
3. Find the Provision device command.
4. In the Services field, select the services you want to enable. Default services include:
   • TELEMETRY - vehicle position and telemetry data
   • DTC_NOTIFICATION - diagnostic trouble code notifications
   • HARD_BRAKE - hard braking event alerts
   • HARD_ACCELERATION - hard acceleration event alerts
5. Click Add to queue to execute the command.

You can also add other available services such as EMER_NOTFN, RECALL_NOTFN, THEFT_NOTFN, INCAB_ALERTS, DRIVERSIGNIN_ALERTS, or EV_PHEV_DATA.
Once the command is executed successfully, the GM platform will start sending vehicle telemetry data to your flespi channel. You can verify this in the Logs & Messages tab of the device.

The configuration process consists of the following stages:

1. Getting credentials from Invers
2. Creating a channel with invers-oneapi protocol

These stages are described below.

Before you can integrate Invers CloudBoxx with flespi, you need to obtain the necessary credentials:

1. Contact the CloudBoxx support team at support@invers.com to request:
   • Username for AMQP broker connection
   • Password for AMQP broker connection
   • Virtual host (if required for your setup)
2. To create an API key for commands and settings management:
   • Visit https://api.cloudboxx.invers.com/logins
   • Log in with your CloudBoxx credentials
   • Generate a new API key
   • Copy and save the API key securely

1. In the Telematics Hub, select Channels.

2. Click the the button .

3. Enter the channel name (for example, Invers CloudBoxx devices).

4. From the Protocol id drop-down list, select invers-oneapi.

   

5. In the Configuration tab, enter the following information:

   • Username: Your AMQP broker username (provided by Invers)
   • Password: Your AMQP broker password (provided by Invers)
   • Virtual host: Your virtual host identifier (if provided by Invers)
   • Queues: Select the event types you want to receive. Default options include:
     • events - vehicle events and notifications
     • trackings - position and tracking data
     • heartbeats - device status updates
   • API Key: Paste the API key you generated from the CloudBoxx portal (required for commands and settings)

6. Click Save+Open to proceed with configuration.

After configuration, check the Logs & Messages tab to verify that the channel is successfully connecting to the Invers AMQP broker and receiving data.

To create a device on flespi:

1. In the Telematics Hub, select Devices.
2. Click the button .
3. Give the device a name (for example, your vehicle name or VIN)
4. In the Device type ID field, select the corresponding OEM name from the dropdown list. For example, Fleetboard, Scania FMS, General Motors OnStar or Invers CloudBoxx.
5. In the ident field, enter the vehicle identifier. Depending on the OEM, it can be VIN, vehicle ID from Fleetboard or QNR (CloudBoxx identification number).
6. Click Save.

Repeat this process for each device you want to monitor in Wialon.

Devices collect messages from the moment they are created. Historical data before device creation on flespi isn’t stored.

To create a stream that forwards data from flespi to Wialon:

1. In the Telematics hub, select Streams.

   

2. Click the button .

3. Give your stream a name. For example, Fleetboard to Wialon. Use the corresponding name for other OEM devices.

4. For Protocol id, select flespi_gateway.

5. In the configuration:

   • If using Wialon Hosting: Select your datacenter from the dropdown.
   • If using Wialon Local: Manually enter your server address and port (typically port 21548).

6. Click Save+Open.

7. Go to the Devices tab to connect your devices to the stream.

8. In the stream settings, click the button .

9. Select the OEM devices you created earlier.

10. Click Save.

For proper device matching in Wialon, subscribe the stream to individual devices, not to the channel.

For each flespi device, create a corresponding unit in Wialon. To configure a unit in Wialon, follow the steps below.

1. Log in to your Wialon Hosting account.
2. Create a unit using this guide and considering the following details:

• For Device type, select flespi gateway.
• When specifying the unique ID, make sure that it matches the device identifier of the tracker device created on flespi (VIN or vehicle ID from Fleetboard).
• If you need to send commands to devices from Wialon, select the device type with the (flespi) suffix instead (for example, Fleetboard (flespi)).

To configure the security settings in Wialon, follow the steps below.

1. Sign in to your top account.

2. Click on your username to open the user menu.

   

3. Select User settings.

4. Go to the Security tab.

5. In the flespi settings section, click Login and sign in to flespi to obtain a token.
6. Click OK.

The configuration is finished. Wialon can now receive data from your device.

To verify that everything is configured correctly and Wialon can receive data from flespi:

1. On flespi, open your stream and go to the Logs & Messages tab.
2. Look for log entries that say stream has sent messages. This indicates that flespi is successfully forwarding data to Wialon.
3. In Wialon, go to the Monitoring tab.
4. Check that your units are receiving data and showing on the map.
5. Click on a unit to view its messages and verify that telemetry data (for example, coordinates or speed) are being received.

This completes the configuration process. Your data from OEM devices should now be flowing from flespi to Wialon.