EC800M模块MQTT无法使用遗嘱功能问题

物联网模组 4G标准模组
1

Revision: EC800MCNLCR06A03M04
/**********************************************************************************************
通讯过程如下
*********************************************************************************************/
AT+QMTCFG=“willex”,1,1,2,0,“/device/CMCC-590425-7C5758416AD3/upward”,99

{“deviceId”:“01B8BA34030080985014A78805”,“eventType”:“Offline”,“timestamp”:0,“deviceType”:“590425”}

OK

AT+QMTCFG=“will”,1

+QMTCFG: “will”,1,2,0,“/device/CMCC-590425-7C5758416AD3/upward”,“{“deviceId”:“01B8BA34030080985014A78805”,“eventType”:“Offline”,“timestamp”:0,“deviceType”:“590425”}”

OK
/*********************************************************************************************/
配置完成后, 创建连接后断开设备电源, 并没有收到配置相关的遗嘱信息.
使用MQTTX客户端测试是有遗嘱信息的.
那么请问这个模块是不支持遗嘱配置还是我配置的过程有错误?

更新:目前还发现当MQTT连接被其他客户端挤掉的时候没有上报断开

2

你好
遗嘱的配置是支持的， 你反馈的这个问题可以提供个完整的流程，或者抓个log看下。

3

相关MQTT的流程
RDY
AT+QHTTPCFG=“contenttype”,4

OK
AT+QMTCFG=“version”,0,4

OK
AT+QMTCFG=“timeout”,0,2,2,0

OK
AT+QMTCFG=“keepalive”,0,0

OK
AT+QMTCFG=“qmtping”,0,5

OK
AT+QMTCFG=“edit/timeout”,0,1,2

OK
AT+QMTCFG=“version”,1,3

OK
AT+QMTCFG=“SSL”,1,1,2

OK
AT+QMTCFG=“timeout”,1,2,2,0

OK
AT+QMTCFG=“keepalive”,1,0

OK
AT+QMTCFG=“qmtping”,1,8

OK
AT+QMTCFG=“edit/timeout”,1,1,2

OK
AT+QINISTAT

+QINISTAT: 0

OK
AT+QINISTAT

+QINISTAT: 0

OK
AT+QINISTAT

+QINISTAT: 0

OK
AT+QINISTAT

+QINISTAT: 1

OK
AT+QINISTAT

+QINISTAT: 1

OK
AT+QINISTAT

+QINISTAT: 3

OK
AT+CREG?

+CREG: 0,0

OK
AT+CREG?

+CREG: 0,1

OK
AT+QIACT=1

OK

AT+QMTCFG=“willex”,1,1,2,0,“/device/CMCC-590425-7C5758416AD3/upward”,99

{“deviceId”:“01B8BA34030080985014A78805”,“eventType”:“Offline”,“timestamp”:0,“deviceType”:“590425”}
OK
AT+QMTCFG=“will”,1

+QMTCFG: “will”,1,2,0,“/device/CMCC-590425-7C5758416AD3/upward”,“{“deviceId”:“01B8BA34030080985014A78805”,“eventType”:“Offline”,“timestamp”:0,“deviceType”:“590425”}”

OK
AT+QMTOPEN=1,“cgw.komect.com”,8883

OK

+QMTOPEN: 1,0
AT+QMTCONN=1,“CMCC-590425-7C5758416AD3”,“deviceOfALC2018”,“4kAVHkSjPNKzX1zE”

OK

+QMTCONN: 1,0,0
AT+QMTPUBEX=1,1,2,0,“/device/CMCC-590425-7C5758416AD3/upward”,97

{“deviceId”:“01B8BA34030080985014A78805”,“eventType”:“MBoot”,“timestamp”:0,“deviceType”:“590425”}
OK

+QMTPUBEX: 1,1,0
AT+QMTOPEN=0,“8.134.96.199”,1883

OK

+QMTOPEN: 0,0
AT+QMTCONN=0,“01B8BA34030080985014A78805”

OK

+QMTCONN: 0,0,0
AT+QMTPUBEX=0,1,2,0,“hxhh_topic_tiaosheng_MQTT2”,97

{“deviceId”:“01B8BA34030080985014A78805”,“eventType”:“MBoot”,“timestamp”:0,“deviceType”:“590425”}
OK

+QMTPUBEX: 0,1,0
AT+QMTCFG=“willex”,1,1,2,0,“/device/CMCC-590425-7C5758416AD3/upward”,99

{“deviceId”:“01B8BA34030080985014A78805”,“eventType”:“Offline”,“timestamp”:0,“deviceType”:“590425”}
OK
AT+QMTCFG=“will”,1

+QMTCFG: “will”,1,2,0,“/device/CMCC-590425-7C5758416AD3/upward”,“{“deviceId”:“01B8BA34030080985014A78805”,“eventType”:“Offline”,“timestamp”:0,“deviceType”:“590425”}”

OK
AT+QMTOPEN=1,“cgw.komect.com”,8883

OK

+QMTOPEN: 1,0
AT+QMTCONN=1,“CMCC-590425-7C5758416AD3”,“deviceOfALC2018”,“4kAVHkSjPNKzX1zE”

OK

+QMTCONN: 1,0,0
AT+QMTPUBEX=1,1,2,0,“/device/CMCC-590425-7C5758416AD3/upward”,97

{“deviceId”:“01B8BA34030080985014A78805”,“eventType”:“MBoot”,“timestamp”:0,“deviceType”:“590425”}
OK

+QMTPUBEX: 1,1,0

4

上面已经附上流程, 能看出遗嘱没有生效的原因吗?