Receiving a multi-line payload response from MQTT-related BG95 AT commands

[mikalai-kavalchuk]

Hello!

I'm trying to implement MQTT-related AT commands for BG95 and have encountered one issue related to receiving multi-line response with AT+QMTRECV command.

I registered URC handler for "QMTRECV" and can handle incoming MQTT publications. But if I send MQTT publication with payload that include \<LF> symbols inside (formatted JSON with line feed): thereafter the first \<LF> symbol in payload interpreted as the end of line so in the URC handler for "QMTRECV" I can only see part of the payload up to the \<LF> symbol. Next parts are come as _ATUNDEFINED messages.

Looks like an issue while processing responses in _handleAllReceived because the responses must include \<CR>\<LF>\<response>\<CR>\<LF> according to AT Commands Manual

I can register __CellularRegisterUndefinedRespCallback to proceed all the rest of "QMTRECV" but it looks like workaround. What can you suggest to do in this situation? Thank you!

[chinglee-iot]

Hi mikalai,

Thank you for your interest in cellular interface. I will take a look at the AT command "AT+QMTRECV" and reply to you later.

[chinglee-iot]

Hi mikalai, Cellular interface support reading byte stream from AT command. We can give the following method a try:

• Use the buffer mode for received message : Message not contained in URC. Receive the message from the buffer.
  
• Receive the message from buffer with recvID : Cellular interface can handle one byte stream in the response.
  
• Reference the Cellular_SocketSend implementation for receiving byte stream from AT command response.

[mikalai-kavalchuk]

Hi chinglee, Thank you for the information! I will try this mode and report the results later

[tpecar-ltek]

I would also like to add here that I've encountered the same issue on SIM800C.

There are however other issues with the current MQTT client on SIM800C before I would consider it viable for production use, and I would encourage others to use the FreeRTOS-Cellular socket interface + coreMQTT (or similar) on the SIM800C platform.

---

For the sake of documenting the issue, on SIM800C the incoming messages are provided via +SMPUBLISH URC and there is no configurable option in AT+SMCONF for a "notification + read at request" mode of operation (as is for example for modem TCP/IP stack).

[chinglee-iot]

Hi tpecar,

Thank you for your feedback to cellular interface. It looks like SIM800C doesn't support buffer access mode for MQTT AT command. Receiving byte stream in URC is a new feature to cellular interface. We would discuss to add this function.

[mikalai-kavalchuk]

Hi mikalai, Cellular interface support reading byte stream from AT command. We can give the following method a try:

• Use the buffer mode for received message : Message not contained in URC. Receive the message from the buffer.
• Receive the message from buffer with recvID : Cellular interface can handle one byte stream in the response.
• Reference the Cellular_SocketSend implementation for receiving byte stream from AT command response.

Hi chinglee! I did everything in the same way as for sockets, as you advised, and now I can receive incoming MQTT publications without any issues.

Thank you so much for your help!

[chinglee-iot]

We have a PR to support the feature to receive data from URC #137. This PR is still under development. One of the similar use case is the socket direct push mode. This PR for BG96 can be referenced. Suggestion to the PR is welcomed.

[chinglee-iot]

PR #137 is merged. I will close this issue first. Feel free to feedback further question here.