@mattjc I tried the 2.1.4 firmware and did not see this problem. Please provide more detailed information.