Wi-Fi bands scheduling kills guest network

[WunderWungiel]

Hello
I have an AXE16000 router running Asuswrt-Merlin firmware, 3006.102.4. I have Wi-Fi scheduling set for all bands (Wireless -> Professional), so they're turned off overnight - from 00:00 to 06:00. 2,4 GHz + 5 GHz-1 + 5 GHz-2 are using Smart Connect and 6 GHz is using seperate SSID.
I'm also using a custom Guest Network for IoT devices.
The problem is, apparently general Wi-Fi scheduling kills guest network, and makes it inactive all day. None of devices can see it, it has 0 clients, even though router reports it as running.

What I have tried:
- adding a custom schedule for Guest Network: from 06:00 to 00:00 (I understand that in Guest Network scheduling controls the Enabled time, and in Wireless it controls Disabled time?)
- changing the schedule to 06:05 to 23:55 (to give it time)
Nothing works, it's still not working when I wake up

If I reboot router or manually disable + enable Guest Network, it starts working.
Any idea?
Thanks in advance

 

[GaselK]

Please post here https://www.snbforums.com/threads/asuswrt-merlin-3006-102-4-is-now-available.94651/
I have the same problem.

 

[bbunge]

This seems to be a known issue. If you really need the Guest network WIFI scheduling go back to Asus firmware.

 

[WunderWungiel]

Same on original ASUS firmware (latest 3.0.0.6.102_36387).

 

[bennor]

Same on original ASUS firmware (latest 3.0.0.6.102_36387).

Several of the BE series of routers have had recent 3006.102.x firmware released that addressed WiFi scheduler and Improved Parental Control scheduling with support for SDN clients. Hopefully those fixes will flow down to the AX series of router 3006.102.x firmware.

BE routers with WiFI scheduler fixes:
ASUS ZenWiFi BQ16 Pro Firmware version 3.0.0.6.102_36934 (2025/05/26)
ASUS RT-BE86U Firmware version 3.0.0.6.102_37841 (2025/04/30)
ASUS RT-BE88U Firmware version 3.0.0.6.102_38151 (2025/04/23)
ASUS RT-BE96U Firmware version 3.0.0.6.102_37839 (2025/05/05)
ASUS GT-BE98 Pro Firmware version 3.0.0.6.102_37839 5-8-2025 release

 

[WunderWungiel]

I managed to find a workaround!
I discovered that restarting Wi-Fi (service restart_wireless) brings guest network back.
So, I set up a cron job for doing this five minutes after Wi-Fi is turned back on.
My example below, with Wi-Fi scheduling ending at 06:00.

/jffs/scripts/services-start:

#!/bin/sh

cru a morning "5 6 * * * service restart_wireless"

Make sure to make it executable:

chmod a+rx /jffs/scripts/services-start

And it works fine. Guest network gets revived.