BLE Startet nicht

[Thomas Braun]

@larryxxl sagte in BLE Startet nicht:

Nodejs-Version: 23.2.0

Zu NEU. noble baut damit nicht mehr.
Davon abgesehen setzt man ungerade Versionen von nodejs nicht ein.
Installier da die stabile und für den ioBroker vorgesehene v20.

Issue dazu:
https://github.com/AlCalzone/ioBroker.ble/issues/870

Grothesk242 created this issue in AlCalzone/ioBroker.ble

closed Switch to @stoprocent/noble - abandonware fork does not build with nodejs23 #870

[LarryXXL]

@thomas-braun

iob diag.txt

Nodejs 20 ist nun aktiv, Aber BLE und Radar2 starten nun beide nicht mehr.

BLE findet Device nicht.

ble.0
2024-11-30 15:20:14.166	info	starting scanner process...
ble.0
2024-11-30 15:20:14.112	info	monitored services:
ble.0
2024-11-30 15:20:14.112	info	enabled plugins: _default
ble.0
2024-11-30 15:20:14.111	info	loaded plugins: Xiaomi, mi-flora, ruuvi-tag, BTHome, _default
ble.0
2024-11-30 15:20:14.054	info	starting. Version 0.14.0 in /opt/iobroker/node_modules/iobroker.ble, node: v20.18.1, js-controller: 7.0.3
ble.0
2024-11-30 15:20:09.906	info	terminating
ble.0
2024-11-30 15:20:09.404	info	Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
ble.0
2024-11-30 15:20:09.404	info	terminating
ble.0
2024-11-30 15:20:09.403	info	Got terminate signal TERMINATE_YOURSELF

Adapter Radar ist in einem Loop "Exception-Code: ENOENT: spawn ping ENOENT"

host.iobrokerII
2024-11-30 15:22:14.101	error	instance system.adapter.radar2.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
radar2.0
2024-11-30 15:22:14.070	info	terminating
radar2.0
2024-11-30 15:22:13.619	info	debug: created State radar2.0.info.connection
radar2.0
2024-11-30 15:22:13.571	info	terminating
radar2.0
2024-11-30 15:22:13.571	info	terminating
radar2.0
2024-11-30 15:22:13.571	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
radar2.0
2024-11-30 15:22:13.570	info	terminating
radar2.0
2024-11-30 15:22:13.570	info	Adapter disconnected and stopped with dostop(null) and callback(true)
radar2.0
2024-11-30 15:22:13.569	info	Unload adapter now with null
radar2.0
2024-11-30 15:22:13.565	error	Exception-Code: ENOENT: spawn ping ENOENT
radar2.0
2024-11-30 15:22:13.565	error	Error: spawn ping ENOENT at ChildProcess._handle.onexit (node:internal/child_process:285:19) at onErrorNT (node:internal/child_process:483:16) at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
radar2.0
2024-11-30 15:22:13.564	error	uncaught exception: spawn ping ENOENT
radar2.0
2024-11-30 15:22:13.564	warn	Uncaught Exception: spawn ping ENOENT
radar2.0
2024-11-30 15:22:13.548	info	Will try to scan BT devices: hci0 78:8A:86:1F:0B:8B
radar2.0
2024-11-30 15:22:13.541	info	debug: Will 'not save' unknown BT devices and will 'save' unknown IP devices!
radar2.0
2024-11-30 15:22:13.540	info	debug: radar2 set to scan every 30 seconds and printers every 720 minutes.
radar2.0
2024-11-30 15:22:13.533	info	Connected with '0.0.0.0' for DHCP Scan
radar2.0
2024-11-30 15:22:13.530	info	arp-scan will use the following interfaces: [ 'ens18' ]
radar2.0
2024-11-30 15:22:13.529	info	debug: use known IP list: [ '192.168.178.10', '192.168.178.10' ]
radar2.0
2024-11-30 15:22:13.529	info	debug: use known BT list: [ '01:12:23:34:45:56' ]
radar2.0
2024-11-30 15:22:13.528	info	debug: radar2 set to flag items away if they are not seen for 3 minutes
radar2.0
2024-11-30 15:22:13.308	info	debug: started #3 hciconfig hci0 up
radar2.0
2024-11-30 15:22:13.190	info	debug: started #2 hciconfig hci0 down
radar2.0
2024-11-30 15:22:13.187	info	Will run hcitool-mode and not noble on device [ [Object] ]!
radar2.0
2024-11-30 15:22:13.173	info	debug: started #1 hcitool dev
radar2.0
2024-11-30 15:22:13.164	info	Will use l2Ping for BT scans.
radar2.0
2024-11-30 15:22:13.160	info	radar2 initialization started...
radar2.0
2024-11-30 15:22:13.122	info	starting. Version 2.2.0 in /opt/iobroker/node_modules/iobroker.radar2, node: v20.18.1, js-controller: 7.0.3

