This problem has resurfaced on a v2 camera that previously never had an issue.
Also see this related thread: