Yes, the first recommendation is making sure the panel is updated to 2.6.2 firmware. Steps are shown here. It looks like you are on 2.6.1 right now.
The individual I spoke to at Qolsys reports he has Control4 enabled on his system on 2.6.2 and is not noticing this.
Note that 2.6.2 has a caveat that it requires 6 digits codes to be enabled. They added that as a requirement for additional security with the third party connections.
Any change in behavior?
As an interim solution, I’d love to be able to trigger this via automation to keep my system up and running. Could you provide a secure webhook/machine instructions to access the link (may be a dev. question)? I tried to inspect the code but it’s behind the page.
I’m not sure we’ll be able to accommodate that, specifically, but I have forwarded an enhancement request to allow repeated scheduled reboots for troubleshooting. That may be something our team can simply add as an option in the system manager. I’ll let you know what I find out.