We are working on the solution for this issue. It will be fixed in the next firmware update.