(gelöst)BLE-Adapter
-
@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.
-
Hardware/Treiber ist offenbar i. O.
Hast du den Adapter nochmal per reuild oder neuinstallation 'angepackt'? -
@ostseereiter und ist jetzt grün? oder immer noch Fehler
-
@crunchip
immer noch rot -
@ostseereiter wenn du die Instanz im debug Modus startest, kommt eventuell ein Hinweis
-
le.0 2022-03-09 17:18:15.441 error Terminating because A dependency requires a rebuild. ble.0 2022-03-09 17:18:14.642 info starting scanner process... ble.0 2022-03-09 17:18:14.636 info monitored services: fe95 ble.0 2022-03-09 17:18:14.634 info enabled plugins: Xiaomi, mi-flora, _default ble.0 2022-03-09 17:18:14.632 info loaded plugins: Xiaomi, mi-flora, ruuvi-tag, _default ble.0 2022-03-09 17:18:14.440 info starting. Version 0.12.0 in /opt/iobroker/node_modules/iobroker.ble, node: v14.19.0, js-controller: 4.0.19 ble.0 2022-03-09 17:18:13.009 debug States connected to redis: 127.0.0.1:9000 ble.0 2022-03-09 17:18:12.752 debug States create User PubSub Client ble.0 2022-03-09 17:18:12.749 debug States create System PubSub Client ble.0 2022-03-09 17:18:12.589 debug Redis States: Use Redis connection: 127.0.0.1:9000 ble.0 2022-03-09 17:18:12.484 debug Objects connected to redis: 127.0.0.1:9001 ble.0 2022-03-09 17:18:12.470 debug Objects client initialize lua scripts ble.0 2022-03-09 17:18:12.231 debug Objects create User PubSub Client ble.0 2022-03-09 17:18:12.229 debug Objects create System PubSub Client ble.0 2022-03-09 17:18:12.221 debug Objects client ready ... initialize now ble.0 2022-03-09 17:18:12.084 debug Redis Objects: Use Redis connection: 127.0.0.1:9001 -
@ostseereiter sagte in BLE-Adapter:
Terminating because A dependency requires a rebuild.
hast du wie oben erwähnt den rebuild ausgeführt?
iobroker rebuild ble -
@crunchip
ja habe ich -
@ostseereiter mit welcher Meldung?
-
@crunchip
das alles ok war ich hatte es nicht gespeichert aber ich kann ja nochmal -
andy@debian:~$ cd /opt/iobroker andy@debian:/opt/iobroker$ iobroker rebuild ble Rebuilding native module "ble" ... Rebuilding native modules done -
@ostseereiter dann weiss ich auch nicht mehr weiter
welche Geräte sind denn eigentlich per ble verbunden?
