Supported Sensors

Checking what your car really delivers and choosing what is read, shown and exported.

This screen lists every sensor known for your vehicle and shows which ones the car actually answers. It is also where you control, sensor by sensor, what is read, what appears in the app and what goes out to the smart home.

There are two tabs: OBD, with what comes from the car, and Calculated and events, with what the app produces.

  1. Find out what the car delivers

    Use Check standard sensor support to have the app probe the ECU and mark each sensor as supported or not. The result is stored, and the list becomes your car's rather than a generic one.

    Check advanced sensor support does the same with the sensors of the manufacturer's profile. When the check cannot run at that moment, the app schedules it for the next connection with the ECU.

  2. Filter the list

    Filter sensors offers five options: All sensors, Supported, Unsupported, Exported and Not exported. The search accepts a name or a PID.

  3. Understand the three switches

    Every sensor has three independent controls:

    • Active turns the reading on. Off, the app stops asking the car about it, which frees speed up for the others.
    • Visible decides whether the sensor appears on the app screens.
    • HA/MQTT decides whether the sensor is exported to the smart home.

    A sensor can be active and invisible, which is common when it only serves as input to a calculation.

  4. Watch out for protected sensors

    There are two protections. Sensors used by features of the app appear locked, marked Used by: with the list of what depends on them; the Active switch cannot be turned off in those cases.

    For the other sensors that feed calculations, turning the switch off opens the Important alert: the sensors that depend on it, listed under Affected sensors, are turned off along with it. The most common case is the fuel rate sensor, which feeds consumption and the efficiency score.

  5. Export sparingly

    The more sensors exported, the more readings the app has to take from the car, and the lower the update rate of each one. Export only what your automation uses.

If something goes wrong

The mark comes from a probe. If it ran with the ignition off or with the ECU still asleep, the result comes out incomplete. Run Check standard sensor support again, with the engine running.

It is also worth installing the manufacturer's advanced profile in Sensor Profiles, because many readings exist only there.

The sensor is locked because a feature of the app depends on it, and the screen shows which one under Used by:. Sensors in that condition stay active.

When the switch can be turned off but other sensors depend on it, the app warns that they will be turned off along with it. Confirm only if you do not use those calculations.

On the free plan the limit applies to the calculated and events family, that is, to what the app produces. The sensors reported by the car are unlimited on any plan.

Every exported sensor is one more reading on the same bus, and the screen itself warns about that. Clear HA/MQTT on whatever your automation does not use.

← All guidesIn the FAQ: Vehicles, profiles and sensors →