Band steering silently breaks IoT device setup flows
telecomtelecom0 views
Modern routers use 'band steering' to automatically move devices between 2.4GHz and 5GHz under a single SSID. But many IoT devices (smart plugs, cameras, thermostats) require 2.4GHz during initial setup and use Bluetooth or a temporary AP to discover the network. Band steering causes the phone running the setup app to jump to 5GHz mid-setup, breaking the provisioning handshake. So what? The IoT device fails to connect, showing a vague 'connection failed' error. So what? Users retry 5-10 times, then Google the problem and find forum posts saying 'disable band steering' or 'create a separate 2.4GHz SSID.' So what? Disabling band steering degrades the experience for all other devices (laptops, phones, tablets) that benefit from automatic band selection. Creating a separate SSID means managing two networks and remembering which devices are on which. So what? A 15-minute smart plug setup becomes a 2-hour networking project that requires knowledge most consumers don't have. This persists because router manufacturers and IoT manufacturers don't coordinate — routers optimize for seamless multi-band, while IoT devices assume a single-band network. Neither side considers the other's behavior during the critical setup flow.
Evidence
TP-Link, Eero, and Google Nest WiFi all enable band steering by default with a single merged SSID. The r/smarthome and r/HomeKit subreddits have hundreds of posts about IoT setup failures resolved by temporarily disabling band steering. Amazon reviews for TP-Link Kasa smart plugs frequently cite 'won't connect to WiFi' with the fix being a separate 2.4GHz network. Apple HomeKit's setup documentation officially recommends a single SSID but many devices fail under band steering.