wifischedule not working on 24.10.1

I am experiencing an issue with wifischedule. While it worked fine on OpenWRT 23.05.5 it does not after upgrading to 24.10. It seems to fail to restart wifi.
Enabling wifi manually via the "Wireless" LUCI interface works fine though. trying to trigger the wifischedule scripts manually using:

/usr/bin/wifi_schedule.sh start
/usr/bin/wifi_schedule.sh stop # forcestop

leads to a hang o the script (there is no output generate. The only output is:
Sun Apr 20 18:13:06 2025 user.info wifi_schedule: /usr/bin/wifi_schedule.sh getmodules

If the wifi is up and running after a manual restart using "Wireless" LUCI interface, disabling wifischedule leads to the following log messages in syslog (3 SSIDs exist (iot_wifi, home_wifi, guest_wifi)):

Sun Apr 20 18:11:10 2025 user.info wifi_schedule: /usr/bin/wifi_schedule.sh forcestop manual
Sun Apr 20 18:11:10 2025 cron.err crond[7065]: crond (busybox 1.36.1) started, log level 5
Sun Apr 20 18:11:10 2025 user.info wifi_schedule: unload_modules mwlwifi mac80211 cfg80211 compat (retries: 10)
Sun Apr 20 18:11:10 2025 daemon.notice hostapd: Set new config for phy phy0:
Sun Apr 20 18:11:10 2025 daemon.notice hostapd: Remove interface 'phy0'
Sun Apr 20 18:11:10 2025 daemon.notice hostapd: phy0-ap0: interface state ENABLED->DISABLED
Sun Apr 20 18:11:10 2025 daemon.debug hostapd: phy0-ap0: STA <mac> MLME: MLME-DEAUTHENTICATE.indication(<mac>, 1)
Sun Apr 20 18:11:10 2025 daemon.notice hostapd: phy0-ap0: AP-STA-DISCONNECTED 7a:89:3a:ba:b3:66
Sun Apr 20 18:11:10 2025 daemon.notice hostapd: phy0-ap0: AP-DISABLED
Sun Apr 20 18:11:10 2025 daemon.notice hostapd: phy0-ap0: CTRL-EVENT-TERMINATING
Sun Apr 20 18:11:10 2025 daemon.err hostapd: rmdir[ctrl_interface=/var/run/hostapd]: Permission denied
Sun Apr 20 18:11:10 2025 kern.warn kernel: [  197.326648] ieee80211 phy1: previous command is running or module removed
Sun Apr 20 18:11:10 2025 kern.warn kernel: [  197.333559] ieee80211 phy1: previous command is running or module removed
Sun Apr 20 18:11:10 2025 daemon.notice hostapd: nl80211: deinit ifname=phy0-ap0 disabled_11b_rates=0
Sun Apr 20 18:11:10 2025 kern.warn kernel: [  197.340598] ieee80211 phy1: previous command is running or module removed
Sun Apr 20 18:11:10 2025 kern.warn kernel: [  197.396175] ieee80211 phy1: previous command is running or module removed
Sun Apr 20 18:11:10 2025 kern.warn kernel: [  197.403260] ieee80211 phy1: previous command is running or module removed
Sun Apr 20 18:11:10 2025 kern.info kernel: [  197.410222] br-iot_wifi: port 1(phy1-ap1) entered disabled state
Sun Apr 20 18:11:10 2025 kern.warn kernel: [  197.416974] ieee80211 phy1: previous command is running or module removed
Sun Apr 20 18:11:10 2025 kern.warn kernel: [  197.423874] ieee80211 phy1: previous command is running or module removed
Sun Apr 20 18:11:10 2025 kern.warn kernel: [  197.430841] ieee80211 phy1: previous command is running or module removed
Sun Apr 20 18:11:10 2025 kern.debug kernel: [  197.437721] ieee80211 phy1: change: 0x40
Sun Apr 20 18:11:10 2025 kern.warn kernel: [  197.437730] ieee80211 phy1: previous command is running or module removed
Sun Apr 20 18:11:10 2025 kern.warn kernel: [  197.444555] ieee80211 phy1: previous command is running or module removed
Sun Apr 20 18:11:10 2025 kern.warn kernel: [  197.451388] ieee80211 phy1: previous command is running or module removed
Sun Apr 20 18:11:10 2025 kern.warn kernel: [  197.458228] ieee80211 phy1: previous command is running or module removed
Sun Apr 20 18:11:10 2025 kern.warn kernel: [  197.465054] ieee80211 phy1: previous command is running or module removed
Sun Apr 20 18:11:10 2025 kern.debug kernel: [  197.471885] ieee80211 phy1: change: 0x100
Sun Apr 20 18:11:10 2025 kern.warn kernel: [  197.471891] ieee80211 phy1: previous command is running or module removed
Sun Apr 20 18:11:11 2025 kern.warn kernel: [  197.516280] ieee80211 phy1: previous command is running or module removed
Sun Apr 20 18:11:11 2025 kern.warn kernel: [  197.523364] ieee80211 phy1: previous command is running or module removed
Sun Apr 20 18:11:11 2025 kern.info kernel: [  197.530408] br-guest_wifi: port 1(phy1-ap0) entered disabled state
Sun Apr 20 18:11:11 2025 kern.info kernel: [  197.547015] mwlwifi 0000:02:00.0 phy1-ap0 (unregistering): left allmulticast mode
Sun Apr 20 18:11:11 2025 kern.info kernel: [  197.554549] mwlwifi 0000:02:00.0 phy1-ap0 (unregistering): left promiscuous mode
Sun Apr 20 18:11:11 2025 kern.info kernel: [  197.562015] br-guest_wifi: port 1(phy1-ap0) entered disabled state
Sun Apr 20 18:11:11 2025 kern.info kernel: [  197.597622] mwlwifi 0000:02:00.0 phy1-ap1 (unregistering): left allmulticast mode
Sun Apr 20 18:11:11 2025 kern.info kernel: [  197.605167] mwlwifi 0000:02:00.0 phy1-ap1 (unregistering): left promiscuous mode
Sun Apr 20 18:11:11 2025 kern.info kernel: [  197.612643] br-iot_wifi: port 1(phy1-ap1) entered disabled state
Sun Apr 20 18:11:11 2025 kern.info kernel: [  197.647940] mwlwifi 0000:01:00.0 phy0-ap0: left allmulticast mode
Sun Apr 20 18:11:11 2025 kern.info kernel: [  197.654097] mwlwifi 0000:01:00.0 phy0-ap0: left promiscuous mode
Sun Apr 20 18:11:11 2025 kern.info kernel: [  197.660224] br-home_wifi: port 1(phy0-ap0) entered disabled state
Sun Apr 20 18:11:11 2025 kern.debug kernel: [  197.738705] ieee80211 phy1: unmapped+free'd 252 0x225d9416 0x2ab6080 4096
<...left out some lines to save space...>
Sun Apr 20 18:11:11 2025 kern.debug kernel: [  197.738712] ieee80211 phy1: unmapped+free'd 253 0xd936985c 0x3e3a080 4096
Sun Apr 20 18:11:11 2025 kern.debug kernel: [  197.738718] ieee80211 phy1: unmapped+free'd 254 0x27763ad5 0x3e38080 4096
Sun Apr 20 18:11:11 2025 kern.debug kernel: [  197.738725] ieee80211 phy1: unmapped+free'd 255 0xbe36efd8 0x3e3c080 4096
Sun Apr 20 18:11:11 2025 kern.info kernel: [  197.738811] ieee80211 phy1: cleaned 0 TX descr
Sun Apr 20 18:11:11 2025 kern.debug kernel: [  197.813576] ieee80211 phy0: change: 0x40
Sun Apr 20 18:11:11 2025 kern.debug kernel: [  197.879646] ieee80211 phy0: change: 0x100
Sun Apr 20 18:11:11 2025 daemon.notice netifd: Network device 'phy1-ap1' link is down
Sun Apr 20 18:11:11 2025 daemon.debug hostapd: phy1-ap0: STA <mac> MLME: MLME-DEAUTHENTICATE.indication(<mac>, 1)
Sun Apr 20 18:11:11 2025 daemon.debug hostapd: phy1-ap0: STA <mac> MLME: MLME-DELETEKEYS.request(<mac>)
Sun Apr 20 18:11:11 2025 daemon.notice hostapd: phy1-ap0: AP-STA-DISCONNECTED 5c:49:7d:a0:99:8b
Sun Apr 20 18:11:11 2025 daemon.notice hostapd: phy1-ap0: INTERFACE-DISABLED
Sun Apr 20 18:11:11 2025 daemon.notice hostapd: Set new config for phy phy1:
Sun Apr 20 18:11:11 2025 daemon.notice hostapd: Remove interface 'phy1'
Sun Apr 20 18:11:11 2025 daemon.notice hostapd: phy1-ap0: interface state ENABLED->DISABLED
Sun Apr 20 18:11:11 2025 daemon.notice hostapd: phy1-ap1: AP-STA-DISCONNECTED 64:90:c1:01:98:8a
Sun Apr 20 18:11:11 2025 daemon.err hostapd: Failed to set beacon parameters
Sun Apr 20 18:11:11 2025 daemon.err hostapd: Failed to set beacon parameters
Sun Apr 20 18:11:11 2025 daemon.notice hostapd: phy1-ap1: AP-DISABLED
Sun Apr 20 18:11:11 2025 daemon.notice hostapd: phy1-ap1: CTRL-EVENT-TERMINATING
Sun Apr 20 18:11:11 2025 daemon.err hostapd: rmdir[ctrl_interface=/var/run/hostapd]: Permission denied
Sun Apr 20 18:11:11 2025 daemon.notice hostapd: phy1-ap0: AP-DISABLED
Sun Apr 20 18:11:11 2025 daemon.notice hostapd: phy1-ap0: CTRL-EVENT-TERMINATING
Sun Apr 20 18:11:11 2025 daemon.err hostapd: rmdir[ctrl_interface=/var/run/hostapd]: Permission denied
Sun Apr 20 18:11:11 2025 daemon.notice hostapd: nl80211: deinit ifname=phy1-ap0 disabled_11b_rates=0
Sun Apr 20 18:11:11 2025 daemon.notice netifd: bridge 'br-guest_wifi' link is down
Sun Apr 20 18:11:11 2025 daemon.notice netifd: Interface 'guest_wifi' has link connectivity loss
Sun Apr 20 18:11:11 2025 daemon.notice netifd: bridge 'br-iot_wifi' link is down
Sun Apr 20 18:11:11 2025 daemon.notice netifd: Interface 'iot_wifi' has link connectivity loss
Sun Apr 20 18:11:11 2025 daemon.notice netifd: bridge 'br-home_wifi' link is down
Sun Apr 20 18:11:11 2025 daemon.notice netifd: Interface 'home_wifi' has link connectivity loss
Sun Apr 20 18:11:11 2025 daemon.notice hostapd: nl80211: Failed to remove interface phy1-ap0 from bridge br-guest_wifi: No such device
Sun Apr 20 18:11:12 2025 daemon.err hostapd: Could not read interface phy1-ap0 flags: No such device
Sun Apr 20 18:11:12 2025 daemon.notice wpa_supplicant[1852]: Set new config for phy phy0
Sun Apr 20 18:11:12 2025 daemon.notice wpa_supplicant[1852]: Set new config for phy phy1
Sun Apr 20 18:11:12 2025 daemon.notice wpa_supplicant[1852]: Could not open phy phy1
Sun Apr 20 18:11:12 2025 daemon.notice netifd: Wireless device 'radio0' is now down
Sun Apr 20 18:11:12 2025 daemon.notice netifd: radio1 (7102): Reference error: left-hand side expression is null
Sun Apr 20 18:11:12 2025 daemon.notice netifd: radio1 (7102): In /usr/share/hostap/wdev.uc, line 177, byte 14:
Sun Apr 20 18:11:12 2025 daemon.notice netifd: radio1 (7102):
Sun Apr 20 18:11:12 2025 daemon.notice netifd: radio1 (7102):  `phy = phydev.phy;`
Sun Apr 20 18:11:12 2025 daemon.notice netifd: radio1 (7102):   Near here ---^
Sun Apr 20 18:11:12 2025 daemon.notice netifd: radio1 (7102):
Sun Apr 20 18:11:12 2025 daemon.notice netifd: radio1 (7102):
Sun Apr 20 18:11:12 2025 daemon.notice netifd: Wireless device 'radio1' is now down

Restarting Wifi using the buttons in the "Wifischedule" LUCI interface does not seem to have any effect due to a hang on "getmodules":
Sun Apr 20 18:13:06 2025 user.info wifi_schedule: /usr/bin/wifi_schedule.sh getmodules

What could be the issue here?

Start with /usr/bin/wifi_schedule.sh and its getmodules path, reproducing the hang with the start and stop commands from the report. Compare the script's behavior with the OpenWrt 24.10.1 logs, including the /usr/share/hostap/wdev.uc reference error. Done means wifischedule can restart Wi-Fi and the getmodules operation no longer hangs.