I agree completely regarding the disadvantages of using frequencies that propagate well. It actually makes more sense to me to work within the ISM spectrum with a P2P protocol that is frequency-agile. This is simpler both in terms of certification and in terms of minimizing interference with critical functionality. This is where most of the ad-hoc networking experiments are taking place anyway.
Oh, and there's anbother point that keeps getting overlooked. The power levels required for long range (say in the multiple miles) reliable communications, ESPECIALLY for tiny devices with likely tiny antennas, operating in the TV bands, are not going to be low.
This is all easy enough to calculate. If you expect efficient use of the limited TV white space spectrum, where thousands or millions of devices would coexist in a few 6 MHz slices of spectrum, the power will be nowhere near the low milliwatt region. Even if each device doesn't need a lot of b/s of network capacity.
I think we already discussed the fact that *if* IoT is done wirelessly, *then* this would require a hefty amount of "frequency reuse" to scale at all.
And that the long range prowess of TV frequencies, since that is the feature of TV frequencies that is being touted as particularly useful here, is exactly what you DON'T want, if you need a lot of frequency reuse. For good frequency reuse, you need to create small cells, not cells that can be multiple tens of miles in diameter.
My suggestion is, mentioning TV spectrum "white spaces" because, at least in some parts of the country, they are available spectrum is okay. However mentioning the long range is a counter-argument that blows the whole case.
I did some numbers last time around. The way to improve on my *clearly* unimpressive result was to reduce the range of the RF link. So to be consistent, it makes more sense to talk about short range use of TV white spaces, e.g. as wireless mikes do, and show just how much of an interference problem the low TV frequencies create, in this scenario. And keep the long range capabilities sort of under the table.
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.