It is also worth knowing that a good part of the app does not depend on the adapter. Logging fill-ups, expenses, services, maintenance, income and reminders, browsing the trip and cost history, seeing where you parked and entering a trip by hand all work with no connection to the car at all. And even without an adapter the app can record trips using GPS.
In combustion cars, generally no: the ECU goes to sleep along with the ignition and there is nothing to read, although some models stay awake for a few minutes after you switch off.
In hybrids and EVs the line sits elsewhere. A hybrid can be ready to drive with the combustion engine stopped, and in that state the ECU answers normally, with the engine speed at zero. An EV has no idle: the equivalent of running is the ready state, and several modules stay active outside it, especially while charging, when they usually do answer OBD.
In either case, if you connect the phone before the car wakes up, the app keeps trying in the background and resumes on its own as soon as the ECU answers. And none of this is the same as factory-fitted telematics (the OnStar family), which uses the manufacturer's own modem and never goes through the OBD port.
Yes. Each measure has its own unit, and the whole app follows: history, charts, exports and what is published to your home automation.
You choose distance and speed, fuel volume, consumption, temperature, pressure, air flow, torque, engine power and weight separately, so mixed conventions work: miles with liters in the United Kingdom, kilometers with psi in Brazil. A new install starts from the usual units of the phone's region.
Two things depend on you for that to work. The first is granting every permission the app asks for, especially background location, choosing the option that grants access all the time, not only while the app is open: without it the system suspends location as soon as you leave the app, which is exactly the situation of a phone in your pocket while you drive. The second is turning off battery optimisation for Car 2 Home, otherwise the system kills the app mid-trip. Brands such as Samsung and Xiaomi are especially aggressive about this.
And it is worth being clear that this applies only during the trip. When it ends and the adapter connection closes, the app shuts the service down, the notification disappears and it goes back to sleep, without draining battery in the background. It is woken again by whichever start method you choose: automatic reconnection when you get in the car, the Start in “driving” mode option under Settings > Connection > Auto start, which works even without an adapter, or a system routine that opens the app when the phone connects to the car.
Just like on Android, this depends on you granting the permissions the app asks for, especially background location and Bluetooth. Under Settings > Connection > Auto start there is also Background reconnect, iPhone-only, where you set for how long and how often the app insists on reconnecting each time it wakes.
There is one iOS detail well worth knowing: if you force-quit the app, swiping it up in the app switcher, Apple stops relaunching it when the adapter reappears. The app needs to fall asleep on its own, not be killed. The trip is not entirely lost in that case, because the second way of waking, the one driven by movement, still works after a force-quit. But it only fires after around 500 metres of driving, so the start of the trip is left out. Letting the app close by itself is what guarantees the whole trip.
And as on Android, all of this applies only during the trip: when it ends, the app goes back to sleep. You can also create a Shortcuts automation along the lines of "when connected to the car's Bluetooth, open Car 2 Home", which gives you a third way to start.
On Android, yes. Under Start the app when the car turns on, on the Connection screen, you pick your car's Bluetooth from the list and the system launches the app when that device appears. The car has to be paired in the Android Bluetooth settings first.
On iPhone the system does not allow it, and the way round is an automation you create once in the Shortcuts app: when Bluetooth connects to your car, open Car 2 Home.
Either way, recording does not depend on the app being on screen. What the automatic start buys you is the app reconnecting sooner.
Most of the time the adapter is connected to another app or another device. An OBD adapter serves one app at a time: if it was left connected to another diagnostic app, or to someone else's phone, it closes Car 2 Home's connection right after opening it.
Close the other app, or turn off its automatic connection, and connect again. When the drop repeats several times in a row, the home screen shows Unstable connection with the adapter with the steps and a button to disconnect.
With the app in the background, the phone's system can close it to free memory, even in the middle of a trip. With Auto-reconnect to adapter turned off, nothing brought the app back, and the rest of the drive went unrecorded.
That is what Restore lost connection is for, in Settings > Connection > Auto start, in the Reconnection section. The option appears when auto-reconnect is off and comes turned on. It only acts during a trip: if the app is closed or loses the connection halfway, it connects again and carries on with the same trip. Outside a trip, nothing changes.
Avoid picking a similar model. Similar names are usually different cars, such as Corolla and Corolla Cross, and it is from the model that the app suggests the manufacturer's advanced profile. A namesake can bring in the wrong profile, which gets in the way more than having no profile at all.
Entering manually does not limit the readings: standard OBD-II sensors depend on the car's ECU, not on the registered name. The model matters for the advanced profile suggestion and for the calculations that use engine and tank.
For live readings, the reach comes from the advanced profiles: the catalog covers EVs and hybrids from dozens of makes (European, Asian and American) with sensors that only exist in those cars, such as high-voltage battery state of charge, pack current and temperature, cell voltage and battery cooling.
What varies is how much each manufacturer decides to expose through the diagnostic port, and that changes from model to model. It is worth installing the advanced profile suggested for your vehicle and checking under Supported Sensors what it delivers.
The problem is what comes next. Being electric, Teslas barely implement the standard OBD-II commands, and the data that matters travels on a proprietary bus. Tesla owners report that apps which query the car command by command, which is how ours works, get no answer, and that is why the apps built for the brand had to decode that bus themselves. We have not tested the app on a Tesla yet, so there is no guarantee of live readings even with the harness installed.
What does work is everything that does not depend on the adapter: Tesla is in the catalog, so you register the vehicle and use charges with consumption in km/kWh, expenses, services, maintenance and reminders, plus trips recorded by GPS.
The manufacturer catalog usually has more sensors than your car's version answers. So when you install an advanced profile, the app measures which sensors your car really answers, on its own and in the background, with the adapter connected. Until the measurement ends, those sensors show Awaiting verification in Supported sensors, and the app does not use them in Main sensors yet.
At the end the Advanced sensors checked notice appears. The sensors of a module that did not answer become unsupported, and the app asks that module again by itself on the next connections.
For a complete result, keep the ignition on until the notice appears. With the car parked the measurement ends faster; while driving, it pauses so as not to get in the way of the trip recording.
Yes. Every sensor carries an Expression field, which computes a value from other sensors, so you can derive things the car does not report directly, such as power at the wheels from engine speed and torque.
On top of that there is an Accumulator, which keeps a rolling window over another sensor. You pick what closes the window, time, distance or a number of samples, and what it returns: sum, average, delta, slope or the last value. That is how you build a sensor like average consumption over the last 50 km.
Built-in and catalog profiles are read only, so you start by exporting the sensor to your own profile and editing the copy.
You can also start a trip whenever you want, without waiting for detection. On Android, from the app, the widgets, Android Auto or a system routine. On iPhone, from the app, the widgets, Live Activities, CarPlay, Shortcuts or by asking Siri. And if you forgot to record one, you can enter the whole trip by hand afterwards.
This happens when the app was woken by the last automatic resource it has: noticing that you are driving. On the normal path the phone tells the app as soon as the adapter is nearby, and recording starts as you pull away.
The most common reason is that the app was closed by hand, swiped out of the recent apps list. Closed that way, it no longer hears that the adapter appeared and only wakes up once the car is already moving, so the first stretch is left out.
To have the app open as soon as you get in the car:
- Android: in Settings > Connection > Auto start, turn on Start the app when the car turns on and pick your car's Bluetooth. Another way is a routine that opens Car 2 Home when the phone connects to the car's Bluetooth or to Android Auto; the Android routine card on the same screen shows the steps.
- iPhone: create an automation in the Shortcuts app that opens Car 2 Home when the iPhone connects to the car's Bluetooth or to CarPlay. The iPhone shortcut card, in Settings > Connection > Auto start, shows the steps.
Whenever you can, leave the app in the background instead of closing it from the recent apps list.
On the free plan, Connection and Maintenance are open. Panel and the live numbers of a trip read from the adapter in Trip Data are part of Pro; a trip recorded by GPS shows its numbers on every plan, and starting and ending a trip from the car works on every plan.
On the free plan, the driving score, last trip, quick action and parking widgets work, the parking one with the address and the walking route; the sensors widget and the map on the parking widget are Pro. On iPhone, the trip score Live Activity is free, while the trip in progress and live sensor ones, and asking Siri for a live sensor value, are Pro.
The Eco Score is the only score that needs a fuel consumption reading, and that reading comes from the adapter: the app derives it from the air flow sensor, with the intake pressure sensor as a fallback. On a trip recorded by GPS alone, with no adapter connected, there is nothing to compute it from and the score is left out rather than shown wrong.
Two other cases leave it out even with the adapter connected: trips under a minute, and trips too short to burn a measurable amount of fuel. The Safe Score is unaffected, because it is built from movement, which the phone measures on its own.
It does, up to a point. After 3 seconds with no GPS fix the app starts estimating position from the phone's own motion sensors, gyroscope and orientation, adding a point per second so the route stays continuous instead of jumping across the gap.
The estimate drifts, so it is capped at 2 minutes. Beyond that the app waits for a real fix. It covers a tunnel or a spiral car park ramp well; it will not carry you through a long underground stretch.
Live, during the trip. This route requires a connected OBD adapter, because that is how the app reads the car's sensors. When the car reports fuel flow, the app uses that value; when it does not, it estimates from other sensors, such as air flow, engine load, engine speed and mixture ratio. What comes out of it is instant consumption, the trip's accumulated consumption and rolling averages over distance driven, useful for ignoring the noise of a hill or a traffic light. How much of this your car delivers depends on the sensors it exposes.
From fill-ups, tank to tank. This is the figure the pump proves: you mark the fill-up as a full tank and the app closes the interval at the next one, dividing the distance driven by the total filled in between. Partial fill-ups count. If you forgot to log one, tick the matching option and the app breaks the interval instead of spoiling the average.
Comparing the two. On every tank the app shows side by side what the car reported and what the pump proved, so you get to know your vehicle's deviation.
The electric side is measured separately, in kWh, with its own consumption, so a plug-in hybrid never mixes the two.
The sources are different. The car's display calculates from the flow estimated by the ECU; tank-to-tank consumption measures what the pump actually delivered.
The calculation windows are different too. Even when the app uses the flow reported by the car itself, the figure may not match the dashboard: each manufacturer averages over its own window of time or distance, with an algorithm that is not published and that hardly ever matches the windows the app offers, be it the instant one, the trip one or the rolling averages over distance. Two correct measurements can diverge simply because they cover different stretches.
That is why the app calculates both and shows them side by side on every tank, so you get to know your car's deviation instead of guessing which one is right. The ECU column only appears when the recorded trips cover a sufficient share of the interval's distance, otherwise the comparison would rest on too small a sample.
In the live calculation. The fuel declared in the vehicle setup defines the basis of the calculation, because each one has a different density and air-fuel mixture. On a flex-fuel car the app goes further: when the car reports the ethanol percentage in the tank, it identifies the blend (from E0 to E100) and readjusts the calculation in real time, without you having to say what you filled with. If the car stops reporting it, the app carries on with the last reliable value instead of getting the maths wrong.
In cost tracking. Liquids, LPG, CNG and electric have their own consumption figures that never mix. A plug-in hybrid shows fuel consumption and electric consumption in km/kWh at the same time, each with its own average, and a gas-converted car keeps gas consumption separate from petrol. In a single fill-up you can log more than one fuel, which covers topping up with two types at the same stop.
When the car does not report its own electric range, the app works it out from the way your car uses its battery, and that has to be learned:
- Use per electric kilometre: the app uses the last 50 km driven on electricity only and needs at least 10 km to show a number.
- Bottom of the battery: a plug-in hybrid never runs the battery down to zero, because the engine takes over first. The app learns where that happens on your car by watching the engine start.
Until then the number may stay blank or change a lot. After a few drives that use the battery until the engine takes over, it settles.
With the adapter connected, the app also notices a charge with the car stopped and suggests recording it as Charge detected. Energy that enters the battery with the car stopped stays out of the electric consumption, so charging at home with the adapter plugged in does not skew the average.
The app only suggests a refuel when it sees the tank fill up: the level goes from below 60% to 90% or more, with the car stopped and the adapter connected, or at the first stops of the next trip if the adapter was off at the station. A partial refuel or a top-up does not become a suggestion, on purpose: the fuel gauge varies with the slope the car is parked on, and a wrong suggestion gets in the way more than it helps.
Also check that Suggest when detected is on in Settings > Notifications. The app never records anything by itself; a refuel without a suggestion is entered by hand, as usual.
Codes are split into confirmed, pending and permanent, which say different things about the severity and stage of the problem.
The explanation of each code comes from an extensive catalog, with symptoms, likely causes and paths to a solution. It does not cover every code in existence, mainly the manufacturer-specific ones, so every fault also brings a search shortcut already prepared with the code, in your language.
You can also clear the codes, and the reading history is kept so you can see whether any came back. Scanning is blocked while the car is moving, on purpose.
Because each one carries a Priority, and the adapter can only ask the car one question at a time. Spending that budget equally on everything would make the numbers that change fast unusable.
There are four levels: High, read in real time, Medium, about every 5 seconds, Low, about every 60 seconds, and Once per session for values that never change, such as the VIN. Speed and engine speed are always read continuously.
You can change the priority of any sensor, and there is a global setting for how fast the priority sensors are polled.
The native integration is made for Home Assistant users. You install it through HACS, pair with a 6-digit code and it keeps a two-way connection with persistent state, so Home Assistant still knows the car's situation after a restart. It is also the simpler route to set up.
MQTT is for people who already have a broker or use platforms beyond Home Assistant, such as Node-RED, openHAB, ioBroker or Grafana. It publishes in several formats, including Home Assistant auto-discovery. In exchange for that flexibility it requires the broker to be running and, to work while you are away from home, requires exposing that broker securely, which takes more setup work.
In short: if your destination is Home Assistant, start with the native one; if it is another system, go with MQTT. The details of each are in Home Assistant and MQTT.
When the car stops answering, the app sends the parked state: speed and RPM at zero and the engine off. It follows the car answering, not the adapter's Bluetooth, which can stay connected with the car switched off.
The other sensors keep the last value read, such as fuel level and odometer, until the next reading. The same holds for MQTT.
Besides removing the ads, the paid plans unlock:
- sensor discovery with no limit on quantity;
- calculated sensors and events with no limit when exporting to Home Assistant and MQTT;
- near-real-time transmission to Home Assistant and MQTT, instead of the free plan's long interval;
- logging income against the vehicle;
- place search when logging fill-ups, expenses, services and maintenance;
- the trip map with no restriction, on the route and on the playback;
- tyre temperature as well as pressure, on vehicles that expose that sensor and are covered by the app's catalog;
- customisable panels in Live Data;
- exporting reports and your data to a file;
- live data outside the app: the sensors widget, the map on the parking widget, the trip and live sensor Live Activities, Panel and the live numbers of an adapter trip on Android Auto and CarPlay, and live sensor values with Siri;
- more registered vehicles and devices.
Pro is yearly or a one-off lifetime purchase; Pro Cloud is monthly or yearly. The yearly Pro can start with a free trial for accounts that never had a paid plan; the length and the price after it appear before you buy. One point that often causes confusion: the lifetime purchase gives you Pro, and does not include the cloud. It covers every Pro feature that works on the device, including future ones, but not features sold separately.
The free plan is supported by ads. And there is one more route: several paid-plan features can be unlocked one at a time, by watching a rewarded ad, without subscribing to anything. That is the case for installing a manufacturer's advanced profile, sensor discovery, the intermediate diagnostic scans, tyre-sensor discovery and some exports. Subscribing removes the ads and takes that step out of the way.
Outside the app, the free plan keeps the trip score Live Activity, the driving score, last trip and quick action widgets, the parking widget with the address and the walking route, and Connection and Maintenance on the car screen.
Quantity. On Free you export up to 5 sensors from the calculated and event family, which gathers what the app produces rather than the car: average consumption, reconstructed odometer, trip summary, parking, driving score, phone sensors and the cost-tracking figures. Sensors read straight from the car's ECU do not count towards that and are unlimited on every plan. The split is not arbitrary: on one side what the vehicle reports, on the other what the app calculates. The diagnostic status the app decodes from the car's reply (check engine light, code count, readiness monitors) counts as calculated; the car's position on the map and the app's own connection status never count. Calculated sensors start with export off, and when the limit is reached the app lists what is using it.
Frequency. On Free, live values are sent at most every 5 minutes, against 0.5 seconds on the paid plans. That interval affects only continuous telemetry, such as speed and engine speed; parking, trip summary and the rest still arrive right away.
The same applies when a free trial ends. Widgets, Live Activities and car screens that belong to Pro show the plan notice, keeping your choices, and come back as soon as you subscribe again.
Data is stored encrypted with AES-256 on the device itself, travels over a TLS connection and, on our side, sits in a database on an isolated network with restricted access, behind several layers of firewall. We follow the LGPD, the GDPR and the CCPA/CPRA, and you can delete your account and data whenever you want. The details are in the Privacy Policy.
Once you sign in, your vehicle and the paired adapter start syncing, which already helps when changing devices. Trips, fill-ups, expenses and the rest of the history only go up with Pro Cloud. On a Pro without the cloud they never leave the phone.
In Settings > Report a bug. Describe what you were doing and what you expected to happen; the more concrete, the faster the diagnosis. You can attach up to 3 files, such as screenshots or photos of the dashboard.
The result screens have their own link, such as Report a problem with this scan in the sensor search and Report a problem with this diagnosis in diagnostics. Prefer the link on the screen where the problem appeared: it carries the data of that reading, which is what makes your case reproducible.
The technical log goes along in every case, without any sensitive information.