Hi team, also receiving this same error on a third device (out of couple of hundred devices) as attached:
Welcome back to the community, @MaxH! So is this an issue with only some of your devices (while other devices are working smoothly without any issue)?
