pub struct TransactionEventRequest {Show 16 fields
pub cost_details: Option<CostDetails>,
pub event_type: TransactionEventEnum,
pub meter_value: Option<Vec<MeterValue>>,
pub timestamp: DateTime,
pub trigger_reason: TriggerReasonEnum,
pub seq_no: i64,
pub offline: Option<bool>,
pub number_of_phases_used: Option<i64>,
pub cable_max_current: Option<i64>,
pub reservation_id: Option<i64>,
pub preconditioning_status: Option<PreconditioningStatusEnum>,
pub evse_sleep: Option<bool>,
pub transaction_info: Transaction,
pub evse: Option<EVSE>,
pub id_token: Option<IdToken>,
pub custom_data: Option<CustomData>,
}Fields§
§cost_details: Option<CostDetails>§event_type: TransactionEventEnum§meter_value: Option<Vec<MeterValue>>§timestamp: DateTimeThe date and time at which this transaction event occurred.
trigger_reason: TriggerReasonEnum§seq_no: i64Incremental sequence number, helps with determining if all messages of a transaction have been received.
offline: Option<bool>Indication that this transaction event happened when the Charging Station was offline. Default = false, meaning: the event occurred when the Charging Station was online.
number_of_phases_used: Option<i64>If the Charging Station is able to report the number of phases used, then it SHALL provide it. When omitted the CSMS may be able to determine the number of phases used as follows: + 1: The numberPhases in the currently used ChargingSchedule. + 2: The number of phases provided via device management.
cable_max_current: Option<i64>The maximum current of the connected cable in Ampere (A).
reservation_id: Option<i64>This contains the Id of the reservation that terminates as a result of this transaction.
preconditioning_status: Option<PreconditioningStatusEnum>§evse_sleep: Option<bool>(2.1) True when EVSE electronics are in sleep mode for this transaction. Default value (when absent) is false.
transaction_info: Transaction§evse: Option<EVSE>§id_token: Option<IdToken>§custom_data: Option<CustomData>