We have successfully reproduced this issue locally.
And after checking with the RD, we found it a known bug and a new firmware which is about to release has fixed it.
The firmware will be uploaded to the official website asap after a series of routine testing.