Connection problems with Blanco Choice All

Hi 👋
first of all, thank you for this project!

Unfortunately, I’m currently unable to connect my Blanco Choice.All to the Homeasistant. I’ve tried multiple attempts, but the connection process always writes "Device not found. Please ensure the Blanco Unit is powered on and in Bluetooth range".

Important note:
I was able to successfully connect to the Blanco Choice.All using my smartphone, so Bluetooth itself seems to be working correctly on the device.

However, I’m not able to connect to it via this project / Home Assistant.

Observations

The device does appear in Home Assistant
Under Bluetooth → Advertisement Monitor (Bluetooth integration), the Blanco Choice.All is visible
Despite being advertised and detected, the connection / pairing does not succeed

What I’ve tried so far

Restarted Home Assistant
Restarted the Blanco Choice.All
Repeated the pairing process multiple times
Verified Bluetooth is enabled and working
Tested Bluetooth connection with a smartphone (successful)

Expected behavior
The Blanco Choice.All should be connectable once it is detected via Bluetooth advertisements.

Actual behavior
The device is visible in the Bluetooth advertisement monitor but cannot be connected or paired.

Environment:

Device: Blanco Choice.All
Home Assistant: 2026.1.0

If you need logs, debug output, or testing on my side, I’m happy to help.
Maybe this is a missing feature or a small compatibility issue that could be solved and shared with the community.

Thanks a lot for your support! 🙌

PS:
We can also continue the discussion in German if that’s easier 🙂
I just decided to open the issue in English so it’s accessible for more people in the community.

@FaerberTorben

@FaerberTorben
I speak German, but let's stay with English.

I am facing the same issues with my Blanco Choice. All, after about 1 minute, I get the error message:

Failed to connect to the device: CHOICE.All-033 - 34:xx Failed to connect after 7 attempt(s): failed to discover services, device disconnected

Just like you, I can see it advertised, and my app is connected, but HA can't connect.
I even unpaired the app to make sure its not limited to conenct to one App at the same time.

Would be lovely to get it work,

BR
Joseph

HA Log

This error originated from a custom integration.

Logger: custom_components.blanco_unit.config_flow
Source: custom_components/blanco_unit/config_flow.py:139
integration: Blanco Unit (documentation, issues)
First occurred: 22:02:33 (4 occurrences)
Last logged: 22:16:17

