Skip to content

v2.0.1-beta.8

Pre-release
Pre-release

Choose a tag to compare

@coreywillwhat coreywillwhat released this 14 Mar 12:50
b7d1ad7

Warning

This is a pre-release version. It is intended for testing purposes and may contain bugs or breaking changes. If you encounter any issues, please report them here.


Overview

This release is part of a large, ongoing effort to modernize the Audi Connect integration — bringing it up to current Home Assistant standards, improving reliability, and laying the groundwork for future development. Development for v2 has been taking place in @coreywillwhat's fork, where you can find the full commit history, development notes, and work in progress.

A note on development transparency: This integration is developed and maintained by a small group of people in their spare time. To help accelerate the modernization effort, Claude Code has been used as a development aid. Every change is personally tested and code-reviewed before being merged.


What's Changed

✨ Features

  • Modernize audiconnect integration to coordinator/runtime_data architecture by @coreywillwhat in #22
  • Add reconfigure flow for updating account password by @coreywillwhat in #28
  • Replace manual VIN text input with vehicle device selector in services by @coreywillwhat in #29
  • Log Vcf-Remaining-Calls rate limit header after every HTTP response by @coreywillwhat in #35
  • Add configurable vehicle refresh and cloud refresh delay options by @coreywillwhat in #36
  • Add System Health panel support with API rate limit reporting by @coreywillwhat in #40
  • Add API requests remaining diagnostic sensor by @coreywillwhat in #41

🐛 Bug Fixes

🏗️ Refactoring

  • Restructure entity architecture to use EntityDescription pattern by @coreywillwhat in #42

🔧 Maintenance


⚠️ Breaking Change: Service Actions Now Use Device Dropdown

Service actions no longer accept a manually entered vin parameter. Instead, you must select the vehicle using the new device dropdown.

What This Means

  • The vin parameter is no longer supported
  • Any automations, scripts, or other references using vin must be updated
  • Service actions now require selecting the target vehicle from the device dropdown in the UI

How to Update Existing Automations or Scripts

  1. Open the automation, script, or other configuration that uses the service action
  2. Locate and remove the vin parameter from the service call
  3. After removing vin, the editor will switch from YAML mode back to UI mode
  4. In UI mode, select the appropriate vehicle from the device dropdown
  5. Save your changes

Full Changelog: v1.19.1...v2.0.1-beta.8