Repository navigation
[18.0][ADD] fleet_telemetry: new module - #238
Open
douglascstd wants to merge 1 commit into
Open
douglascstd wants to merge 1 commit into
douglascstd wants to merge 1 commit into
Conversation
douglascstd
force-pushed
the
18.0-add-fleet_telemetry
branch
from
October 6, 2026 21:34
5f2ecad to
8139afd
Compare
Assisted-by: Claude Opus 5.5
douglascstd
force-pushed
the
18.0-add-fleet_telemetry
branch
from
October 6, 2026 21:41
8139afd to
6f98868
Compare
douglascstd
marked this pull request as ready for review
October 7, 2026 11:40
This was referenced Oct 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
New module
fleet_telemetry: a generic, provider-agnostic storage for vehicletelemetry (GPS positions and tracker data) in the Fleet app.
The goal is to give provider integration modules (Traccar, etc.) a common data
model to push positions into Odoo, instead of each integration defining its own.
Features
fleet.telemetry.device): trackers identified byprovider + external reference, linked to a
fleet.vehicle, with chatter andtracking. Unique per company/provider/reference.
fleet.telemetry): positions with GPS date, server date,latitude, longitude, speed, course, altitude, address and a JSON
attributesfield for any provider-specific data. Unique percompany/provider/external position reference.
route_day, used for filtering and grouping routes by day._merge_duplicate_telemetry()helper to merge duplicated positions receivedfor the same device, GPS date and coordinates (keeps the oldest record, fills
empty values, merges attributes, keeps the latest server date).
read-only in the UI (meant to be created by integrations).
fleet managers have full access.
No map rendering dependency on purpose. Maps can be provided by a separate
module.
Tests
Unit tests cover devices (defaults, uniqueness), computed dates, position
uniqueness, attribute merging, duplicate merging (including skipped incomplete
groups) and access rights.
How to test
fleet_telemetry.linked to a vehicle.
integration module) and check them in Fleet > Configuration > Telemetry >
Telemetry, filtering/grouping by vehicle, device or route day.
Assisted-by: Claude Opus 5.5 (unit tests and readme fragments)