Thank you for your feedback. I have found your problem in our BUG library, but it is still in a suspended state and I hope to fix it in the 3.200 version of the firmware.