[bluetooth_proxy:439]: Only one API subscription is allowed at a time

drthanwho commented 1 year ago

The problem

Since I while my bluetooth sensors stopped comming through the esp bluetooth proxies to HA. On the other hand, on another HA that has bluetooth itself I can see the sensors comming through there so I know they are working.

I hadn't found and errrors on the esp logs but just today I found the one bellow.

[bluetooth_proxy:439]: Only one API subscription is allowed at a time

Which version of ESPHome has the issue?

2023.8.2

What type of installation are you using?

Home Assistant Add-on

Which version of Home Assistant has the issue?

No response

What platform are you using?

ESP32-IDF

Board

No response

Component causing the issue

bluetooth_proxy

Example YAML snippet

esp32:
  board: esp-wrover-kit
  framework:
    type: esp-idf

packages:
  wifi: !include common_substitutions/wifi.yaml
  device_base: !include common_substitutions/device_base.yaml

esp32_ble_tracker:
  scan_parameters:
    interval: 1100ms
    window: 1100ms
    active: false

bluetooth_proxy:
  active: false

Anything in the logs that might be useful for us?

No response

Additional information

No response

rikroe commented 1 year ago

I've seen the same when I tried debugging why one of my TRVs is not available anymore. However I do not know if it is the culprit or connected in any way.

I'm using active bluetooth proxy and esp32_ble_tracker with default settings.

danswett commented 3 months ago

I'm having this same issue and it's been going on for several months. I have three ESP32s set up as bluetooth proxies, and they'll work fine for a few days and then all of a sudden all my proxied bluetooth devices become unavailable. When I go pull logs from one of the ESPs they always have the error referred to in this ticket.

Here's the config from one of the ESPs:

esphome:
  name: pool-esp32
  friendly_name: Pool ESP32

esp32:
  board: esp32dev
  framework:
    type: esp-idf

esp32_ble_tracker:
  scan_parameters:
    # We currently use the defaults to ensure Bluetooth
    # can co-exist with WiFi In the future we may be able to
    # enable the built-in coexistence logic in ESP-IDF
    active: true

bluetooth_proxy:
  active: true

# Enable logging
logger:
  level: DEBUG

# Enable Home Assistant API
api:
  encryption:
    key: redacted

ota:
  platform: esphome
  password: redacted

wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password

I don't know what causes it to work again - rebooting the ESPs sometimes seems to fix it.

ssieb commented 3 months ago

You can't have 2 HA instances using the proxy at the same time. That sounds like the issue for the initial post at least.

evlo commented 1 month ago

can his be changed to have multiple HA connected to one bt proxy? With switch etc. it is not an issue As far as i know there is no way to even stop one HA from using just btproxy part of esphome device.

Currently I see only workaround as having multiple BT proxy esphome devices each connected to one server and at least one connected to secondary server would need to be just dedicated to bt proxifying.

ssieb commented 1 month ago

A switch is very different from the proxy. The BT proxy is very heavy and the current design is to do as little work as possible on the ESP. It doesn't do any processing of the packets. Managing multiple data streams would cause difficulty as would having to manage BT connections coming from multiple sources.

evlo commented 1 month ago

workarounds i came up with:

ble to mqtt
ble client for each device
dedicated ble proxy for each instance

so far I'm think most reliable and sustainable would be ble client

in my case i do not need any connections to the devices just read advertisements - for the time being - however my goal was to replace zigbee with ble device, but the development with the Bluetooth proxy makes me question that decision.

I do understand that my usecase with both local and remote server is quite rare.

esphome / issues