Devlog

The flag that never arrived

Firmware

Early October we took a sensor for a walk, away from a base set up indoors, to see where the link gave out. Out past where the base could hear it, we tripped the flag on purpose, then walked back into range.

The alarm never came.

The sensor had tried to send the flag, heard nothing back, and backed off: a few quick retries, then a long wait. Walking back into range didn’t help, because it wasn’t due to try again for a long time. And the base was ignoring the “I’m flagged” bit in the sensor’s regular check-ins.

The fix was two changes. A sensor with a flag to report now keeps trying often for the first ten minutes and every minute after that, and tries again the moment any message gets through. And the base now raises the alarm from a check-in that says the flag is up, even if it missed the flag message itself. We reproduced the problem on the bench by taking the base off the air, then checked that the alarm went off soon after it came back, exactly once.

The next release added a way to dismiss an alarm by hand from the app, for the case where a sensor can’t clear it itself.

We’ll publish range numbers when the field tests are done, with the conditions written down. This test wasn’t about range. It was about what happens at the edge of it.