Clients
Files (bypass download)
Recipes
Change settings
Config exports
Pull a device's configuration (.dcm) over the Remote UI and keep it here. CPCA first checks the device (model + serial) on the IP.
Downloads
Recipe run log
Models
The device code is what the app reads over UART (e.g. A354D). The name is what shows in the Run log. New codes are added automatically on first run; rename the name and it updates everywhere in the Run log.
Active runs
Users
API tokens (Bearer — for Claude / automation)
A token grants access via Authorization: Bearer <token> with the linked user's role. The raw token is shown only once on creation.
Server self-update
Upload a server publish .zip (tagged with an increasing version), then Apply — the server swaps its binaries with an external script and restarts. data/, logs/ and appsettings*.json are preserved. Requires a deploy key (set Security:DeployKey on the server).
Last apply log
—
Client auto-update
Upload a client build, then on a client (Clients → select → “Auto-update”) pick it and schedule it. The client updates itself on its next connection (preserves its identity + settings). Build the packages with the publish commands, then upload the resulting .zip.
Device logs
Logs received from devices at /canon/action/log (script execution reports). CHECK requests are auto-allowed.