2.3.0

New Features

Charging Manager Role

• New role option: Added the possibility to use the Charging Manager role for enhanced security
• Recommended by default: Charging Manager is now the recommended and default role for new installations
• Limited access: Charging Manager role provides secure, limited access suitable for charging management (read vehicle data and authorize charging-related commands: wake, charge_start, charge_stop, set_charging_amps)

In-Memory Log Storage and Web Log Viewer

• New logging system: Introduced a in-memory log storage system that captures all internal logging
• Web-based log viewer: Access logs directly from the dashboard at /logs with a modern, responsive interface

Recommended Actions

Review your active key role: If you're using the Owner role, consider switching to Charging Manager if you only need charging-related functions. Review the updated security recommendations in the README.

What's Changed

• Add multi-role key management and migration support by @wimaha in #144
• Add in-memory log storage and web log viewer by @wimaha in #145
• Default key role to charging_manager for improved security by @wimaha in #146
• Improve log viewer mobile responsiveness and styling by @wimaha in #147
• Update docs with security recommendations and new screenshots by @wimaha in #148

Full Changelog: 2.2.1...2.3.0

2.2.1

In version 2.2.1, bugs are fixed and the reliability of the connection is improved. Please also note the change description for version 2.2.0.

What's Changed

• Refactor BLE scan context for reliable timeout and fix context cancellation handling in BLE connection logic by @wimaha in #142
• Allow retry on BLE scan timeout in TryConnectToVehicle by @wimaha in #143
• Update README with troubleshooting section by @wimaha in #141

Full Changelog: 2.2.0...2.2.1

2.2.0

Breaking Changes

• Vehicles are no longer automatically woken up before fetching data ("vehicle_data"). This is a solution for evcc-io/evcc#25707. Note: If you are using the TeslaBLE template (https://docs.evcc.io/docs/devices/vehicles#tesla-ble), you do not need to make any further adjustments. The new version of the proxy works with it without issues.

Other

• Introduces per-endpoint, per-VIN in-memory caching for VehicleData API responses, configurable via the new vehicleDataCacheTime environment variable (default: 30 seconds) (0f1a219)
• Bump Go version from 1.24 to 1.25

What's Changed

• All changes by @wimaha in #139

Full Changelog: 2.1.3...2.2.0

2.1.3

What's Changed

• Add Version API Endpoint by @wimaha in #121

Full Changelog: 2.1.2...2.1.3

2.1.2

What's Changed

• Fix a bug with ConnectionCtx (If an HTTP request was received just before the Bluetooth connection timeout (29 seconds), the request was aborted due to the timeout and not retried with a new connection.) by @wimaha in #115 (fixes #102)
• Log outputs cleaned up by @wimaha in #116

Full Changelog: 2.1.1...2.1.2

2.1.1

What's Changed

• response for body controller state and check vehicle presence by @wimaha in #113
  • Response for body controller state optimization. (fixes #87)
  • Check vehicle presence: Scan for vehicle BLE advertisements to check for vehicle presence and abort quickly if none are detected (from #95) Thanks to @Lenart12

Full Changelog: 2.1.0...2.1.1

2.1.0

What's Changed

• API context propagation by @Lenart12 in #85
• Bump Go-Version and dependencies for security reasons by @wimaha in #112

Full Changelog: 2.0.3...2.1.0

2.0.3

What's Changed

• Add cache control configuration and initialization by @Lenart12 in #81
• Error on unrecognized command by @wimaha in #74
• Start creating tests by @wimaha in #75

New Contributors

• @Lenart12 made their first contribution in #81

Full Changelog: 2.0.2...2.0.3

2.0.2

What's Changed

• fix ARMv6 build with goarm= by @AloisKlingler in #70
• • So Issue #32 is finally fixed
• Optimized Makefile and Dockerfile by @wimaha in #71
• Create Default Workflow by @wimaha in #72
• Fix linting errors by @wimaha in #73

New Contributors

• @AloisKlingler made their first contribution in #70

Full Changelog: 2.0.1...2.0.2

2.0.1

What's Changed

• Optimized status by @wimaha in #69
• New commands by @aneisch in #68

New Contributors

• @aneisch made their first contribution in #68

Full Changelog: 2.0.0...2.0.1