Retrying the readings for unpaired devices led to a nasty concurrency bug where duplicate components were created,, and attempting to enforce locking per device so that components are created atomically live-locked the ingestor. Instead we're only going to retry the hardware_info packet for now: readings will start being ingested when the onboarding completes.
Retrying the readings for unpaired devices led to a nasty concurrency bug where duplicate components were created,, and attempting to enforce locking per device so that components are created atomically live-locked the ingestor. Instead we're only going to retry the hardware_info packet for now: readings will start being ingested when the onboarding completes.