The discussion in https://devzone.nordicsemi.com/f/nordic-q-a/79364/maximum-number-of-bytes-that-can-be-used-in-beacon-advertising suggests that we should be able to populate 27 bytes of a beacon, with the remainder consisting of Manufacturer ID, length, and a type byte. However, none of the examples suggest how to actually do this. we were using extended beacons but ran into a use case where the recipient only had BLE 4.2 so now it's about how many bytes we can squeeze out of traditional beacons...
My experiments with using ble_advdata_manuf_data_t and calling ble_data_encode() suggest that I can only directly affect the contents of a much smaller number of bytes without getting an NRF_ERROR_DATA_SIZE error.
I then tried just manually put in the 2 bytes of Manufacturer ID, a type (??) and a length (31 or 27?) then put in data, without calling ble_data_encode(). What I got back was BLE_ERROR_GAP_UUID_LIST_MISMATCH, so apparently that's not quite the correct approach. Suggestions would be most welcome.
Thanks!