Hey y’all! Carolina from support here!
Had a customer this week ask whether they could send a raw HEX payload over TagoTiP UDP and have the platform automatically convert it to the expected TagoTiP format. Great question! Here we go with the tip, which applies to all TagoTiP transports: UDP, TCP, HTTP, and MQTT.
The answer is: Yes! You can totally handle it using raw passthrough + a Payload Parser!
All TagoTiP transports support a raw passthrough prefix (>) that lets you send raw bytes directly to your device’s Payload Parser, skipping the standard variable format entirely. The >x prefix indicates the payload is in HEX format, but other formats are also supported. Just make sure to use the > prefix so the protocol knows to treat it as raw data.
UDP:
echo -n ‘PUSH|4deedd7bab8817ec|sensor-01|>xDEADBEEF01020304’ \
| nc -u -w1 udp.tip.us-e1.tago.io 5683
TCP:
echo ‘PUSH|4deedd7bab8817ec|sensor-01|>xDEADBEEF01020304’ \
| nc tcp.tip.us-e1.tago.io 5693
HTTP:
curl -X POST https://http.tip.us-e1.tago.io/v1/tip/sensor-01 \
-H “Authorization: TagoTiP 4deedd7bab8817ec” \
-H “Content-Type: text/plain” \
-d ‘>xDEADBEEF01020304’
MQTT:
mosquitto_rr -h mqtt.tip.us-e1.tago.io -p 1883 \
-u 4deedd7b -P ab8817ec \
-t ‘$tip/sensor-01/push’ -e ‘$tip/sensor-01/ack’ \
-m ‘>xDEADBEEF01020304’
Note: >x is used in the examples above for HEX payloads. Adjust the prefix according to your payload format.
In all cases, the raw bytes are delivered to your device’s Payload Parser, where you write a script to decode them and map to TagoIO variables.
So if your device can’t send native TagoTiP format, here are your options:
-
Best case: configure the firmware to send native TagoTiP format
-
Raw passthrough: use > and create a Payload Parser to decode the bytes
-
Device fully locked? A middleware between your device and TagoIO is the way to go
For the full TagoTiP protocol docs, check out each transport: UDP | TCP | HTTP | MQTT
Hope this saves someone some time! Let me know in the comments if you have any questions.
Happy Weekend,