Heerko Groefsema

Is it only the keyboard_example that produces the stack overflow, or also the mouse_example and joystick_examples?

I'm going to assume the code is registering constant key presses. This might be because the software is assuming pins having pull down resistors, while the hardware is using pull...

The code will only start advertising the device (for a short while) after a pin is triggered. If this pin will remain triggered constantly, it might explain the stackoverflow. In...

Can you try to call co_start_test() instead of the normal start? ``` if __name__ == "__main__": d = Device() d.co_start_test() ``` Note that once this test starts, you have 30...

Thank you so much for testing this. Since I do not own an ESP32C3 board and currently don't have access to my ESP32 board, I am going to have to...

Could be indeed. I would really like to see the outcome of the 3rd test though, because that could mean I messed something up!

This is odd. You're mentioning a reset. Is this a full power cycle on the keyboard? If so, the Bluetooth might require pairing again. Note that this package does not...

I'm assuming you are using my keyboard example and that you're calling d.stop() before calling d.start() for the second time. The way this simple keyboard example works is that in...

Ok, thanks. I think this is an issue where (somehow) Windows doesn't recognize the device as the same one that was paired earlier. I'm unsure why this is happening. It...

I have been able to replicate your issue. The issue appears when the bluetooth device is restarted either through a hardware reset or by the software calling `stop()`, creating a...