So we have a great set of 52832-based set of products in the field that negotiate, agree to, and support MTUs larger than 23 bytes. Nordic's is incidentally one of the least trouble-ridden SoCs and s/w stacks I've ever worked with. One of our products handles multiple peripherals simultaneously while also acting as a BLE central and periph.
Anyway I can't force nRF usage everywhere and have a need to talk to a class of periphs that come up short in 4.2 hardware compatibility with respect to supporting MTUs > 23 bytes even though they'll agree to it during negotiation. Does anyone have a pointer to the rpi/bluepy workaround for this issue? Failing that I'll fragment the messages myself and ask the other fellow to buffer until the end of message but a nice fix in the bluepy side would be a lot easier for all involved.
TIA Howard
