Closed Mile-Lile closed 1 month ago
and these are errors from my logs, look at 19:19:44
The problem abstractly is that on/off is not a process, but a result. And if the time for this result has already passed, it won't be triggered. The actual problem with processing is not in this repo, but in the wifischedule app.
You might try to set the stop time to 23:59 to see whether this is an edge case problem.
It's also possible that your router has no good concept of what time it actually is after a reboot - set also NTP.
@systemcrash @openwrt@newk.it thx Paul... I reported here because link here points to github luci, although it makes no sense that problem is in GUI... it is just simpe script that changes cron... how can I find the author of the script?
I have ntp enabled... so probably script should wait execution after time sync....
because link here points to github luci, although it makes no sense that problem is in GUI
Well, you should look into the actual underlying functional package "wifischedule" instead of the GUI for it.
@newkit seems to be the original author of the package, and @rindeal seems to have modified the startup functionality latest... https://github.com/openwrt/packages/commits/3724047164218a58948933bf61eb089d36b67074/net/wifischedule
@hnyman Hannu thx, will try to reach them..
Steps to reproduce:
Example: Replace the following lines and remove this
Actual behavior:
Router starts with wifi off even if it is BUSINESSHOURS when wifi should be on
Expected behavior:
Wifi should be on (regardless of rebooting), and should be off at the midhinght, script should check clock somehow
Additional Information:
OpenWrt version information from system
/etc/openwrt_release