Last updated
Last updated
Blynk.Cloud MQTT API uses Names to reference Datastreams.
Changing datastream names in the template settings can make your existing devices misbehave. If this happens, you can either revert your changes or update your device firmware Over the Air to conform to the new datastream structure.
Publish topic ds/DATASTREAM, payload: value in plain text (i.e. 123, hello or 3.1415926)
DATASTREAM - the datastream name
For multivalue (array-like) values, the individual items in the payload are separated using a 0x00 byte, i.e: First\u0000Second\u0000Third. The separator is a NUL character, that is also represented as \u0000 in Unicode.
Publish topic batch_ds, payload: JSON-encoded object with datastream name as the key and datastream value as the value. The JSON value type must match with the datastream type. Use string for datastream with String data type, number for datastream with Integer, Double or Enum value type, true or false for datastream with Boolean data type and array of two numbers for datastream with Location data type (use longitude as the first array element and latitude as the second). Example:
Publish topic ds/DATASTREAM/erase, payload: empty
DATASTREAM - the datastream name
Subscribe to topic: downlink/ds/DATASTREAM
DATASTREAM - the datastream name
Usually, you'll want to subscribe to a widcard topic like downlink/# or downlink/ds/#.
Publish topic get/ds, payload: datastream names separated by comma (i.e. Brightness,Color)
The device will receive requested datastream values on downlink/ds/DATASTREAM topic.
Publish topic get/ds/all, payload: empty
The device will receive requested datastream values on downlink/ds/DATASTREAM topic.
For this to work, open Datastream settings and enable Advanced Settings -> Sync with latest server value.