Definition
WiFi IoT uses WiFi (802.11 series) networks to connect smart devices, suitable for indoor fixed scenarios with stable power supply and higher data rate requirements. WiFi 6 (802.11ax) introduces features such as OFDMA, MU-MIMO, and TWT (Target Wake Time), better supporting dense IoT connections and low-power needs. It complements cellular IoT (NB-IoT, Cat.1): WiFi is suitable for indoor, high-speed, fixed scenarios; cellular is suitable for wide-area, mobile, low-power scenarios.
Technical Features
- High Speed and Bandwidth: WiFi 6 single-stream can reach up to 1.2 Gbps, supporting high-bandwidth services such as 4K video and real-time monitoring
- OFDMA and Multi-User: Divides the channel into RUs (Resource Units), allowing multiple devices to transmit simultaneously, improving efficiency in dense scenarios
- TWT Power Saving: The device negotiates wake-up times with the AP, reducing idle listening and extending battery life
- Widespread Deployment: Extensive coverage in homes, businesses, and public places, low cost, low access threshold
Comparison with LoRa and Bluetooth
Zigbee and Bluetooth are suitable for low-power, short-range, and self-organizing networks; WiFi is suitable for high-speed, direct IP connection, and cloud integration. Smart homes often use a WiFi + Bluetooth/Zigbee hybrid solution: WiFi handles main control and cloud connection, Bluetooth/Zigbee handles sensors and low-power devices.
SimtoLink focuses on cellular IoT as the core, with WiFi IoT as a supplement. For scenarios with WiFi coverage, such as smart homes, offices, and industrial gateways, SimtoLink can provide a WiFi + cellular dual-mode solution: WiFi handles daily data access, and cellular serves as backup or mobile connectivity. The SimtoLink cloud platform supports multi-protocol access, facilitating unified management of WiFi and cellular devices for customers.
Association Success Only Means the Radio Link Is Up
In 802.11, a device that has “joined WiFi” has only finished authentication and association and received an association identifier under some BSSID. An open network, a personal passphrase (WPA2-PSK, or WPA3 Simultaneous Authentication of Equals), and enterprise 802.1X are different kinds of authentication. A correct passphrase protects only the frames on the air. It does not prove that this device is allowed to reach the cloud platform. After association there is still DHCP or a static address, then name resolution and an application session. Keeping association, address, and session apart is what stops “this machine is on the router client list” from being read as “the data has already been stored.”
What WiFi 6 adds on this link is a way of scheduling. OFDMA splits one transmission opportunity into resource units, so an access point can serve several stations that send small packets in the same transmission, and each sensor does not occupy the whole 20 MHz of channel time by itself. Target Wake Time is a wake window the station and the access point agree in advance. Outside that window the station may turn its receiver off. Both features need support on the access point and a negotiation that actually succeeds. If the access point only advertises WiFi 6 capability and the station falls back to legacy power save, average current stays close to continuous listening. A battery budget built on the assumption that negotiation succeeded will be off.
A physical-layer peak is not an application rate either. A single stream can reach about 1.2 gigabits per second of air-interface symbol rate only when 160 MHz, a high-order modulation, and a high signal-to-noise ratio are all present at once. That figure is a physical-layer number under a short guard interval. On the 2.4 GHz, 20 MHz channel that indoor devices commonly use, the preamble, acknowledgements, retransmissions, and contention still have to come off, and the share the application layer can hold steadily is much smaller. A camera cares about sustained throughput. A sensor cares whether a small packet can get out inside a crowded contention window. The two cannot share this peak when capacity is planned.
It Fits When Power Is Stable and the Site Is Yours to Manage
WiFi holds when the device has continuous power, or can accept frequent charging, and the access points on the site are ones you configure. Indoor cameras, industrial screens beside a production line, and gateways that need local discovery or a large firmware image are better served by WiFi than by paying for cellular attach over and over. If the access point runs a captive portal that only presents an authentication page to a browser, a headless module never gets a chance to accept the terms. Association can succeed and still yield no address that can leave the network.
A coin cell, or sparse meter reading that has to cross a factory hall, should not be placed on WiFi just because a router is visible on site. Those nodes fit low-duty-cycle LoRa better. When a home already has a group of nodes that sleep very deeply, the sensible role for a WiFi device is the uplink of a border router: collect a Thread mesh and forward it, rather than sending every sensor to crowd the same SSID. Dual mode is a different boundary. WiFi carries the heavy volume inside the site, and cellular sends an alert only when the access point loses power or the SSID changes. Holding both links up as long connections that report the same full data set only adds another state machine.
The band itself is a condition of use. 2.4 GHz penetrates better, but it overlaps Bluetooth, some USB 3.0 noise, and neighboring networks, so channels that truly do not overlap are few. 5 GHz has more channels and fades faster. It suits high throughput in the same room, not a meter on the far side of a load-bearing wall. 6 GHz exists only when the module, the access point, and the band permitted locally all line up. A module labeled as supporting 6E does not gain that band on its own if the access point is still operating on 5 GHz. Planning should look at the channel and the signal quality the station actually associated on.
Passphrases, Roaming, and Power Save Each Create a False Online State
Hiding the network name is not access control. A device that has already saved the name still announces it while probing, and hiding the name makes it harder for some modules to find the network again after waking from sleep. A passphrase written into a mass-produced image and left unrotated for a long time means every unit that comes back for repair holds the key to the current network. A personal passphrase also cannot be revoked per device. One leaked configuration forces a change on every node. Enterprise authentication can bind a certificate or an account to a single device, but the module must finish 802.1X, and the clock and the certificate chain cannot remain at factory values. WPA3 can stop a weak passphrase from being guessed offline after the handshake is captured. As long as the network still accepts a WPA2 personal passphrase, the practical strength of the whole network stays at that level, and older modules keep using the weaker handshake.
A gateway or a handheld that has been moved can also stick to a distant access point. As long as the beacon can still be heard, the station may never scan for a closer one. The physical-layer rate falls to a very low modulation, one small packet occupies a long stretch of air time, and the other sensors on the same channel slow down together. Assisted roaming requires the station and the access point both to implement the matching signaling. Turning “seamless roaming” on in the controller does not rewrite the thresholds stored in the module firmware. Thresholds set too aggressively make the station associate back and forth between two access points whose signals are close, and the DHCP lease and the upper-layer session start over each time.
Power-save settings create a false online state in the same way. If Target Wake Time never negotiated successfully and the station still sleeps against a window that does not exist, it misses downlink discovery frames and multicast maintenance packets, and the cloud sees the device as intermittently offline. When the access point does not convert multicast into unicast, sleeping stations systematically fail to receive LAN discovery. Turning sleep off entirely for the sake of stability lets a battery-powered sensor run down quickly while the association state stays healthy the whole time. Check association duration, the sleep flag, and average current together. The client list only shows that the radio is still attached.