Unexpected error during validation
Traceback (most recent call last):
  File "/usr/local/lib/python3.13/site-packages/bleak_retry_connector/__init__.py", line 474, in establish_connection
    await client.connect(
    ...<2 lines>...
    )
  File "/usr/local/lib/python3.13/site-packages/habluetooth/wrappers.py", line 364, in connect
    await super().connect(**kwargs)
  File "/usr/local/lib/python3.13/site-packages/bleak/__init__.py", line 623, in connect
    await self._backend.connect(self._pair_before_connect, **kwargs)
  File "/usr/local/lib/python3.13/site-packages/bleak/backends/bluezdbus/client.py", line 355, in connect
    await self._get_services(
        dangerous_use_bleak_cache=dangerous_use_bleak_cache
    )
  File "/usr/local/lib/python3.13/site-packages/bleak/backends/bluezdbus/client.py", line 707, in _get_services
    self.services = await manager.get_services(
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^
        self._device_path, dangerous_use_bleak_cache, self._requested_services
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/usr/local/lib/python3.13/site-packages/bleak/backends/bluezdbus/manager.py", line 719, in get_services
    await self._wait_for_services_discovery(device_path)
  File "/usr/local/lib/python3.13/site-packages/bleak/backends/bluezdbus/manager.py", line 889, in _wait_for_services_discovery
    raise BleakError("failed to discover services, device disconnected")
bleak.exc.BleakError: failed to discover services, device disconnected

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/config/custom_components/blanco_unit/config_flow.py", line 139, in validate_input
    client = await establish_connection(
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ...<3 lines>...
    )
    ^
  File "/usr/local/lib/python3.13/site-packages/bleak_retry_connector/__init__.py", line 582, in establish_connection
    _raise_if_needed(name, device.address, exc)
    ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/bleak_retry_connector/__init__.py", line 440, in _raise_if_needed
    raise BleakConnectionError(msg) from exc
bleak_retry_connector.BleakConnectionError: CHOICE.All-033 - 34:xx:xx...: Failed to connect after 5 attempt(s): failed to discover services, device disconnected

@peppi911

Hey @peppi911
What do you think about us chatting and trying to fix the problem?

Maybe on Discord?

@FaerberTorben

@FaerberTorben

I don't have an Android tool and not much experience with mobile apps and Python.
I'm a Java (SpringBoot), iOS guy :/

But I'm not developing myself much anymore, as I opted for cloud infrastructure.
Additionally, I'm not very experienced with reverse engineering.

But it's obvious that @Nailik would need support and some contributors.
Especially as he doesn't have all the Blanco systems to test.

BR
Joseph

@FaerberTorben

Hi sorry i am just seeing this now.
@FaerberTorben debug log would be helpful to see if it is the same error that @peppi911 reported.

Also how do you use it? BLE stick / esphome proxy? What version of HA do you use? Is it within HAOS or some custom docker setup?

Unfortunately the issues seems to be within the connection attempt from bleak and thats hard to guess.

Best would be probably if you could test it locally, i'll add my CLI testing tool later. Then it's at least possible to see if it is a problem in combination with HomeAssistant or a specific bleak version.

You could also use NRF Connect to check which services the device advertises.

Habe leider auch das Problem, dass keine Verbindung aufgebaut werden kann.

Failed to connect to the device: SODA-074 - 8C:4B:14:4A:BD:1D: Failed to connect after 4 attempt(s): failed to discover services, device disconnected

Homeassistent/Proxmox und BLE Stick via usb passthrough.

Blanco Drink.soda gerät

Log:
Dieser Fehler stammt von einer benutzerdefinierten Integration

Logger: custom_components.blanco_unit.config_flow
Quelle: custom_components/blanco_unit/config_flow.py:139
Integration: Blanco Unit (Dokumentation, Probleme)
Erstmals aufgetreten: 08:47:37 (4 Vorkommnisse)
Zuletzt protokolliert: 10:09:59

Unexpected error during validation
Traceback (most recent call last):
File "/usr/local/lib/python3.13/site-packages/bleak_retry_connector/init.py", line 474, in establish_connection
await client.connect(
...<2 lines>...
)
File "/usr/local/lib/python3.13/site-packages/habluetooth/wrappers.py", line 364, in connect
await super().connect(**kwargs)
File "/usr/local/lib/python3.13/site-packages/bleak/init.py", line 623, in connect
await self._backend.connect(self._pair_before_connect, **kwargs)
File "/usr/local/lib/python3.13/site-packages/bleak/backends/bluezdbus/client.py", line 355, in connect
await self._get_services(
dangerous_use_bleak_cache=dangerous_use_bleak_cache
)
File "/usr/local/lib/python3.13/site-packages/bleak/backends/bluezdbus/client.py", line 707, in _get_services
self.services = await manager.get_services(
^^^^^^^^^^^^^^^^^^^^^^^^^^^
self._device_path, dangerous_use_bleak_cache, self._requested_services
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "/usr/local/lib/python3.13/site-packages/bleak/backends/bluezdbus/manager.py", line 719, in get_services
await self._wait_for_services_discovery(device_path)
File "/usr/local/lib/python3.13/site-packages/bleak/backends/bluezdbus/manager.py", line 889, in _wait_for_services_discovery
raise BleakError("failed to discover services, device disconnected")
bleak.exc.BleakError: failed to discover services, device disconnected

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File "/config/custom_components/blanco_unit/config_flow.py", line 139, in validate_input
client = await establish_connection(
^^^^^^^^^^^^^^^^^^^^^^^^^^^
...<3 lines>...
)
^
File "/usr/local/lib/python3.13/site-packages/bleak_retry_connector/init.py", line 582, in establish_connection
_raise_if_needed(name, device.address, exc)
~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/bleak_retry_connector/init.py", line 440, in _raise_if_needed
raise BleakConnectionError(msg) from exc
bleak_retry_connector.BleakConnectionError: SODA-074 - 8C:4B:14:4A:BD:1D: Failed to connect after 6 attempt(s): failed to discover services, device disconnected

I quickly added test_cli.py so you can test on a local machine. I currently test on macos which uses a different bluetooth backend than linux. maybe some of you can test the test_cli.py on macos to verify if Blanco Choice.All would connect?

I tested it with Linux on my PI and connection to my device works

Bleak Version: 2.1.1
Python Version: 3.13.5
Platform: linux
BLE: BleakBackend.BLUEZ_DBUS

latest home assistant uses (https://github.com/home-assistant/core/blob/dev/homeassistant/package_constraints.txt)

bleak-retry-connector==4.4.3
bleak==2.0.0

but i couldn't reproduce the issue with those versions either

Kann ich leider nicht testen

Hey guys, I think I found something important...

While scanning for the Blanco Choice in Home Assistant, I noticed that it appears to be using a randomized MAC address.

In the device list it shows up as:
XX:XX:XX:XX:XX:XX Choice-All (Randomized Mac) as u can see in the Image

That would explain why HA can see the device, but fails when trying to connect or discover, the device identity is basically not stable.

Many BLE devices use MAC randomization for privacy, so this might be a firmware thing on the Blanco side.

Maybe the integration needs to connect based on a stable identifier (service UUID / manufacturer data).

Hope this helps! 🙌🏻

@FaerberTorben

@FaerberTorben thanks that's an interesting find.
The integration could use the service id but it would be problematic if another device exposes the same id. Then it would need to loop over all devices exposing this service id and try to connect with the pin and check if it is correct. I'd also like to add a function to check if the correct device is connected in the setup flow.

The integration should then store the serial number and use this in the future to check if the correct device is connected.

Could you by any chance try the test_cli.py first to see if this works?
Also can you check with NRF connect? maybe the device exposes some identifier directly without connecting (otherwise the blanco app would have the same problem).

Hi, I have also a Blanco Choice All and tried this new integration.

I can´t use BT directly on the HA VM, so I installed a ESP-Home BT proxy on an ESP32dev.

I can connect to the Blance and it is connected, but all other sensors, switch and so on can´t read from the device.
From debug log I can see, that the bt handshake with the pin is working and i see some communication.

What I also see, the integration is looping between connected and completed unavailable.

The MAC address is on my device always the same, we can also pair different Android phones at the same time.

Blanco_debuglog.txt

@thommy2312

hi @thommy2312 thanks for the information - however i moved it to a new issue because it's more about the protocol and this issue is about connecting at all.

HI guys, please try again with 0.0.5

I update so that the initial connect (when it was discovered automatically by homeassistant) uses the passed ble device directly instead of scanning for the mac on its own. This should hopefully fix the connection issues.
The logic is also included in bootup and reconnect.

Hello,

Soeben mit 0.0.5 getestet, leider ohne Erfolg:

Dieser Fehler stammt von einer benutzerdefinierten Integration

Logger: custom_components.blanco_unit.config_flow
Quelle: custom_components/blanco_unit/config_flow.py:164
Integration: Blanco Unit (Dokumentation, Probleme)
Erstmals aufgetreten: 17:03:10 (1 Vorkommnis)
Zuletzt protokolliert: 17:03:10

Unexpected error during validation
Traceback (most recent call last):
File "/usr/local/lib/python3.13/site-packages/bleak_retry_connector/init.py", line 474, in establish_connection
await client.connect(
...<2 lines>...
)
File "/usr/local/lib/python3.13/site-packages/habluetooth/wrappers.py", line 364, in connect
await super().connect(**kwargs)
File "/usr/local/lib/python3.13/site-packages/bleak/init.py", line 623, in connect
await self._backend.connect(self._pair_before_connect, **kwargs)
File "/usr/local/lib/python3.13/site-packages/bleak/backends/bluezdbus/client.py", line 355, in connect
await self._get_services(
dangerous_use_bleak_cache=dangerous_use_bleak_cache
)
File "/usr/local/lib/python3.13/site-packages/bleak/backends/bluezdbus/client.py", line 707, in _get_services
self.services = await manager.get_services(
^^^^^^^^^^^^^^^^^^^^^^^^^^^
self._device_path, dangerous_use_bleak_cache, self._requested_services
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "/usr/local/lib/python3.13/site-packages/bleak/backends/bluezdbus/manager.py", line 719, in get_services
await self._wait_for_services_discovery(device_path)
File "/usr/local/lib/python3.13/site-packages/bleak/backends/bluezdbus/manager.py", line 889, in _wait_for_services_discovery
raise BleakError("failed to discover services, device disconnected")
bleak.exc.BleakError: failed to discover services, device disconnected

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File "/config/custom_components/blanco_unit/config_flow.py", line 164, in validate_input
client = await establish_connection(
^^^^^^^^^^^^^^^^^^^^^^^^^^^
...<3 lines>...
)
^
File "/usr/local/lib/python3.13/site-packages/bleak_retry_connector/init.py", line 582, in establish_connection
_raise_if_needed(name, device.address, exc)
~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/bleak_retry_connector/init.py", line 440, in _raise_if_needed
raise BleakConnectionError(msg) from exc
bleak_retry_connector.BleakConnectionError: SODA-074 - 8C:4B:14:4A:BD:1D: Failed to connect after 6 attempt(s): failed to discover services, device disconnected

Please enable debug logging, maybe this gives more info.
Also check if you have the latest firmware in the official app and post the information here.

I also updated to 120s connection timeout in 0.0.6.

you can try my custom version. i also had a lot of bluetooth problems and they are now all fixed, but i did so many changes that it's hard to create a merge request with a fix. i will not maintain my custom version. if it works for you we maybe should find a way to bring the fixes into this version.
https://github.com/Kotlin-Native/blanco_unit

Hi Nailik,

afterfirst of all a big THANK YOU - I can confirm that the BLANCO CHOICE.All is working with your Home Assistant integration.

My setup:
Device: BLANCO CHOICE.All
Integration version: 0.0.10
Home Assistant: 2026.8.3
Main Controller firmware: R161406
Communication Controller firmware: 1.5.10
Connection via Home Assistant Bluetooth / ESPHome Bluetooth proxy

The integration successfully connects to the CHOICE.All and provides the CHOICE.All-specific entities, including:
I have also been able to read the device status and settings reliably.

So from my side, I would consider CHOICE.All confirmed working, at least with this firmware/version combination.

One thing I noticed: the BLANCO UNIT app provides detailed water-consumption statistics (daily/weekly/monthly/yearly). It would be great if these statistics could eventually also be exposed by the Home Assistant integration. I would be happy to help test this or provide protocol data if needed.

Thanks again for the great work!
Martin

One thing I noticed: the BLANCO UNIT app provides detailed water-consumption statistics (daily/weekly/monthly/yearly). It would be great if these statistics could eventually also be exposed by the Home Assistant integration. I would be happy to help test this or provide protocol data if needed.

The data is accumulated in the blanco.unit server. it would only be possible to query the faucet very often and then calculate the data inside home assistant. Unfortunately my blanco device (drink.soda) does not post information onto bluetooth on every status change (e.g. when dispensing water), maybe they changed it for choice.all, would be interesting to know.

@Kotlin-Native

you can try my custom version. i also had a lot of bluetooth problems and they are now all fixed, but i did so many changes that it's hard to create a merge request with a fix. i will not maintain my custom version. if it works for you we maybe should find a way to bring the fixes into this version. https://github.com/Kotlin-Native/blanco_unit

Thanks so much! You're version works for me with a Blanco Choice.ALL, no ESP32 or whatever Bluetooth proxy involved, direct BLE connection from the Home Assistant host (Gigabyte Brix GB-BNi3-N305 with Bluetooth). Latest release from this repo (0.0.11) does not work (as others reported, after entering PIN the connection cannot be established).

I will try to separate the changes (if feasible) which you made @Kotlin-Native and then apply one after another to identify what actually fixes the connection issue....if the changes can be somewhat grouped and separated.

I will try to separate the changes (if feasible) which you made @Kotlin-Native and then apply one after another to identify what actually fixes the connection issue....if the changes can be somewhat grouped and separated.

That would be very nice, i'd like to understand what's causing the problem and providing a fix.

I will try to separate the changes (if feasible) which you made @Kotlin-Native and then apply one after another to identify what actually fixes the connection issue....if the changes can be somewhat grouped and separated.

The fix for the connection itself was already made long time ago here:
https://github.com/Nailik/blanco_unit/pull/12/changes

but with that version i had problems every week with leaking bluetooth connection that forced me to restart my home assistant pc. that why i made alot of more changes in communication to solve that.

Hi, I have a Blanco Drink.Soda. Everything ran stably with version 0.0.10. It was a bit glitchy at first—entities would appear and disappear—but that was likely due to the Blanco unit itself. After a hard reboot (unplugging it), it remained stable for weeks. I updated to 0.0.11 this morning, but afterwards, none of the entities were available. Reboots, etc., didn't help. I deleted the integration and re-enrolled it, but got the same result. I’ve now reverted to 0.0.10. Just wanted to share this info :) Thanks for your great work. Greetings from Stuttgart.

@mt0711

@mt0711 thanks for the report. This is a regression from #21 and not specific to the Drink.Soda. The first refresh now runs in the background, so platform setup sees no data yet and binary_sensor, select and sensor abort with 'NoneType' object has no attribute 'device_type'; only button and number are created. Staying on 0.0.10 is the right workaround until the fix is released. Fix in #22.

@mt0711

@mt0711 the fix is released as 0.0.12, so you can update from 0.0.10 again and the missing entities will come back.

Fix BLE connection leaks and pair during setup

in a desparate attempt to fix the still present issue with the Choice All i did some changes to the connection/retry logic in Release 0.0.14 and also create a test release to handle different MRU sized packages.

I hope someone can test that and report back with logs.

@Nailik

@Nailik as described here:
https://github.com/Nailik/blanco_unit/pull/24#issuecomment-6371347020
I tested 0.0.14.
Pairing works now with Choice All.
I have some bluetooth disconnects sometimes.
I will test 0.0.14 the next days and give an update in a few days

@Vurgus

@Vurgus can you please share some details about you devices?
Are you using a Bluetooth proxy?

I have just updated to 0.0.14.

Prior to the update my integration was running flawless using a ble proxy.

After updating i deactivated my ble proxy and tried to reconnect the choice all via the integrated bluetooth of the cm5 module in my home assistant yellow. Didn't work. Unfortunately.

Hope the log helps.

Logger: custom_components.blanco_unit.config_flow
Quelle: custom_components/blanco_unit/config_flow.py:227
Integration: Blanco Unit (Dokumentation, Probleme)
Erstmals aufgetreten: 23:09:12 (4 Vorkommnisse)
Zuletzt protokolliert: 23:12:44

Communication with the device failed: BleakConnectionError: CHOICE.All-242 - EC:C9:FF:B9:FA:B2: Failed to connect after 4 attempt(s): [org.bluez.Error.AuthenticationFailed] Authentication Failed
Communication with the device failed: BleakConnectionError: CHOICE.All-242 - EC:C9:FF:B9:FA:B2: Failed to connect after 4 attempt(s): [org.bluez.Error.AuthenticationCanceled] Authentication Canceled

For now i will reactivate the ble proxy.

@MarkusMas

@MarkusMas can you enable the debug log and check if there is better/more info?

@Nailik

Hello @Nailik, i have just repeated the test.

For that i have removed the home assistant yellow from the rack and placed it right next (about 1 m) to the blanco unit to rule out any connection issues related to the distance (under usual conditions my ble proxy sits right next to the home assistant yellow in the rack). I then deactivated the ble proxy by deactivation the bluetooth adapter and the ems esp integration in home assistant. then i activated the integrated bluetooth adapter and restarted home assistant.

After the full restart i went to the connectivity settings (bluetooth map) to make sure the bluetooth adapter can see the blanco unit. It was the case.

Then i went to the existing blanco integration and clicked reconfigure.

I got an error message.

Then i tried to add a new device in the same intagration and entered the name "choice.test" manually. I tried twice and got the same error twice.

2026-10-27 13:26:21.441 ERROR (MainThread) [custom_components.blanco_unit.config_flow] Communication with the device failed: BleakConnectionError: CHOICE.All-242 - EC:C9:FF:B9:FA:B2: Failed to connect after 4 attempt(s): [org.bluez.Error.AuthenticationFailed] Authentication Failed

i have attached the debug log you were asking for.

home-assistant_blanco_unit_2026-10-27T12-26-24.450Z.log

..one more thing that i am not sure about: i think in previous versions the mac adress and name was auto detected. today i had to manually type the mac-adress and name. is this on purpose?

Navigation Menu

Repository navigation

Connection problems with Blanco Choice All #2

42 remaining items

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Connection problems with Blanco Choice All #2

Description

Activity

FaerberTorben commented on Jan 10, 2026

peppi911 commented on Jan 22, 2026

FaerberTorben commented on Jan 22, 2026

peppi911 commented on Jan 23, 2026

Nailik commented on Jan 23, 2026

EAFSL commented on Jan 23, 2026

Nailik commented on Jan 23, 2026

EAFSL commented on Jan 23, 2026

FaerberTorben commented on Jan 24, 2026

Nailik commented on Jan 24, 2026

thommy2312 commented on Jan 26, 2026

Nailik commented on Jan 27, 2026

Nailik commented on Jan 27, 2026

EAFSL commented on Jan 27, 2026

Nailik commented on Jan 27, 2026

42 remaining items

Kotlin-Native commented on Aug 15, 2026

zwischenlichten commented on Sep 2, 2026

Nailik commented on Sep 3, 2026

alxflam commented on Sep 3, 2026

Nailik commented on Sep 3, 2026

Kotlin-Native commented on Sep 4, 2026

mt0711 commented on Sep 4, 2026

lackas commented on Sep 4, 2026

lackas commented on Sep 5, 2026

Nailik commented on Oct 18, 2026

Vurgus commented on Oct 23, 2026

MarkusMas commented on Oct 23, 2026

Nailik commented on Oct 23, 2026

MarkusMas commented on Oct 27, 2026

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions