Stream live MQTT data into Unreal Engine actors – free, open-source plugin (UE 5.5)

I build industrial digital twins in Unreal Engine, and the part I kept rewriting was getting device data into the scene: socket code, parsing, threading, then wiring values into Blueprints. So I turned it into a plugin and open-sourced the core: Titan Twin Lite (MIT).

GitHub: GitHub - huahu223/TitanTwinLite: Free open-source MQTT data binding for Unreal Engine 5 digital twins (Lite version of Titan Twin) · GitHub

What it does

An MQTT topic like factory/robot001/temperature lands as the property temperature on the actor whose entity id is robot001, and a binding component writes it into a Blueprint variable, a UMG widget or an Anim Instance variable. No networking code in your project.

  • Native MQTT 3.1.1 client (TLS, QoS 0/1/2, auto-reconnect), running on a worker thread
    • Scalar and JSON payloads, batch JSON
    • Address templates (factory/{entity}/{property}) map thousands of topics with one rule
    • Every value carries timestamp, quality and unit
    • Full C++ source

5-minute setup

  1. Copy TitanTwinLite into your project’s Plugins folder (C++ project, UE 5.5).
    1. Run a broker, e.g. Mosquitto on 127.0.0.1:1883.
    1. Add to Config/DefaultGame.ini:
[/Script/TitanTwinMqtt.TwinMqttSettings]
Host=127.0.0.1
Port=1883
bAutoConnect=True
+Subscriptions=(bEnabled=True,TopicFilter="factory/#",PayloadFormat=Scalar)

[/Script/TitanTwinDataSource.TwinDataSourceSettings]
bEnableRuntimeRuleMapping=True
+AutomaticMappingRules=(bEnabled=True,AddressTemplate="factory/{entity}/{property}",bCaseSensitive=True)
  1. On an actor, add TwinEntityComponent (Entity Id robot001) and TwinPropertyBindingComponent with one binding: Source Property temperature → Target Variable Temperature (a float on the actor).
    1. Play, then publish:
mosquitto_pub -h 127.0.0.1 -t factory/robot001/temperature -m 52.3

Temperature becomes 52.3.

I tested this with a Python simulator publishing 12 robots × 5 values every second; the values in UE matched the sender exactly.

Need more?

The full version, Titan Twin, adds OPC UA, HTTP polling, alarms (trigger / acknowledge / resolve with hysteresis), commands back to devices, history replay and Pixel Streaming, for UE 5.5–5.8. It will be on Fab soon.

Feedback, issues and PRs are welcome. What protocols would you want next – Modbus? ROS 2?