Hi everyone,
recently I've discovered the Auto Upgrade feature.
I followed the step by step guide using ROS 7.
I configured everything as written in the guide but but when I click on Refresh it doesn't work.
The packages that can be downloaded or updated do not appear.
Has anyone tried this works in ROS 7?
Do you know if it works only with ROS 6 or also with ROS 7?

Thanks

You mean the "Auto Upgrade" item found in the "System" menu?
That is an ancient system, it isn't even properly documented, that likely was invented long ago and seems mostly abandoned.
I would not recommend to use it. In fact I am surprised that it has not yet been removed.

Thanks for the reply.
Yes, I mean exactly the "Auto-Upgrade" item found in the "System" menu.
I'm surprised too since it's all perfectly documented here in the official Mikrotik support page.
Is there an alternative to mass update ROS 7?

If you are the administrator of the network, you really want to use Dude:

https://mikrotik.com/thedude
https://wiki.mikrotik.com/wiki/Manual:The_Dude4

I'm surprised too since it's all perfectly documented here in the official Mikrotik support page.

That does not document this specific menu at all! There are several things described there, but they are different methods.

Is there an alternative to mass update ROS 7?

First you need to determine if you even want to do that.
Also, it depends a lot on your network. How many routers do you have, do you manually manage these or use some management system (including dude, but do not consider deploying that just for this purpose!).
Also, how do you manage updates (within v6) at the moment.

I'm already using The Dude.
Until version 6 I updated all Mikrotik devices through The Dude.
Now I have had to update many devices to ROS 7 and The Dude won't let me update devices that use ROS 7.
At the moment I update about 180 Mikrotik Routers using The Dude.

Yeah, the Dude is basically dead. When developments in RouterOS are not handled by the Dude, they do not fix it. Also, they make arbitrary changes to RouterOS (that could easily have been avoided) that result in failures in the Dude, and are not fixed.
That is a reason why I wrote "do not consider deploying that just for this purpose!". It is basically a dead end.

Now of course that does not really fix your problem. It has always amazed me that RouterOS does not include a "default" method of auto-updating, especially now that they focus more and more on the home user market.
One would expect the devices to auto-update to a "well-working" version, especially in case security issues are found.
Admins that "know better" could always change that. But now, one has to write and manually install scripts to auto-update...

Write a script:
create a scheduler to run the script

The auto upgrade will only automatically update the firmware on the next reboot.
So after reboot you may need another script that run on boot that will check if a firmware update is ready and force another reboot:

The auto upgrade will only automatically update the firmware on the next reboot.

Yes, but notice that this "next reboot" must be a software-requested reboot. It will NOT be installed merely because the user turns the device off and on, or similar.
So, you probably need to include that in the script.