Hello
When I tried to learn the development of nrf54H20, I run some samples supplied in the SDK2.7.0.
Most of them works well.
But when i try the Bluetooth: Multiple advertising sets, the result seems does not match the description.
In the description, we can see that there should be two advertise, one is named "Nordic Beacon", which is a unconnectable advertise, another one is named "Nordic multi adv sets", which is a connectable advertise.
But when i built it then burned it to the nRF54H20 DK, i found there is no "Nordic Beacon" advertise can be found through the nRF Connect for Mobile application, but only the "Nordic multi adv sets" advertise.
During my researching, I found that the advertise name which was supposed to be 'Nordic Beacon', but has been changed to 'Nor'.
And after my debugging, i found there are three things caused that result.
1. the non_connectable_data use the "Nordic multi adv sets" name.
2.the data length is too long so the complete name(0x09 type) was coverted to shortened name(0x08 type)
So it was only show the first three letters.
That URI can prove that this is the advertise we want that cannot be connected to.
3.the bt_set_name api seems not work well or to be using the wrong usage
At least it seems possible that the name set in "connectable_adv_create" may override the name set in "non_connectable_adv_create", even if this API works well, it seems to be globally effective.
So I feel that this example did not achieve the expected purpose and does not correspond to the description in the Testing process, so I am raising this issue to you here. Can you help confirm it.
Thank you very much!