Managing Redundant Bluetooth LE Connections

this article explains how ditto manages redundant bluetooth low energy (le) connections within the mesh network by default, the tradeoffs with mesh size in mind, and how to deviate from this default behavior so you can ensure continuous sync uptime in your mesh /#default ditto behavior /#considerations by mesh size /#enabling redundant connections default ditto behavior by default, if a peer is already connected through a transport other than bluetooth le, such as lan, apple wireless direct link (awdl), and so on, ditto avoids these redundant connections to ensure optimal sync performance in the mesh considerations by mesh size maintaining redundant bluetooth le connections can impact sync performance, especially in larger meshes with approximately 65 to 100 devices or more, where increased network overhead may cause a slowdown in the data replication process however, in some use cases, such as the point of sale (pos) system, where continuous operation is mission critical, the benefits of having fallback connections outweigh this loss in sync performance for example, in a pos system, maintaining redundant connections may be preferred since any delay in establishing a mesh connection if wi fi becomes unavailable negatively affects business operations enabling redundant connections to change the default behavior and enable redundant connections, set the system parameter mesh chooser avoid redundant bluetooth to false dql alter system set mesh chooser avoid redundant bluetooth = false