Was this issue ever resolved in newer firmware versions? I am having the same issue (FW, L0.0.00.00.05.08,A.02.01). Getting the topic rather than the message. I don’t get the AT commands debug output. How do I enable that?
I recommend you updating the firmware version on the module.
The examples are tested against the latest version of the module.
Not all AT commands are backwards compatible. Setting the mno profile in the latest version is required.
Thanks. I updated to the latest firmware with the same result. Topic instead of message. I’ll try it with the debug enabled to see what data is coming through.
Does MQTT SN work reliably with the built-in ublox stack?
I am still having trouble getting the mqtt_test example to read incoming messages. Debug does not provide more info with regards to the raw message coming in:
@Jan have you been able to reproduce the problem. Any guidance how to get it to work?
I am currently communicating payload values in the topic in the prototype but for the finished product I need to get this to work.
I haven’t had so much time to investigate the issue.
What I have seen is that in the example there is an issue with connecting to the mosquitto server.
Although when using a custom server or the public hivemq, I don’t have any issues.
I hope that when I find the issue for the mosquitto problem that it will be the same for your AWS issue.
I managed to solve it some time ago and I wanted to share the solution.
Maybe it was just my lack of understanding how char arrays and strings work. Both, topic and payload are in the buffer. The topic is terminated by a null byte and ‘print()’ stops after that. Splitting topic and payload into separate arrays solves the issue.