Diesel Exhaust Fluid (AdBlue) level not exposed as sensor despite dieselExhaustFluid: Display capability and README listing it as supported

[naked-head]

Checklist

• I am aware, that marq24 is a grumpy old guy, so it can happen that my issue will be closed instantly when essential information is missing (e.g. no debug logs provided, no issue description, no steps to reproduce the issue, etc...).
• I know, that any attachment send via eMail reply to a github issue notifications will be ignored and deleted by github automatically. With other words this will not work!
• I confirm that I have read & understand the main Integration 'check-list'
• I confirm, that I do not have any other fordpass integration installed/configured (please also check deactivated configurations)
• My home assistant version is up to date.
• I am using the latest version of the integration | See the release list @github or in home assistant use the HACS 'Update Information' function to ensure that the latest released version of the integration is installed. This HACS function can be accessed via the 3-dot menu on the right side for each integration in the HACS integration list.
• I have checked all issues (incl. the closed ones) for similar issues in order to avoid reporting a duplicate issue .
• I have prepared DEBUG log output | In most of the cases of a technical error/issue or if you miss data, I would have the need to ask for DEBUG log output of the integration. There is a short tutorial/guide 'How to provide DEBUG log' here. If no debug log is provided, the issue will be closed instantly.
• I confirm it's really an issue | In the case that you want to understand the functionality of a certain feature/sensor Please be so kind and make use if the discussion feature of this repo (and do not create an issue) - TIA
• I confirm, that I did not read any of the previous bulletin-points and just checked them all. | I don't wanted to waste my time with details, I don't read or follow any existing instructions. | Instead, I want that the maintainer of this repo will spend time explaining the world to me — that's marq24's job!. | I live by the motto: Better to ask twice, than to think about it once. | It's marq24's own fault that he provides open-source software and is willing to offer free support.

Add a description

Small aside: nice checklist, by the way.

Description
The README lists Diesel Exhaust Fluid (AdBlue) level as a supported data point. The vehicle's vehicleCapabilities payload also reports dieselExhaustFluid: Display, indicating the Ford backend considers this data available for this vehicle. However, no sensor exposing the AdBlue/DEF fluid level (percentage or range) is created by the integration.

Vehicle

• Model: Ford Transit (2019), 2025 model year, diesel (ICE)
• Region: EU (Italy)

What I checked

• sensor.fordpass_xxx_vehicles → vehicleCapabilities[0].dieselExhaustFluid = Display
• sensor.fordpass_xxx_metrics (raw metrics blob) contains:
  • dieselExhaustFilterStatus (value: NORMAL_OPERATION) — DPF status, not fluid level
  • dieselParticulateFilterSootLevel (value: 0) — soot level, not AdBlue
  • No dieselExhaustFluidLevel (or similarly named) key present anywhere in the metrics payload
• sensor.fordpass_xxx_dieselsystemstatus only exposes a status string (NORMAL_OPERATION), no percentage/level attribute

Question
Since the README lists this as supported and the capability flag is Display, is the raw fluid-level value simply missing from the current backend response for this vehicle/region, or is it present in the raw payload but not yet mapped into a sensor/attribute by the integration?

home-assistant_fordpass_2026-07-27T12-34-57.440Z.log

Add your DEBUG log output

[marq24]

In the Integration options you can enable to store the plain JSON response from the FordBackend systems - I assume, that these JSONs does not contain any AdBlue Level information (if you like, you can email me the file(s), so I can double check that as well...

2026-07-27 14:34:54.662 DEBUG (MainThread) [custom_components.fordpass.sensor] [Transit (2019)] SENSOR 'exhaustFluidLevel' skipping cause no data available: type: NoneType - value:'None'

but this log line already indicate, that there is no data found in the JSON response...

[marq24]

so if you have dieselExhaustFilterStatus, but not dieselExhaustFluidLevel in the metrics object, then this integration can not invent a value for you - sorry :-) - probably you have to wait for XMas then...

[naked-head]

Ha! Fair enough — I'll add AdBlue level to my Christmas list, right after world peace. 🎄

We must have crossed messages — I'd already sent the raw JSON over email just before seeing your reply here... I'm an old slow man...

Thanks for the fast turnaround.

[marq24]

But your issue create some additional value (even if the missed sensor can't be provided, cause the source is already missing) - I just found 'dieselParticulateFilterSootLevel' in your provided source JSON files!

So I will add that to the dieselExhaustFilterStatus attribute(s)...

Level Range	Status	What It Means	Action Required
0% – 70%	Normal	Filter is light to moderately loaded.	Passive regeneration occurs naturally during highway driving.
80% – 100%	Regen Threshold	The ECU prepares to trigger an Active Regeneration.	Engine injects extra fuel to raise exhaust heat and burn off soot.
100% – 115%	Warning / Pending	Active regen was attempted but interrupted (e.g., short trips).	Dashboard light/prompt appears ("Continue Driving").
> 120% – 140%+	Critical / Fault	Soot load is too high to safely perform automatic active regen.	Fault code P2463 sets; limp mode activates; requires a shop forced/service regen or manual cleaning.

[naked-head]

That's a genuinely useful find, thank you! Glad the soot level data turns out to be actionable even though the AdBlue field itself isn't recoverable — for a vehicle that doesn't always get long highway runs, having visibility into DPF regen status before it hits fault territory is honestly more valuable to me day-to-day than the AdBlue percentage would have been.

I'll keep an eye on the release notes for when this lands. Thanks again for digging through the JSON!