Hi, we suffered same bug. There is fixed firmware which solved our problem, but code is not publicly available. Contact support and ask for firmware version 200.2.9.13.188. It's firmware which was developed after we opened support ticket roughly 2 months ago regarding this issue, you could tell support our case id as reference: 00497963.