<p>We finally mostly live in the WiFi future. Dual band access points are more common than not, and there are <ahref="https://on.google.com/hub/">cloud managed consumer models</a>. <ahref="https://en.m.wikipedia.org/wiki/IEEE_802.11ac">802.11ac</a> is de rigueur and flavors of <ahref="https://en.m.wikipedia.org/wiki/MIMO">MIMO</a> are in abundance. <ahref="https://en.m.wikipedia.org/wiki/IEEE_802.11h-2003">DFS</a> counterbalances the ever expanding channel width issues in 5 GHz with more available channel space.</p>
<p>The 2.4 GHz disaster area, however, lives on. Its wall penetrating abilities, once a selling point, now terrorize apartment complexes. Even in my detached house, a WiFi scanner left open overnight has a list of 2.4 GHz BSSIDs that requires scrolling, stomping over each other on the three effective channels. There’s even a <ahref="http://www.smallnetbuilder.com/wireless/wireless-features/31743-bye-bye-40-mhz-mode-in-24-ghz-part-1">2.4 GHz 40 MHz</a> BSSID in there, to my horror (and it’s a printer!).</p>
<p>Why can’t we have nice things? Access points let you turn off 2.4 GHz and leave all this behind, right? <ahref="https://en.m.wikipedia.org/wiki/Beamforming">Beamforming</a> and other fanciness gets us range in 5 GHz, right? Worst case, <ahref="https://www.eero.com/">mesh access points</a> are becoming a consumer thing, and we can get stations close to every client, right?</p>
<p>Wrong. Unfortunately, there are still device manufacturers out there who think that dual band is only for fancy people, not for their devices. The extra dollar for the better chip and antenna would blow their margins.</p>
<p>Let’s start with the good news: those who have recently learned their lessons.</p>
<ul>
<li>The <ahref="https://www.google.com/intl/en_us/chromecast/tv/">Chromecast 2</a> adds 802.11ac support, where the previous version only supported 2.4 GHz. Unfortunately, its antennas are still tiny, so sandwiching it behind a wall-mount TV is style over substance. It also has a <ahref="https://code.google.com/p/google-cast-sdk/issues/detail?id=676">strange problem with 802.11r</a>.</li>
<li>The <ahref="http://www.amazon.com/Amazon-W87CUN-Fire-TV-Stick/dp/B00GDQ0RMG">FireTV Stick</a> supports 5 GHz 802.11n, but amazingly not the DFS channels. The <ahref="http://www.amazon.com/gp/product/B00U3FPN4U">FireTV</a> adds 802.11ac, but is still broken for DFS.</li>
<li>The <ahref="http://www.amazon.com/Nest-Learning-Thermostat-3rd-Generation/dp/B0131RG6VK">third generation</a> of the Nest Thermostat adds 5 GHz support, though 802.11n only.
Google’s Nexus line has supported 802.11ac for awhile now. However, at least the Nexus 9 was <ahref="https://productforums.google.com/forum/#!topic/nexus/_dOk9Jfv9CA">quirky</a> in 5 GHz. The <ahref="https://pixel.google.com/pixel-c/">Pixel C</a> seems to be fine.</li>
</ul>
<p>On to the ugly:</p>
<ul>
<li>The <ahref="https://nest.com/support/article/Nest-Protect-2nd-generation-system-requirements-and-technical-specifications">Nest Protect</a>, while cool, is 2.4 GHz only. Presumably, this is because the wired and battery-only models need to communicate and saving battery is critical on the latter.</li>
<li>Chamberlain’s <ahref="http://chamberlain.custhelp.com/app/answers/detail/a_id/6067/~/why-wont-the-wi-fi-garage-door-opener-or-myq-garage-%28wi-fi-hub%29-connect-to-my">connected garage door gear</a> is 2.4 GHz only. This is a bit more sad, since it’s all wired power.</li>
<li>The <ahref="https://developer.qualcomm.com/hardware/dragonboard-410c">DragonBoard 410c</a>, the new hotness in the Raspberry Pi-like world, is 2.4 GHz only. More power budget problems?</li>
<li><ahref="https://www.amazon.com/oc/dash-button">Amazon Dash Buttons</a> seem to be yet another low-power case; 2.4 GHz only.</li>
</ul>
<p>It’s nice to see this list getting shorter. It’s sad to see brand new devices or top-of-product-line devices shipping with 2.4 GHz only.</p>
