BG96 blocks incomming MQTT message while publish in progress

IoT Modules LPWA Module
1

Hi All,

We experience an issue with the BG96 module.
When we publish a MQTT message we see the message on the MQTT broker when we check with MQTT explorer.
But the module returns an error after 20 seconds, 3 retries with 5 second timeout.
So most likely something with the acknowledge went wrong. (QOS is 2)
So far not an issue, but in these 20 seconds we see with MQTT explorer that an message is published for our device on a topic which we are subscribed to.
But we don’t receive any notification from this.
The message which we expected to see is the last will message that we set. (We see it with MQTT explorer)
So it seems the module didn’t reply on a keep-alive on-time.
Also we receive no notification through an AT URC that the MQTT connection is lost.
When we want to publish an other message we receive an ERROR result on the AT command.

2023-10-04T12:43:18.946 --> 41542B434750414444523D310D______________________________________________________________________________________________________ AT+CGPADDR=1.
2023-10-04T12:43:18.997 <-- 0D0A2B434750414444523A20312C31302E322E352E3232350D0A0D0A4F4B0D0A________________________________________________________________ ..+CGPADDR: 1,10.2.5.225....OK..
2023-10-04T12:43:19.146 --> 41542B434F50533F0D______________________________________________________________________________________________________________ AT+COPS?.
2023-10-04T12:43:19.197 <-- 0D0A2B434F50533A20302C302C224F6469646F222C380D0A0D0A4F4B0D0A____________________________________________________________________ ..+COPS: 0,0,"Odido",8....OK..
2023-10-04T12:43:19.396 --> 41542B43474D520D________________________________________________________________________________________________________________ AT+CGMR.
2023-10-04T12:43:19.446 <-- 0D0A424739364D415230324130384D31470D0A0D0A4F4B0D0A______________________________________________________________________________ ..BG96MAR02A08M1G....OK..
2023-10-04T12:43:19.596 --> 41542B4353510D__________________________________________________________________________________________________________________ AT+CSQ.
2023-10-04T12:43:19.646 <-- 0D0A2B4353513A2033312C39390D0A0D0A4F4B0D0A______________________________________________________________________________________ ..+CSQ: 31,99....OK..
2023-10-04T12:44:13.946 --> 41542B514D545055423D302C34322C312C302C2273797374656D7374617475732F342F322F512D4C4954452F32322D36353938302D393939222C3133300D____ AT+QMTPUB=0,42,1,0,"systemstatus/4/2/Q-LITE/22-65980-999",130.
2023-10-04T12:44:13.997 <-- 0D0A3E20________________________________________________________________________________________________________________________ ..> 
2023-10-04T12:44:14.046 --> 0A3F0A180A06512D4C49544510021A0C32322D36353938302D3939391208426174746572696A1A01312208426174746572696A280138B40D5A015660FD83F5A8 .?....Q-LITE....22-65980-999..Batterij..1".Batterij(.8..Z.V`....
2023-10-04T12:44:14.046 --> 060A3F0A180A06512D4C49544510021A0C32322D36353938302D3939391208426174746572696A1A01322208426174746572696A280138EA105A015660FD83F5 ..?....Q-LITE....22-65980-999..Batterij..2".Batterij(.8..Z.V`...
2023-10-04T12:44:14.046 --> A806____________________________________________________________________________________________________________________________ ..
2023-10-04T12:44:14.097 <-- 0D0A4F4B0D0A____________________________________________________________________________________________________________________ ..OK..
2023-10-04T12:44:34.246 <-- 0D0A2B514D545055423A20302C34322C320D0A__________________________________________________________________________________________ ..+QMTPUB: 0,42,2..
2023-10-04T12:44:34.396 --> 41542B434750414444523D310D______________________________________________________________________________________________________ AT+CGPADDR=1.
2023-10-04T12:44:34.446 <-- 0D0A2B434750414444523A20312C31302E322E352E3232350D0A0D0A4F4B0D0A________________________________________________________________ ..+CGPADDR: 1,10.2.5.225....OK..
2023-10-04T12:44:34.596 --> 41542B434F50533F0D______________________________________________________________________________________________________________ AT+COPS?.
2023-10-04T12:44:34.646 <-- 0D0A2B434F50533A20302C302C224F6469646F222C380D0A0D0A4F4B0D0A____________________________________________________________________ ..+COPS: 0,0,"Odido",8....OK..
2023-10-04T12:44:34.846 --> 41542B43474D520D________________________________________________________________________________________________________________ AT+CGMR.
2023-10-04T12:44:34.897 <-- 0D0A424739364D415230324130384D31470D0A0D0A4F4B0D0A______________________________________________________________________________ ..BG96MAR02A08M1G....OK..
2023-10-04T12:44:35.046 --> 41542B4353510D__________________________________________________________________________________________________________________ AT+CSQ.
2023-10-04T12:44:35.097 <-- 0D0A2B4353513A2033312C39390D0A0D0A4F4B0D0A______________________________________________________________________________________ ..+CSQ: 31,99....OK..
2023-10-04T12:45:18.996 --> 41542B434750414444523D310D______________________________________________________________________________________________________ AT+CGPADDR=1.
2023-10-04T12:45:19.046 <-- 0D0A2B434750414444523A20312C31302E322E352E3232350D0A0D0A4F4B0D0A________________________________________________________________ ..+CGPADDR: 1,10.2.5.225....OK..
2023-10-04T12:45:19.196 --> 41542B434F50533F0D______________________________________________________________________________________________________________ AT+COPS?.
2023-10-04T12:45:19.246 <-- 0D0A2B434F50533A20302C302C224F6469646F222C380D0A0D0A4F4B0D0A____________________________________________________________________ ..+COPS: 0,0,"Odido",8....OK..
2023-10-04T12:45:19.446 --> 41542B43474D520D________________________________________________________________________________________________________________ AT+CGMR.

Is there something we can do so that we receive the +QMTRECV while we are waiting fo the publish timeout? Or better can we configure some setting so the keep-alive is handled while waiting for the publish timeout?

2

The firmware version of the module is BG96MAR02A08M1G_01.200.01.200.

3

Have you checked MQTT socket state? as error shows, this publish message was failed.
So, please check MQTT connection and MQTT server is good or not? then do a QPING to check if other services if working.