@John Johnson yeah this is a solid use case and you're thinking about it the right way. The MultiNav Pro+ is built on the STM32WB07 which gives you full control over the advertising PDU type — you're not stuck with connectable-only, and you don't need to gut the firmware to get there. The AI Firmware Builder in the Dev Hub is honestly the fastest path here: just describe your beacon setup (non-connectable undirected, position + sensor payload, whatever interval you want) and it'll spit out production-ready firmware with the advertising parameters set correctly from the start, no SDK archaeology required.
On your range question — the honest answer is the improvement is real but probably not dramatic in the way you might hope. The RF front end and PA are doing the same work regardless of PDU type, so you're not unlocking hidden TX power. What you do gain is more deterministic channel time since you're not burning intervals on connection request handling or supervision timeouts, which in a dense multi-beacon deployment actually matters more than people expect. Whether that translates to measurable extra meters at the edge of range is deployment-specific — antenna orientation and ground reflection geometry are going to swamp that difference at the distances this module can push.
If you want real comparative data, I'd suggest running both modes at a fixed interval and distance with RSSI logging on the scanner side — that'll tell you more than any theoretical answer. Worth posting your results here too, that kind of field data is genuinely useful for others doing similar deployments.
