Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

2.11.0 crashes in HA with BLE and Classic enabled

See original GitHub issue

Describe the bug an exception is thrown and the container quits

To reproduce I have room-assistant running in supervised HA on debian, running on qemu. TPLink bluetooth adapted connected to the VM.

Relevant logs

/usr/lib/node_modules/room-assistant/node_modules/@abandonware/noble/lib/hci-socket/hci.js:100
    this._deviceId = this._socket.bindRaw(deviceId);
                                  ^
Error: EALREADY, Operation already in progress
    at Hci.init (/usr/lib/node_modules/room-assistant/node_modules/@abandonware/noble/lib/hci-socket/hci.js:100:35)
    at Hci.pollIsDevUp (/usr/lib/node_modules/room-assistant/node_modules/@abandonware/noble/lib/hci-socket/hci.js:115:14)
    at listOnTimeout (internal/timers.js:549:17)
    at processTimers (internal/timers.js:492:7) {
  errno: 114,
  code: 'EALREADY',
  syscall: 'bind'
}

Relevant configuration

global:
  instanceName: server
  integrations:
    - homeAssistant
    - bluetoothClassic
    - bluetoothLowEnergy
bluetoothClassic:
  addresses:
    - mac1
    - mac2
    - mac3
debug_level: verbose
cluster:
  autoDiscovery: false
  peerAddresses:
    - 'ip:6425'
bluetoothLowEnergy:
  processIBeacon: false
  whitelist:
    - mac4
    - mac5
    - mac2
  tagOverrides:
    mac2:
      name: my phone
    mac3:
      name: my watch

Expected behavior That it would keep running with both integrations working. Disabling BLE makes it work with the same configuration.

Environment

room-assistant version: 2.11.0
installation type: Hass.io
hardware: x86 QNAP NAS, running a debian VM
OS: Debian

Additional context

Issue Analytics

State:
Created 3 years ago
Comments:14 (6 by maintainers)

Top GitHub Comments

1reaction

mKeRixcommented, Oct 26, 2020

Hm, this looks similar to #302. I just got another idea what the fault could be, but I need to investigate it some more. Until then: the watchdog feature can also automatically restart the add-on for you whenever this happens.

Thanks for reporting with all the details!

0reactions

mKeRixcommented, Jan 17, 2021

@joopy The unknown handle warnings are not a big concern, they come from a downstream library. The current beta version silences these warnings, that fix will come to the regular versions eventually as well.