Homeassistant authorization callback error with 0.211.1

[xMatzeDE]

Describe the bug

Authorize homeassistant, always end up in "callback error"

Steps to reproduce

1. Open Authorize to Homeassistant from "Burger menu" or from settings
2. Login to Home Assistant with Admin credentials
3. After 3-4 seconds it end up with callback error

Configuration details

root@evcc:~# evcc dump --cfg
[main  ] INFO 2025/12/10 21:25:33 using config file: /etc/evcc.yaml
[main  ] INFO 2025/12/10 21:25:33 using sqlite database: /var/lib/evcc/evcc.db
[mercedes] DEBUG 2025/12/10 21:25:38 identity.NewIdentity - database token found
[lp-1  ] DEBUG 2025/12/10 21:25:38 charge total import: 20137.875kWh

Version: `0.211.1`



# open evcc at http://evcc.local:7070
network:
  schema: http
  host: evcc.home.arpa # .local suffix announces the hostname on MDNS
  port: 7070

database:
  type: sqlite
  dsn: /var/lib/evcc/evcc.db

log: debug
levels:
  cache: error


- type: template
#  template: offline
  template: homeassistant
  uri: http://homeass.home.arpa:8123
  soc: sensor.vr3uhzkxznt094561_batterie
  name: e208
  title: Peugeot e208
  capacity: 50
  icon: car
  phases: 3
  mode: pv
  minCurrent: 6
  maxCurrent: 16
  identifiers:
  - *****
  welcomecharge:

Log details

nslookup evcc.home.arpa
Server: adguard.home.arpa
Address: 192.168.100.11

Name: evcc.home.arpa
Address: 192.168.100.254

nslookup homeass.home.arpa
Server: adguard.home.arpa
Address: 192.168.100.11

Name: homeass.home.arpa
Address: 192.168.100.10

[homeassistant] TRACE 2025/12/10 21:30:30 POST http://homeass.home.arpa:8123/auth/token
[homeassistant] TRACE 2025/12/10 21:30:35 client_id=http%3A%2F%2F192.168.100.254%3A7070&code=7736fa0007ed4b15ab982999122f7b07&code_verifier=ToAsdyQNqGzkfoSlz7i2ZJfGZmlZ6y_pKJ75oAFCzb0&grant_type=authorization_code&redirect_uri=http%3A%2F%2F192.168.100.254%3A7070%2Fproviderauth%2Fcallback

What type of operating system or environment does evcc run on?

Linux

External automation

• I have made sure that no external automation like HomeAssistant or Node-RED is active or accessing any of the mentioned devices when this issue occurs.

Nightly build

• I have verified that the issue is reproducible with the latest nightly build

Version

root@evcc:~# evcc -v evcc version 0.211.1