This is a bug. Fixed in firmware 4.1.0 release 2.