Skip to Content
TroubleshootingCore and biometrics

Core and biometrics troubleshooting

For Pod 3 sensor or scheduler incidents after a reset, start with Pod 3 sensor and scheduler errors, including the web and CLI evidence to collect.

Core will not start

On the Pod, read the status and recent logs:

sp-status journalctl -u sleepypod.service -n 200 --no-pager

For installed key-only SSH access, the documented port is 8822:

ssh -p 8822 root@POD_IP

Database or native-module errors can come from running the wrong Node.js binary. The service uses /usr/local/bin/node; use that binary for manual scripts when comparing behavior. Preserve databases before attempting a repair or reinstall.

App logs are quiet or missing

Check System → Storage → Data recording. Quiet captures app warnings/errors; Off suppresses app diagnostic output. Enable Debug for 15 minutes, reproduce the issue, and copy the relevant output from System → Logs. The app setting does not control firmware or OS logging. RAM-backed journal messages disappear on reboot, so save them first.

Web UI down, service restarting in a loop

Check whether the installed build still exists:

ls -l /home/dac/sleepypod-core/.next/standalone/server.js journalctl -u sleepypod.service -n 50 --no-pager

If server.js is missing, the build is gone. The usual cause is running next build or pnpm build on the Pod: Next empties .next before compiling, and the Pod’s 2GB of RAM can’t finish the build. Newer Core releases log No production build at .next/standalone/server.js; older ones show a misleading pnpm permission error while the service restarts repeatedly.

Recover by reinstalling a pre-built bundle:

sp-update # on the Pod: latest release ./scripts/deploy POD_IP # from a computer: your local checkout

Never build on the Pod. See Core development.

Biometrics are empty

  1. Check the selected side and date. For live measurements, confirm the bed is occupied.
  2. Open Settings → Device → Sensor data source. It names the firmware pipeline (NATS or .RAW), the source Core chose at startup, and the age of the last frame, and it explains a fallback or an override. For module state use System → Health, and for live input use Sensors.
  3. On NATS firmware, confirm fresh frames and output rows; an absent RAW archive is not an ingestion failure. Calibrator may need time to collect its initial live sample window. If no frames arrive at all and the Core journal logs [natsSource] no frames received, compare your firmware with sensor data by firmware. EmmcWear firmware 4b7552d5 publishes on rawmem subjects, which older Core builds do not read. On newer builds, the card’s Publishing prefixes row marks any prefix Core does not read, and Subject prefix lets you pin it.
  4. On RAW firmware, check the hot directory and firmware journal:
ls -la /persistent/biometrics/*.RAW journalctl -u frank -n 100 --no-pager
  1. For RAW readers, confirm RAW_DATA_DIR points to the firmware’s hot directory. For either transport, check module logs and increasing biometrics rows. A healthy web UI does not prove processing is running.
  2. If using cross-generation hardware (such as a Pod 3 hub paired with a Pod 4 cover) or older firmware, inspect journalctl -u frank for bootloader errors (such as BL: Likely wrong Firmware address). See Update stock firmware to update underlying daemons and microcontroller firmware.

See sensor pipeline and calibration for record types, source selection, and transport-specific limitations.

RAW archives are empty

This section applies to RAW firmware. NATS-only firmware need not create these files.

The firmware deletes rotated frames quickly. A linker timer pins frames until the archiver can compress them. Check both stages:

journalctl -u sleepypod-biometrics-linker -n 50 --no-pager journalctl -u sleepypod-biometrics-archiver -n 50 --no-pager df -P /persistent

The linker may be quiet when there is no new frame. Repeated failures, dropped frames, or a growing pending queue warrant checking storage and service health.

Powered, but not heating or cooling

Compare target, bed, and water-temperature trends. A stalled pump can leave power reported as on while temperature stays flat. Check thermal diagnostics, water level, and firmware logs. Repeatedly raising the target will not resolve a transport or pump fault.

Schedules do not run

Check the device clock, timezone, selected days, and side. Core waits for a valid clock after startup. Look for scheduler errors in the Core journal.

The upstream runbook below is the authoritative reference for device-specific paths and deeper diagnostics.


Source reference: NATS diagnostics  · System navigation  · Debugging runbook  · Deployment and service details  · Missing-build crash loop 

Last updated on