# November 2025 ### 2025-11-28 #### - Added: Mercedes-Benz has added few data points to "Charging" Starting 28th Nov, we are adding the following data points to "charging" packages: * `charging.get.estimated_range` * `charging.get.max_range` * `usage.get.electric_consumption_rate_since_reset` * `usage.get.electric_consumption_rate_since_start` #### - Removed: Mercedes-Benz has removed some data points from "Fuel and Energy Consumption" Starting 28th Nov, we are removing the following data points from "Fuel and Energy Consumption" packages: * `charging.get.estimated_range` * `charging.get.max_range` * `usage.get.electric_consumption_rate_since_reset` * `usage.get.electric_consumption_rate_since_start` {% hint style="warning" %} If you relying on these data make sure to contact us and enable "charging" package {% endhint %} ### 2025-11-17 #### - Changed: Delta Push Enabled for Newly Added Mercedes-Benz Vehicles We have enabled Delta Push for all newly onboarded Mercedes-Benz vehicles.\ Delta Push reduces redundant data transmissions by sending updates only when signal values or timestamps change. This results in lower data volumes and more efficient processing for all consuming systems. Existing active Mercedes-Benz vehicles are not affected and will continue operating with the previous behaviour until end of March {% hint style="info" %} **Fleet-wide Delta Push Migration by 31st March 2026** Mercedes-Benz has announced that Delta Push will become the default behavior. In alignment with this transition, all Mercedes-Benz vehicles in our platform will be migrated to Delta Push by end of March 2026.\ This ensures compatibility with upcoming changes and provides a more efficient, future-proof data delivery model {% endhint %} ### 2025-11-13 #### - Added: Introducing MQTT V2(Enterprise) Broker The **MQTTV2 broker** is a new streaming option that will replace our original MQTT broker.\ It offers higher throughput and leverages new features of the MQTT protocol. While developing MQTTV2, we also refactored parts of our internal system. Instead of sending MQTT messages where each message contains individual properties, we now bundle multiple vehicle data points into a single message. This change was made to ensure: * Higher throughput * Delivery of vehicle data in batches exactly as they were received from the car or OEM Read more about the new streaming option on [MQTT V2](https://app.gitbook.com/s/5qJVhvD9HNUZIro3LyTa/vehicle-data/mqtt-v2 "mention") ### 2025-11-10 #### - Changed: Migrated to Volvo Cars Streaming Vehicle API In this update we no longer make use of Volvo Cars REST API, but are using a streaming interface that they now offer. The changes are internal and do not require any changes by our customers. There are several benefits of this migration going forward, and we have a few immediate updates that are live: * GPS data is updated up to every 1 minute. This is a big upgrade from previously providing data at ignition off. * EV and Charging data updated on change. Previously we only got updates every 5 minutes due to the REST API polling frequency. Now we receive all EV events as they change and all samples are pushed to our data stream.