In case you didn’t see it, @BartekZooz said there’s a firmware fix in the works to handle this issue. Yay!