I reverted the firmware to 4.03 and it is operating correctly. I’ve read through the release notes for 4.1 and it doesn’t say anything about disabling this feature. I’m going to try and manually patch to 4.1 and see if it repeats the issue (and report back). I may even try the beta! :slight_smile: