Hi Johan,
Sorry to hear about the trouble. This issue has been resolved in the 3.6 release and there is also a patch fix for this in the 3.5.1 train. Feel free to email your local SE or email me direct (marcus.burton -at- arris.com) and I will help get you squared away.
thanks,
Marcus