Implementation Details

Current Repo Behaviour

• handle_vehicle_message validates V2ICPVehicleRequest payloads.
• For seq > 0, the router rejects payloads that omit h2_stat or bat_stat with 422 Unprocessable Entity.
• Successful message requests return V2ICPBackendResponse with the incoming seq, the incoming vin, and an empty BackendParameterSet.
• record_diagnostic accepts a DiagnosticEvent and replies with 202 Accepted; the event is not persisted.
• /vdv261/schemas and /vdv261/schemas/{schema_name} expose JSON schemas derived from the Pydantic models.

Behaviour Documented But Not Implemented Here

• VAS discovery, tunnel establishment, TLS handshake, and port-443 transport rules.
• HTTP Basic Authentication enforcement and credential lookup during requests.
• Retry cadence, idle timeout management, reconnect scheduling, and any session-level state machine.
• Business logic for computing backend directives such as driveoff, prec_dsrd, prec_hvac, ambienttemp, target_dist, or target_soc.
• Storage, forwarding, or monitoring workflows for diagnostic events.

Documentation Workflow

• make openapi regenerates ./schema/openapi.json from the router's /vdv261/openapi.json endpoint.
• VDV_261_API_Reference.md renders that generated OpenAPI file with Redoc.
• make docs builds the MkDocs site for local review.

Supporting Material

• Detailed protocol and background: VDV_261_04_Technical_Specification.md
• Communication flows: VDV_261_06_Communication_Sequences.md