Guide

How to detect idling on a Honda CR-V via API

· 4 min read

To detect idling on a Honda CR-V, query the DIMO Telemetry API segments resource with the idling mechanism, which returns contiguous periods where engine RPM stays in the idle range. DIMO supports idling on the CR-V through both the DIMO LTE R1 (2008 and newer) and AutoPi (2010–2025), and both report engine RPM (powertrainCombustionEngineSpeed).

DIMO gives developers API access to vehicle-state data: diagnostics, fault codes, battery and fuel health, odometer, and maintenance signals. The Honda CR-V vehicle page has the full signal list. For any other vehicle, see how to detect vehicle idling.

Steps​

  1. Create a Developer License and get a Developer JWT in the Developer Console. You need the license's Client ID, Redirect URI and API Key. The Developer JWT gives general API access but no vehicle data.
  2. Get the CR-V shared with your app through DIMO Connect. Vehicle owners consent to and control sharing, so builders get data with clear provenance. You need a shared vehicle before you can request a Vehicle JWT.
  3. Exchange your Developer JWT for a Vehicle JWT through the Token Exchange API. Request privilege 1 (all-time, non-location data) and privilege 4 (all-time location). Both are required for the segments query, which returns each segment's start and end location.
  4. Call the segments query on the Telemetry API with mechanism: idling. Idling detection requires a DIMO device. On a CR-V, the DIMO LTE R1 and AutoPi both qualify and report engine RPM (powertrainCombustionEngineSpeed). The query range is limited to 31 days.
  5. Tune detection with config. maxIdleRpm sets the upper RPM bound for idle (default 1000, min 300, max 3000). minSegmentDurationSeconds filters short segments (default 240). signalCountThreshold controls sensitivity.
  6. Add signalRequests for context per idle period. On a CR-V, powertrainCombustionEngineSpeed is reported by both devices. The DIMO LTE R1 also reports powertrainFuelSystemRelativeLevel, so on that device you can request it with FIRST and LAST aggregations to see fuel level at the start and end of each idle period.

Code​

This GraphQL query returns idle segments for one CR-V over a week. Replace 12345 with your CR-V's token ID, change the dates, and send it to the Telemetry API with the header Authorization: Bearer <Vehicle JWT>.

query GetIdlingSegments {
segments(
tokenId: 12345
from: "2026-11-01T00:00:00Z"
to: "2026-11-08T00:00:00Z"
mechanism: idling
config: { maxIdleRpm: 1000, minSegmentDurationSeconds: 240 }
signalRequests: [
{ name: "powertrainCombustionEngineSpeed", agg: MAX }
]
limit: 50
) {
start {
timestamp
value { latitude longitude }
}
end {
timestamp
value { latitude longitude }
}
duration
isOngoing
startedBeforeRange
signals { name agg value }
}
}

Want to test it? Pick up a Developer License from the Developer Console and use the authentication guide to get a Vehicle JWT.

FAQ​

Which Honda CR-V connections support idling detection?​

The DIMO LTE R1 (2008 and newer) and AutoPi (2010–2025) both support idling on the CR-V. Idling detection requires a DIMO device. See the full signal list on the Honda CR-V vehicle page.

What counts as idling?​

An idling segment is a contiguous period where engine RPM stays in the idle range. By default, windows with a maximum RPM at or below 1000 are treated as idle. You can change this with maxIdleRpm.

How do I ignore very short idle periods?​

Set minSegmentDurationSeconds in config. The default is 240 seconds, with a minimum of 60 and a maximum of 3600.

Methodology: this guide is based on the DIMO documentation for Authentication, Building Your First App, and the Telemetry API Vehicle Segments reference, and on the Honda CR-V vehicle page.

More guides · Browse vehicles