[SOLVED] Setting MultiTech Conduit to receive from a mDot?


Dear all

I have create a data source with MultiTech Conduit called Conduit007 at http://things.ubidots.com/api/v1.6/datasources/57ac09ab762542398b14f54d
Then I create a variable at Conduit007 called Tombol at

I have copy the example program from https://ubidots.com/docs/devices/conduit.html#setting-up-node-red and modify with my token = atGG1f5rAKofAdE2fBBZa5AwOZNRND at Function (Node-Red).
see Function ubidots photo

If I want to create a mqtt output (using node-red), how to create a broker information for ubidots?

I also copy example program from https://ubidots.com/docs/devices/mDot.html#send-one-value-to-ubidots
But the program did not pass beyond Line 81, why?
The network name and network pass are okay
The debug output from mDot at COM20 (9600 bps, 8N1)

Please help. Thank you very much in advance for your help and attention.

Warmest Regards,


Hey @sliawatimena, according to your pic you are being able to receive data from the mDot.

However, it seems you are sending a “Hello World” text, which our sample Node doesn’t recognize. As explained here, our node understands data in this format:


For example:


The Node will automatically create a data source with tag=DEV-EUI and variable with name “Tombol” and value “1”.

If you want to build your own node using MQTT, you can easily do it by using our MQTT broker and nodered’s MQTT client.


Dear Hackmed,

I sent AT+SEND=Tombol: 1. The node-red flow can capture data from mDot.
However there is no change at Tombol in ubidots.

I still wondering about data source Conduit007 URL Endpoint:
and variable Tombol at URL Endpoint http://things.ubidots.com/api/v1.6/variables/57ac143f76254270dd7cad82
How to utilize them?

In Function ubidots node, do I only just modify the TOKEN with mine? I got token from my API Credentials.

Here are the tombol status. The tombol’s value changed because I clicked it manually at ubidots dashboard, not from mDot data.

Thank you very much in advance.

Warmest Regards,


This conversation was continued in github: https://github.com/ubidots/ubidots-mDot/issues/1