Every candidate had formula "a", which was right for two of them and lazy for
the rest.
21 A0 at 7E1 is not a guess. The awesomeit profile for this exact model, year
and engine reads gear, gear position and transmission fluid temperature from
that block, so it becomes three real sensors with the published byte
positions: N at byte 13 minus 40 for the fluid temperature, U at byte 20 and
V at byte 21 through their lookup tables. Gear and position need decode
because bytes 20 and 21 are past the range formula variables can address. If
the block answers, the raw response also lands in the log for the odometer
search, so nothing is lost by making these real.
01 A6 has a standard formula, so it uses the built-in odometer preset instead
of reading one byte. If the car answers it, the value is the dash reading
directly with no calibration.
21 01, 22 B001 and 22 B003 at 7C6 keep formula "a" because no byte layout for
them exists anywhere — the awesomeit database and OBDb both carry only 22 B002
on 7C6. Writing a formula would be inventing one. These stay existence probes;
the raw hex in the log is the deliverable, and the real formula gets written
once that hex says where the value sits. The comment now states this outright
rather than leaving "a" unexplained.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The working odometer comes from the engine ECU's 21 03 block and sits 1436.5 km
above the dash, corrected with offset_value. Probing more 7E0 blocks cannot
improve on that — they read the same counter and carry the same bias. A value
that matches the dash has to come from a different module.
Add read-only probes on the two independent candidates:
21 01 @ 7C6 the cluster's mode 21 block. 7C6 refuses 22 B002 but answers
with 7F 22 22 rather than staying silent, so the module is
present and other identifiers are untested
22 B001 @ 7C6 identifiers adjacent to B002, unrecorded anywhere
22 B003 @ 7C6
21 A0 @ 7E1 the transmission. The awesomeit profile for this exact model
reads gear and fluid temperature from this block, so it
exists here and may hold its own distance counter
01 A6 the standard odometer PID. The mode 01 support list for a
2013 Accent stops at 0145 so this is a long shot, but it
would return the dash value directly and costs one request
Deliberately left out: 22 B002 at 7C6, which this car refuses outright, and
01 2F, which answers NO DATA. Both are recorded in the comment so they do not
get retried.
Note in the template that OBDb's Accent captures come from North American
petrol cars and do not describe this diesel — 7E0.2103 is marked unsupported
there yet works here — so candidates are settled on the car, not from the
capture.
Probes publish only the first byte; the point is the raw response in the log.
Remove the block once the question is answered.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Real readings from the car on 2026-07-30:
odometer 197394.5 km
odometer at last regen 197055.5 km
distance since regen 339.0 km
dash 195958 km
197055.5 + 339.0 = 197394.5 to the decimal, which confirms bytes 49, 53 and
57 are all decoded correctly. The ECU counter simply runs 1436.5 km — 0.733%
— above the cluster. It exists to time DPF service intervals, is fed by a
different speed source than the legal odometer, and drifts from it over a
vehicle's life.
Apply that as offset_value on the odometer, and on the odometer at last
regeneration since it reads the same counter and the cross-check only holds
if both move together. Distance since regeneration is a difference, carries
no bias, and stays as it is.
One reading cannot tell a constant error from a proportional one. A constant
is assumed for now and the comment records how to settle it: after 100 km or
more, a gap still at 1436.5 confirms the constant, while a gap near 1437.2
means it scales and offset_value should give way to scale 0.000992723.
Drop fuel_percent. Standard 01 2F answers NO DATA on this car — OBDb's Accent
capture that recorded it as supported is a North American petrol car — and
the cluster refuses 22 B002, so there is no route to fuel level here.
Drop probe_2103 now that the real sensors report, and give both DPF sensors a
state_class so Home Assistant stops warning that a unit is set without one.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Replace the log-only probe with actual sensors now that OBD sensors can
extract values by byte offset. All three come from the same 21 03 response on
the engine ECU:
offset 49 odometer at the last DPF regeneration
offset 53 distance driven since that regeneration
offset 57 total odometer
Each is a 32-bit big-endian value scaled by 0.001 to give kilometres. The two
DPF fields are marked diagnostic and exist as a cross-check: the value at 49
plus the value at 53 should equal the value at 57, which tells us the offsets
are right rather than merely plausible.
Whether this car's 21 03 frame reaches byte 57 is still unverified. If it does
not, decodeStructured returns null and nothing is published, so the sensors
stay empty instead of reporting a wrong distance. The probe is kept for now so
the raw response still lands in the log either way.
Document `decode` on OBD sensors in both READMEs.
Needs hassble-android feat/obd-offset-decode.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The Accent does not expose the odometer through the cluster. OBDb's captured
command support for real cars records 7C6.7CE.22B002 as unsupported on the
2013, 2015 and 2019 Accent (2018 is the lone exception), which is exactly the
7F 22 22 conditionsNotCorrect this car returns. So obd_hyundai_kia, which is
correct for the 35 other HKMC models, cannot work here.
Add a template for the Accent RB diesel (1.6 TCI-U2) carrying what is known
to work on this car, plus a probe for the remaining unknown:
- fuel level as a percentage via standard 012F, recorded as supported on 7E0
for every captured Accent year
- intake temperature and barometric pressure from 21 01, taken from the
awesomeit profile for this exact model, year and engine
- probe_2103, which requests 21 03 purely so the response lands in the app
log as raw hex
21 03 on the engine ECU is where OBDb's make-wide HYUNDAI_ODO_V2 lives, at
bytes 57-60 divided by 1000. Two neighbouring fields sit in the same frame —
the odometer at the last DPF regeneration at bytes 49-52, and the distance
driven since that regeneration at bytes 53-56 — and they are distinct values,
not the odometer. The awesomeit profile for this car reads bytes 53-55 of the
same 21 03 response, so the frame is known to arrive at least that far; the
odometer is two bytes beyond.
The probe is needed because formula variables only reach byte 19, so byte 57
cannot be addressed yet. Once the raw response confirms the frame length and
the value matches the dash, OBD sensors need offset-based decode and the probe
can be replaced by a real sensor.
Note the exception in obd_hyundai_kia so it points at this template.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The comment claimed some Kia clusters shift the odometer to i:k:k:l. That
misread a search snippet: bytes j:k:l are a separate field holding the same
odometer in miles for North American clusters, not an alternate km layout.
Verified against OBDb (obdb.community), where 11 Hyundai/Kia models —
Elantra, Sonata, Tucson, Kona, Santa Fe, Veloster, Forte, K5, Seltos,
Sportage, Telluride — all publish the identical layout for 7C6 / 22 B002:
e fuel level (liters)
f cluster volts div 12.8
g:h:i odometer 24-bit km
j:h:l odometer 24-bit miles
OBDb's 12.8 divisor for byte f equals the 0.078125 multiplier already in the
template, which confirms OBDb indexes bytes the same way Torque letters do,
i.e. excluding the 62 B0 02 echo. So g:h:i is right as written.
Fuel level stays at e*0.5. OBDb is split — Santa Fe and Soul carry div 2
while ten others carry no scale and max 255, the uncalibrated 8-bit default.
The awesomeit plugin (35 models) and the Elantra CN7 list both scale by 0.5,
and e*1.0989 % maps to a 45.5 L full tank, so 0.5 is the calibrated value.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The obd_hyundai_kia template shipped four PIDs that belong to other makes, so
a Hyundai or Kia never answered them:
22 132A → GM/Chevrolet (Malibu, Cruze, Trax, Spark)
22 2203 + ATSH743 → Renault Samsung (SM5, SM6, QM3, QM6)
22 FD40 → SsangYong (Korando, Rexton W, Tivoli)
22 F22E → SsangYong Tivoli
The odometer formulas were wrong independently of the PID: FD40 reads the
odometer from bytes U:V, not a:b.
Replace them with the HKMC instrument cluster DID, which carries odometer,
fuel level and cluster voltage in one response:
ATSH7C6 + 22 B002 → 62 B0 02 [a][b][c][d][e][f][g][h][i] …
e → fuel level e*0.5 L
f → cluster volts f*0.078125 V
g:h:i → odometer 24-bit km
Cross-checked against the Elantra CN7 PID list, JejuSoul/OBD-PIDs-for-HKMC-EVs
and the awesomeit Torque plugin database (35 HKMC models, 2013 onwards).
Requires hassble-android to group sensors by (mode, pid) and to expose
response bytes past h — all three sensors share one PID and the odometer
needs byte i.
Also document the formula byte range and the ATSH restore rule in both READMEs.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Remove redundant OBD initialization commands (ATZ, ATE0, ATL0, ATS0, ATH0) from configs. config.yaml now only uses ATSP6 for the device, and templates.yaml clears init_commands for one template and sets only ATSP6 for the other. This reduces unnecessary reset/echo/linefeed commands and relies on explicit protocol selection.