v0.2.3 — Observation logging
What's new
Diagnostic infrastructure for go-e chargers — five new debug log categories and an energy + power snapshot suffix on every observation line. Observation-only — no session-engine behaviour changes.
New debug log categories
PLUG_STATE— plug connect / disconnect (binary_sensor.goe_{serial}_car_0)CABLE_LOCK— cable lock status (sensor.goe_{serial}_cus_value)MODEL_STATUS— charger's own status text (sensor.goe_{serial}_modelstatus_value)ERR_STATE— charger error state (sensor.goe_{serial}_err_value)TRX_STATE— RFID transaction state
Every observation line — and the existing CAR_STATE line — now carries the suffix | wh=<v> power=<v>.
Configuration
Four new optional entity slots in Settings → Devices & Services → EV Charging Manager → ⚙ Configure:
- Plug-connected binary sensor
- Cable lock sensor
- Charger model-status sensor
- Charger error sensor
Auto-populated for goe_gemini profile from the configured serial — both at fresh install and as a one-time migration when you upgrade. Slots you clear manually are preserved (no re-fill on next reload).
How to use
- Update via HACS.
- Open the integration's options flow and verify the four observation slots are pre-filled.
- Toggle Enable debug logging ON.
- After your next charging session, inspect
/local/ev_charging_manager_debug.log.
See docs/PR-20-test-checklist.md for the full operator test protocol.
Why
The next planned change is a redesign of session boundaries (car_value transitions split sessions when the car briefly enters Complete mid-charge). This release collects the diagnostic evidence (plug state, cable lock, model status) needed to anchor session boundaries on the right signal in the follow-up.
No behaviour changes
- Existing session tracking unchanged
- Balancing-cycle gate (v0.2.1) unchanged
- BMS pause/resume promotion (v0.2.2) unchanged
- Event payloads unchanged — InfluxDB export contract preserved