To detect idling on a Toyota Corolla, query the segments resource of the DIMO Telemetry API with mechanism: idling, using a vehicle that has a DIMO device. Both the DIMO LTE R1 (2010 and newer) and the AutoPi (2008 and newer) report idling for the Corolla, and both report engine RPM (powertrainCombustionEngineSpeed), which is what idle detection is based on.
DIMO gives developers API access to vehicle-state data: diagnostics, fault codes, battery and fuel health, odometer, and maintenance signals. Vehicle owners consent to and control sharing, so builders get data with clear provenance. See the Toyota Corolla vehicle page for the full list of supported signals. For any other vehicle, see how to detect vehicle idling.
Steps
- Create a Developer License in the Developer Console and note your Client ID, Redirect URI and API Key.
- Get a Corolla shared with your app. The owner grants access through DIMO Connect, and you need a vehicle shared with you before you can fetch a Vehicle JWT.
- Get a Developer JWT, either the system-generated one in the Developer Console or one generated with your API key through a server SDK.
- Exchange the Developer JWT for a Vehicle JWT with the Token Exchange API. Request privilege 1 (all-time, non-location data) and privilege 4 (all-time location). The
segmentsquery requires both. - Send the Vehicle JWT to the Telemetry API in the header
Authorization: Bearer <Vehicle JWT>. - Query
segmentswithmechanism: idling. The idling mechanism finds contiguous periods where engine RPM stays in the idle range and requires a DIMO device. The maximum date range is 31 days. - Tune detection with
config.maxIdleRpmsets the upper bound for idle RPM (default 1000, min 300, max 3000).minSegmentDurationSecondsdrops short segments (default 240, min 60, max 3600).signalCountThresholdsets how sensitive activity detection is (default 10). - Read
duration,start,endandisOngoingfrom each segment. IfisOngoingis true, the segment extends past your query range andendis not returned.
Code
query GetIdlingSegments {
segments(
tokenId: 12345
from: "2026-11-01T00:00:00Z"
to: "2026-11-07T00:00:00Z"
mechanism: idling
config: {
maxIdleRpm: 1000
minSegmentDurationSeconds: 240
}
signalRequests: [
{ name: "speed", agg: MAX }
]
limit: 50
) {
start {
timestamp
value { latitude longitude }
}
end {
timestamp
value { latitude longitude }
}
duration
isOngoing
startedBeforeRange
signals { name agg value }
}
}
Send this query to the Telemetry API with the header { "Authorization": "Bearer <yourVehicleJwt>" }, replacing 12345 with your Corolla's vehicle token ID. The speed request asks for the maximum speed in each idle segment alongside the default signals.
Ready to try it? Get a Developer License in the Developer Console, then follow the authentication guide.
FAQ
Which Corolla hardware supports idle detection?
On a Toyota Corolla, both the DIMO LTE R1 (2010 and newer) and the AutoPi (2008 and newer) report idling. The idling mechanism requires a DIMO device.
Which signal does idle detection depend on?
Idle segments are contiguous periods where engine RPM stays in the idle range. Both the DIMO LTE R1 and the AutoPi report powertrainCombustionEngineSpeed for the Corolla.
How do I change what counts as idle?
Set maxIdleRpm in the config argument. Windows where the maximum RPM is at or below that value are treated as idle. The default is 1000.
How do I filter out very short idle periods?
Set minSegmentDurationSeconds in config. The default is 240 seconds, and the allowed range is 60 to 3600.
Methodology: This guide is based on the DIMO documentation for Authentication, Building Your First App, and the Telemetry API Vehicle Segments reference, plus the Toyota Corolla vehicle page.