IoT

IoT extends internet connectivity beyond traditional computers and phones to everyday physical objects. A smart thermostat reports temperature and receives schedule changes. A security camera streams video to the cloud. A connected washing machine sends a notification when the cycle ends. Each device is a small network node — typically running a stripped-down OS on low-power hardware with Wi-Fi, Ethernet, Zigbee, or Bluetooth connectivity.

Common IoT devices on a home network

A typical smart home accumulates IoT devices quickly. Common categories include:

• Lighting — smart bulbs and switches (Philips Hue, LIFX, Lutron)
• Power and energy — smart plugs, outlet switches, energy monitors
• Security — video doorbells, indoor and outdoor cameras, smart locks, motion sensors
• Climate — smart thermostats (Nest, Ecobee), air quality monitors, smart vents
• Appliances — connected refrigerators, washing machines, dishwashers, robot vacuums
• Entertainment — smart TVs, streaming sticks, voice assistants (Echo, Google Home)

A home with a moderate smart home setup can easily reach 30–50 connected IoT devices. Each occupies a DHCP lease, an entry in the router's connection table, and generates periodic background traffic.

IoT connectivity types

IoT security risks

IoT devices are among the most frequently compromised devices on home networks for several compounding reasons. Many ship with weak or default credentials (admin/admin, or a password printed on a label) that owners never change. Unlike phones and computers, IoT devices typically have no display or notification mechanism to alert users when a firmware update is available — many owners never apply a single update over the device's lifetime. Manufacturers frequently discontinue software support for older models while the hardware continues to function. An attacker who compromises a camera or smart plug gains a foothold inside your network from which they can scan for other devices, intercept traffic, or launch further attacks.

IoT network isolation

The standard defence against IoT compromise is network segmentation. Create a dedicated VLAN or guest Wi-Fi network for all IoT devices and configure your router or firewall to prevent traffic from flowing between the IoT segment and your main LAN. A compromised smart bulb on the IoT VLAN cannot reach your NAS, laptops, or phones on the main network. Most modern mesh Wi-Fi systems and mid-range routers support this configuration. At minimum, use the router's guest Wi-Fi feature for IoT devices if VLANs are not available — guest networks isolate clients from each other and from the main LAN by default on most consumer hardware.

IoT and 2.4 GHz vs 5 GHz

The majority of IoT devices — smart bulbs, plugs, sensors, cameras, thermostats — support only 2.4 GHz Wi-Fi. This is because 2.4 GHz has longer range and better wall penetration than 5 GHz, suits the low-bandwidth needs of most IoT devices, and allows manufacturers to use cheaper, lower-power Wi-Fi chipsets. When setting up an IoT device, ensure you are connecting it to your 2.4 GHz network, not the 5 GHz band. Many modern routers combine both bands under a single SSID (band steering) — this can cause confusion during IoT setup. If a device fails to connect, temporarily disabling the 5 GHz band or creating a dedicated 2.4 GHz SSID resolves most setup issues.

Bandwidth consumption of IoT devices

Most IoT sensors and controls consume negligible bandwidth — a thermostat checking in every minute uses kilobytes per day. Security cameras are the exception. A single 1080p camera streaming continuously to the cloud at 1–2 Mbps consumes 10–20 GB per day. Four cameras can consume your entire monthly data allowance on a capped ISP plan. Local recording (to NVR or NAS via RTSP) eliminates cloud upload bandwidth. Higher-resolution cameras (4K) multiply this further. When planning a camera system, account for upload bandwidth — a 50 Mbps upload connection handles roughly 20–25 HD cameras streaming simultaneously.

Matter and Thread — the new unified standard

Matter is an open connectivity standard (formerly Project CHIP) backed by Apple, Google, Amazon, and Samsung that aims to unify smart home device interoperability. A Matter-certified device works with any Matter-compatible hub or voice assistant regardless of brand, ending the fragmentation of proprietary ecosystems. Thread is the IP-based mesh networking protocol that Matter uses for low-power devices — sensors, locks, and bulbs form a self-healing mesh network that routes around failures. Thread requires a Thread Border Router (built into Apple TV 4K, HomePod, Nest Hub, and others) to bridge the Thread mesh to your IP network. Matter over Wi-Fi is also supported for higher-bandwidth devices.

IoT device limits on cheap routers

Consumer routers maintain a connection tracking table (NAT table) with a finite number of entries — typically 4,096 to 16,384 concurrent connections on budget hardware. Each IoT device that communicates with the internet holds one or more table entries. At 50+ devices each making multiple cloud connections, cheaper routers can exhaust their connection tables, causing new connections to fail intermittently. Signs include random devices losing internet connectivity despite showing Wi-Fi connected. The fix is a router with a larger connection table or one specifically designed for dense IoT deployments.

IoT and IPv6

IPv6 is well-suited to IoT because it eliminates the NAT layer that creates complications for inbound connections and peer-to-peer communication between devices. Each IoT device can have its own globally unique IPv6 address, simplifying remote access without port forwarding. However, this also means each device is directly reachable from the internet if the firewall is not configured to block unsolicited inbound IPv6 traffic — a firewall rule that is often overlooked during IPv6 deployment. Thread uses IPv6 natively for all device addressing within the mesh network.

Frequently Asked Questions

How do IoT devices affect my home network?

Each device occupies an IP address and generates background traffic — polling cloud servers, syncing state, streaming data. A home with 30+ IoT devices creates constant low-level load. More critically, IoT devices are frequent attack targets; isolate them on a separate VLAN or guest network.

What protocols do IoT devices use?

Wi-Fi and Ethernet for IP connectivity; Zigbee and Z-Wave for low-power mesh; MQTT for lightweight machine-to-machine messaging; Bluetooth LE for close-range; and often proprietary cloud APIs over HTTPS.

Are IoT devices a security risk?

Yes — they frequently ship with default or weak credentials and rarely receive updates. Change default passwords immediately, enable automatic firmware updates, and isolate IoT devices on a separate network segment from your main devices.