Complete guide to Tick device settings, cloud sync, and remote management
Tick uses a layered configuration system with local files and cloud-based management
These files are stored on the Pico's filesystem and control device behavior.
| Config | Location | Live Update | Reboot Required | How to Update |
|---|---|---|---|---|
| config.json | /config.json | No | Yes | Setup mode, config command |
| device_id | No | Yes | Setup mode only | |
| device_key | No | Yes | Setup mode only | |
| device_name | No | Yes | Setup mode only | |
| api_endpoint | No | Yes | Setup mode only | |
| profile | No | Yes | config profile <name> |
|
| wifi.json | /wifi.json | No | Yes | config wifi <ssid> <pass> |
| settings.json | /settings.json | Yes | No | Commands with --save flag |
| service intervals | Yes | No | sync set <sec> --save |
|
| sensor intervals | Yes | No | sensor set <name> <sec> --save |
|
| log_level | Yes | No | log <level> --save |
These settings can be changed while the device is running. Changes are lost on reboot unless saved with --save.
| Setting | Live Update | Command |
|---|---|---|
| Sync interval | Yes | sync set <seconds> |
| Log level | Yes | log dbg|inf|wrn|err |
| NTP interval | Yes | time interval <minutes> |
| Service interval | Yes | service set <name> <sec> |
| Garbage collection | Yes | gc (manual trigger) |
Settings stored in the cloud (Azure Table Storage) and managed via the Twin dashboard.
| Setting | Live Update | How to Update |
|---|---|---|
| Device name | Yes | UI settings modal → Save |
| Profile (metadata) | Yes | UI settings modal → Save |
| Device key | Yes | UI → Regenerate Key |
| Queued commands | Yes | UI → Push Config / Command |
Profiles define the default configuration for sensors and services. Located in /profiles/ on the device.
| Profile | Static | Purpose |
|---|---|---|
base.json |
Yes | Core sensors/services (memory, uptime, device, network) |
indoor.json |
Yes | Indoor monitoring (extends base) |
outdoor.json |
Yes | Outdoor monitoring (extends base) |
counter.json |
Yes | Counter sensor configuration (extends base) |
Profiles are read-only at runtime. Changing profile requires a reboot.
Different ways to update device configuration depending on your access and needs.
| Method | Updates | When Applied |
|---|---|---|
| Setup Mode (AP) | All device configs | On save + reboot |
| Commands | Runtime + settings.json | Immediately (or on reboot for config) |
| Cloud UI | Cloud metadata + queued commands | On next device sync |
| Push Config | Queues config profile/wifi + reboot |
On next sync → then reboot |
Use these in the Console tab or via cloud commands
configShow current configprofileShow active profilesettingsShow saved settingsconfig profile <name>Change profile (reboot)config wifi <ssid> <pass>Change WiFi (reboot)settings clearClear saved settingssync set 60Set sync to 60ssync set 60 --saveSet + persistlog dbg --saveDebug logging + persistPush configuration changes to devices even when offline
In the Twin dashboard, click the gear icon next to any device to open its settings modal.
Under "Device Config (Push to Device)", you can change:
Click "Push Config" to queue the changes. The device will receive and apply them on its next sync cycle.
WiFi changes will automatically trigger a device reboot after applying.
Commands are stored in the cloud command queue. When the device syncs:
If the device is offline, commands remain queued until it reconnects.