I was working on a private mesh standard for a startup a few years back because of a perceived opportunity resulting from the fractured nature of the ecosystem,

I was working on a private mesh standard for a startup a few years back because of a perceived opportunity resulting from the fractured nature of the ecosystem, resulting in no devices really using mesh. We have Bluetooth mesh, Wifi mesh standards, Thread, Alljoyn, and plenty more, but no one is benefitting from any mesh protocols in day to day life. Some of these standards are decent technologically, but the real problem comes down to device drivers. Most wifi/bluetooth devices have drivers (and sometimes firmware, too) which are completely inflexible in sending out frames outside of their standard protocols. This is especially difficult with the abstraction layers programmed into the firmware and the fact that very different hardware is used to share spectrum (to optimize for time hopping on bluetooth, for example). The solution: adoption of a standardized, Linux-like driver protocol for enabling custom frames to easily be sent and received on shared spectrum BEFORE adoption of the protocols built on top. That being said, augmenting the Wifi standard to support mesh is probably the closest development to that goal that I've seen in a while, since vendors typically start supporting the new 802.11 standards pretty quickly.