h2zero

Please try enabling nimble in your config or adding my esp-nimble-component library to your components folder.

I didn't think this would be too much of an issue since the vector would just allocate up to the peak number of devices found and not need to allocate...

If you are not using the broadcaster role then you should also disable the peripheral role and it will work. I'll address this with a macro in a future patch.

From the logs: >E NimBLERemoteCharacteristic: "

>Either that, or doing a single WriteValue with 36 bytes is causing the problem (but I thought it was allowed to send up to the MTU value in one go...

The remote device may not be able to support that much data in it's characteristic buffer. I don't have an answer to that but long writes in the library happen...

This is the way it is represented by the NimBLE stack, thus it is the "native" address. Unfortunately this does cause some confusion for users occasionally.

Hi @BarakChamo I have not tried compiling for the S3 yet. As you have pointed out there are differences that need to be accounted for on the different chips. Looks...

I don't have any specific classes for this but it could be done quite simply with the existing framework. There are multiple ways to handle this but packetizing would seem...

Thanks for testing it, it seemed to be working for me last night but that wasn't a thorough test and I can confirm some scanners don't read it. You were...