MOD-EDIT: Code in code-tags gesetzt!

nach dem nodejs Update auf v20 wurden BLE und Radar2 Adapter gelöscht und neu installiert.

was hakt nun ? dankbar für jeden Tip.

[haselchen]

@larryxxl

sudo setcap 'cap_net_admin,cap_net_bind_service,cap_net_raw+eip' $(eval readlink -f `which node`)

BLE Adapter neu starten...

Feedback?

Wenn das nicht hilft, dann:

Für noble

cd /opt/iobroker/node_modules/@abandonware/noble
npm i --production

Für bluetooth-hci-socket

cd /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket
npm i --production

[LarryXXL]

@haselchen said in BLE Startet nicht:

sudo setcap 'cap_net_admin,cap_net_bind_service,cap_net_raw+eip' $(eval readlink -f which node)

hatte ich schon gemacht. für BLE und Radar2.

BLE

ble.0
2024-11-30 15:35:35.534 info starting scanner process...

ble.0
2024-11-30 15:35:35.484 info monitored services:

ble.0
2024-11-30 15:35:35.484 info enabled plugins: _default

ble.0
2024-11-30 15:35:35.483 info loaded plugins: Xiaomi, mi-flora, ruuvi-tag, BTHome, _default

ble.0
2024-11-30 15:35:35.424 info starting. Version 0.14.0 in /opt/iobroker/node_modules/iobroker.ble, node: v20.18.1, js-controller: 7.0.3

ble.0
2024-11-30 15:35:35.348 debug States connected to redis: 127.0.0.1:9000

ble.0
2024-11-30 15:35:35.297 debug States create User PubSub Client

ble.0
2024-11-30 15:35:35.296 debug States create System PubSub Client

ble.0
2024-11-30 15:35:35.290 debug Redis States: Use Redis connection: 127.0.0.1:9000

ble.0
2024-11-30 15:35:35.277 debug Objects connected to redis: 127.0.0.1:9001

ble.0
2024-11-30 15:35:35.273 debug Objects client initialize lua scripts

ble.0
2024-11-30 15:35:35.254 debug Objects create User PubSub Client

ble.0
2024-11-30 15:35:35.254 debug Objects create System PubSub Client

ble.0
2024-11-30 15:35:35.253 debug Objects client ready ... initialize now

ble.0
2024-11-30 15:35:35.236 debug Redis Objects: Use Redis connection: 127.0.0.1:9001

ble.0
2024-11-30 15:35:33.603 info terminating

ble.0
2024-11-30 15:35:33.100 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason

ble.0
2024-11-30 15:35:33.100 info terminating

ble.0
2024-11-30 15:35:33.099 info Got terminate signal TERMINATE_YOURSELF

admin.0
2024-11-30 15:30:13.226 info <== Disconnect system.user.admin from ::ffff:192.168.0.150

admin.0
2024-11-30 15:30:05.276 info ==> Connected system.user.admin from ::ffff:192.168.0.150

@haselchen said in BLE Startet nicht:

sudo setcap 'cap_net_admin,cap_net_bind_service,cap_net_raw+eip' $(eval readlink -f which node)

host.iobrokerII
2024-11-30 15:42:16.335 error instance system.adapter.radar2.0 terminated with code 3 (NO_ADAPTER_CONFIG_FOUND)

radar2.0
2024-11-30 15:42:15.803 warn Terminated (NO_ADAPTER_CONFIG_FOUND): Without reason

radar2.0
2024-11-30 15:42:15.756 error adapter disabled

ble.0
2024-11-30 15:41:51.302 info terminating

ble.0
2024-11-30 15:41:50.800 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason

ble.0
2024-11-30 15:41:50.800 info terminating

ble.0
2024-11-30 15:41:50.799 info Got terminate signal TERMINATE_YOURSELF

