It seems this is a bug in the newest special airOS firmware. We will try to fix this as soon as possible.
