I was able to identify the problem and restore the old behaviour. In the July update, I quietly added a hardware watchdog. This isn’t in use yet, but in the future it will allow devices to automatically reboot if they have a hard lockup.
When we were calling shutdown, the watchdog was rebooting the device as the timeout was being triggered. The Vero 2’s hardware watchdog thought that the device had frozen, so it was triggering a restart. I have now resolved this behaviour in this commit:
The fix will be available in the next OSMC update.
Thanks for reporting this problem, I did not notice it when testing the July update.
Sam