nRF52840, MQTT, TLS1.2

RE: nRF52840, MQTT, TLS1.2

Reto — Wed, 19 Apr 2017 15:29:11 GMT

Thread specification V1.1.1 says:

Thread-compliant device MUST support UDP
The implementation of TCP is OPTIONAL; a Thread-compliant device MAY implement TCP

Would be nice if Nordic supportS TCP in near future. I may contact the regional sales manager.

Thank you Peter. Reto

RE: nRF52840, MQTT, TLS1.2

Petter Myhre — Wed, 19 Apr 2017 15:07:48 GMT

-We do not discuss future plans here, but you can contact the regional sales manager for your area, if you don't know who it is, send me a PM with your location, and I'll let you know.

-As far as I know, Thread doesn't use TCP, only UDP. Maybe this question is of help to you.

RE: nRF52840, MQTT, TLS1.2

Reto — Wed, 19 Apr 2017 12:27:52 GMT

Thank you Petter. I am thinking of leaving this path and going with nRF52840 and Thread SDK, as it seems more supported by Nordic. In this case: I would not build the border router by myself (I would buy a 802.15.4 / Wifi / LAN boarder router). But Thread SDK does not support MQTT and I need MQTT (as I want to connect do IBM Watson IoT).

But how long will it take until you support MQTT-SN (UDP) over Thread on nRF52840?
I don't think I can use MQTT/TCP over Thread: right?

Thank you Petter! Reto

RE: nRF52840, MQTT, TLS1.2

Petter Myhre — Wed, 19 Apr 2017 11:48:42 GMT

I don't know if ESP32 supports IPv6/6LoWPAN over BLE and if it can act as a 6LoWPAN boarder router.

You should still be able to do DFU OTA
If you want to do IPv6 over BLE, yes, but the current IoT SDK doesn't support nRF52840

RE: nRF52840, MQTT, TLS1.2

Reto — Sun, 16 Apr 2017 19:59:10 GMT

Hi Petter

Let's say I would use a ESP32 as IoT Gateway (running MQTT, TLS1.2, Wifi, Bluetooth 4.2) and nRF52840 as sensor nodes (running MQTT, TLS1.2, Bluetooth 4.2, TLS1.2).

Am I still able to update the nRF52840 over-the-air (SoftDevice, application)?
I guess I should use the nRF5 IoT SDK with MQTT clients on the nRF52840?

Drawback would be: BLE 4.2 (range) compared to BLE 5.

Thank you Petter.

RE: nRF52840, MQTT, TLS1.2

Petter Myhre — Tue, 11 Apr 2017 10:20:40 GMT

No problem :)

RE: nRF52840, MQTT, TLS1.2

Reto — Tue, 11 Apr 2017 09:24:36 GMT

Sounds like a plan. Great. Thank you so much for your support Petter!

RE: nRF52840, MQTT, TLS1.2

Petter Myhre — Tue, 11 Apr 2017 08:34:47 GMT

You are correct. Then I recommend starting off with the normal SDK, nRF5 SDK 13.0.0, more specifically the ble_app_uart and ble_app_uart_c examples.

RE: nRF52840, MQTT, TLS1.2

Reto — Mon, 10 Apr 2017 15:05:51 GMT

Thank you Petter! So, if I got this right, then it means the following:

There is no way running MQTT (TLS1.2) on a nRF52 and having this nRF52 running as Bluetooth master (central role / observer role)?
Alternative? Running MQTT on ESP8266? ESP8266 communicate with nRF52-central-role-device over UART. Sensor devices (nRF52 peripheral role / broadcaster role) communicate to nRF52-central-role-device over Bluetooth.

If this is correct: With which SDK should I start?

Again: Thank you very much Petter.

RE: nRF52840, MQTT, TLS1.2

Petter Myhre — Mon, 10 Apr 2017 14:30:55 GMT

Unfortunately, we do not have support for IPSP router role, which you would need in the gateway.

See this for more information.

RE: nRF52840, MQTT, TLS1.2

Reto — Mon, 10 Apr 2017 12:05:42 GMT

MQTT endpoint in every nRF52840 FW. That is:

Gateway (Bluetooth master)
Sensors (Bluetooth slaves)

Thank you for your question :-)

RE: nRF52840, MQTT, TLS1.2

Petter Myhre — Mon, 10 Apr 2017 10:37:24 GMT

Where do you want the MQTT endpoint(s)? In each node or in the gateway?