We have identified an issue affecting our ability to consume the Renault data stream.

We have informed Renault and are awaiting their feedback.

Update:
* The issue is related to an expired certificate between High Mobility and Renault’s system. We have received a new certificate, but it is not working as expected. We are working with the OEM to identify the root cause and resume the data stream.
* The issue has been resolved. We are working with Renault to prevent such downtime happen again...

Impact:
Some Kia vehicles may provide timestamps with an incorrect offset. The timestamps are expected to be sent in UTC, but due to a vehicle software issue, some timestamps are being sent with an additional +1 hour daylight saving time offset.

Details:
We have shared the affected data with Kia, and they have acknowledged that there is an issue affecting some vehicles.

Kia is currently working on a fix, but they have not shared a timeline yet.

In the meantime, we are investigating whether...

We have identified an issue with some Toyota vehicles that do not provide fuel_level data.

After investigation by the OEM, the issue appears to be related to vehicles whose VIN starts with AHT.

We are currently waiting for Toyota to investigate further and provide a timeline for a fix.

Starting in late March, we observed that some vehicle activations were being rejected due to a "telematics hardware error". We raised multiple cases with the OEM, and Stellantis has confirmed the issue and is working on a fix.

According to Stellantis, the issue was resolved on April 10. We are currently monitoring vehicle activations to confirm that the problem is fully resolved.