debugfs: File 'le_min_key_size' in directory 'hci0' already present!

Describe the bug Bluetooth distances stop being reported after some time, only reboot fixes the issue.

To reproduce cluster with 4 nodes - distances stop being reported. API response (or MQTT updates) stop including distances reboot to resolve

Relevant logs Log output that correlates to the bug. You can get debug output with room-assistant -v.

dmesg -T From pizero using ethernet hat:

[Mon Dec 14 21:48:42 2020] random: crng init done
[Mon Dec 14 21:48:42 2020] random: 7 urandom warning(s) missed due to ratelimiting
[Mon Dec 14 21:48:42 2020] 8021q: 802.1Q VLAN Support v1.8
[Mon Dec 14 21:48:42 2020] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[Mon Dec 14 21:48:43 2020] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[Mon Dec 14 21:48:43 2020] uart-pl011 20201000.serial: no DMA platform data
[Mon Dec 14 21:48:44 2020] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[Mon Dec 14 21:48:44 2020] r8152 1-1.4:1.0 eth0: carrier on
[Mon Dec 14 21:48:44 2020] Adding 102396k swap on /var/swap.  Priority:-2 extents:1 across:102396k SSFS
[Mon Dec 14 21:48:48 2020] Bluetooth: Core ver 2.22
[Mon Dec 14 21:48:48 2020] NET: Registered protocol family 31
[Mon Dec 14 21:48:48 2020] Bluetooth: HCI device and connection manager initialized
[Mon Dec 14 21:48:48 2020] Bluetooth: HCI socket layer initialized
[Mon Dec 14 21:48:48 2020] Bluetooth: L2CAP socket layer initialized
[Mon Dec 14 21:48:48 2020] Bluetooth: SCO socket layer initialized
[Mon Dec 14 21:48:48 2020] Bluetooth: HCI UART driver ver 2.3
[Mon Dec 14 21:48:48 2020] Bluetooth: HCI UART protocol H4 registered
[Mon Dec 14 21:48:48 2020] Bluetooth: HCI UART protocol Three-wire (H5) registered
[Mon Dec 14 21:48:48 2020] Bluetooth: HCI UART protocol Broadcom registered
[Mon Dec 14 21:48:49 2020] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[Mon Dec 14 21:48:49 2020] Bluetooth: BNEP filters: protocol multicast
[Mon Dec 14 21:48:49 2020] Bluetooth: BNEP socket layer initialized
[Mon Dec 14 21:48:58 2020] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[Mon Dec 14 21:48:58 2020] Bridge firewalling registered
[Mon Dec 14 21:57:52 2020] cgroup: cgroup: disabling cgroup2 socket matching due to net_prio or net_cls activation
[Mon Dec 14 22:23:13 2020] Bluetooth: hci0: link tx timeout
[Mon Dec 14 22:23:13 2020] Bluetooth: hci0: killing stalled connection 71:5b:45:12:2f:06
[Mon Dec 14 22:33:00 2020] Bluetooth: hci0: link tx timeout
[Mon Dec 14 22:33:00 2020] Bluetooth: hci0: killing stalled connection 6f:9f:6c:bf:96:cd
[Tue Dec 15 00:37:29 2020] debugfs: File 'le_min_key_size' in directory 'hci0' already present!
[Tue Dec 15 00:37:29 2020] debugfs: File 'le_max_key_size' in directory 'hci0' already present!
[Tue Dec 15 01:11:58 2020] debugfs: File 'le_min_key_size' in directory 'hci0' already present!
[Tue Dec 15 01:11:58 2020] debugfs: File 'le_max_key_size' in directory 'hci0' already present!
[Tue Dec 15 01:27:09 2020] debugfs: File 'le_min_key_size' in directory 'hci0' already present!
[Tue Dec 15 01:27:09 2020] debugfs: File 'le_max_key_size' in directory 'hci0' already present!
[Tue Dec 15 01:35:23 2020] debugfs: File 'le_min_key_size' in directory 'hci0' already present!
[Tue Dec 15 01:35:23 2020] debugfs: File 'le_max_key_size' in directory 'hci0' already present!

dmesg -T from Pi3b on eth0

[Tue Dec 15 02:46:24 2020] Bluetooth: hci0: Frame reassembly failed (-84)
[Tue Dec 15 02:46:24 2020] Bluetooth: hci0: Frame reassembly failed (-84)
[Tue Dec 15 02:46:24 2020] Bluetooth: hci0: Frame reassembly failed (-84)
[Tue Dec 15 02:46:24 2020] Bluetooth: hci0: Frame reassembly failed (-84)
[Tue Dec 15 02:46:24 2020] Bluetooth: hci0: Frame reassembly failed (-84)
[Tue Dec 15 02:46:24 2020] Bluetooth: hci0: Frame reassembly failed (-84)
[Tue Dec 15 02:46:24 2020] Bluetooth: hci0: Frame reassembly failed (-84)
[Tue Dec 15 02:46:24 2020] Bluetooth: hci0: Frame reassembly failed (-84)

Relevant configuration Paste the relevant parts of your configuration below.

global:
  instanceName: office
  integrations:
    - bluetoothLowEnergy
cluster:
  weight: 5
bluetoothLowEnergy:
  timeout: 10
  whitelist:
    - Iphone-BLE-deviceId-1
    - Iphone-BLE-deviceId-2
  tagOverrides:
  Iphone-BLE-deviceId-1:
    name: 1
  Iphone-BLE-deviceId-2:
    name: 2
entities:
  behaviors:
    Iphone-BLE-deviceId-1:
      rollingAverage:
        window: 5
    Iphone-BLE-deviceId-2:
      rollingAverage:
        window: 5

Expected behavior A clear and concise description of what you expected to happen.

Environment

• room-assistant version: beta
• installation type: [e.g. NodeJS, Docker, Hass.io] Docker (running on 2 x pi-zero - wired eth0 & 2x pi 3B - eth0)
• hardware: 2 x Pi0 (eth0) 2 x Pi3B (eth0)
• OS: Raspbian Buster Lite

Additional context SSH responsive, API responses: /entities:

[
  {
    "attributes": {
      "nodes": [
        "livingroom",
        "serverroom",
        "kitchen",
        "office"
      ]
    },
    "id": "status-cluster-size",
    "name": "office Cluster Size",
    "distributed": false,
    "stateLocked": true,
    "state": 4
  },
  {
    "attributes": {
      "quorumReached": true
    },
    "id": "status-cluster-leader",
    "name": "office Cluster Leader",
    "distributed": false,
    "stateLocked": true,
    "state": "office"
  }
]

/status

{
  "status": "ok",
  "info": {
    "bt_successive_errors": {
      "status": "up"
    }
  },
  "error": {},
  "details": {
    "bt_successive_errors": {
      "status": "up"
    }
  }
}

Looks like this could be a number of issues:

1. Baud rate: https://github.com/raspberrypi/firmware/issues/1150#issuecomment-603695039
2. Power supply (investigating) - getting under voltage on one Pi
3. BT usage rate

[mKeRix]

FYI: the latest beta (v2.13.0-beta.4) contains the fixes that helped with distances not being reported after a while in my setup.

[github-actions[bot]]

There hasn’t been any activity on this issue recently. In an effort to provide a better overview of current issues we automatically clean some of the old ones. Many of them may already be resolved in newer versions of room-assistant. This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.