Re: Eddystone TLM
Hi Marcio, Luiz,toggle quoted messageShow quoted text
-----Original Message-----Even if we had such an interface we still wouldn't know for sure if a potential observer/scanner had received the adv packet at all. One way to address this would be to add a Vendor Specific HCI event on reception of a Scan Request event. This has been done in the past with good results, and it can be used by the app as a confirmation that an advertisement packet has been received by a peer. It obviously requires scannable advertising.
There is already a radio_active_callback() in the current Bluetooth Controller in Zephyr that can be used for this purpose in combined builds (Host + Controller). What it might be missing is an ID of some sort indicating which kind of operation (conn event, adv event, etc) took place.
We would of course need to expose this to the application via a public interface.