Connecting YellowFox Telematics: Mileage Readings and Driving-Licence Checks

Overview

At regular intervals, the YellowFox service fetches data from your YellowFox telematics portal and transfers two things into FMWeb:

1. Mileage readings: For each vehicle with a stored YellowFox identifier, FMWeb adopts the current odometer reading along with a timestamp from the vehicle's position. The change is documented in the vehicle's mileage history (source YellowFox).
2. Driving-licence checks: For drivers who present their driving licence at the YellowFox NFC reader, FMWeb adopts "Zuletzt vorgelegt am" (Last presented on), the next check and the check interval, and writes an entry into the check history (source "YellowFox"). Only checks that are newer than the stored date are taken over.

Without a valid YellowFox license, the service skips processing and logs this in the log (Article 112).

Prerequisites: maintaining the identifiers

• Vehicles: In the vehicle file, fill the "YF Fahrzeug Ident" (YF vehicle identifier) field with the YellowFox vehicle identifier. Vehicles without an identifier are ignored.
• Drivers: In the driver file, fill the "NFC" field with the driver's tag ID. The NFC identifier must be unique – on saving, FMWeb checks for duplicates ("NFC bereits vergeben" / NFC already assigned).

Configuration

Systemadministration → Hintergrundaufgaben (System Administration → Background Tasks) (/applications/backgroundtasks/dashboard) → "YellowFox Task" tab:

1. Switch on "Ist aktiv?" (Is active?).
2. Set the waiting time between runs in hours (1–24).
3. Enter the API Benutzer (API user) and API Passwort (API password) from your YellowFox account (have API access enabled by YellowFox if necessary).
4. Select the tenants for which data should be imported.
5. Click "YellowFox Einstellungen testen" (Test YellowFox settings) – FMWeb fetches the driver list as a test. While the service is active, Speichern (Save) remains locked until the test has succeeded.

Monitoring and troubleshooting

In the "Logs" tab you find the message "YFoxTask complete" for each run, plus any errors from driver or vehicle processing; clicking a row shows the details (Article 15).

Typical causes when data does not arrive:

• Vehicle/driver without a (correct) "YF Fahrzeug Ident" or "NFC" identifier
• Tenant not in the task's tenant selection
• API credentials changed – run the test button again

Frequently asked questions

Does YellowFox overwrite manually recorded mileage readings? The service sets the vehicle's current odometer reading to the telematics value of the respective run; the changes are traceable in the mileage history. Manual odometer entries are retained as their own entries.

Can I use YellowFox and Fleet-ID in parallel? Yes. Both services write into the same driving-licence fields but each only takes over newer checks – the most recent presentation "wins", and the source is visible in the history.

Related articles

• 15 – Background Tasks Dashboard
• 116 – FleetSync: Driving-Licence Check with Fleet-ID
• 20 – Managing Vehicles and Drivers
• 14 – KFZ-Info Calculation