Closed johnkjellberg closed 2 years ago
Are you running the latest bluez including recent patches? I had same issue with an older version of bluez and it seems very robust now.
I will try and report back. My Bluez was a couple of weeks old.
That didn't help. Every couple of seconds I get the following output from the daemon(80:E4:DA:70:91:A7 is my Flic that won't work until I restart the daemon, the others work):
Button::gdBusDeviceSignalCallback, message received: PropertiesChanged [80:E4:DA:70:91:A7]
('org.bluez.Device1', {'Connected': <false>}, @as []) [80:E4:DA:70:91:A7]
check [80:E4:DA:70:91:A7]
Verifying -> Disconnecting [80:E4:DA:70:91:A7]
Button disconnecting [80:E4:DA:70:91:A7]
close [80:E4:DA:70:91:A7]
cancelCalls [80:E4:DA:70:91:A7]
stopCharacteristics [80:E4:DA:70:91:A7]
stopButtonCharacteristic [80:E4:DA:70:91:A7]
stopConfigCharacteristic [80:E4:DA:70:91:A7]
check [80:E4:DA:70:91:A7]
gdBusButtonCharacteristicStopNotifyCallbackCancellable not null [80:E4:DA:70:91:A7]
gdBusConfigCharacteristicStopNotifyCallbackCancellable not null [80:E4:DA:70:91:A7]
Button::gdBusButtonCharacteristicStopNotifyCallback [80:E4:DA:70:91:A7]
Successfully stopped notify on button characteristics [80:E4:DA:70:91:A7]
check [80:E4:DA:70:91:A7]
gdBusConfigCharacteristicStopNotifyCallbackCancellable not null [80:E4:DA:70:91:A7]
Button::gdBusConfigCharacteristicStopNotifyCallback [80:E4:DA:70:91:A7]
Successfully stopped notify on config characteristics [80:E4:DA:70:91:A7]
check [80:E4:DA:70:91:A7]
Disconnecting -> Disconnected [80:E4:DA:70:91:A7]
Button disconnected [80:E4:DA:70:91:A7]
check [80:E4:DA:70:91:A7]
Button::gdBusDeviceSignalCallback, message received: PropertiesChanged [80:E4:DA:70:91:A7]
('org.bluez.Device1', {'Connected': <true>}, @as []) [80:E4:DA:70:91:A7]
check [80:E4:DA:70:91:A7]
Disconnected -> Connecting [80:E4:DA:70:91:A7]
Button connecting [80:E4:DA:70:91:A7]
startCharacteristics [80:E4:DA:70:91:A7]
startButtonCharacteristic [80:E4:DA:70:91:A7]
startConfigCharacteristic [80:E4:DA:70:91:A7]
check [80:E4:DA:70:91:A7]
startCharacteristics [80:E4:DA:70:91:A7]
startButtonCharacteristic [80:E4:DA:70:91:A7]
Failed to start notify on button characteristic: this call is pending [80:E4:DA:70:91:A7]
startConfigCharacteristic [80:E4:DA:70:91:A7]
Failed to start notify on config characteristic: this call is pending [80:E4:DA:70:91:A7]
Button::gdBusButtonCharacteristicStartNotifyCallback [80:E4:DA:70:91:A7]
Successfully started notify on button characteristics [80:E4:DA:70:91:A7]
check [80:E4:DA:70:91:A7]
startCharacteristics [80:E4:DA:70:91:A7]
startConfigCharacteristic [80:E4:DA:70:91:A7]
Failed to start notify on config characteristic: this call is pending [80:E4:DA:70:91:A7]
Button::gdBusConfigCharacteristicStartNotifyCallback [80:E4:DA:70:91:A7]
Successfully started notify on config characteristics [80:E4:DA:70:91:A7]
check [80:E4:DA:70:91:A7]
startCharacteristics [80:E4:DA:70:91:A7]
Button::gdBusButtonCharacteristicSignalCallback, message receieved: PropertiesChanged [80:E4:DA:70:91:A7]
('org.bluez.GattCharacteristic1', {'Notifying': <true>}, @as []) [80:E4:DA:70:91:A7]
check [80:E4:DA:70:91:A7]
startCharacteristics [80:E4:DA:70:91:A7]
Button::gdBusConfigCharacteristicSignalCallback, message received: PropertiesChanged [80:E4:DA:70:91:A7]
('org.bluez.GattCharacteristic1', {'Notifying': <true>}, @as []) [80:E4:DA:70:91:A7]
check [80:E4:DA:70:91:A7]
startCharacteristics [80:E4:DA:70:91:A7]
Connecting -> Connected [80:E4:DA:70:91:A7]
Button connected [80:E4:DA:70:91:A7]
Connected -> Verifying [80:E4:DA:70:91:A7]
check [80:E4:DA:70:91:A7]
Button::gdBusConfigCharacteristicSignalCallback, message received: PropertiesChanged [80:E4:DA:70:91:A7]
('org.bluez.GattCharacteristic1', {'Value': <[byte 0x40, 0xef, 0x03, 0x8e, 0xba, 0x11, 0xae, 0x42, 0x6e, 0x83, 0x29, 0x34, 0xd6, 0x74, 0xb5, 0xed, 0x90, 0x2f, 0x4d, 0x3e]>}, @as []) [80:E4:DA:70:91:A7]
Startup type: 64 [80:E4:DA:70:91:A7]
check [80:E4:DA:70:91:A7]
Button::gdBusConfigCharacteristicVerifyReadValueCallback [80:E4:DA:70:91:A7]
check [80:E4:DA:70:91:A7]
Button::gdBusConfigCharacteristicQuickVerifyWriteValueCallback [80:E4:DA:70:91:A7]
check [80:E4:DA:70:91:A7]
I'm running "armv7l" version of the daemon on a RPi 2. After about a day it stops working for a specific Flic. That Flic does not flash red, so I guess it is still connected somehow. It works fine for other Flics. And as soon as i restart the daemon it works again.
Not sure what data I can send you. Since the log is missing timestamps I'm not really sure what data is relevant.