I'm having the same issue as this thread. In that thread it's suggested that the v1.0 hardware can be updated to the v2 or even v3 firmware and it should fix the issue. I just wanted to confirm that...