@Scott Andrew yeah this is exactly the right thing to be thinking about before you deploy, not after — urban 2.4GHz environments are genuinely brutal and the open-field numbers won't translate directly.
The honest answer is that the 5km ground-to-ground spec is going to take a hit in dense urban conditions. How much depends heavily on your node placement — if your modules have any elevation at all (rooftops, upper floors, even lamp posts), you recover a lot of that margin because you're getting above the worst of the ground-level multipath and WiFi saturation. The receiver sensitivity on the MultiNav Pro+ is doing real work here; it's not a commodity module that just gives up when the noise floor rises, but physics is still physics.
The BLE frequency hopping helps with coexistence to some degree — you're not just sitting on one channel getting hammered. But if you're doing city-scale asset tracking, I'd honestly plan your architecture around the assumption that you're working with maybe 30-50% of the open-field range in a dense urban core, and design your node density accordingly. Treat the 5km as your ceiling, not your planning number.
Worth sharing what your node placement situation actually looks like — fixed infrastructure, mobile assets, or a mix? That changes the answer a fair bit.
