Car 2 Home works with vehicles that comply with the OBD-II or EOBD standard. In practice, that covers virtually every gasoline car sold in the United States from 1996, in the European Union from 2001 (2004 for diesel), and most modern vehicles in other markets. A few non-standard protocols are supported on a best-effort basis.
This is normal — we can't maintain a profile for every trim of every model ever made. Select the generic profile for your manufacturer (for example, Renault OBD-II or Ford OBD-II). The generic profile will use the standard OBD-II PIDs that your car's ECU exposes.
Mostly no. The OBD-II standard was created to monitor combustion-engine emissions, so EVs are not legally required to support it and most of them don't. You may still be able to read a few basic values (battery voltage, trouble codes) depending on the vehicle.
It depends. Some pre-OBD-II vehicles were fitted with a 16-pin connector that physically accepts the adapter but internally speaks a proprietary OBD-I protocol. Check under the hood for an emissions label that explicitly mentions OBD-II compliance.
Yes, within the same store account. A PRO subscription purchased through Google Play is valid on any Android device signed in with the same Google account. The same applies to Apple — a PRO purchase on the App Store is valid across iPhones and iPads using the same Apple ID.
No. Apple and Google operate completely independent billing systems, and neither store recognizes receipts issued by the other. If you want PRO on both platforms, you currently need to subscribe on each one separately.
Car 2 Home never handles payments directly — all transactions are processed by Apple App Store or Google Play. When a card is declined, the cause is almost always on the store or bank side.
No telemetry, VIN, or OBD data is ever sent to Car 2 Home servers. The app reads data from your car via the OBD-II adapter and publishes it over MQTT directly to the broker you configure. Our backend is not part of this flow.
No. The MQTT integration is the app's distinguishing feature, but the app also works as a standalone OBD-II scanner — live data, fault codes, logs, dashboards — without any server configured.
Anything that speaks MQTT, which includes Home Assistant, Node-RED, openHAB, Domoticz, ioBroker, and most DIY setups.
You don't need to pair OBD adapters through iOS settings. Bluetooth LE adapters are discovered and connected inside the Car 2 Home app itself — open the connection screen in the app, scan, and select your adapter there.
Only Bluetooth Low Energy (4.0+) and Bluetooth MFi adapters. Classic Bluetooth adapters (version 2.x / 3.x) cannot be used with iOS at all.
Yes. Enable background operation in Settings → Connection → Work in background inside the app. On many Android builds you also need to disable battery optimization for Car 2 Home, or the OS will kill the connection after a few minutes.
For safety reasons, Android Auto restricts third-party apps to a narrow set of categories and mandates the use of Google-provided UI templates. Those templates forbid animated content and continuous live dashboards.