> For the complete documentation index, see [llms.txt](https://docs.high-mobility.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.high-mobility.com/changelog/readme/august-2025.md). # August 2025 High Mobility platform updates on August 2025 * Remove the requirement of passing `control_measure` when activating virtual sandbox vehicle with VIN `2HM00000000000001` . * Add Battery State of Charge to BMW data catalog. * Maintenance on KIA integration. * Migrate to Renault FAM and data V3. * Vehicle activation works as before * Following `dashboard_lights.get.dashboard_lights` are removed: * `engine_drag_torque_control_failure` * `engine_oil_level` * `engine_drag_torque_control_failure` * Re-adding stuck VW vehicles. We have noticed that sometimes VW vehicles get stuck during activation. Based on our experience, re-adding them to the OEM’s API resolves the issue. We have now automated this process: if a vehicle remains stuck for two days, it will be removed and re-added to the OEM. All our customers will automatically benefit from this improvement without making any changes to their code. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.high-mobility.com/changelog/readme/august-2025.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.