Hi  @HBEN1603 

Thanks for posting here.

How many sites do you have in total?

Did you check the reboot schedule settings at the correct site, as the devices are?

Please choose the site view, and go to Settings > Services > Reboot Schedule and check again.

If there is no related config anywhere, please click Force Provision for all the devices and see if the issue persists. (Config >Manage Device > Force Provision)

Hi @Vincent-TP,

Thank you for responding. I will certainly try and do a force provision and see if that helps.

Kind regards,

Ben

Hi @Vincent-TP,

I just to wanted to let you know that the devices are still rebooting to do an "update" even when there's isn't one. So I went ahead and force provision the affected devices, all which adopted again successfully but has given them a new IP address and not the one I usually reserve them with, but I am just going to leave them for now as I think it'll correct itself after a while now they've force provisioned.

I'll give you another update next Sunday to see if your solution has worked and mark as resolved if successful.

Many thanks,

Ben

Hi  @HBEN1603 

Thanks for letting us know. Please take your time to test.

Unfortunately, it has done it again!

I have tried all sorts after analysing the fact that it has to come down to the controller being the issue here. Not the devices themselves, just the controller.

As I have said earlier on in this post is that I did have an update schedule in place last year, but this schedule has since been removed and it still keeps "updating" the devices when there's isn't an firmware update available, despite provisioning them.

One thing I'd like to see is whether this update schedule is still configured in the controller's line of code even when the schedule no longer exists on the UI, however it is deemed impossible to find this out.

Please could someone figure this out for me as I am starting to lose hope here.

Thank you.

Ben

  @HBEN1603 

Id try this - take full backup of controller, factory reset it, then restore the backup when you are going through the initial config.

Sounds a lot like the disappearing VPN issues that were around during the 5.14 to 5.15 controller updates (the vpns were there, working, but invisible on the controller and unable to be deleted or edited)