Please take a look at the topic that is currently tracking this problem with the latest V2 Firmware release: