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>
1. parking_beacon: manufacturer_hex_prefix "04" 추가
- SmartKey 인증 패킷(07xx, 22B)이 parking_floor/location을 오염시키던 문제 수정
- length: 14 (정확한 길이 일치)로 22B 패킷 디코드 단계에서도 차단
2. apt_key_door 신규 추가
- manufacturer_id 861 + prefix "02" → 출입 이벤트 6바이트 패킷만 매칭
- instance_mode: shared, MAC 지정 없음
- door_status: entering / exiting / idle 텍스트 센서
- publish.min_interval: 1s (기본 10s 오버라이드, 이벤트가 수 초 내 전환)
Co-Authored-By: Claude Sonnet 4.6 <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.
state_class: none is parsed as the string "none" by kaml/snakeyaml (not null).
ConfigValidator treated any unknown state_class as ERROR, so parking_floor was
silently excluded from entity declarations — it never reached Home Assistant.
- parking_floor: changed to state_class: measurement (correct for floor number)
- parking_location: removed state_class: none (meaningless for text_sensor)
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
README.md rewritten as English-only with cross-link to README.ko.md.
README.ko.md added as Korean-only translation.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Full documentation of every config.yaml field — root structure, defaults,
all three device sources (advertisement/gatt_notify/obd), match conditions,
decode types, controls, publish rules, OBD preset table, and 5 full examples.
Includes common pitfalls (hex literals, AND-logic, instance_mode, source_field).
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
service_data_uuid + manufacturer_id 두 조건 AND 매칭이 실패 원인:
Android BLE 스캔 결과에서 F51C 서비스 UUID가 service data 또는 service UUID
목록에 포함되지 않으면 항상 NO MATCH 발생.
Fix: service_data_uuid 제거, manufacturer_hex_prefix "0215" (iBeacon 타입 마커)로
대체 → Apple 제조사 데이터(ID 76)로 시작하는 iBeacon 포맷 기기만 매칭.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Configure MAC-per-instance Jaalee decoding and manufacturer 0x035D parking time, battery, and location.
Co-authored-by: Cursor <cursoragent@cursor.com>