Access Point Firmware Releases

This section provides a release history of firmware for access points managed by WatchGuard Cloud (AP130, AP230W, AP330, AP332CR, AP430CR, AP432).

Latest Release

v3.1.18-0.B730236 (Beta for AP130/AP330 only) — Release Date: 2 February 2026

This firmware release is for AP130 and AP330 devices only, and contains stability and performance improvements, new features, enhancements, and resolved issues.

To learn more or to report an issue, go to the Wi-Fi in WatchGuard Cloud Beta test community.

New Features

Platform Update for Improved Performance and Stability

This firmware release includes an important update to the internal platform to improve overall wireless performance, connectivity, and stability of AP130 and AP330 devices.

DCS Enhancements and Interference Mitigation (Beta)

The Dynamic Channel Selection (DCS) algorithm is updated to improve the evaluation and selection of channels and prevent co-channel and adjacent channel interference. During a regular scan, DCS evaluates channels by the number of BSSIDs that use a channel and the current amount of channel utilization to determine the best channel to use.

You can also enable a new DCS Interference Mitigation feature that enables the 5 GHz radio to manage the current real-time channel congestion and interference by switching to a less congested channel if the current channel utilization is greater than the configured utilization threshold (default 60%). Interference Mitigation is not supported on the 2.4 GHz radio.

These beta features are currently only supported on AP130 and AP330 devices with beta firmware v3.1.

Client Balancing (Beta)

You can now enable a new Client Balancing feature in the radio settings of an Access Point Site. Client Balancing utilizes the BSS transition management (BTM) feature of the 802.11v protocol and information about the current state of the network to steer wireless clients to the most optimal access point. This network optimization helps evenly distribute client connections across multiple access points in dense Wi-Fi deployments. Wireless clients are steered to less-congested access points, even if the signal strength is not as strong as a nearby access point that already has a high number of connected clients.

You can only enable Client Balancing in the 2.4 GHz and 5 GHz radio settings of an Access Point Site configuration. This ensures that all access points are enabled with this feature to share data and optimize client balancing.

This beta feature is currently only supported on AP130 and AP330 devices with beta firmware v3.1.

Scheduled Reboots (Beta)

You can now schedule a one-time or recurring access point reboot. Regular reboots help refresh access point resources and optimize channel selection. The access point will reboot at the scheduled date and time based on the time zone set in the device configuration.

You can schedule a one-time reboot from the Device Settings or Device Summary page of an access point. Recurring reboots must be configured in the device configuration or an Access Point Site. In an Access Point Site configuration, you can also select the Stagger Reboots option so that access points subscribed to the site do not reboot at the same time and reboot in 5-minute intervals to prevent network disruption.

  • AP130 and AP330 access points on beta firmware version 3.1 support the ability to schedule both one-time reboots and recurring reboots.
  • All access point models currently on firmware version 2.7 and lower currently only support a scheduled one-time reboot.

Enhancements

  • The access point’s ability to capture fault report and crash details after an irregular system event is improved. [AP-1534, AP-2747]
  • The access point diagnostic snapshot file now includes the device startup event logs to improve data capture after irregular device reboots. [AP-2318]
  • The access point diagnostic snapshot file now includes improved process memory usage information. [AP-2735]
  • A new "collectmem" CLI command is available that collects memory process information and usage for a specified number of days. This information is logged and added to the diagnostic snapshot file of the access point for troubleshooting.

Resolved Issues

  • Access points no longer randomly reboot when Fast Handover is enabled. [AP-859. AP-2721]
  • Access points no longer crash when the number of client connection attempts exceeds the configured client limit on the device. [AP-2544, AP2577]
  • SSID broadcast schedule issues that caused frequent client dissociation no longer occur when Wi-Fi scheduling is enabled. [AP-2470]
  • RADIUS accounting packets from the access point now correctly include the client’s Framed-IP-Address in the first packet. This prevented wireless clients from passing traffic on applied RADIUS policies until the next accounting interval. [AP-1452]
  • You can now correctly download a diagnostic snapshot file after a packet capture (pcap) file download fails. [AP-2561]
  • Repeated configuration deployments no longer cause the access point to stop Airspace Monitoring scanning on the wired network. [AP-2555]
  • The Security column for wireless client connection details now correctly shows “WPA2 Personal” when Protected Management Frames (802.11w) is enabled instead of “Open”. [AP-2588]
  • The access point no longer sends traffic to www.google.com, 8.8.8.8, and ipinfo.io at boot time. [AP-2599]
  • An access point no longer starts the IPsec process after a device reboot when an access point VPN is disabled. [AP-2634]
  • Wireless clients can now connect to PPSK SSIDs when single or double quote characters (‘, “) are used in the passphrase. [AP-2772]
  • The previous behavior of the device automatically rebooting after 30 minutes of LAN interface inactivity to recover the connection is removed. [AP-2819]
  • Wireless clients were unable to connect to SSIDs with Enterprise authentication when an Access Point VPN is enabled [AP-2788, AP-2829]

Previous Releases