Community news, upcoming events and general discussions
Threads: 34 Posts: 85
Get technical support from the community
Threads: 1251 Posts: 6913
Threads: 16 Posts: 58
Tell us how to make XDK better!
Threads: 35 Posts: 117
Share and discuss community member projects
Threads: 67 Posts: 296
I am using the simple MQTT client example and moddified it with my WLAN and MQTT connection parameters.
The client connects successully, sends and receives messages.
However the connection is dropped intermittently and eventually the client will not re-connect.
The MQTT broker (Solace PubSub+) reports a client disconnect - "reason(Header Parse Error)".
The application logging on the XDK console log reports the following:
INFO | XDK DEVICE 1: MqttEventHandler : Event - 17
INFO | XDK DEVICE 1: MqttEventHandler : Event - 4
INFO | XDK DEVICE 1: AppControllerFire : MQTT publish failed
INFO | XDK DEVICE 1: Error in XDK110 Application package.
INFO | XDK DEVICE 1: Package ID: 153
INFO | XDK DEVICE 1: Module ID: 39
INFO | XDK DEVICE 1: Severity code: 2
INFO | XDK DEVICE 1: Error code: 120
The thing is - why I am asking this here - is that the client pushes and receives hundreds of messages without issue for minutes.
And then it fails - so the issue could be the broker but also the client. Is the client sending some sort of keep alive messages periodically?
Could something like heartbeat otr status messages be different form regular messages transmitted?
I would like to uynderstand a bit better how the ServalStack works but there seems to be pretty minimal information on it on the web apart form the XDK documentation?
Just to close this off - it looks like you were right pointing me towards WLAN connectivity.
It seemed to be related to WiFi signal strength and the fact that the example does not necessarily detect WLAN connectivity issues.
Thanks for pointing me in the right direction.