I’ll answer my own question, so that I can mark it as answered:
This was a bug, fixed in firmware 1.10