You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So, I got the LilyGO T-Keyboard, powered it on and went to the BLE config under Windows 10 and was able to pair the device. After that, there is no "keyboard" functionality. The device also will periodically disconnect and say "Wait bluetooth...." and then finally connect.
I plugged the T-Keyboard into a USB port and pulled up a terminal program and see this constantly (as fast as the serial console will display at 115200 baud):
So, does this mean that the T-Keyboard is not compatible with Windows? I tried the PC motherboard's built-in Bluetooth and an external Bluetooth (USB) device, and both had the same issue. Ironically, this works flawless with my iPhone13 so I know the T-Keyboard hardware is functional. This seems like a problem with interfacing to Windows. Does anyone know why?
The text was updated successfully, but these errors were encountered:
So, I got the LilyGO T-Keyboard, powered it on and went to the BLE config under Windows 10 and was able to pair the device. After that, there is no "keyboard" functionality. The device also will periodically disconnect and say "Wait bluetooth...." and then finally connect.
I plugged the T-Keyboard into a USB port and pulled up a terminal program and see this constantly (as fast as the serial console will display at 115200 baud):
[2319993][E][BLECharacteristic.cpp:537] notify(): << esp_ble_gatts_send_ notify: rc=-1 Unknown ESP_ERR error
So, does this mean that the T-Keyboard is not compatible with Windows? I tried the PC motherboard's built-in Bluetooth and an external Bluetooth (USB) device, and both had the same issue. Ironically, this works flawless with my iPhone13 so I know the T-Keyboard hardware is functional. This seems like a problem with interfacing to Windows. Does anyone know why?
The text was updated successfully, but these errors were encountered: