Closed seime closed 1 year ago
@seime Can you verify if this issue still happens with the latest 4.0.0 snapshot? As i'm working on improving the bluetooth bindings by adding null annotations i suspect it was allready fixed.
If not i'll try to come up with a solution. At that point it would be helpfull if you set the binding at log leverl debug.
I no longer have this setup as usbip was too flaky, but maybe it is possible to reproduce it by simply disconnecting the bluetooth usb adapter?
I don't own this device, so i can't reproduce it. And you don't have this setup anymore, so i think we better close this issue and re-open whenever there is a need to.
Setup: PI 4b, no local Bluetooth dongle but connected via usbip.
This happens when the USB-adapter disappers (
lsusb
does no longer report it) on the openhab side (due to usbip stops working). The binding remains in this state even if adapter is reconnected, and continues to spit out these exceptions every 10s.Expected behaviour:
Restarting openHAB solves the problem (not necessary to restart os bluetooth.service)
Tried to update
bluez-dbus-osgi
to0.1.4
without success.