I have 2 objectives BT beacon and concurrent ESB with Thread using time slotting
A.
I would like my thread devices to broadcast BT beacons.
As this does not require any reception and is only a short message send once a sec or so.
I really do not want a complete soft device adding 151kb to a code when i only need about 2kb (working bt beacon based on nordic github example).
The primary radio owner should be thread which with BT is normal not possible due to time restrictions of BT. But as i see should be no problem with BT beacon...
B.
Due to the fact that Openthread will ignore otherwise correct received multicast packets because of it's logical bonding with it's routers.
It is very difficult to disseminate a lot of common data quickly and there is a very low security of packet delivery as eg children only accepts broadcast from is connected router...
Therefore i would like to use a proprietary ESB protocol for the one to many data. Most likely most of the time but keep thread for peer to peer and network structure.
As I see it both objectives share a common question.
Add note. As the Bt beacon is very simple it could also be considered a custom implementation as with ESB.
Leading to the question:
Can I use the radio arbiter api to have thread and a proprietary ESB protocol concurrently or is the arbiter "buisness code" only implemented in the softdevice?