host.iobrokerII
2024-11-30 15:41:44.617 error instance system.adapter.radar2.0 terminated with code 6 (UNCAUGHT_EXCEPTION)

radar2.0
2024-11-30 15:41:44.587 info terminating

radar2.0
2024-11-30 15:41:44.135 info debug: created State radar2.0.info.connection

radar2.0
2024-11-30 15:41:44.089 info terminating

radar2.0
2024-11-30 15:41:44.089 info terminating

radar2.0
2024-11-30 15:41:44.088 warn Terminated (UNCAUGHT_EXCEPTION): Without reason

radar2.0
2024-11-30 15:41:44.088 info terminating

radar2.0
2024-11-30 15:41:44.088 info Adapter disconnected and stopped with dostop(null) and callback(true)

radar2.0
2024-11-30 15:41:44.087 info Unload adapter now with null

radar2.0
2024-11-30 15:41:44.083 error Exception-Code: ENOENT: spawn ping ENOENT

radar2.0
2024-11-30 15:41:44.083 error Error: spawn ping ENOENT at ChildProcess._handle.onexit (node:internal/child_process:285:19) at onErrorNT (node:internal/child_process:483:16) at process.processTicksAndRejections (node:internal/process/task_queues:82:21)

radar2.0
2024-11-30 15:41:44.082 error uncaught exception: spawn ping ENOENT

radar2.0
2024-11-30 15:41:44.082 warn Uncaught Exception: spawn ping ENOENT

radar2.0
2024-11-30 15:41:44.067 info Will try to scan BT devices: hci0 78:8A:86:1F:0B:8B

radar2.0
2024-11-30 15:41:44.060 info debug: Will 'not save' unknown BT devices and will 'save' unknown IP devices!

radar2.0
2024-11-30 15:41:44.059 info debug: radar2 set to scan every 30 seconds and printers every 720 minutes.

radar2.0
2024-11-30 15:41:44.042 info Connected with '0.0.0.0' for DHCP Scan

radar2.0
2024-11-30 15:41:44.034 info arp-scan will use the following interfaces: [ 'ens18' ]

radar2.0
2024-11-30 15:41:44.034 info debug: use known IP list: [ '192.168.178.10', '192.168.178.10' ]

radar2.0
2024-11-30 15:41:44.033 info debug: use known BT list: [ '01:12:23:34:45:56' ]

radar2.0
2024-11-30 15:41:44.031 info debug: radar2 set to flag items away if they are not seen for 3 minutes

radar2.0
2024-11-30 15:41:44.021 info found and will use '@abandonware/noble'

radar2.0
2024-11-30 15:41:44.003 info Will use l2Ping for BT scans.

radar2.0
2024-11-30 15:41:43.998 info radar2 initialization started...

radar2.0
2024-11-30 15:41:43.957 info starting. Version 2.2.0 in /opt/iobroker/node_modules/iobroker.radar2, node: v20.18.1, js-controller: 7.0.3

admin.0
2024-11-30 15:41:40.507 info <== Disconnect system.user.admin from ::ffff:192.168.0.150

admin.0
2024-11-30 15:41:34.562 info ==> Connected system.user.admin from ::ffff:192.168.0.150

[Thomas Braun]

@larryxxl

Bitte CodeTags verwenden und das Logfile aus

iob logs --watch

nehmen. Das ist dann auch chronologisch richtig.

[LarryXXL]

@thomas-braun

pi@iobrokerII:~$ iob logs --watch
2024-11-30 15:46:50.275  - error: radar2.0 (15194) adapter disabled
2024-11-30 15:46:50.363  - warn: radar2.0 (15194) Terminated (NO_ADAPTER_CONFIGFOUND): Without reason
2024-11-30 15:46:50.896  - error: host.iobrokerII instance system.adapter.radar.0 terminated with code 3 (NO_ADAPTER_CONFIG_FOUND)

[haselchen]

@larryxxl

Hast du die anderen beiden Befehle eingegeben?

[LarryXXL]

@haselchen ja beide Befehle wurden ausgeführt.

