Direct Device MQTT Topic Reference
This page lists the Direct Device topics in one place. These topics are not used for Gateway-mediated Children; see the Gateway MQTT reference for that architecture.
Subscribe — Server → Device
| Topic | QoS | AES | Purpose |
|---|---|---|---|
{projectCode}/ServerToDevice/{deviceSerial} | 1 | variant | Main command delivery |
{projectCode}/DeviceSetting/{deviceSerial} | 1 | variant | Dedicated Setting saved data |
{projectCode}/ReceiveDeviceUpdate/{deviceSerial} | 1 | variant | Topic name confirmed; final OTA behavior remains future/deferred |
{projectCode}/ReceiveGeneralData/{deviceSerial} | 1 | variant | General tagged data/response channel |
{projectCode}/DeviceLastValue/{deviceSerial} | 1 | variant | Last-value response |
{projectCode}/Debugger/{deviceSerial} | 1 | variant | Remote Debugger |
{projectCode}/SendScenarioSetting | 1 | none | Local Scenario save/delete |
{projectCode}/ReceiveRunScenario | 1 | none | Local Scenario run/enable/disable |
{projectCode}/Time | 0 | none | UTC clock bootstrap |
{projectCode}/Time/Tehran | 0 | none | Tehran-local clock bootstrap |
For topics with an AES variant, the encrypted form appends /AES, for example:
{projectCode}/ServerToDevice/{deviceSerial}/AES
Publish — Device → Server
| Topic | QoS | AES | Purpose |
|---|---|---|---|
{projectCode}/DeviceToServer | 0 | variant | Main Device state/data |
{projectCode}/SendNotificationToCenter | 1 | variant | approved notification code to Producer/Center |
{projectCode}/SendNotificationToUser | 1 | variant | approved notification code to Project user/master |
{projectCode}/RunServerScenarioFromDevice | 1 | variant | execute a Server Scenario |
{projectCode}/RequestDeviceLastValue | 1 | variant | request another Device's last-value snapshot |
{projectCode}/SendGeneralData | 1 | variant | general tagged data |
{projectCode}/ControlOthers | 1 | variant | control another Device Operation |
{projectCode}/ReceiveRunScenario | 1 | none | Device-initiated Local Scenario run |
Removed topic
DeviceToDevice is removed from the AirNgin contract and must not be used in new firmware.
Important
Direct Device and Gateway are separate contracts. Never substitute these topics for the .../v1/gw/... namespace used by Gateway-mediated Children.