Sorry for the inconvenience! This bug has been addressed in the latest firmware, which is currently available in beta.