(gelöst)BLE-Adapter
-
Plattform linux Betriebssystem linux bullseye Architektur x64 CPUs 2 Geschwindigkeit 1646 MHz Modell AMD G-T56N Processor RAM 7.25 GB System-Betriebszeit 02:22:53 Node.js v14.19.0 time 1646406832512 timeOffset -60 Anzahl der Adapter 400 NPM 6.14.16 Datenträgergröße 21.38 GB freier Festplattenspeicher 14.35 GB Betriebszeit 02:22:38 Aktive Instanzen 56 location /opt/iobroker/ Hostname debian -
iobroker stop iobroker fix iobroker start -
@thomas-braun
erledigt aber immer noch gelb auch der switchtbot ble Adapter ist gelb2022-03-04 16:33:38.427 error ENODEV, No such device ble.0 2022-03-04 16:33:37.389 info starting scanner process... ble.0 2022-03-04 16:33:37.382 info monitored services: fe95 ble.0 2022-03-04 16:33:37.380 info enabled plugins: Xiaomi, mi-flora, _default ble.0 2022-03-04 16:33:37.379 info loaded plugins: Xiaomi, mi-flora, ruuvi-tag, _default ble.0 2022-03-04 16:33:37.189 info starting. Version 0.12.0 in /opt/iobroker/node_modules/iobroker.ble, node: v14.19.0, js-controller: 4.0.15 ble.0 2022-03-04 16:33:28.234 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason ble.0 2022-03-04 16:33:28.229 info terminating ble.0 2022-03-04 16:33:28.224 info Got terminate signal TERMINATE_YOURSELF ble.0 2022-03-04 16:31:45.354 error ENODEV, No such device ble.0 2022-03-04 16:31:44.195 info starting scanner process... ble.0 2022-03-04 16:31:44.178 info monitored services: fe95 ble.0 2022-03-04 16:31:44.176 info enabled plugins: Xiaomi, mi-flora, _default ble.0 2022-03-04 16:31:44.172 info loaded plugins: Xiaomi, mi-flora, ruuvi-tag, _default ble.0 2022-03-04 16:31:43.938 info starting. Version 0.12.0 in /opt/iobroker/node_modules/iobroker.ble, node: v14.19.0, js-controller: 4.0.15 ble.0 2022-03-04 16:31:19.968 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason ble.0 2022-03-04 16:31:19.959 info terminating ble.0 2022-03-04 16:31:19.956 info Got terminate signal TERMINATE_YOURSELFswitchbot-ble.0 2022-03-04 16:32:26.970 error [scanDevices] Error: Error: ENODEV, No such device switchbot-ble.0 2022-03-04 16:32:26.635 info starting. Version 0.3.3 (non-npm: mrbungle64/ioBroker.switchbot-ble#4acdb210384fa9ebb9b6b93846950ed2767123c0) in /opt/iobroker/node_modules/iobroker.switchbot-ble, node: v14.19.0, js-controller: 4.0.15 switchbot-ble.0 2022-03-04 16:32:17.308 info Got terminate signal TERMINATE_YOURSELF -
Da wird das Gerät nicht richtig aufgefahren. So direkt fällt mir dazu aber nix ein.
Die beiden Adapter schließen sich aber soweit ich weiß aus, weil nur ein Prozess auf die BlueTooth-Hardware zugreifen kann. -
@thomas-braun
ok danke mal sehen ob noch jemand eine Idee hat. -
Irgendwie sieht es so aus ob der Stick nicht mehr erkannt wird. zu sehen ist nur die UPS und Zigbee
andy@debian:~$ lsusb Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0451:16c8 Texas Instruments, Inc. CC2538 USB CDC Bus 002 Device 002: ID 0463:ffff MGE UPS Systems UPS Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub -
Nun habe ich mehrmals den Stick entfernt und wieder rein dann wurde er erkannt.
Nun wieder alles grün.Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0451:16c8 Texas Instruments, Inc. CC2538 USB CDC Bus 002 Device 002: ID 0463:ffff MGE UPS Systems UPS Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub -
Hallo Freunde,
Nun habe ich den JS update spinnt wieder der BLE-AdapterTerminating because A dependency requires a rebuild. -
@ostseereiter sagte in BLE-Adapter:
Terminating because A dependency requires a rebuild.
Da müsste man mehr sehen.
-
2022-03-09 15:52:25.449 error Terminating because A dependency requires a rebuild. ble.0 2022-03-09 15:52:24.786 info starting scanner process... ble.0 2022-03-09 15:52:24.781 info monitored services: fe95 ble.0 2022-03-09 15:52:24.779 info enabled plugins: Xiaomi, mi-flora, _default ble.0 2022-03-09 15:52:24.776 info loaded plugins: Xiaomi, mi-flora, ruuvi-tag, _default ble.0 2022-03-09 15:52:24.604 info starting. Version 0.12.0 in /opt/iobroker/node_modules/iobroker.ble, node: v14.19.0, js-controller: 4.0.19leider nur das
-
-
@thomas-braun
nur iobroker fix -
jetzt mal das gemacht
andy@debian:~$ sudo service bluetooth start andy@debian:~$ sudo service bluetooth status ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2022-03-09 15:20:44 CET; 1h 6min ago Docs: man:bluetoothd(8) Main PID: 406 (bluetoothd) Status: "Running" Tasks: 1 (limit: 8870) Memory: 4.7M CPU: 69ms CGroup: /system.slice/bluetooth.service └─406 /usr/libexec/bluetooth/bluetoothd Mär 09 15:20:44 debian bluetoothd[406]: Starting SDP server Mär 09 15:20:44 debian bluetoothd[406]: Bluetooth management interface 1.18 initialized Mär 09 15:20:44 debian bluetoothd[406]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed. Mär 09 15:20:44 debian bluetoothd[406]: sap-server: Operation not permitted (1) Mär 09 15:32:13 debian bluetoothd[406]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed. Mär 09 15:32:13 debian bluetoothd[406]: sap-server: Operation not permitted (1) Mär 09 15:34:29 debian bluetoothd[406]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed. Mär 09 15:34:29 debian bluetoothd[406]: sap-server: Operation not permitted (1) Mär 09 15:36:45 debian bluetoothd[406]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed. Mär 09 15:36:45 debian bluetoothd[406]: sap-server: Operation not permitted (1) andy@debian:~$ -
@ostseereiter sagte in BLE-Adapter:
Bluetooth management interface 1.18 initialized Mär 09 15:20:44 debian bluetoothd[406]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
sudo nano /etc/systemd/system/bluetooth.target.wants/bluetooth.serviceÄndere
ExecStart=/usr/lib/bluetooth/bluetoothdin
ExecStart=/usr/lib/bluetooth/bluetoothd --noplugin=sapDann Service einmal neustarten.
sudo systemctl daemon-reload sudo service bluetooth restart -
alles erledigt aber adapter immer noch rot.
andy@debian:~$ sudo service bluetooth status ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2022-03-09 16:41:56 CET; 2min 38s ago Docs: man:bluetoothd(8) Main PID: 123701 (bluetoothd) Status: "Running" Tasks: 1 (limit: 8870) Memory: 736.0K CPU: 46ms CGroup: /system.slice/bluetooth.service └─123701 /usr/libexec/bluetooth/bluetoothd --noplugin=sap Mär 09 16:41:56 debian systemd[1]: Starting Bluetooth service... Mär 09 16:41:56 debian bluetoothd[123701]: Bluetooth daemon 5.55 Mär 09 16:41:56 debian systemd[1]: Started Bluetooth service. Mär 09 16:41:56 debian bluetoothd[123701]: Starting SDP server Mär 09 16:41:56 debian bluetoothd[123701]: Excluding (cli) sap Mär 09 16:41:56 debian bluetoothd[123701]: Bluetooth management interface 1.18 initialized -
Installier den ble-Adapter nochmal neu.
-
@ostseereiter was steht bei
ble.0.info.driverStateIf the adapter starts but won't connect to your bluetooth hardware, please check the info.driverState state in ioBroker. If it is unauthorized, you need to give node additional permissions. For Linux, this is as simple as sudo setcap cap_net_raw+eip $(eval readlink -f `which node`) -
@crunchip sagte in BLE-Adapter:
sudo setcap cap_net_raw+eip $(eval readlink -f
which node)andy@debian:~$ sudo ble.0.info.driverState [sudo] Passwort für andy: sudo: ble.0.info.driverState: Befehl nicht gefunden andy@debian:~$ sudo setcap cap_net_raw+eip $(eval readlink -f `which node`) andy@debian:~$ -
-
@thomas-braun
ooh wie peinlich.
