Skip to Content

Device

Settings → Device holds settings for the whole Pod. Every control saves as soon as you change it, and a Saved message confirms it.

Device settings with timezone, temperature unit, auto power-off cap, pump stall protection, daily maintenance, and LED cards
Settings → Device with pump protection, daily prime, and LED night mode turned on. Synthetic example data.

Clock and schedule defaults

Time format chooses 12-hour or 24-hour display. This is saved on the Pod, so connected clients share the preference; it does not change the timezone or the times stored in your schedules.

Default after schedule ends chooses Turn off or Maintain final temperature for new curves. Existing curves retain their own choice. See schedule end actions.

Pod

  • Timezone. Schedules, alarms, and Autopilot time windows run in this timezone. If things happen at the wrong hour, check this first. The default is America/Los_Angeles.
  • Temperature unit. °F or °C for the whole Pod. This is the same setting as Units in Appearance.

Power

Auto power-off cap turns a side off after it has been on for a set time. Turn on the switch and choose 1 to 48 hours; the default is 12 hours. Sides set to Always on in Sides, and run-once sessions, are not affected.

Pump protection

Pump stall protection turns a side off if its water pump slows down or stops, which protects the Pod when water is not flowing. It is off until you turn it on. While it is off, the System dashboard shows a reminder.

When it is on, you can adjust:

SettingRangeDefaultMeaning
Trip threshold100–1500 RPM500Pump speed below which a reading counts as stalled
Dwell samples1–102Stalled readings in a row, about 60 seconds apart, before turning off
Pump auto-recoveryOn/offOffTurn the side back on once the pump recovers
Recovery RPM500–3000 RPM1500Pump speed that counts as recovered
Recovery samples1–103Recovered readings in a row before turning the side back on

Number fields save when you leave the field. Values outside the range are adjusted to the nearest allowed value.

When protection turns a side off, the Temp screen shows a banner. Re-enable turns the side back on at its previous temperature. Stall events also appear in Pump alerts on the System dashboard.

Reconnect and Restart service

  • Reconnect reloads the page. Use it if the app stops updating.
  • Restart service asks for confirmation, then makes the Pod briefly unavailable while Core restarts.

In Core v3.0, Restart service runs the updater for the main channel, the same as Check for updates in Updates. If you use the dev channel, it switches the Pod to main. Use it only when you are happy to update.

Sensor data source

This card tells you which firmware pipeline the Pod is on and whether sensor frames are reaching Core, which is the first thing to check when biometrics are empty. On NATS firmware it also shows which NATS subjects Core reads, and lets you change them.

  • Firmware. How the Pod’s firmware hands sensor data to Core. Newer firmware (April 2026 and later) publishes to a local NATS JetStream server. Older firmware writes .RAW files, either on a tmpfs through a frank.sh shim or a frank.service drop-in, or straight to /persistent. EmmcWear firmware (4b7552d5) still uses NATS but under new rawmem subjects. On Core builds without core#917  this card then shows No frames. See sensor data by firmware.
  • Reading from. The source Core chose when the service started: NATS stream or .RAW files. Core detects this itself, once per start, so after a firmware update it needs a restart to detect again. Check for updates in Updates rebuilds and restarts Core on your current channel. Restart service on this page also restarts it, but in Core v3.0 it runs the main channel updater, so skip it on dev (see the warning under Reconnect and Restart service).
  • Last frame. How long ago the newest sensor frame arrived, and its type. Live means frames are flowing. Stalled means nothing has arrived for over a minute.

Core builds that include core#918  add three rows. Subjects and Publishing prefixes appear while Core is reading NATS. Subject prefix also appears when Core reads .RAW files on NATS firmware, for example when an override forces .RAW.

  • Subjects. Whether Core picks the subject prefix itself (auto) or reads one you chose (pinned), and which prefix feeds each reading type, for example raw: sens.capsense, sens.piezo · rawmem: frz.temp.
  • Publishing prefixes. The prefixes the firmware publishes sensor (sens.*) readings under, up to 16, and how recently, for example raw 2s ago · rawv2 (not read) 1s ago. A prefix marked (not read) is one Core does not subscribe to.
  • Subject prefix. Choose Auto, raw, rawmem, or Custom…. Auto reads raw and rawmem, preferring raw for each reading type. Pin a prefix only if the firmware publishes somewhere else. A custom prefix takes letters, digits, _ or -, up to 32 characters, with no dots or wildcards.

If no frames arrive and the firmware publishes under a prefix Core doesn’t read, the card says so: “Firmware publishes under rawv2, which this pod doesn’t read. Set the subject prefix to rawv2.”

After you change the prefix, the live sensor stream re-subscribes straight away. The biometrics modules read the prefix when they start, so the card offers Restart biometrics modules. That restarts the piezo processor, sleep detector, and environment monitor. The calibrator picks up the change on its next restart.

A note appears under the rows when the chosen source does not match the firmware, or when an environment override (PIEZO_SENSOR_SOURCE or PIEZO_NATS_DISABLED) is forcing a source. On a development machine without a Pod the card shows no firmware.

There is no switch between .RAW files and NATS. Core picks one source per start and never runs both at once, so a toggle would need a restart to take effect. The subject prefix control only changes which NATS subjects Core reads. The same information is in the System dashboard under Health, and on the Pod in sp-status. An agent can read it and change the prefix through MCP.

Daily maintenance

  • Daily reboot. Restarts the Pod at the time you choose. Off by default; the default time is 03:00.
  • Daily prime. Circulates water to clear air from the lines at the time you choose. Off by default; the default time is 14:00. Choose a time when nobody is in bed.

For liquid BZK, refilling, priming, and seal compatibility, see Water care and maintenance liquid.

LED

  • Brightness. 0–100% for the Pod’s light. It saves when you let go of the slider.
  • Night mode. Dims the light during a time window. Choose the Window (22:00–07:00 by default) and the Night brightness (0% by default).

Source reference: Device settings form  · Settings API  · Update trigger 

Last updated on