pi@iobrokerII:~$ iob logs --watch
2024-11-30 15:46:50.275  - error: radar2.0 (15194) adapter disabled
2024-11-30 15:46:50.363  - warn: radar2.0 (15194) Terminated (NO_ADAPTER_CONFIGFOUND): Without reason
2024-11-30 15:46:50.896  - error: host.iobrokerII instance system.adapter.radar.0 terminated with code 3 (NO_ADAPTER_CONFIG_FOUND)
pi@iobrokerII:~$ iob logs --watch
2024-11-30 15:46:50.275  - error: radar2.0 (15194) adapter disabled
2024-11-30 15:46:50.363  - warn: radar2.0 (15194) Terminated (NO_ADAPTER_CONFIGFOUND): Without reason
2024-11-30 15:46:50.896  - error: host.iobrokerII instance system.adapter.radar.0 terminated with code 3 (NO_ADAPTER_CONFIG_FOUND)
2024-11-30 15:51:22.881  - info: radar2.0 (15292) starting. Version 2.2.0 in /opt/iobroker/node_modules/iobroker.radar2, node: v20.18.1, js-controller: 7.0.3
2024-11-30 15:51:22.927  - info: radar2.0 (15292) radar2 initialization started...
2024-11-30 15:51:22.932  - info: radar2.0 (15292) Will use l2Ping for BT scans.
2024-11-30 15:51:22.951  - info: radar2.0 (15292) found and will use '@abandonware/noble'
2024-11-30 15:51:22.961  - info: radar2.0 (15292) debug: radar2 set to flag items away if they are not seen for 3 minutes
2024-11-30 15:51:22.963  - info: radar2.0 (15292) debug: use known BT list: [ '01:12:23:34:45:56' ]
2024-11-30 15:51:22.963  - info: radar2.0 (15292) debug: use known IP list: [ '192.168.178.10', '192.168.178.10' ]
2024-11-30 15:51:22.964  - info: radar2.0 (15292) arp-scan will use the following interfaces: [ 'ens18' ]
2024-11-30 15:51:22.970  - info: radar2.0 (15292) Connected with '0.0.0.0' for DHCP Scan
2024-11-30 15:51:22.985  - info: radar2.0 (15292) debug: radar2 set to scan every 30 seconds and printers every 720 minutes.
2024-11-30 15:51:22.985  - info: radar2.0 (15292) debug: Will 'not save' unknown BT devices and will 'save' unknown IP devices!
2024-11-30 15:51:22.995  - info: radar2.0 (15292) Will try to scan BT devices: hci0    78:8A:86:1F:0B:8B
2024-11-30 15:51:23.010  - warn: radar2.0 (15292) Uncaught Exception: spawn ping ENOENT
2024-11-30 15:51:23.010  - error: radar2.0 (15292) uncaught exception: spawn ping ENOENT
2024-11-30 15:51:23.011  - error: radar2.0 (15292) Error: spawn ping ENOENT
    at ChildProcess._handle.onexit (node:internal/child_process:285:19)
    at onErrorNT (node:internal/child_process:483:16)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
2024-11-30 15:51:23.011  - error: radar2.0 (15292) Exception-Code: ENOENT: spawn ping ENOENT
2024-11-30 15:51:23.016  - info: radar2.0 (15292) Unload adapter now with null
2024-11-30 15:51:23.017  - info: radar2.0 (15292) Adapter disconnected and stopped with dostop(null) and callback(true)
2024-11-30 15:51:23.017  - info: radar2.0 (15292) terminating
2024-11-30 15:51:23.017  - warn: radar2.0 (15292) Terminated (UNCAUGHT_EXCEPTION): Without reason
2024-11-30 15:51:23.018  - info: radar2.0 (15292) terminating
2024-11-30 15:51:23.018  - info: radar2.0 (15292) terminating
2024-11-30 15:51:23.067  - info: radar2.0 (15292) debug: created State radar2.0.info.connection
2024-11-30 15:51:23.385  - debug: ble.0 (15303) Redis Objects: Use Redis connection: 127.0.0.1:9001
2024-11-30 15:51:23.403  - debug: ble.0 (15303) Objects client ready ... initialize now
2024-11-30 15:51:23.405  - debug: ble.0 (15303) Objects create System PubSub Client
2024-11-30 15:51:23.406  - debug: ble.0 (15303) Objects create User PubSub Client
2024-11-30 15:51:23.428  - debug: ble.0 (15303) Objects client initialize lua scripts
2024-11-30 15:51:23.434  - debug: ble.0 (15303) Objects connected to redis: 127.0.0.1:9001
2024-11-30 15:51:23.449  - debug: ble.0 (15303) Redis States: Use Redis connection: 127.0.0.1:9000
2024-11-30 15:51:23.457  - debug: ble.0 (15303) States create System PubSub Client
2024-11-30 15:51:23.458  - debug: ble.0 (15303) States create User PubSub Client
2024-11-30 15:51:23.512  - debug: ble.0 (15303) States connected to redis: 127.0.0.1:9000
2024-11-30 15:51:23.515  - info: radar2.0 (15292) terminating
2024-11-30 15:51:23.552  - error: host.iobrokerII instance system.adapter.radar2.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2024-11-30 15:51:23.610  - info: ble.0 (15303) starting. Version 0.14.0 in /opt/iobroker/node_modules/iobroker.ble, node: v20.18.1, js-controller: 7.0.3
2024-11-30 15:51:23.671  - info: ble.0 (15303) loaded plugins: Xiaomi, mi-flora, ruuvi-tag, BTHome, _default
2024-11-30 15:51:23.672  - info: ble.0 (15303) enabled plugins: _default
2024-11-30 15:51:23.672  - info: ble.0 (15303) monitored services:
2024-11-30 15:51:23.721  - info: ble.0 (15303) starting scanner process...

















