Neuer ioBroker-Blog online: Monatsrückblick März/April 2026

[adarof]

Hallo
Ich komme nicht weiter. Habe nach längerer Zeit mal das OS vom Raspi geupdated, um NodeJS upzudaten um dann iobroker Update für JSController zu machen...

nach dem Systemupdate bleibt der BLE Adapter leider in Gelb - auch Logging auf "Silly" bringt nichts hilfreiches - er scheint glücklich:

ble.0	2020-01-08 19:38:34.844	silly	inMem message ble.0.* ble.0.info.driverState val=unauthorized, ack=true, ts=1578512314831, q=0, from=system.adapter.ble.0, lc=1578512314831
ble.0	2020-01-08 19:38:34.839	silly	inMem message ble.0.* ble.0.info.driverState val=unknown, ack=true, ts=1578512314829, q=0, from=system.adapter.ble.0, lc=1578512314829
ble.0	2020-01-08 19:38:34.467	info	monitored services: fe95
ble.0	2020-01-08 19:38:34.464	info	enabled plugins: Xiaomi, _default
ble.0	2020-01-08 19:38:34.463	info	loaded plugins: Xiaomi, mi-flora, ruuvi-tag, _default
ble.0	2020-01-08 19:38:34.293	info	starting. Version 0.7.2 in /opt/iobroker/node_modules/iobroker.ble, node: v8.17.0
ble.0	2020-01-08 19:38:34.160	debug	statesDB connected
ble.0	2020-01-08 19:38:34.102	debug	objectDB connected

Leider kommen keine Werte.

das HCI ist immernoch "0" und auch ein

sudo hciconfig hci0 reset | down | up 

sowie reboot bringt nichts.

Das Systemlog zeigt folgendes - was mich aber nicht schlauer macht:

Jan  8 19:27:48 raspberrypi btuart[358]: bcm43xx_init
Jan  8 19:27:48 raspberrypi btuart[358]: Flash firmware /lib/firmware/brcm/BCM43430A1.hcd
Jan  8 19:27:48 raspberrypi btuart[358]: Set BDADDR UART: b8:27:eb:d9:23:36
Jan  8 19:27:48 raspberrypi btuart[358]: Set Controller UART speed to 921600 bit/s
Jan  8 19:27:48 raspberrypi btuart[358]: Device setup complete
Jan  8 19:27:48 raspberrypi systemd[1]: Started Configure Bluetooth Modems connected by UART.
Jan  8 19:27:48 raspberrypi systemd[1]: Reached target Multi-User System.
Jan  8 19:27:48 raspberrypi systemd[1]: Reached target Graphical Interface.
Jan  8 19:27:48 raspberrypi systemd[1]: Starting Update UTMP about System Runlevel Changes...
Jan  8 19:27:48 raspberrypi systemd[1]: Created slice system-bthelper.slice.
Jan  8 19:27:48 raspberrypi systemd[1]: Starting Bluetooth service...
Jan  8 19:27:48 raspberrypi systemd[1]: Started Update UTMP about System Runlevel Changes.
Jan  8 19:27:48 raspberrypi bluetoothd[496]: Bluetooth daemon 5.43
Jan  8 19:27:48 raspberrypi systemd[1]: Started Bluetooth service.
Jan  8 19:27:48 raspberrypi systemd[1]: Reached target Bluetooth.
Jan  8 19:27:48 raspberrypi systemd[1]: Started Raspberry Pi bluetooth helper.
Jan  8 19:27:48 raspberrypi systemd[1]: Startup finished in 1.645s (kernel) + 8.258s (userspace) = 9.903s.
Jan  8 19:27:48 raspberrypi bluetoothd[496]: Starting SDP server
Jan  8 19:27:48 raspberrypi kernel: [    9.971133] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Jan  8 19:27:48 raspberrypi kernel: [    9.971141] Bluetooth: BNEP filters: protocol multicast
Jan  8 19:27:48 raspberrypi kernel: [    9.971156] Bluetooth: BNEP socket layer initialized
Jan  8 19:27:48 raspberrypi bluetoothd[496]: Bluetooth management interface 1.14 initialized
Jan  8 19:27:48 raspberrypi bluetoothd[496]: Failed to obtain handles for "Service Changed" characteristic
Jan  8 19:27:48 raspberrypi dbus[360]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
Jan  8 19:27:48 raspberrypi bluetoothd[496]: Sap driver initialization failed.
Jan  8 19:27:48 raspberrypi bluetoothd[496]: sap-server: Operation not permitted (1)

Läuft da etwas, was den hci0 blockiert?
Was kann ich noch machen?

Gruss -

[adarof]

...nach Update muss erneut das hier ausgeführt werden:

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

Lesson learned - sorry, legt Euch wieder hin