Wireless and low power links
Check radio performance, power use, device authentication and key management together. Include battery loss, interference and reconnection in the recovery plan.
Sources and scopeSource record 25 August 2026
Technical source record: 25 August 2026. Check the linked documentation for current product requirements.
Inherited check dated 13 September 2026. Supporting evidence for this inherited check has not been independently confirmed.
Recorded scope: Bluetooth Core 6.3 release status and the Zigbee 4.0 and Suzi certification announcement were checked. Other radio families, regional approvals and individual product capabilities retain their earlier source dates.
Family level baseline; exact regional radio rules, profiles, commissioning method, security revision, certification, and product capabilities must be verified per deployment.
On this page
Overview#
Radio reach is variable and crosses walls, fences, vehicles, and tenancy boundaries. Signal strength is neither identity nor authorisation. Design for eavesdropping, rogue transmitters, interference, replay/jamming symptoms, battery exhaustion, gateway compromise, and loss of the cloud or border router.
Family map#
| Family | Integration model | Security/configuration questions |
|---|---|---|
| WiFi | 802.11 LAN carrying IP protocols | personal versus enterprise authentication, 802.1X method, protected management, client isolation, roaming, VLAN policy |
| Bluetooth LE | GAP discovery/connection, GATT services/characteristics, optional mesh/profile layers | exact Core/profile version, association method, bonding, MITM protection, privacy addresses, key storage, authorisation per characteristic |
| Zigbee | coordinator/trust centre, router/end device mesh, clusters and profiles | install/link/network keys, joining policy, key update, device/cluster revision, group and binding scope |
| Thread | IPv6 mesh with border router; application layer is separate | network credentials, commissioning owner, border router redundancy, partitioning, backbone exposure, application security |
| Z Wave | controller managed sub GHz mesh and command classes | S2 class/DSK, inclusion/exclusion authority, command class security, controller backup/replacement |
| LoRaWAN | end device, gateways, network/application servers | OTAA/ABP, root/session keys, frame counters, join/rejoin, regional parameters, confirmed message limits |
| NFC | very short range reader/writer, card emulation, peer modes | tag/credential authenticity, relay risk, secure element/application protocol, anti cloning and transaction freshness |
IEEE lists 802.11-2024 as the current base wireless LAN standard.1 Bluetooth SIG adopted Core 6.3 in May 2026, but deployed products may qualify against earlier supported editions; profile and security feature support matter more than the marketing version alone.2 Thread Group publishes Thread 1.4.1 resources.3 CSA's download page is the authoritative place to check current Zigbee and Matter specifications.4
Zigbee 4.0 and Suzi#
CSA opened product certification for Suzi on 2 September 2026. Suzi extends Zigbee into sub GHz bands and complements existing 2.4 GHz operation. The programme follows Zigbee 4.0 and supports bridges with both radio types. Check regional frequency rules, hardware, certification and the actual bridge functions before choosing equipment. An existing Zigbee label does not establish Suzi support.5
Commissioning and keys#
- Make join/inclusion windows short, local, operator authorised, and auditable. A button press isn't sufficient audit identity.
- Use unique install codes/DSKs/device credentials; never publish QR/setup codes or copy fleet keys into logs and tickets.
- Authenticate the network/controller/border router to the joining device where the protocol permits; otherwise rogue infrastructure may capture credentials.
- Record fabric/network ID, device immutable identity, radio address history, assigned role, profile/schema revision, security level, key epoch, commissioner, and evidence.
- Test removal, loss, controller replacement, key rotation, replay/counter persistence after reset, factory reset, and decommissioning on a bench.
Z Wave Alliance states S2 has been mandatory for new certifications since 2017, but actual inclusion security still needs evidence from the controller/device transaction and certification record.6 LoRa Alliance publishes the LoRaWAN 1.0.4 package; select the exact regional parameters and backend interfaces separately.7
Availability and semantics#
Budget airtime, duty cycle, channel occupancy, retry, mesh depth, sleeping intervals, battery, gateway queueing, and backhaul outage. Avoid turning every loss into an immediate alarm storm. Conversely, don't show a cached battery device value as live without an age/quality indicator.
WiFi/Bluetooth/802.15.4 coexistence in 2.4 GHz, metal enclosures, moving vehicles, weather, antenna placement, and deliberate interference can change performance after commissioning. Use site approved spectrum/RF assessment and country specific regulatory settings; never raise power or change channel plans outside local rules.
Wireless must not be the sole path for life safety or safe egress unless the complete certified system explicitly supports it. Validate pairing/join policy, interference, range boundaries, coexistence, loss, recovery, and regional radio compliance in an authorised environment.