Hi @frank_schmidt, I think I already answered here: Extension Conflict?, but the basic summary: Both Bluetooth and NeoPixels require really precise timing and both are at the limit of what the v1 could do. It couldn’t reliably do both at the same time. The ColorBit extension uses Microsoft’s ws2812b (NeoPixel) Extension…Microsoft was aware that you couldn’t reliably use both Bluetooth and NeoPixels, so they made their ws2812b extension mutually exclusive with Bluetooth…which means that the ColorBit also ends up disablinging Bluetooth.
About the only alternative is to use some other external module that eliminates the timing problem or use multiple micro:bits. For example, two micro:bits could communicate over a wired (serial) connection. One micro:bit would be able to handle bluetooth and the other neopixels. Of course, this introduces others sources of complexity 