Boron's gone offline

[robc]

What is your keepAlive() setting?

// SYNTAX
Particle.keepAlive(23 * 60); // send a ping every 23 minutes

At first glance, it may be that the cloud did not acknowledge two default (23 minute) keepAlive() pings. So, the cloud may have timed your devices out and assigned them offline status.

https://docs.particle.io/reference/device-os/firmware/boron/#particle-keepalive-

If the above is what is happening to you, you may want to set your keepAlive() manually with a more frequent ping. Or, (what I do) send Particle.publish() occasionally with a NO_ACK parameter. This last method reduces the overhead of data a bit.

Hopefully, you might monitor the console and find your Borons go back online (for X reason). Then you can access them OTA without a physical visit to reset.

Took me a while to find this:

@rickkas7

Now that I think about it, I think you might need to miss two keep-alive pings for the device to be marked offline. Since the offline indicator doesn’t know what keep-alive you’ve set, it assumes the default setting, so 46 minutes to an hour doesn’t seem unreasonable to me.

Because keep-alive pings use ACK mode, using NO_ACK would reduce the data usage in half.