Hey @brianl. Looks like I didn’t notice that you’d already tried this! Sorry about that. I got another report of this issue and finally realized the root cause of this issue. We’ve got it fixed up now in firmware version v2.10.21, currently available via the beta app, which you could sign up for here.
If you’ve got some time to try out this version, we’d love to hear whether or not this works for you.