The spacing between the Xenon and the Boron is now only a few feet. I am trying to setup a system which is “forgiving” of OTA updates to both Gateway and attached mesh devices. I am however “almost” happy with the Boron firmware.
If this is your primary concern, it sounds better to have this flagged up as an issue to be looked into for the firmware team.
I will not be performing OTA updates during the on-site testing (not because it is not reliable now), but instead, ensure that the use case of collecting data and publishing data works reliably.
But, just my opinion based on field testing that I do quite a fair bit.
Based on my testing where i OTA to an Argon
every 30 seconds, this code allows a Xenon
to connect back reliably, but not 100%. Read, not 100%
, maybe 99%
SYSTEM_MODE(AUTOMATIC);
unsigned long cloud_check_time = 0;
void loop()
{
if (!Particle.connected() && millis() - cloud_check_time > 5000) {
Mesh.disconnect();
delay(1000);
Mesh.connect();
delay(1000);
Particle.connect();
cloud_check_time = millis();
}
}