I know, that was very confusing. Anyways, in the v3.3.8 firmware (available now in stable channel), we fixed this issue.