02-12-2020, 01:16 PM
First of all, it is strange that you needed to change the name in the config file, because it is supposed to connect to anything that contains the set name in its name. So it should work even if the Micro:Bit adds the [abcde] part at the end. Could this just have been a coincidence as it only worked once anyway or are you sure that it is not working without the "[tetat]"?
The error message means that phyphox was able to connect to the Micro:Bit, but the Micro:Bit did not offer the LED service. Did you flash a sketch onto the Micro:Bit that launches the Bluetooth LED service?
If you are unsure about this, you can also try to connect to the Micro:Bit with an app called "nRF Connect" by Nordic Semiconductor (disclaimer: This is not our work and we have no connection to Nordic Semiconductor). With this you can connect to any BLE device and check the services offered by the device. If your Micro:Bit is set up correctly, you should see the "micro:bit LED Service". Interestingly, I just found that nRF Connect actually detects the micro:bit and has some demo macros to test the LED service.
The error message means that phyphox was able to connect to the Micro:Bit, but the Micro:Bit did not offer the LED service. Did you flash a sketch onto the Micro:Bit that launches the Bluetooth LED service?
If you are unsure about this, you can also try to connect to the Micro:Bit with an app called "nRF Connect" by Nordic Semiconductor (disclaimer: This is not our work and we have no connection to Nordic Semiconductor). With this you can connect to any BLE device and check the services offered by the device. If your Micro:Bit is set up correctly, you should see the "micro:bit LED Service". Interestingly, I just found that nRF Connect actually detects the micro:bit and has some demo macros to test the LED service.