Enhancements to Wireless Health in Zyxel APs (Firmware 7.10)

Zyxel_Claudia

Zyxel’s Wireless Health feature is getting a major boost in firmware 7.10, introducing better interference detection, enhanced self-optimization, and improved logging accuracy. These improvements aim to increase network stability and automate performance optimizations more effectively.

1. Monitoring Non-WiFi Interference for Better Optimization

APs will now actively monitor non-WiFi interference sources, including:

• Noise floor levels (background signal interference)
• Non-WiFi utilization percentage (how much interference comes from external sources like Bluetooth, microwaves, or other RF devices)

How does it Work

If an AP detects noise floor and high non-WiFi interference every one minute, it may need to switch to a better channel using DCS Now.

• Execute “DCS Now” when:
  1. Three consecutive scans detect high non-WiFi interference.
  2. Five poor results in the last 10 scans indicate persistent interference.

DCS Lock Time (30-Minute Cooldown Period)

To prevent constant channel changes, the AP will not trigger DCS Now again for 30 minutes after an adjustment.

2. Adaptive Channel Width Optimization for 5GHz & 6GHz

Previously, adaptive channel width optimization (which dynamically adjusts channel width for stability) was not available for 160MHz and 240MHz channels in the 5GHz band.

Adaptive channel width optimization now works on 160MHz & 240MHz channels in firmware 7.10.

• If interference is detected, the AP will automatically adjust the channel width to 20MHz for better stability.
• Kick-off stations with too many retransmission

3. More Accurate Event Logs for Manual Channel Configurations

Before firmware 7.10, if an AP was set to a manual channel list, the event log would incorrectly show that DCS Now was triggered, even though no action was actually taken.

Fix in Firmware 7.10:

• If an AP is using manually selected channels, the event log will now correctly display:"No action due to manual channel."

This does not change the actual behavior - it just ensures the event log accurately reflects what happens.