support

Troubleshooting Guide

Baseline runbook for connectivity, telemetry, and Unreal runtime issues.

Last Updated: 2026-02-26

Troubleshooting Guide

Use this runbook in order. It isolates where the pipeline is failing: device, cloud, or Unreal runtime.

Step 1: Confirm Device Health

Check:

  • Device is powered — USB-C connected, or battery not depleted
  • Network credentials are valid
  • Local network permits outbound MQTT to the Twinise broker

If device is not visible in registry, resolve provisioning/auth before continuing.

Step 2: Confirm Cloud Ingestion

From the device registry:

  • device_id is online
  • Last event timestamp is recent
  • The expected metric keys appear in the latest frame

If online but no telemetry:

  • Inspect firmware publish interval
  • Validate payload keys and value types
  • Check sensor hardware wiring/availability

Step 3: Confirm Unreal Connectivity

In Unreal project settings:

  • Endpoint URL is correct
  • Signed in to your Twinise account from the plugin panel, and the session has not expired
  • Plugin/module is enabled

At runtime:

  • Print latest received timestamp
  • Verify delegate/event is bound
  • Verify bound device_id matches exact case

Common Symptoms

Device Offline

Likely causes:

  • Firewall/proxy blocking outbound traffic
  • Invalid provisioning token
  • Wrong SSID/password

Actions:

  1. Reprovision credentials.
  2. Allow required outbound endpoints/ports.
  3. Reboot device and retry handshake.

Device Online, No Metrics

Likely causes:

  • Publish interval too high
  • Metric keys changed in firmware
  • Sensor read failure

Actions:

  1. Confirm the device is waking on schedule — compare last-event timestamps across two expected wake cycles.
  2. Compare the metric keys in the latest frame against the ones your bindings expect.
  3. Run local sensor diagnostics.

Cloud Good, Unreal Static

Likely causes:

  • Plugin not signed in, or the session expired
  • No active binding to target actor
  • Value mapping/clamping hides visible changes

Actions:

  1. Sign in again from the plugin panel and confirm the endpoint.
  2. Log incoming payload values in runtime.
  3. Test with exaggerated metric-to-visual mapping.

Escalation Data To Capture

Before escalating, capture:

  • device_id
  • Timestamp range (UTC)
  • Last known firmware version
  • Unreal engine version and plugin version
  • One sample payload

Related Pages