>A licensed existing solution or something custom? We went with something licensed. >Do you think this applies to most use cases? I should have included "tim

>A licensed existing solution or something custom? We went with something licensed. >Do you think this applies to most use cases? I should have included "time slotting AND channel hopping." Given how congested the 2.4GHz band is, I think it does apply to a lot of battery powered use cases (especially wearables). Some use cases see a far greater benefit than others. The deployment environment also plays a big part. If you have a lot of traffic on a channel, the radio hops to another channel so there's reduced error rates (reduced transmission reattempts = saved energy). If you have a quiet radio environment and a lot of devices that communicate infrequently or a very small number of devices on the mesh, you may not see a huge benefit. One downside of a time slot channel hopping protocol is that you need a more expensive crystal in your hardware for accurate time keeping/scheduling. Upside is that you have a reduced total cost of ownership as you need to buy fewer replaceable batteries.