Support bluetooth

[devil304]

@kbrddestroyer I have init sequence and send date command but I wasn't able to test it (even on windows) because communicating via BT is more complicated than USB HID.
Set time command: 5528000000000000d7+ self._format_time(time)
So time command is the same as on USB but with 55 on the beginning.

[devil304]

@kbrddestroyer
RAW untested init sequence:
send 558f00000000000070
rcvd 558ff1040000010070
send 558700000000000078
rcvd 55870104020764
send 77
rcvd 774a0305
send 558700000000000078
rcvd 55870104020764
send 55800000000000007f
rcvd 55800305000000007f
send 55840000000000007b
rcvd 55840001000000007b
send 55850000000000007a
rcvd 55850000000000007a
send 558700000000000078
rcvd 55870104020764
send 558600000000000079
rcvd 558600000000000079
send 55910000000000006e
rcvd 55910001000000006e
send 55920000000000006d
rcvd 5592b400b40008070807
send 559700000000000068
rcvd 559700000000000068

[devil304]

I was capturing it using BT 5.0, so a BT LE (GATT) connection. I don't know why, but BT 3.0 is disconnecting immediately on Windows for me.

[devil304]

I was finally able to communicate at all with the keyboard using BT LE, but I wasn't able to get correct handle 0x002c, which is used by Windows driver to communicate with the keyboard.

[kbrddestroyer]

I bought usb Bluetooth adapter and now waiting for it to be shipped here. At the moment I won't be able to debug anything related to Bluetooth

[devil304]

Ok, no worries I'm still fighting with it, trying to get correct handle 😅

[devil304]

That's what I'm getting so far. This is services and characteristics of GATT client (BT LE) I'm getting.

Service handle: 0x1, sharing mode: Exclusive, session: Active, open status: Success
   Characteristic handle: 0x2, properties: Read
Service handle: 0x4, sharing mode: Unspecified, session: Active, open status: AccessDenied
Service handle: 0x30, sharing mode: Exclusive, session: Active, open status: Success
   Characteristic handle: 0x31, properties: Read, Notify
Service handle: 0x34, sharing mode: Exclusive, session: Active, open status: Success
   Characteristic handle: 0x35, properties: Read
   Characteristic handle: 0x37, properties: Read
Service handle: 0x39, sharing mode: Exclusive, session: Active, open status: Success
   Characteristic handle: 0x3A, properties: Notify
   Characteristic handle: 0x3D, properties: Write

As you can see, I can't access service 0x4 and I'm not getting characteristic with handle 0x2c which we are looking for.

[devil304]

I was trying to unpack Windows driver, hoping I would find something there. And its Electron app (which is good), but it's self contained version with all data in exe rather then in asar package. And I wasn't able to get to any helpful data. But I found something that was a surprise for me. This keyboard is based on open-source firmware QMK. So if I will not get any further with BT the way I'm trying now, then maybe I will try to find source code of this keyboard chip.

[devil304]

@kbrddestroyer on Linux, I tried SimplePyBle library in Python, and I got characteristics from this service, which was inaccessible on Windows and it's looking promising

Service: 00001812-0000-1000-8000-00805f9b34fb
Characteristic: ['read', 'write_command']
Characteristic: ['read', 'write_request', 'notify']
Characteristic: ['read', 'write_request', 'write_command']
Characteristic: ['read']
Characteristic: ['read', 'write_command']
Characteristic: ['read', 'write_request', 'notify']
Characteristic: ['read', 'write_request', 'notify']
Characteristic: ['read', 'write_request', 'notify']
Characteristic: ['read', 'write_request', 'notify']
Characteristic: ['read', 'write_request', 'notify']
Characteristic: ['read', 'write_request', 'notify']
Characteristic: ['read', 'write_request', 'write_command']
Characteristic: ['read', 'write_request', 'write_command']
Characteristic: ['read']

Current problem is that I'm getting Operation Not Authorized from BlueZ (Linux BLE driver) when trying to write to any characteristic.

[devil304]

Current state: I tried using 1:1 BlueZ wrapper for C# and am still getting same exception. So I opened an issue on BlueZ github.

[devil304]

Service UUID: 00001812-0000-1000-8000-00805f9b34fb
/org/bluez/hci0/dev_F4_EE_25_2F_79_E6/service0004/char002b
CUUID: 00002a4d-0000-1000-8000-00805f9b34fb ,Flags: read, write-without-response, write

Service and characteristic for GATT to communicate, still to be tested but I cross-checked with data captured from Windows driver

[kbrddestroyer]

I did not manage to communicate with keyboard via Bluetooth either

[devil304]

@kbrddestroyer I'm still working on that, in my free time 😅

[devil304]

This is service and path to characteristic on dbus

'org.bluez.GattCharacteristic1', '/org/bluez/hci0/dev_F4_EE_25_2F_79_E6/service0004/char002b

(where F4_EE_25_2F_79_E6 is BT address of device)
I'm trying to use dbus bindings for python but dbus-fast is complicated

I checked that, according to Wireshark, Windows driver for this keyboard isn't making any explicit connections to it, and messages aren't encrypted. It just sends a normal message on that characteristic, and that's it. But I don't know how when this characteristic is inaccessible using any method I tried so far.

[kbrddestroyer]

I'm sorry, I was busy this month with some work
I'll try to add Bluetooth support right after the GIF branch merge

[devil304]

I sadly wasn't able to do any further progress.