mqtt-client

./configure \
  --prefix="${INSTALL_DIR}" \
  --libdir="${LIBDIR}" \
  --bindir="${BINDIR}" \
  --sbindir="${SBINDIR}" \
  --sysconfdir="${SYSCONFDIR}" \
  --localstatedir="${LOCALSTATEDIR}" \
  --datarootdir="${DATAROOTDIR}" \
  --datarootdir="${DATADIR}" \    <--- Should this second datarootdir be datadir?
  --disable-all-plugins \
  --host="

Current behavior (how does the issue manifest):
The lambda invoke activity returns a value object which includes the payload and the []byte serialized response. This really has no real purpose and causes confusion between the unmarshaled payload in the return param result .

Expected behavior:
Remove the value param, as both the unmarshaled payload and the status are both returne

Some more stats for perfromace would be nice:

• Messages last minute
• Messages last hour
• Messages last 24h
• Shortest time between messages
• Min/max/average message payload size

Device normal info

• Smart Wireless Switch M2

Device info:

{
"active_time": 1624995021,
"biz_type": 18,
"category": "wxkg",
"create_time": 1624995021,
"icon": "smart/icon/ay1536047723331OpdLN/166bec229d0c60605b4d068e0d9b7e50.png",
"id": "eb7669e6fb880cb4c******",
"ip": "",
"lat": "",
"local_key": "***",
"lon

Problem or use case

The client is currently only logging errors and warnings. For debugging purposes and during application development, it would be very useful to also have logs detailing the message flow.

Preferred solution or suggestions

TRACE level logging for incoming and outgoing MQTT control packet types, e.g., PUBLISH, SUBSCRIBE, PUBACK, SUBACK.

Hi all,

Firstly many thanks for this library - I'm working heavily with the ESP8266 NonOS SDK and have been looking for a replacement MQTT library due to several problems with the current one. The ESP folks have rewritten the MQTT in their RTOS SDK but have made some weird decisions around the use of blocking socket calls and other things :-(

This library has a lot of potential to replace th