Being investigated in CRE-22806. This will be fixed in an upcoming backend release (no sensor upgrade necessary).
Contact Technical Support for assistance