Services → Input/Output → Status
switching the relais 5,10 manually works fine.
Then in the scheduler i configure an instance like this:
Relay (5,10) / Weekdays / Every Friday, 13:50 / Every Friday, 14:00
switched on the enable switch for the instance and also the higher-level switch above.
But at 13:50 nothing happens on the relais 5,10.
As additional info: i did a firmware update this week from 7.6.10 to 7.14.2, an then deleted all the scheduler instances after that.
With the old firmware first i had do switch off all scheduler instances to switch the relais manually, otherwise the scheduler overwrites the relais(?)
But now with the newer firmware nothing seems to happen with the scheduler.
Can i check the scheduler otherwise? Or debug something in the logfiles?
Could you please confirm whether the Scheduler service is visible under the Services → Input/Output drop-down section on your device? This feature might not be pre-installed by default after an update to 7.14.2 and should be added manually via System → Package Manager if missing.
Additionally, when configuring the I/O Scheduler, please make sure that the correct time zone is set under System → Administration → Date & Time settings.
P.S. I’ve tested the I/O Scheduler function on a RUT956 (with 7.14.2) on my end, and it’s performing as expected.
I have now removed and reinstalled the scheduler package.
Checked the timezone (europe/Zurich), and configured just one scheduler instance a few minutes in the future.
Then i watched the relais status in Services → Input/Output → Status,
but when the time is reached, nothing happens.
Evertime i change to Services → Input/Output → Scheduler
there is a notification (upper right corner): “Scheduler instances will be active only when scheduler is enabled”
but i have both enable-switches ON.
Is this normal?
Some scheduler instances were already configured before the FW update, maybe its a problem with the update?
Thank you for the update. To help determine whether the issue is related to the firmware update or a configuration conflict, could you try the following:
Create a backup file via System → Maintenance → Backup, so you can safely restore your current configuration later if needed.
Perform a factory reset of your router.
After the reset, manually reconfigure the I/O Scheduler instance to trigger a relay in the next few minutes or as suitable.
Check if it operates correctly.
If the issue persists after these steps, please provide:
A screenshot of the Scheduler settings page.
The system log immediately after the moment when the scheduled relay should have triggered. You can find this in System → Maintenance → Troubleshoot, under the System log (Show) section.
If i do a factory reset will the APN configuration also be lost?
Since i don’t have the router on site (it is remote in the field) can i still reach it after a factory reset?
Yes, if the device is only reachable remotely, after a factory reset you’ll lose access to it. Maybe the device is also connected to RMS? Then, a system defaults reset could be performed without losing access to the device afterwards.
short story:
“System settings”-Reset and do a complete new configuration (manually)
Longer story:
No settings found to get the scheduler running, importing a configuration backup always ends with the scheduler not working.
So registered/connected the router to RMS and executed a “System settings” Reset, so i can reconfigure the router in RMS.
Then does a minimal configuration (mobile) of the router and tested the scheduler → works correct.
But now the router’s WebGUI was no longer accessible on the internet.
I had to change the setting Firewall->Zones->wan->Input, from Reject to Accept
The WebGUI is now accessible again and the scheduler also seems to work correctly.
I think there must be some problem with the old existing configuration and the new firmware?
Thank you very much for the update and for sharing your solution. Great to hear you managed to get everything working again.
Likely this was the case, as it does sound like there was a configuration conflict between the older and newer firmware versions.
Also, just to mention for future cases:
When performing a system defaults reset (having the device connected on RMS), you can immediately change the device’s admin password through RMS as soon as it comes back online. This way, you’ll regain WebUI and SSH access straight away.
I have changed the default password, but the WebUI is only accessible, with the setting Firewall->Zones->wan->Input Accept
(i think that was not the factory default value)
Or is there something else not optimal in the configuration?
