This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Combining Mqtt-sn publisher subscriber Thread example on different topics

Hello, 

Can anyone please provide me some idea about how to combine the mqtt-sn publisher example publishing on data topic with the mqtt-sn subscriber example subscribed on cmd topic. 

I want to combine this both example, I have looked for refference on devzone and got one post but there also the subscribe and publishing was on same topic. 

Can someone please provide some basic code snippet. Thanks. 

Parents Reply Children
  • Hello, I am talking about nRF5 SDK for thread... I want to combine both examples for example subscribe on one topic , publish on another topic

  • Hi Brian,

    I am sorry for the late reply. Can I ask how far have you come with your development? If you are in earlier stages of development I want to remind you that nRF5 SDK and MQTT-SN may not be a futureproof concept. I suggest you migrate to our Openthread solution using nRF Connect SDK. Depending on what you want to do you could take a look at new protocols like e.g Matter.

    Best regards,

    Marjeris

  • Hi Brian,

    I am sorry for the late reply. Can I ask how far have you come with your development? If you are in earlier stages of development I want to remind you that nRF5 SDK and MQTT-SN may not be a futureproof concept. I suggest you migrate to our Openthread solution using nRF Connect SDK. Depending on what you want to do you could take a look at new protocols like e.g Matter.

    Best regards,

    Marjeris

  • Hey,

    Actually we are almost at the end of development phase just integrated DFU with mqtt-sn example. We preferred nRF5 SDK for Thread MQTT-SN example as it provided production ready example as stated in SDK overview. It's not that we haven't considered using NCS previously but there aren't many examples in NCS as compared to nRF5 SDK for Thread. 

    I know that nRF SDK for Thread won't be developed but I guess support is still available for the same 

Related