| Wi-Fi HaLow access point or gateway | Connects HaLow end devices to a local network or application platform; may provide Ethernet or another backhaul connection. | Confirm the regional sub-GHz band, channel options, and channel width match the end devices. Wi-Fi HaLow uses IEEE 802.11ah and does not connect directly to ordinary 2.4 GHz or 5 GHz Wi-Fi clients. | Check backhaul type, supported client capacity, antenna placement, power supply, and whether the gateway can be centrally managed. Sub-GHz coverage can be useful for longer links, but actual range depends on buildings, interference, antennas, and local radio limits. | Verify available authentication and encryption modes, unique credentials, firmware-update support, and whether management access can be restricted. WPA3 availability and options depend on the specific implementation. | Best starting point for a new HaLow network or for connecting several HaLow devices to an existing IP network. |
| Battery-powered sensor node | Periodic readings such as temperature, humidity, occupancy, or equipment status. | Confirm that the node and access point support the same regional band and HaLow configuration. Check application protocol and data format compatibility as well as radio compatibility. | Ask for battery-life assumptions, reporting interval, sleep behavior, and operating-temperature range. Validate coverage at the actual installation location rather than relying on a quoted maximum range. | Check how device identity and network credentials are provisioned, whether credentials can be changed, and how firmware and security updates are delivered over the device’s service life. | Good for low-data-rate monitoring where long battery life and broader-area connectivity matter more than high throughput. |
| Camera or other higher-data-rate endpoint | Video, image capture, or frequent data uploads from locations where conventional Wi-Fi coverage is difficult. | Confirm supported channel width and sustained throughput, not just the advertised peak rate. The end device, access point, and application must all support the required settings and data path. | Test the live stream or upload at the intended distance and through the actual walls and obstacles. Check power requirements, antenna installation, and whether the network can handle simultaneous traffic from all endpoints. | Require authenticated network access and protected application traffic. Check update policy, account controls, and whether remote access can be disabled or limited when not needed. | Consider only when measured link capacity meets the application’s real bitrate and latency needs; a longer-range radio link does not guarantee video-grade throughput. |
| Wi-Fi HaLow module or development kit | Adding HaLow connectivity to a custom product or testing a prototype before production. | Check host interface, driver and software support, antenna requirements, supported regulatory domain, and whether the module’s radio configuration works with the intended access point. | Confirm integration documentation, power consumption in transmit and sleep states, thermal limits, and antenna placement requirements. Production designs may require additional regional compliance testing. | Review secure boot or signed-update capabilities where available, key-storage options, vulnerability-update process, and the supplier’s support period before designing around the module. | Best for engineering teams that need design flexibility and can manage integration, testing, and ongoing software maintenance. |
| HaLow-to-Ethernet or network bridge | Connects a remote wired device or local network segment to a HaLow link. | Check whether the bridge operates transparently or routes traffic, and confirm support for the required addressing, discovery, and application protocols. | Verify Ethernet speed, power method, enclosure rating, mounting options, and the number of devices supported behind the bridge. Test end-to-end latency and link stability at the site. | Secure both the HaLow radio link and the bridge’s administrative interface. Change default credentials, restrict management access, and check for firmware updates. | Useful when existing wired equipment must communicate across a site without replacing the equipment itself. |
| Industrial or building-control endpoint | Metering, alarms, control signals, and equipment monitoring in commercial or industrial settings. | Confirm that the required control protocol is supported end to end; HaLow provides wireless connectivity, but does not by itself guarantee compatibility with a particular automation system. | Check environmental ratings, interference conditions, installation rules, redundancy needs, and whether the application can tolerate wireless delays or temporary outages. Validate the system under representative site conditions. | Check network segmentation, least-privilege access, credential rotation, event logging, and the process for patching devices that remain installed for many years. | Suitable when the application’s reliability and response-time requirements have been tested against the proposed wireless design. |
| Asset-tracking or location-reporting tag | Periodic status or location-related reports for mobile equipment and assets. | Confirm that the tag’s reporting method and application platform are compatible with the HaLow gateway. HaLow connectivity alone does not provide location measurement; location features require suitable positioning methods or infrastructure. | Evaluate expected coverage along the full route, reporting frequency, battery replacement plan, mounting, and performance in motion or around metal structures. | Check device authentication, protection of transmitted identifiers and data, update support, and controls for disabling a lost or retired tag. | Useful for site-based reporting where gateway coverage is available and the required location method is separately provided. |