^[[A^[[A^[[A^[[A^[[A^[[A^[[A^Cpi@iobrokerII:~$
pi@iobrokerII:~$
pi@iobrokerII:~$
pi@iobrokerII:~$ iob logs --watch
2024-11-30 15:46:50.275  - error: radar2.0 (15194) adapter disabled
2024-11-30 15:46:50.363  - warn: radar2.0 (15194) Terminated (NO_ADAPTER_CONFIG_FOUND): Without reason
2024-11-30 15:46:50.896  - error: host.iobrokerII instance system.adapter.radar2.0 terminated with code 3 (NO_ADAPTER_CONFIG_FOUND)
2024-11-30 15:51:22.881  - info: radar2.0 (15292) starting. Version 2.2.0 in /opt/iobroker/node_modules/iobroker.radar2, node: v20.18.1, js-controller: 7.0.3
2024-11-30 15:51:22.927  - info: radar2.0 (15292) radar2 initialization started...
2024-11-30 15:51:22.932  - info: radar2.0 (15292) Will use l2Ping for BT scans.
2024-11-30 15:51:22.951  - info: radar2.0 (15292) found and will use '@abandonware/noble'
2024-11-30 15:51:22.961  - info: radar2.0 (15292) debug: radar2 set to flag items away if they are not seen for 3 minutes
2024-11-30 15:51:22.963  - info: radar2.0 (15292) debug: use known BT list: [ '01:12:23:34:45:56' ]
2024-11-30 15:51:22.963  - info: radar2.0 (15292) debug: use known IP list: [ '192.168.178.10', '192.168.178.10' ]
2024-11-30 15:51:22.964  - info: radar2.0 (15292) arp-scan will use the following interfaces: [ 'ens18' ]
2024-11-30 15:51:22.970  - info: radar2.0 (15292) Connected with '0.0.0.0' for DHCP Scan
2024-11-30 15:51:22.985  - info: radar2.0 (15292) debug: radar2 set to scan every 30 seconds and printers every 720 minutes.
2024-11-30 15:51:22.985  - info: radar2.0 (15292) debug: Will 'not save' unknown BT devices and will 'save' unknown IP devices!
2024-11-30 15:51:22.995  - info: radar2.0 (15292) Will try to scan BT devices: hci0    78:8A:86:1F:0B:8B
2024-11-30 15:51:23.010  - warn: radar2.0 (15292) Uncaught Exception: spawn ping ENOENT
2024-11-30 15:51:23.010  - error: radar2.0 (15292) uncaught exception: spawn ping ENOENT
2024-11-30 15:51:23.011  - error: radar2.0 (15292) Error: spawn ping ENOENT
    at ChildProcess._handle.onexit (node:internal/child_process:285:19)
    at onErrorNT (node:internal/child_process:483:16)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
2024-11-30 15:51:23.011  - error: radar2.0 (15292) Exception-Code: ENOENT: spawn ping ENOENT
2024-11-30 15:51:23.016  - info: radar2.0 (15292) Unload adapter now with null
2024-11-30 15:51:23.017  - info: radar2.0 (15292) Adapter disconnected and stopped with dostop(null) and callback(true)
2024-11-30 15:51:23.017  - info: radar2.0 (15292) terminating
2024-11-30 15:51:23.017  - warn: radar2.0 (15292) Terminated (UNCAUGHT_EXCEPTION): Without reason
2024-11-30 15:51:23.018  - info: radar2.0 (15292) terminating
2024-11-30 15:51:23.018  - info: radar2.0 (15292) terminating
2024-11-30 15:51:23.067  - info: radar2.0 (15292) debug: created State radar2.0.info.connection
2024-11-30 15:51:23.385  - debug: ble.0 (15303) Redis Objects: Use Redis connection: 127.0.0.1:9001
2024-11-30 15:51:23.403  - debug: ble.0 (15303) Objects client ready ... initialize now
2024-11-30 15:51:23.405  - debug: ble.0 (15303) Objects create System PubSub Client
2024-11-30 15:51:23.406  - debug: ble.0 (15303) Objects create User PubSub Client
2024-11-30 15:51:23.428  - debug: ble.0 (15303) Objects client initialize lua scripts
2024-11-30 15:51:23.434  - debug: ble.0 (15303) Objects connected to redis: 127.0.0.1:9001
2024-11-30 15:51:23.449  - debug: ble.0 (15303) Redis States: Use Redis connection: 127.0.0.1:9000
2024-11-30 15:51:23.457  - debug: ble.0 (15303) States create System PubSub Client
2024-11-30 15:51:23.458  - debug: ble.0 (15303) States create User PubSub Client
2024-11-30 15:51:23.512  - debug: ble.0 (15303) States connected to redis: 127.0.0.1:9000
2024-11-30 15:51:23.515  - info: radar2.0 (15292) terminating
2024-11-30 15:51:23.552  - error: host.iobrokerII instance system.adapter.radar2.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2024-11-30 15:51:23.610  - info: ble.0 (15303) starting. Version 0.14.0 in /opt/iobroker/node_modules/iobroker.ble, node: v20.18.1, js-controller: 7.0.3
2024-11-30 15:51:23.671  - info: ble.0 (15303) loaded plugins: Xiaomi, mi-flora, ruuvi-tag, BTHome, _default
2024-11-30 15:51:23.672  - info: ble.0 (15303) enabled plugins: _default
2024-11-30 15:51:23.672  - info: ble.0 (15303) monitored services:
2024-11-30 15:51:23.721  - info: ble.0 (15303) starting scanner process...

[Thomas Braun]

@larryxxl

sudo hcitool lescan

sagt?

[LarryXXL]

@thomas-braun said in BLE Startet nicht:

sudo hcitool lescan

pi@iobrokerII:~$ sudo hcitool lescan
[sudo] Passwort für pi:
LE Scan ...
C4:7C:8D:67:4D:75 (unknown)
32:37:48:71:31:42 (unknown)
5C:85:7E:13:24:5D (unknown)
5C:85:7E:13:24:5D Flower care
D8:D6:68:9E:43:9B (unknown)
D8:D6:68:9E:43:9B (unknown)
D8:D6:68:9E:43:9B TY
6B:67:61:43:6C:36 (unknown)
5C:85:7E:B1:25:58 (unknown)
5C:85:7E:B1:25:58 Flower care
08:A6:F7:3A:4C:96 (unknown)
08:A6:F7:3A:4C:96 (unknown)
C4:7C:8D:67:4D:75 Flower care
08:A6:F7:3A:4C:96 (unknown)
08:A6:F7:3A:4C:96 (unknown)
08:A6:F7:3A:4C:96 (unknown)
08:A6:F7:3A:4C:96 (unknown)
08:A6:F7:3A:4C:96 (unknown)
6B:67:61:43:6C:36 (unknown)
6B:67:61:43:6C:36 EL_B2kgaCl6
08:A6:F7:3A:4C:96 (unknown)
08:A6:F7:3A:4C:96 (unknown)
08:A6:F7:3A:4C:96 IPSTube_3A4C96
C4:7C:8D:67:4E:78 (unknown)
C4:7C:8D:67:4E:78 Flower care
5C:85:7E:13:24:29 (unknown)
5C:85:7E:13:24:29 Flower care
54:EF:44:2B:0D:7A (unknown)
4A:63:26:56:43:FD (unknown)
4A:63:26:56:43:FD (unknown)
5C:85:7E:13:26:95 (unknown)

[Thomas Braun]

@larryxxl sagte in BLE Startet nicht:

enabled plugins: _default

Du wirst da noch plugins aktivieren müssen, wenn du die Flower care Dinger sehen willst.

[haselchen]

@larryxxl

BLE funktioniert doch?!
Ich sehe da keine Fehler im Log.

Wie sehen deine Radar Einstellungen aus?

Edit:

Was soll das _default in den Plugins?

[haselchen]

@thomas-braun

Sind aktiviert

ble.0
2024-11-30 15:20:14.111 info loaded plugins: Xiaomi, mi-flora, ruuvi-tag, BTHome, _default

[LarryXXL]

@thomas-braun

Plugins xiaomi, mi-flora
aber Adapter bleibt Gelb. nicht verbunden mit Gerät oder Dienst.

[LarryXXL]

@haselchen

Radar 2 läuft ebenfalls nicht. auch nicht mit Noble.

[LarryXXL]

@haselchen

BLE plugins sind Xiaomi, mi-flora im Log stehen noch andere Plugins.

ble.0
2024-11-30 16:12:35.326	info	starting scanner process...

ble.0
2024-11-30 16:12:35.276	info	monitored services: fe95

ble.0
2024-11-30 16:12:35.276	info	enabled plugins: Xiaomi, mi-flora, _default

ble.0
2024-11-30 16:12:35.275	info	loaded plugins: Xiaomi, mi-flora, ruuvi-tag, BTHome, _default

ble.0
2024-11-30 16:12:35.212	info	starting. Version 0.14.0 in /opt/iobroker/node_modules/iobroker.ble, node: v20.18.1, js-controller: 7.0.3

ble.0
2024-11-30 16:12:35.136	debug	States connected to redis: 127.0.0.1:9000

ble.0
2024-11-30 16:12:35.080	debug	States create User PubSub Client

ble.0
2024-11-30 16:12:35.079	debug	States create System PubSub Client

ble.0
2024-11-30 16:12:35.073	debug	Redis States: Use Redis connection: 127.0.0.1:9000

ble.0
2024-11-30 16:12:35.059	debug	Objects connected to redis: 127.0.0.1:9001

ble.0
2024-11-30 16:12:35.056	debug	Objects client initialize lua scripts

ble.0
2024-11-30 16:12:35.037	debug	Objects create User PubSub Client

ble.0
2024-11-30 16:12:35.036	debug	Objects create System PubSub Client

ble.0
2024-11-30 16:12:35.035	debug	Objects client ready ... initialize now

ble.0
2024-11-30 16:12:35.019	debug	Redis Objects: Use Redis connection: 127.0.0.1:9001

ble.0
2024-11-30 16:12:33.069	info	terminating

ble.0
2024-11-30 16:12:32.568	info	Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason

ble.0
2024-11-30 16:12:32.568	info	terminating

ble.0
2024-11-30 16:12:32.566	info	Got terminate signal TERMINATE_YOURSELF

[funky4t]

Ich würd mich gern hier "anhängen"... Habe den Broker als VM in Proxmox laufen und der BLE lief bis dahin okay. Ich musste aus einem anderen Grunde heute ein Proxmox Backup einspielen, lief alles reibungslos bis ich merkte, dass meine BLE devices (Xiaomi Temp/Humidtiy) sich angeblich seit 7 Tagen (Date vom letzten Backup) nicht aktualisiert haben. Hab den BLE Adapter gecheckt, der DriverState steht auf unknown und die Objects werden nicht upgedatet. Ich hab die States gelöscht, danach wurden sie auch nach BLE Neustart nicht neu geschrieben. Adapter gelöscht, neu installiert, leider erfolglos.

Hab mit ChatGPT ebenfalls einiges getestet, leider erfolglos. Komisch war da, dass

sudo hcitool lescan

auf der Broker wie hier diverse BLE Geräte anzeigte, die aber im BLE Adapter nicht angelegt wurden.

iob logs --watch

ergibt folgendes:

2024-12-07 21:12:38.011  - info: host.debianbroker stopInstance system.adapter.ble.0 (force=false, process=true)
2024-12-07 21:12:38.014  - info: ble.0 (8139) Got terminate signal TERMINATE_YOURSELF
2024-12-07 21:12:38.015  - info: ble.0 (8139) terminating
2024-12-07 21:12:38.015  - info: ble.0 (8139) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2024-12-07 21:12:38.106  - info: host.debianbroker stopInstance system.adapter.ble.0 send kill signal
2024-12-07 21:12:38.516  - info: ble.0 (8139) terminating
2024-12-07 21:12:38.558  - info: host.debianbroker instance system.adapter.ble.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2024-12-07 21:12:41.677  - info: host.debianbroker instance system.adapter.ble.0 in version "0.14.0" started with pid 10359
2024-12-07 21:12:41.954  - debug: ble.0 (10359) Redis Objects: Use Redis connection: 127.0.0.1:9001
2024-12-07 21:12:41.978  - debug: ble.0 (10359) Objects client ready ... initialize now
2024-12-07 21:12:41.979  - debug: ble.0 (10359) Objects create System PubSub Client
2024-12-07 21:12:41.979  - debug: ble.0 (10359) Objects create User PubSub Client
2024-12-07 21:12:42.034  - debug: ble.0 (10359) Objects client initialize lua scripts
2024-12-07 21:12:42.036  - debug: ble.0 (10359) Objects connected to redis: 127.0.0.1:9001
2024-12-07 21:12:42.116  - debug: ble.0 (10359) Redis States: Use Redis connection: 127.0.0.1:9000
2024-12-07 21:12:42.182  - debug: ble.0 (10359) States create System PubSub Client
2024-12-07 21:12:42.182  - debug: ble.0 (10359) States create User PubSub Client
2024-12-07 21:12:42.258  - debug: ble.0 (10359) States connected to redis: 127.0.0.1:9000
2024-12-07 21:12:42.334  - info: ble.0 (10359) starting. Version 0.14.0 in /opt/iobroker/node_modules/iobroker.ble, node: v20.18.1, js-controller: 7.0.3
2024-12-07 21:12:42.398  - info: ble.0 (10359) loaded plugins: Xiaomi, mi-flora, ruuvi-tag, BTHome, _default
2024-12-07 21:12:42.398  - info: ble.0 (10359) enabled plugins: Xiaomi, _default
2024-12-07 21:12:42.398  - info: ble.0 (10359) monitored services: fe95
2024-12-07 21:12:42.448  - info: ble.0 (10359) starting scanner process...
2

In der Vergangenheit hab ich die BLE Themen immer mit Google oder ChatGPT hinbekommen, aber heute stoße ich an meine Grenzen.

Falls ich hier völlig falsch bin seht es mir bitte nach, der Broker ist für mich Hobby und ich sehe ich eher als User. Aber wenn ich helfen kann einen Bug einzukreisen unterstütze ich gern. Falls der Bug vorm Bildschirm ist, lern ich gern dazu!

Ergebnis von

iob diag

findet ihr hier: iobdiag.rtf

Was ich noch versucht habe sind

iob fix

ohne Fehlermeldung durchgelaufen

sudo setcap cap_net_raw+eip $(eval readlink -f `which node`)

ohne Effekt, hat sonst immer funktioniert.

Ich werde morgen mal eine neue VM mit IOB und nur dem BLE aufsetzen und dann schauen, wie sich der BT Stick darin verhält....

[Thomas Braun]

@funky4t

Ja, der ble-Adapter ist gerade kaputt.
Gibt auch schon Issues dazu.

Und bitte die Ausgabe von iob diag nicht als rtf oder word-Dokument oder sowas hier rein klatschen, das kann ich mit meinem Editor nicht gut lesen.
Die reine Ausgabe in CodeTags eingebettet hier rein, mehr braucht es nicht.

[funky4t]

Herzlichen Dank @thomas-braun für deine Info zum Adapter und dem DIAG, dann muss ich vorläufig nicht weiter probieren.

[Thomas Braun]

@funky4t

Genauer:

https://github.com/AlCalzone/ioBroker.ble/issues/871
Evtl. muss die alternative verwendet werden:
https://github.com/AlCalzone/ioBroker.ble/issues/870

chris299 created this issue in AlCalzone/ioBroker.ble

closed driverState shows "unknown" #871

Grothesk242 created this issue in AlCalzone/ioBroker.ble

closed Switch to @stoprocent/noble - abandonware fork does not build with nodejs23 #870