@DTom Same happening to me, same firmware version and I can confirm this didn't happen on earlier firmware versions (can't say for sure if previous one had the issue or not but for sure this did not...