receive MQTT signals directly from AWS on thread end device

Hello,

I am working on a thread based project for a class and I was wondering if it was possible to receive an MQTT packet directly from AWS through the border router? Or is it required to use MQTT-SN with a MQTT broker on the border router. If the only option is the MQTT broker on the border router, should I be using the pub/sub end device thread example?

Environment:

RaspberryPi 3b - connected to home wifi

nrf52840-Dongle - plugged into the RaspberryPi

nrf52840-DK V3 - acting as end device 

CLI example located in <InstallFolder>/examples/thread/cli/uart/hex/nrf52840_xxaa.hex on DK

Parents
  • Hello Liam,

    Are you using nRF 5 SDK or NCS. If you are using nRF 5, I would recommend you to switch.

    Given that you are using NCS, I would not use MQTT-SN. It is difficult. Use MQTT instead.

    possible to receive an MQTT packet directly from AWS through the border router?

    This might require the Thread device to have a public IP, but you could get around that. For MQTT, the Thread device will subscribe to a MQTT Broker. And since the device have subscribed "via a TCP connection", the Broker likely do not need to know the address of the Thread Device.

    Regards,

    Elfving

Reply
  • Hello Liam,

    Are you using nRF 5 SDK or NCS. If you are using nRF 5, I would recommend you to switch.

    Given that you are using NCS, I would not use MQTT-SN. It is difficult. Use MQTT instead.

    possible to receive an MQTT packet directly from AWS through the border router?

    This might require the Thread device to have a public IP, but you could get around that. For MQTT, the Thread device will subscribe to a MQTT Broker. And since the device have subscribed "via a TCP connection", the Broker likely do not need to know the address of the Thread Device.

    Regards,

    Elfving

Children
No Data
Related