MQTT Example - About Broker's IP

RE: MQTT Example - About Broker's IP

Stian Røed Hafskjold — Tue, 30 Aug 2016 10:31:44 GMT

Hi, I just meant that I don't know how the data is represented at your end.. If you see raw data, only the payload, or if the payload is decoded into text strings or whatever. But if you got it working now it doesn't matter:)

RE: MQTT Example - About Broker's IP

MANGO — Wed, 10 Aug 2016 14:27:38 GMT

Sorry for the late response. The expected string was received and Wireshark showed the topic and payload as you mentioned.

Lastly, about "But I'm not sure at which level you can read the message on your broker.",

I don't know what you mean about the "level".

Which "level" are you inferring?

-Best Regards, Mango

RE: MQTT Example - About Broker's IP

MANGO — Sat, 30 Jul 2016 18:03:00 GMT

Oh, I will check it with Wireshark.

I think the nRF52 send a hexadecimal value. The Mosquitto client which subscribed "led/state" didn't show any character but created new line after pressing button from the nRF52.

RE: MQTT Example - About Broker's IP

Stian Røed Hafskjold — Wed, 27 Jul 2016 16:07:05 GMT

It should receive more than two bytes. The message consists of the topic: "led/state", a 2 byte message counter and one byte describing on or off. But I'm not sure at which level you can read the message on your broker. Maybe it only shows the last byte describing the led state (and translates it into a 16 bit integer). What is the value of the bytes you receive?

RE: MQTT Example - About Broker's IP

MANGO — Wed, 20 Jul 2016 17:49:12 GMT

Testing with your provided hex file, my broker received 2 bytes when pressing button 2.

Is this correct?

About the this "weird" phenomenon, maybe I selected an incorrect source (.c) file when using Keil MDK 5.

I will reconfigure the project settings again.

Thanks for your help.

RE: MQTT Example - About Broker's IP

Stian Røed Hafskjold — Tue, 19 Jul 2016 09:41:04 GMT

This is really weird. I've not seen that before. I can provide you with a hex that I know is working. I'll post it in my answer.

RE: MQTT Example - About Broker's IP

MANGO — Fri, 15 Jul 2016 06:24:29 GMT

I cannot understand why the destination port is 8883 (shown in Wireshark),

even though I configured the port to 1883, the non secure port, with Keil MDK.

What seems to be the problem?

RE: MQTT Example - About Broker's IP

Stian Røed Hafskjold — Thu, 14 Jul 2016 08:54:41 GMT

After executing 6tunnel you get: bind, address already in use. Try to ps aux | grep 6tunnel to see what command is actually running. If it is not the correct one, kill the process and start it again.

What happens if you sniff the BT0 interface in wireshark? Do you see any activity?

RE: MQTT Example - About Broker's IP

MANGO — Wed, 13 Jul 2016 15:54:22 GMT

Well, I posted the result after installing 6tunnel in my edited answer.

What seems to be the problem?

-Best Regards, Mango

RE: MQTT Example - About Broker's IP

Stian Røed Hafskjold — Wed, 13 Jul 2016 13:27:37 GMT

It is on your RPi3. You can use the ip address the way you describe. The command is correct.
Because no matter what the destination ip address is, the 6tunnel will forward every packet arriving on port 1883 to the ip address you specify in the 6tunnel command.

Remember that the MQTT example uses secure connections and port 8883 as default. You can read here on how to not use secure connections and port 1883 instead. (Or you can use secure connections and 6tunnel with port 8883 instead. But it might require some extra setup on the EC2 side.)

RE: MQTT Example - About Broker's IP

MANGO — Wed, 13 Jul 2016 13:01:05 GMT

Do I have to install 6tunnel in RPi3 Jessie or my cloud service (Amazon EC2)?

In my case, my EC2 instance is using Ubuntu v14.

Suppose the "cloud_hostname" (in Amazon, it is called as public IP) is 11.22.33.44

and I use port 1883.

So I should type

# 6tunnel -6 1883 11.22.33.44 1883

in my RPi3 after installing 6tunnel?

"And just leave the m_broker_addr as it is." Why is that?

RE: MQTT Example - About Broker's IP

Stian Røed Hafskjold — Tue, 12 Jul 2016 14:39:21 GMT

The IoT SDK only supports ipv6, and the m_broker_addr variable should contain the ipv6 address of the MQTT broker. If your cloud service don't support ipv6, you need to translate the ipv6 packets into ipv4 somehow. You can try 6tunnel: http://toxygen.net/6tunnel/

sudo apt-get install 6tunnel

And forward packets from port 1883 (8883 if you are using secure connection)

6tunnel -6 1883 cloud_hostname 1883

And just leave the m_broker_addr as it is.

EDIT:

hex file modified to use non secure connection: nrf52832_xxaa_s1xx_iot.hex