How often a cellular unit reports, and why it changes

Cellular units hand over readings faster while a store is open and slower while it is closed, to keep the fleet's data use sensible without ever delaying an alert.

This is about cellular units — which is every current unit. A legacy Wi-Fi unit posts every reading as it takes it, so none of the scheduling below applies to it.

A cellular unit measures constantly and keeps a record every five minutes whatever else is happening. What is scheduled is how often it hands that record over the mobile network. Hand-overs are scheduled rather than continuous to keep the fleet's data use sensible and to spare the unit's power supply — there is no per-unit data charge to you, and a change in heat level never waits for the schedule.

When	How often it hands over	Why
While the store is open	Every 30 minutes by default	Often enough to keep the picture current, while every hand-over the modem skips is one less strain on the unit's power supply. A change in heat level does not wait for this schedule.
While the store is closed	Every hour by default	An empty kitchen at 3am gains nothing from frequent hand-overs.
Out of heat season	The closed rate, all day	Only applies if a season is configured. By default there is no season and nothing slows down.

Two things override the schedule upwards, and both are automatic. A unit hands over within a couple of minutes when the heat level changes or conditions are climbing fast, and a unit put into elevated reporting stays fast until it is calm again. The schedule describes the quiet case, not the urgent one.

Open and closed come from the store's operating hours, which you set on each store — so getting those right is what makes the fast window line up with your actual shifts. A unit can also carry its own hours, for a walk-in cooler on a different schedule from the kitchen it opens onto.

In the dashboard: Stores & locations — Your sites, their store numbers and hours, and who to contact at each one.

You never set a timezone on the device. The server converts your store's local hours into something the unit can compare without a clock it can trust, and recomputes it when the clocks change — so a shift window does not drift an hour twice a year.

Heat season is configuration, never an assumption, and the default is all year. That default is deliberate: indoor process heat has no season, and a foundry, bakery or laundry in January is hotter than a restaurant in July. If your sites genuinely are weather-driven, ask us to set a season for the company or for individual stores — Phoenix and Minneapolis do not share a summer, and a franchise spanning both needs to say so per store.

Every mistake in this configuration resolves to reporting MORE often, not less. An unrecognised season, an unparseable set of hours, a timezone we don't know: all of them fall back to the fast schedule. That means a few more hand-overs, and it is the only acceptable direction to fail in.

How fast you may go is bounded by your plan: Pro's in-hours floor is 30 minutes, and Enterprise can select a 15-minute hand-over. Asking for something faster than your plan allows does not fail silently — you get the fastest rate your plan does allow.

Related