RE: openThread and MQTT communication on a nrf52840DK

Unitware — Mon, 21 Jun 2021 16:38:54 GMT

I gave up, did some preliminary TCP connections and measured really low bandwith with lots of retransmissions and such. And that was before I even started with TLS. So I'll stick to UDP on the thread network and a gateway to convert to MQTT later on.

RE: openThread and MQTT communication on a nrf52840DK

Unitware — Wed, 09 Jun 2021 12:23:14 GMT

Hi did you find a solution to this? I have been trying for a few days now and still have no success with the TCP communication.
Ping works well in both directions but TCP connect ends up in error -116

RE: openThread and MQTT communication on a nrf52840DK

Didrik Rokhaug — Mon, 07 Sep 2020 15:33:02 GMT

Hi.

[quote user=""]I have not been able to find an example where MQTT is implemented ontop of a openThread network, is there any?[/quote]

Unfortunatly not.

[quote user=""]I thought i could take the MQTT example for nrf9160 and replace the LTE communication with openThread that the coApp example uses.[/quote]

I work mostly with the nRF9160, so I am not very familiar with Thread, but I'll try to answer this as best I can.

First, the mqtt_simple sample was built for the nRF9160, so you will find some nRF91-specific code there. But, it should not be a big problem to remove it, and replace it with the corresponding Thread code. In particular, the modem_configure() function must be replaced with the Thread code for setting up a connection.

As far as I can see, there should not be any huge issues with replacing the LTE stack with the Thread stack. The MQTT library is built on a POSIX socket interface, which the Thread stack also seems to expose.

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/1.3.0/nrf/ug_thread_stack_architecture.html

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/1.3.0/nrf/ug_thread_ot_integration.html#overview

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/1.3.0/zephyr/reference/networking/sockets.html#bsd-sockets-interface

So, as far as I can tell, except for the code responsible for establishing a connection (LTE or Thread), the sample should otherwise only need changes to prj.conf. A good place to start is probably to look at the coap_client Thread sample, and compare what options are set there versus in the mqtt_simple and coap_client samples for the nRF9160. You can remove the LTE link control, BSD library and AT Host related configuration options, as they are specific to the nRF91. The other big option you need to remove is the CONFIG_NET_SOCKETS_OFFLOAD, and set CONFIG_NET_NATIVE, as you want to use Zephyr's network stack.

From there, you can start figuring out what options you need to bring over from the coap_client Thread sample.

Best regards,

Didrik