Service & Diagnostics
The everyday commands for checking, restarting, and diagnosing a device.
Once a device is installed and registered, day-to-day operation comes down to a handful of commands: check whether the service is running, restart it if not, and — if something looks wrong — run the health check to see what it finds. This page covers all of it.
Check the service status
door-statusShows whether the bytegate-edge service is currently running, along with its recent log
lines. This is the first thing to run when a device seems unresponsive.
Start, stop, or restart it
door-start
door-stop
door-restartdoor-restart is the one you'll reach for most — it's the quickest way to recover from a
device that's stuck or misbehaving without touching its configuration.
Watch the logs live
door-logsFollows the service's log output in real time (Ctrl+C to stop watching). Useful while
reproducing an issue — leave it running and watch what happens as you scan a QR code.
Update the device
door-updateRuns the update script to pull and install the latest release. See OTA from the Dashboard and Manual SSH Update for the full update workflows — this alias is the manual-path shortcut for it.
Run a full health check
cd ~/bytegate-edge
./scripts/diagnose.shRuns a broad diagnostic sweep — system resources, version/git state, Python environment, configuration, the systemd service, recent logs, hardware, cloud connectivity, the upload queue, data directories, and OTA readiness — and prints a PASS/WARN/FAIL summary at the end. Run this before escalating an issue; it usually tells you exactly what's wrong.
Field tip
If door-status or any other alias reports that the service isn't found at all, don't
reinstall from scratch — re-run ./scripts/setup_systemd_service.sh from the
bytegate-edge directory. It's a repair tool: it regenerates and reinstalls the systemd
unit, then starts the service, without touching your existing .env or
config_production.yaml.
Last updated on