Vehicle status time drifted more than 15 minutes from current time: Server reported 2038-01-19

[tosate]

Description

While polling vehicle status, the handler failed with a MqttGatewayException indicating a huge time drift in the vehicle status timestamp.
This happened multiple times today.

Error Log

2025-11-08 12:55:17,107 [ERROR]: handle_vehicle loop failed with an unexpected exception - handlers.vehicle
Traceback (most recent call last):
  File "/usr/src/app/handlers/vehicle.py", line 139, in handle_vehicle
    await self.__polling()
  File "/usr/src/app/handlers/vehicle.py", line 172, in __polling
    ) = await self.update_vehicle_status()
  File "/usr/src/app/handlers/vehicle.py", line 277, in update_vehicle_status
    result = self.vehicle_state.handle_vehicle_status(vehicle_status_response)
  File "/usr/src/app/vehicle.py", line 267, in handle_vehicle_status
    processing_result = self.__vehicle_response_publisher.publish(vehicle_status)
  File "/usr/src/app/status_publisher/vehicle/vehicle_status_resp.py", line 65, in publish
    raise MqttGatewayException(msg)
exceptions.MqttGatewayException: Vehicle status time drifted more than 15 minutes from current time: 4454 days, 14:18:49.893897. Server reported 2038-01-19 03:14:07+00:00

Expected Behavior

Vehicle status polling should tolerate or correct minor timestamp inconsistencies and avoid raising an exception when the timestamp appears far in the future (possibly caused by a data formatting or overflow bug).

Additional Context

It seems that the vehicle API or timestamp conversion logic is returning a UNIX timestamp close to the 32-bit overflow limit (2038-01-19).
The software may need to handle or sanitize timestamps that are far in the future before publishing to MQTT.