Skip to Content

Logs

System → Logs shows recent messages from the Pod’s services. Read it when something failed and you want to know why. Nothing here changes the Pod.

Logs page with Core, Piezo Processor, Sleep Detector, and Environment Monitor sources, the firmware console, and the log viewer with level filters
System → Logs showing synthetic Core messages.

Read a service’s log

  1. Under Sources, choose a service: Core, Piezo Processor, Sleep Detector, or Environment Monitor. A green dot means it is running.
  2. Filter by level with All, Info, Warn, or Error, or type in Filter to find a word.
  3. Leave Follow on to keep the newest lines in view as they arrive. Turn it off to scroll back.

The viewer shows the last 200 lines. Copy and Download save them for a bug report. Select the refresh button to reload.

The Health page’s Logs buttons open this page with the right service already chosen.

Enable detailed app logs

In System → Storage → Data recording, select Debug for 15 minutes before reproducing an issue. Logging automatically returns to the selected Quiet/Off mode, or you can select Stop debug logging earlier. Quiet keeps app warnings and errors; Off suppresses app diagnostic logs. The filters on this Logs page only filter what was captured—they do not enable more logging.

The installer configures the journal in RAM. Copy or download logs before rebooting; messages that were suppressed or lost on reboot cannot be recovered. Firmware/OS logs and direct third-party output are outside the app logging control.

Firmware console

Open console shows raw output from the Pod’s firmware. Switch between Logs and Frames, filter by type, Pause or Resume, and Clear the view. Use it to check the firmware is sending data at all.

Collect a CLI support bundle

For startup failures or Pod 3 sensor and scheduler incidents, collect a bundle before another reboot. Connect from your computer using the installed SSH key:

ssh -p 8822 root@POD_IP

Then run on the Pod:

sp-info sp-status sp-bundle-logs

sp-info prints hardware, firmware, and Core build context. The bundle includes service journals, the firmware journal, a combined app/firmware timeline, service state, and sensor routing diagnostics. It writes /tmp/sleepypod-bundle-<timestamp>.tar.gz by default and redacts known secrets. Keep redaction enabled and review the contents before sharing.

Copy the generated file to your computer using its exact filename. Run this from your computer, replacing TIMESTAMP with the value printed on the Pod:

scp -P 8822 root@POD_IP:/tmp/sleepypod-bundle-TIMESTAMP.tar.gz .

For a quick text capture of the last hour, run on the Pod:

sp-logs --firmware --since '1 hour ago'

Without a time window, sp-logs --firmware follows Core and firmware messages live. A bundle defaults to the current boot. To select an incident window from retained journals, use explicit timestamps with a timezone:

sp-bundle-logs --since '2026-10-24 17:00:00 UTC' --until '2026-10-24 17:30:00 UTC'

Replace those example times with the actual incident window. A time window can search retained boots, but cannot recover RAM-backed journals lost in a reboot.

If the installed version lacks these helper commands or options, collect the journals directly:

journalctl -u sleepypod.service -u frank.service --since '1 hour ago' --no-pager journalctl -u sleepypod-piezo-processor.service -u sleepypod-sleep-detector.service --since '1 hour ago' --no-pager

The firmware console above provides live firmware output; the CLI captures the frank.service journal and startup history for a support handoff.


Source reference: Support bundle  · CLI logs  · Build context  · Recording controls  · Log viewer  · Firmware console 

Last updated on