Ryan Powell
Ryan Powell
I'm going to guess that the devices on coded phy are generating a new address every time the restart. You may have to either bond with them so the identity...
What device are you using? I know that the controller in the S3 has some flakey coded phy handling where the devices that use the nimble controller (c6) work perfectly.
I suspect this is an issue in the controller then, which is not part of this library and is closed source. I'll try to verify this and then raise an...
Should be workable after #2177 is merged, Zigbee support is a ways off though.
2.0.0 was an accidental release and is still pending removal from the library manager unfortunately. I suggest reverting back to 1.4.3 until 2.0.0 is officially released with the documentation to...
Okay, that's cool 😄. Do you have another device you can test with, perhaps an esp32?
This has been covered in #703
No easy way to do that. If the device is already connected you would need to either disconnect and advertise so the other device can connect or start advertising after...
I suspect you are doing too much in your callbacks. You can either increase the nimble host task stack size or move your code out of the callbacks and just...