A customer recently decided to upgrade their monitoring device to include bA's mesh networking capability in a relatively small environment. This small environment hosts less than 100 nodes including the coordinator. This small area exposed an interesting problem with academic mesh networking knowledge when distance isn't the primary factor in utilizing a mesh network:

When mesh networks are deployed in a localized region they should never report directly to a broadcast request. If the B tree implementation is used for Source it should also be used for Destination.

The default Data Logger on this network, for example, would periodically send a Node Discover broadcast request to the network and expect the top level routers to respond. Since the routers default to responding via the least number of hops and the distance between the nodes was negligible, they all responded directly to the coordinator and subsequently flooded the UART of the receiving device.