Still not able to setup new Besen integration

The problem

Following up on issue: https://github.com/home-assistant/core/issues/181210.

After updating to Home Assistant 2026.9.1, I am still unable to configure my Besen BS20. After entering the PIN, the setup process eventually fails with the following error:

Can't connect

During the setup process, my ESPHome Bluetooth Proxy establishes and maintains an active connection to the charger:

I was previously (and am still) using the evseMQTT add-on connected to an MQTT broker. This has always worked reasonably well, although not perfectly due to an unstable Bluetooth connection using the local Bluetooth adapter.

For testing the new Besen integration, I stopped the evseMQTT add-on and disabled the Besen MQTT device. I also disabled Bluetooth on my phone to prevent the EVSE phone app from connecting to the charger, and power-cycled the charger.

Unfortunately, none of these actions made any difference.

The ESPHome Bluetooth Proxy is configured with active connections and 3 connection slots. During the Besen setup process, the connection monitor shows 1/3 active connections.

So it appears that the Bluetooth connection itself is established successfully, but the Besen login/handshake does not complete.

Also see relevant log information.

What version of Home Assistant Core has the issue?

core-2026.9.1

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Besen

Link to integration documentation on our website

https://www.home-assistant.io/integrations/besen

Diagnostics information

No response

Example YAML snippet

Anything in the logs that might be useful for us?

Logger: homeassistant.components.besen.config_flow
Bron: components/besen/config_flow.py:101
Integratie: Besen (documentatie, problemen)
Eerst voorgekomen: 16:15:58 (4 gebeurtenissen)
Laatst gelogd: 20:41:29

Besen login did not complete; retrying a fresh Bluetooth connection in 5 seconds (attempt 1/3)

Additional information

No response

Start at components/besen/config_flow.py:101 and review the setup flow around the logged retry message. Reproduce the Besen setup with the Bluetooth Proxy and inspect the relevant logs; done means the PIN login and handshake complete successfully instead of ending with “Can't connect.”