[BUG] <title>Blutooth error since version 2025.9.2-ls139

[chris-1243]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

Since version 2025.9.2-ls139, there is an error in my startup log regarding the bluetooth management

Expected Behavior

If capabilities are added to the compose file, not to see such error.

Steps To Reproduce

1. Update from 2025.9.1-ls138 to a higher tag (latest)
2. See the error above in the container log

Environment

- OS: Debian boowkworm, no VM, plain docker
- How docker service was installed: via apt repository, latest version (28.4.0)

CPU architecture

x86-64

Docker creation

sudo docker compose pull && sudo docker compose up -d


In my `docker-compose.yaml`, such capabilities are added


########################### SECRETS
secrets:
  ssl:
    file: $SECRETSDIR/homeassistant/certs/homeassistant.pem

########################### SERVICES
services:
  homeassistant:
    container_name: homeassistant
    image: linuxserver/homeassistant
    secrets:
      - source: ssl
        target: /etc/ssl/homeassistant.pem
    depends_on:
      mosquitto:
        condition: service_started
    environment:
      TZ: $TZ
      PUID: $PUID
      PGID: $PGID
    volumes:
      - /var/run/dbus:/var/run/dbus:ro # Bluetooth adapter
      - $DOCKERDIR/automation/homeassistant:/config
    network_mode: host
    # Bluetooth adapter / "PING (ICMP)" capabilities
    cap_add:
      - NET_ADMIN
      - NET_RAW
    # Uncomment those lines if the "PING (ICMP)" integration is not active
#    security_opt:
#      - no-new-privileges=true
    restart: always

Container logs

homeassistant  | [migrations] started
homeassistant  | [migrations] no migrations found
homeassistant  | ───────────────────────────────────────
homeassistant  |
homeassistant  |       ██╗     ███████╗██╗ ██████╗
homeassistant  |       ██║     ██╔════╝██║██╔═══██╗
homeassistant  |       ██║     ███████╗██║██║   ██║
homeassistant  |       ██║     ╚════██║██║██║   ██║
homeassistant  |       ███████╗███████║██║╚██████╔╝
homeassistant  |       ╚══════╝╚══════╝╚═╝ ╚═════╝
homeassistant  |
homeassistant  |    Brought to you by linuxserver.io
homeassistant  | ───────────────────────────────────────
homeassistant  |
homeassistant  | To support LSIO projects visit:
homeassistant  | https://www.linuxserver.io/donate/
homeassistant  |
homeassistant  | ───────────────────────────────────────
homeassistant  | GID/UID
homeassistant  | ───────────────────────────────────────
homeassistant  |
homeassistant  | User UID:    1000
homeassistant  | User GID:    1000
homeassistant  | ───────────────────────────────────────
homeassistant  | Linuxserver.io version: 2025.9.3-ls141
homeassistant  | Build-date: 2025-09-17T02:02:22+00:00
homeassistant  | ───────────────────────────────────────
homeassistant  |
homeassistant  | **** New container detected, fixing python package permissions. This may take a while. ****
homeassistant  | Setting permissions
homeassistant  | [custom-init] No custom files found, skipping...
homeassistant  | 2025-09-18 08:55:47.230 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration swissweather which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
homeassistant  | 2025-09-18 08:55:47.230 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration adaptive_lighting which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
homeassistant  | 2025-09-18 08:55:47.231 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
homeassistant  | Connection to localhost (::1) 8123 port [tcp/*] succeeded!
homeassistant  | [ls.io-init] done.
homeassistant  | 2025-09-18 08:55:49.950 ERROR (MainThread) [habluetooth.manager] Missing required permissions for Bluetooth management: Missing NET_ADMIN/NET_RAW capabilities for Bluetooth management. Automatic adapter recovery is unavailable. Add NET_ADMIN and NET_RAW capabilities to the container to enable it

[github-actions]

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

[hia-007]

Hello,
I am also encoutering same issue since version 2025.9.1.

Here is my docker-compose file:

home-assistant:
    container_name: home-assistant
    image: lscr.io/linuxserver/homeassistant:2025.9.3
    environment:
      - PUID=1000
      - PGID=1000
    ports:
      - 8123:8123                   # Web interface
    volumes:
      - ./hass/config:/config
      - ./hass/data:/mnt/Data
      - ./hass/user:/home/user
      - ./hass/media:/mnt/Media
      - /var/run/dbus:/var/run/dbus:ro
      - /run/dbus:/run/dbus:ro
      - /etc/timezone:/etc/timezone:ro
      - /var/run/docker.sock:/var/run/docker.sock
    cap_add:
      - NET_ADMIN
      - NET_RAW
    restart: unless-stopped
    privileged: true
    network_mode: host

System information: Debian Trixie, ARM64 running on Raspberry Pi 4, Docker Engine version 28.4.0.

I also tried with the following linuxserver home assistant versions - 2025.9.1, 2025.9.2, 2025.9.3 - all giving same error.

Apparently this was an issue on the Home-Assistant Core side also (home-assistant/core#151738), but it has been resolved on their end.

[aptalca]

I'm also seeing it on my instance. It's likely an issue with upstream's detection mechanism. I'll have to dig into that. I'll also have to check whether it's an issue in their container as well

[chris-1243]

@aptalca Thanks for the fix.

No more errors on 2025.9.4-ls143

[hia-007]

Works perfect. Thanks for the quick fix!