Sign in to access device dashboards, automation rules, and technical support tools.
Tap Scan QR and point the camera at the QR code on the device.
You can also enter the device setup URL manually and click Load.
Enter the device's serial number above to issue it a unique MQTT credential during setup.
⚠ Unable to display the device page in this viewer.
The device may be blocking embedded views. Open the URL directly in a new tab to configure it, then return here to record the activation.
| Name | Value | Type | Timestamp |
|---|
Every device authenticates to the broker with a unique X.509 client certificate. Use Revoke Access to block a lost, stolen, or decommissioned device from reconnecting or publishing — a replacement certificate can only be issued from the Onboarding Station during an in-person reconfiguration. If the device is currently connected, revoking does not immediately drop its live session (the broker only re-checks credentials on reconnect); use Force Disconnect All Sessions below if you need to guarantee it's severed right now.
"Revoke All Orphaned" ignores the search box above and the checkboxes below — it always targets every active certificate with no matching fleet device.
| Client Identity | Serial Number | Status | Issued | Revoked | Actions | |
|---|---|---|---|---|---|---|
| Loading device certificates... | ||||||
Runs the daily expiry scan immediately instead of waiting for its 2:30 AM slot — useful when verifying notification delivery during testing.
Emergency action — restarts the MQTT broker, immediately dropping every currently connected device (not just revoked ones). Legitimate devices reconnect automatically within seconds; a device with a revoked certificate cannot.
A revoked certificate's row is never deleted automatically -- only this scheduled purge removes it. The credential.revoked audit entry is kept permanently in the Audit Activity report regardless of this setting.
Purge job runs daily at 2:35 AM.
These values are pre-filled on the device setup page when the Onboarding Station is used. Broker host and Sparkplug group are managed here. Port, TLS certificate details, and per-device client certificates are derived elsewhere.
The network-facing IP or hostname devices use to reach this broker.
Manage website login users and roles (VIEWER, OPERATOR, ADMIN).
Optional contact info (email/phone) is used for automated report notification routing and audit visibility.
| Display Name | Username | Roles | Phone | Status | Last Login | Actions | |
|---|---|---|---|---|---|---|---|
| Loading users... | |||||||
Issue and manage API keys for external system integration via the Public REST API.
The raw key value is shown only at creation time and is never stored in recoverable form.
| Name | Scope | Created By | Created | Last Used | Status | Expiry | Actions |
|---|---|---|---|---|---|---|---|
| Loading API keys... | |||||||
Push real-time events to external systems (LIMS, ERP, Slack, custom APIs) as they happen.
Each endpoint can subscribe to specific event types or receive all events.
| Name | URL | Events | Status | Last Triggered | Actions |
|---|---|---|---|---|---|
| Loading webhooks... | |||||
When enabled, received MQTT messages are included in the Logback-managed activity log stream (configured in logback-spring.xml).
Configure your IFTTT Webhooks API key. This key is shared across all IFTTT automation rules and stored securely on the server — it is never returned to the browser after saving.
Save your IFTTT event names here so you can pick from a list when creating rules instead of typing them manually.
Set a default webhook endpoint used to pre-fill webhook destinations in Automation Rules and Scheduled Report notifications.
Configure named Slack and Microsoft Teams incoming webhook destinations. Automation Rules and Scheduled Report notifications reference these by name — the webhook URL is write-only and never shown after saving.
Configure native SMTP email delivery in a dedicated settings dialog.
Configure optional SMS delivery for short alert-style notifications. The log provider is ideal for local testing because it records sends in the portal logs without contacting an external SMS service.
Shared by every system notification — Database Backup failures, System Health Alerts, and MQTT client certificate expiry warnings — instead of a separate webhook per feature. Optional; email/SMS above work independently of this.
Used to build absolute report links in webhook notifications (deep links and artifact downloads). Example: https://portal.example.com
Enter your entitlement key to activate a Premium or Enterprise subscription. The key is validated server-side and never returned to the browser after saving.
Publish a high-visibility message to all logged-in users (for maintenance windows, service restarts, and outage communications).
Leave blank and click Save to clear the current notification.
Document files and every retained version are stored in the portal database. Warning thresholds notify uploaders; hard limits block only future uploads.
Enter 0 to disable a warning or hard limit. Lowering a limit does not delete existing documents.
Automatic backup is not available when running . Use your database server's native backup tools instead — for example, pg_dump and point-in-time recovery for Postgres.
Portal databases are backed up automatically each day at 2:00 AM. Backups use SQLite's VACUUM INTO for a safe, consistent snapshot — concurrent historian writes are never blocked.
Sends an alert to all Admin users with a configured email or phone number, plus the System Notification Webhook below if one is configured. Uses the SMTP and SMS settings configured above.
To restore: click Schedule Restore next to a backup, then restart the portal. The selected backup will be swapped in at startup before any connections open.
Sends an alert to Admin users (and the System Notification Webhook, if configured) if the MQTT broker connection stays down past the threshold below, or if live dashboard updates start backing up. Without this, the only way to learn about an outage is noticing the dashboard or a customer calling.
Sends an alert to all Admin users with a configured email or phone number. Uses the SMTP and SMS settings configured above. A recovery alert is sent when the broker reconnects.
Choose how long raw historian metric rows are kept before the daily cleanup job removes older data.
Allowed range: 30 to 730 days. Cleanup runs daily at 2:00 AM using this setting.
How often the dashboard's live metric values (and their sparklines) refresh in place on the device grid. Alarm and online/offline status changes are unaffected by this setting — those always update immediately.
Allowed range: 5 to 120 seconds. Takes effect the next time the dashboard is loaded.
Fleet devices that have not reported (sent an NBIRTH) within the archive threshold are automatically moved to archived status. Archived devices that remain silent past the purge threshold are permanently deleted.
Archive job runs daily at 2:30 AM. Archived devices appear in Fleet Inventory → Archived where they can be manually restored or deleted.
Define automation rules that run when a device metric crosses a threshold. Rules apply fleet-wide by model number or device type.
| Name | Target | Condition | Trigger Actions | Cooldown | Status | Actions |
|---|
Point a rule's webhook URL at the address below to capture and inspect the exact payload that gets sent.
Schedule report runs by selected day(s) and hour(s), track run history, and download generated artifacts.
Report artifacts are stored in the database, not on disk — a longer retention period keeps more generated PDFs (typically tens of KB to a few MB each) in the database. Size for retention days × schedule frequency × typical report size.
| Name | Report Type | Schedule | Status | Last Run | Next Run | Actions |
|---|
Define when a numeric Key Signal shows as out-of-band on the Dashboard and device detail. Thresholds always apply by device type, optionally narrowed by model configuration — independent of notifications.
| Name | Device Type | Key Signal | Range | Gate Conditions | Deadband | Actions |
|---|
| Serial | Display Name | Model | Firmware | Last Seen | Location |
|---|
| Serial | Display Name | Model | Archived | Purge In |
|---|
| Device | Location | Tracked Items | Most Urgent | Due | Actions |
|---|
| Name | Target | Message Preview | Active Until | Cooldown | Dismissal | Devices Sent | Status |
|---|
Generate tabular fleet reports with filters and export options.
Current fleet inventory with status, versions, and location context.
| Serial | Display Name | Device Type | Model | Firmware | Status | Last Seen | Location |
|---|
| Assigned At | Serial | Display Name | Location | Ended At | Assigned By | Reason |
|---|
| Serial | Display Name | Device Type | App Version | IOB Version | Target | Status | Reason |
|---|
| Name | Scope | Status | Schedule | Counts | Actions |
|---|
| Serial | Display Name | Device Type | Model | Last Seen | Minutes Since Seen | Status | Location |
|---|
| Location | Devices | Avg Uptime % | Downtime (min) | SLA Meet | SLA Below |
|---|
| Serial | Display Name | Device Type | Model | Uptime % | Downtime (min) | Outages | SLA | Status | Location |
|---|
| Rule | Enabled | Target | Firings (window) | Devices Impacted | Recent Firing | Last Fired (rule) |
|---|
| Alarm | Active | Cleared | Open | Devices | MTTA (min) | MTTR (min) |
|---|
| When | Actor | Role | Action | Entity | Context | Summary |
|---|
| When | Type | Actor | Action | Target | Entity | Detail |
|---|
| Location Path | Type | Total | Online | Offline | Online % | Avg Uptime % | Est. Uptime Devs | Connects | Alarms | Avg Telemetry / Dev / Day |
|---|
| Period | New Devices | Cumulative | MoM % | Active | Connects | Disconnects | Reconnect Rate | Alarms | Metric Records |
|---|
| Serial | Display Name | Device Type | Score | Status | Stale (min) | Missed Heartbeat Windows | Dupes | Blank | Longest Gap (min) | Top Issue |
|---|
Find an authorized Labconco servicer near you.