The notion of running slowly when nothing is happening and then responding when potentially relevant headers are detected and speeding up makes a lot of sense. This would be especially beneficial in environments lacking signals - which currently seem to cause the phones to go into overdrive seeking a signal. The effort fails and the battery is quickly drained for no reason. If nothing relevant is happening, the slow clock nap is a great strategy.
There is a sleep mode in WiFi which enables a client device to tell the AP that it will not be listening until it awakes and polls the AP. Since this discussion doesn't even acknowledge that capability, I'm skeptical of any of the rest of the claims within the article.
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.