Thanks, Stefan. That's useful to know. I've just done some searching and found this note: If you use filters (like namePrefix) to find a device, you must still specify the services you plan to access in the optionalServices array to connect to them. So you might need to have something like the follo...

You could try the filter property set to the following, assuming this is the correct Service ID for your hardware project: filters: [ { services: [0xffe0] } ] I tried a test project on my mobile phone and I had to use the Chrome browser. I tried another browser and that did nothing, presumably becau...

Thanks for reporting this. I wonder if it is related to this post:
https://www.flowcode.co.uk/forums/viewtopic.php?t=1505

Anyway, we'll have a look and get this fixed.

I think that filter should work. The Service and Characteristic values needs to be correct for your ESP32 device. If you call "RequestDevice", the browser should ask to connect to your device. Once connected, the "OnValueChanged" macro should be called when the data for that Char...

Yes, that's the component. But a slightly newer version is attached here (this one has a proper icon). The complication is the "filter" expression. Due to domain origin issues in (most?) browsers, this needs to reference the actual device being connected to. There are examples in the toolt...

BTW, a beta version of the BLE Web Developer component was posted by Ben here:
viewtopic.php?p=22575#p22575

Have you managed to tried it? This might actually work as-is. But if it doesn't, it would be useful to know.

Great news, Daniel. Thanks for letting us know.

I'm glad my input was of some small use.

I have made a Web Developer component, but it is currently unreleased and needs a little more work. I'll look into it again and see if we can get something out soon.

I've not make a bootloader for this type of device, but I did a quick search and found this which may be of help: https://support.microchip.com/s/article/PIC24-dsPIC33-bootloaders---How-to-Create-and-Verify-a-Custom-Linker-File You probably don't need to create a linker script that deals with both t...

Do you know what specific source code it being compiled to live within the bootloader area? Or is the problem just that the IVT code is not being placed into the relocated area? Or is it something else? It might help to create a *very* simple example of the issue in MPLAB and replicate it in Flowcod...