So, for a week or so (possibly since 1.0.0 release) we noticed some inconsistencies on both handshaking and OTA update confirmations with electrons.
on Particle console, the device’s connections do not always appear, despite the fact it connects and sends messages, which makes the console pretty inefficient at showing a proper state of the devices.
we update devices, they reset, connect and informs their current version (which has updated) in our DB, but Particle keeps trying to update them anyway, thinking they haven’t updated… so the updates keep failing and the device resetting.
Detail: we’re using MANUAL and SYSTEM_THREAD enabled.
- is firmware update causing a reboot or should we handle that ourselves?
- is resetReason still RESET_REASON_UPDATE (if caused by system)?
The OTA updates seem to have always been a sensitive topic with quite some inconsistencies (specifically with system_thread enabled, which we HAVE to use in order to avoid getting blocked on connection-related operations), is there any plan to prioritize this and have it working consistently and efficiently? I fear Particle credibility on the market may be seriously impacted by consistent upgrade failures…