AsyncMQTT_Generic library
How To Install Using Arduino Library Manager
Features
This AsyncMQTT_Generic library is based on and modified from Marvin Roger's async-mqtt-client Library , to provide support to many more boards besides ESP32/ESP8266, such as STM32F, Portenta_H7, etc. boards . Those supported boards can be used with ESP8266/ESP32’s WiFi, LAN8742A Ethernet, Portenta_H7 WiFi/Ethernet.
Why Async is better
Using asynchronous network means that you can handle more than one connection at the same time
You are called once the request is ready and parsed
When you send the response, you are immediately ready to handle other connections while the server is taking care of sending the response in the background
Speed is OMG
Easy to use API, HTTP Basic and Digest MD5 Authentication (default), ChunkedResponse
Easily extensible to handle any type of content
Supports Continue 100
Async WebSocket plugin offering different locations without extra servers or ports
Async EventSource (Server-Sent Events) plugin to send events to the browser
URL Rewrite plugin for conditional and permanent url rewrites
ServeStatic plugin that supports cache, Last-Modified, default index and more
Simple template processing engine to handle templates
Currently supported Boards
This AsyncMQTT_Generic library currently supports these following boards:
ESP32
ESP8266
WT32_ETH01 (ESP32 + LAN8720A) from v1.1.0
To-be-supported Boards
STM32F/L/H/G/WB/MP1 boards with built-in Ethernet LAN8742A such as :
STM32F4/F7 boards using Ethernet LAN8720 such as :
Nucleo-144 (F429ZI, NUCLEO_F746NG, NUCLEO_F746ZG, NUCLEO_F756ZG)
Discovery (DISCO_F746NG)
STM32F4 boards (BLACK_F407VE, BLACK_F407VG, BLACK_F407ZE, BLACK_F407ZG, BLACK_F407VE_Mini, DIYMORE_F407VGT, FK407M1)
Portenta_H7 using either Murata WiFi
or Vision-shield Ethernet
Changelog
Releases v1.1.0
Add support to WT32_ETH01 (SSL and non-SSL)
Add examples for WT32_ETH01
Releases v1.0.1
Fix Library Manager warnings
Suppress all compiler warnings
Optimize library code by using reference-passing
instead of value-passing
Initial Releases v1.0.0
Initial porting and coding to support ESP32 (SSL and non-SSL) and ESP8266 (non-SSL)
Examples
1. For ESP32
FullyFeatured_ESP32
FullyFeaturedSSL_ESP32
2. For ESP8266
FullyFeatured_ESP8266
3. For WT32_ETH01
FullyFeatured_WT32_ETH01
FullyFeaturedSSL_WT32_ETH01
Debug Terminal Output Samples
1. FullyFeatureSSL_ESP32 on ESP32_DEV
This is terminal debug output when running FullyFeaturedSSL_ESP32 on ESP32_DEV connecting to broker.emqx.io
secured MQTT server (port 8883).
Starting FullyFeatureSSL_ESP32 on ESP32_DEV
AsyncMQTT_Generic v1.1.0 for ESP32 core v2.0.0+
Connecting to Wi-Fi...
WiFi ready
WiFi STA starting
WiFi STA connected
WiFi connected
IP address: 192.168.2.81
Connecting to MQTT...
Connected to MQTT broker: broker.emqx.io, port: 8883
PubTopic: async-mqtt/ESP32_SSL_Pub
************************************************
Session present: 0
Subscribing at QoS 2, packetId: 1
Publishing at QoS 0
Publishing at QoS 1, packetId: 2
Publishing at QoS 2, packetId: 3
************************************************
Subscribe acknowledged.
packetId: 1
qos: 2
Publish received.
topic: async-mqtt/ESP32_SSL_Pub
qos: 2
dup: 0
retain: 1
len: 6
index: 0
total: 6
Publish received.
topic: async-mqtt/ESP32_SSL_Pub
qos: 0
dup: 0
retain: 0
len: 10
index: 0
total: 10
Publish acknowledged
packetId: 2
Publish received.
topic: async-mqtt/ESP32_SSL_Pub
qos: 1
dup: 0
retain: 0
len: 6
index: 0
total: 6
Publish received.
topic: async-mqtt/ESP32_SSL_Pub
qos: 2
dup: 0
retain: 0
len: 6
index: 0
total: 6
Publish acknowledged
packetId: 3
2. FullyFeatureSSL_WT32_ETH01 on WT32-ETH01 with ETH_PHY_LAN8720
This is terminal debug output when running FullyFeaturedSSL_WT32_ETH01 on WT32-ETH01 connecting to broker.emqx.io
secured MQTT server (port 8883).
Starting FullyFeatureSSL_WT32_ETH01 on WT32-ETH01 with ETH_PHY_LAN8720
WebServer_WT32_ETH01 v1.4.1 for core v2.0.0+
AsyncMQTT_Generic v1.1.0 for ESP32 core v2.0.0+
ETH starting
ETH connected
ETH got IP
IP address: 192.168.2.97
Connecting to MQTT...
Connected to MQTT broker: broker.emqx.io, port: 8883
PubTopic: async-mqtt/WT32_ETH01_SSL_Pub
************************************************
Session present: 0
Subscribing at QoS 2, packetId: 1
Publishing at QoS 0
Publishing at QoS 1, packetId: 2
Publishing at QoS 2, packetId: 3
************************************************
Subscribe acknowledged.
packetId: 1
qos: 2
Publish received.
topic: async-mqtt/WT32_ETH01_SSL_Pub
qos: 0
dup: 0
retain: 0
len: 15
index: 0
total: 15
Publish acknowledged
packetId: 2
Publish received.
topic: async-mqtt/WT32_ETH01_SSL_Pub
qos: 1
dup: 0
retain: 0
len: 6
index: 0
total: 6
Publish received.
topic: async-mqtt/WT32_ETH01_SSL_Pub
qos: 2
dup: 0
retain: 0
len: 6
index: 0
total: 6
Publish acknowledged
packetId: 3
1 Like
Releases v1.2.0
Add support to STM32F/L/H/G/WB/MP1 (without TLS/SSL) using built-in LAN8742A
Ethernet, such as Nucleo-144, DISCOVERY, etc.
Add examples for STM32
Debug Terminal Output Samples
1. FullyFeature_STM32 on NUCLEO_F767ZI
This is terminal debug output when running FullyFeature_STM32 on STM32F7 NUCLEO_F767ZI connecting to broker.emqx.io
MQTT server. The Ethernet loss was tested by disconnecting, then reconnecting the Ethernet cable.
Starting FullyFeature_STM32 on NUCLEO_F767ZI
AsyncMQTT_Generic v1.2.0 for STM32
Connected to network. IP = 192.168.2.118
Connecting to MQTT...
Connected to MQTT broker: broker.emqx.io, port: 1883
PubTopic: async-mqtt/STM32_Pub
************************************************
Session present: 0
Subscribing at QoS 2, packetId: 1
Publishing at QoS 0
Publishing at QoS 1, packetId: 2
Publishing at QoS 2, packetId: 3
************************************************
Subscribe acknowledged.
packetId: 1
qos: 2
Publish received.
topic: async-mqtt/STM32_Pub
message: STM32 Test3
qos: 2
dup: 0
retain: 1
len: 11
index: 0
total: 11
Publish acknowledged.
packetId: 2
Publish received.
topic: async-mqtt/STM32_Pub
message: STM32 Test1
qos: 0
dup: 0
retain: 0
len: 11
index: 0
total: 11
Publish received.
topic: async-mqtt/STM32_Pub
message: STM32 Test2
qos: 1
dup: 0
retain: 0
len: 11
index: 0
total: 11
Publish received.
topic: async-mqtt/STM32_Pub
message: STM32 Test3
qos: 2
dup: 0
retain: 0
len: 11
index: 0
total: 11
Publish acknowledged.
packetId: 3
Ethernet disconnected <==== Test disconnect Ethernet very short time
Ethernet reconnected.
Ethernet disconnected <==== Test disconnect Ethernet long enough time to force MQTT disconnection
Ethernet reconnected.
Disconnected from MQTT. <==== MQTT disconnected and reconnected
Connected to MQTT broker: broker.emqx.io, port: 1883
PubTopic: async-mqtt/STM32_Pub
************************************************
Session present: 0
Subscribing at QoS 2, packetId: 4
Publishing at QoS 0
Publishing at QoS 1, packetId: 5
Publishing at QoS 2, packetId: 6
************************************************
Subscribe acknowledged.
packetId: 4
qos: 2
Publish received.
topic: async-mqtt/STM32_Pub
message: STM32 Test3
qos: 2
dup: 0
retain: 1
len: 11
index: 0
total: 11
Publish acknowledged.
packetId: 5
Publish received.
topic: async-mqtt/STM32_Pub
message: STM32 Test1
qos: 0
dup: 0
retain: 0
len: 11
index: 0
total: 11
Publish received.
topic: async-mqtt/STM32_Pub
message: STM32 Test2
qos: 1
dup: 0
retain: 0
len: 11
index: 0
total: 11
Publish received.
topic: async-mqtt/STM32_Pub
message: STM32 Test3
qos: 2
dup: 0
retain: 0
len: 11
index: 0
total: 11
Publish acknowledged.
packetId: 6
Releases v1.2.1
Add support to many STM32F4 and STM32F7 (without TLS/SSL) using LAN8720
Ethernet, such as F407xx, NUCLEO_F429ZI, DISCO_F746NG, NUCLEO_F746ZG, NUCLEO_F756ZG, etc.
Add examples for STM32_LAN8720
Debug Terminal Output Samples
1. FullyFeatured_STM32_LAN8720 on BLACK_F407VE
This is terminal debug output when running FullyFeatured_STM32_LAN8720 on STM32F4 BLACK_F407VE connecting to broker.emqx.io
MQTT server.
Starting FullyFeatured_STM32_LAN8720 on BLACK_F407VE
AsyncMQTT_Generic v1.2.1 for STM32
Connected to network. IP = 192.168.2.132
Connecting to MQTT...
Connected to MQTT broker: broker.emqx.io, port: 1883
PubTopic: async-mqtt/STM32_Pub
************************************************
Session present: 0
Subscribing at QoS 2, packetId: 1
Publishing at QoS 0
Publishing at QoS 1, packetId: 2
Publishing at QoS 2, packetId: 3
************************************************
Subscribe acknowledged.
packetId: 1
qos: 2
Publish received.
topic: async-mqtt/STM32_Pub
message: STM32 Test3
qos: 2
dup: 0
retain: 1
len: 11
index: 0
total: 11
Publish acknowledged.
packetId: 2
Publish received.
topic: async-mqtt/STM32_Pub
message: STM32 Test1
qos: 0
dup: 0
retain: 0
len: 11
index: 0
total: 11
Publish received.
topic: async-mqtt/STM32_Pub
message: STM32 Test2
qos: 1
dup: 0
retain: 0
len: 11
index: 0
total: 11
Publish received.
topic: async-mqtt/STM32_Pub
message: STM32 Test3
qos: 2
dup: 0
retain: 0
len: 11
index: 0
total: 11
Publish acknowledged.
packetId: 3
Releases v1.3.0
Add support to Portenta_H7 , using either Murata WiFi
or Vision-shield Ethernet
Add examples for Portenta_H7_Ethernet
and Portenta_H7_WiFi
Debug Terminal Output Samples
1. FullyFeatured_PortentaH7_WiFi on PORTENTA_H7_M7
This is terminal debug output when running FullyFeatured_PortentaH7_WiFi on STM32H7 PORTENTA_H7_M7 using Murata WiFi
, connecting to broker.emqx.io
MQTT server.
Starting FullyFeatured_PortentaH7_WiFi on PORTENTA_H7_M7
AsyncMQTT_Generic v1.3.0 for Portenta_H7_M7
Connecting to SSID: HueNet1
Connected to SSID: HueNet1
Local IP Address: 192.168.2.134
Signal strength (RSSI):-37 dBm
Connecting to MQTT...
Connected to MQTT broker: broker.emqx.io, port: 1883
PubTopic: async-mqtt/Portenta_H7_WiFi_Pub
************************************************
Session present: 0
Subscribing at QoS 2, packetId: 1
Publishing at QoS 0
Publishing at QoS 1, packetId: 2
Publishing at QoS 2, packetId: 3
************************************************
Subscribe acknowledged.
packetId: 1
qos: 2
Publish received.
topic: async-mqtt/Portenta_H7_WiFi_Pub
message: Portenta_H7_WiFi Test 3
qos: 2
dup: 0
retain: 1
len: 23
index: 0
total: 23
Publish acknowledged.
packetId: 2
Publish received.
topic: async-mqtt/Portenta_H7_WiFi_Pub
message: Portenta_H7_WiFi Test1
qos: 0
dup: 0
retain: 0
len: 22
index: 0
total: 22
Publish received.
topic: async-mqtt/Portenta_H7_WiFi_Pub
message: Portenta_H7_WiFi Test 2
qos: 1
dup: 0
retain: 0
len: 23
index: 0
total: 23
Publish received.
topic: async-mqtt/Portenta_H7_WiFi_Pub
message: Portenta_H7_WiFi Test 3
qos: 2
dup: 0
retain: 0
len: 23
index: 0
total: 23
Publish acknowledged.
packetId: 3
2. FullyFeatured_Portenta_H7_Ethernet on PORTENTA_H7_M7
This is terminal debug output when running FullyFeatured_PortentaH7_Ethernet on STM32H7 PORTENTA_H7_M7 , using built-in Ethernet
, connecting to broker.emqx.io
MQTT server.
Starting FullyFeatured_PortentaH7_Ethernet on PORTENTA_H7_M7
AsyncMQTT_Generic v1.3.0 for Portenta_H7_M7
Connected to network. IP = 192.168.2.133
Connecting to MQTT...
Connected to MQTT broker: broker.emqx.io, port: 1883
PubTopic: async-mqtt/Portenta_H7_Ethernet_Pub
************************************************
Session present: 0
Subscribing at QoS 2, packetId: 1
Publishing at QoS 0
Publishing at QoS 1, packetId: 2
Publishing at QoS 2, packetId: 3
************************************************
Subscribe acknowledged.
packetId: 1
qos: 2
Publish received.
topic: async-mqtt/Portenta_H7_Ethernet_Pub
message: Portenta_H7_Ethernet Test3
qos: 2
dup: 0
retain: 1
len: 26
index: 0
total: 26
Publish acknowledged.
packetId: 2
Publish received.
topic: async-mqtt/Portenta_H7_Ethernet_Pub
message: Portenta_H7_Ethernet Test1
qos: 0
dup: 0
retain: 0
len: 26
index: 0
total: 26
Publish received.
topic: async-mqtt/Portenta_H7_Ethernet_Pub
message: Portenta_H7_Ethernet Test2
qos: 1
dup: 0
retain: 0
len: 26
index: 0
total: 26
Publish received.
topic: async-mqtt/Portenta_H7_Ethernet_Pub
message: Portenta_H7_Ethernet Test3
qos: 2
dup: 0
retain: 0
len: 26
index: 0
total: 26
Publish acknowledged.
packetId: 3
Ethernet disconnected <==== Test disconnect Ethernet very short time
Ethernet reconnected.
Ethernet disconnected <==== Test disconnect Ethernet long enough time to force MQTT disconnection
Ethernet reconnected.
[ATCP] setCloseError() to: Connection reset => -14
Disconnected from MQTT. <==== MQTT disconnected and reconnected
Connected to MQTT broker: broker.emqx.io, port: 1883
PubTopic: async-mqtt/Portenta_H7_Ethernet_Pub
************************************************
Session present: 0
Subscribing at QoS 2, packetId: 4
Publishing at QoS 0
Publishing at QoS 1, packetId: 5
Publishing at QoS 2, packetId: 6
************************************************
Subscribe acknowledged.
packetId: 4
qos: 2
Publish received.
topic: async-mqtt/Portenta_H7_Ethernet_Pub
message: Portenta_H7_Ethernet Test3
qos: 2
dup: 0
retain: 1
len: 26
index: 0
total: 26
Publish acknowledged.
packetId: 5
Publish received.
topic: async-mqtt/Portenta_H7_Ethernet_Pub
message: Portenta_H7_Ethernet Test1
qos: 0
dup: 0
retain: 0
len: 26
index: 0
total: 26
Publish received.
topic: async-mqtt/Portenta_H7_Ethernet_Pub
message: Portenta_H7_Ethernet Test2
qos: 1
dup: 0
retain: 0
len: 26
index: 0
total: 26
Publish received.
topic: async-mqtt/Portenta_H7_Ethernet_Pub
message: Portenta_H7_Ethernet Test3
qos: 2
dup: 0
retain: 0
len: 26
index: 0
total: 26
Publish acknowledged.
packetId: 6
Releases v1.4.0
Add support to Teensy 4.1 using QNEthernet Library
Add example for QNEthernet
Debug Terminal Output Samples
1. FullyFeatured_QNEthernet on TEENSY 4.1 using QNEthernet
This is terminal debug output when running FullyFeatured_QNEthernet on TEENSY 4.1 , using built-in Ethernet with QNEthernet Library
, connecting to broker.emqx.io
MQTT server.
Starting FullyFeatured_QNEthernet on TEENSY 4.1
AsyncMQTT_Generic v1.4.0 for Teensy 4.1 QNEthernet
Initialize Ethernet using static IP => Connected! IP address:192.168.2.222
Connecting to MQTT...
Connected to MQTT broker: broker.emqx.io, port: 1883
PubTopic: async-mqtt/Teensy41_QNEthernet_Pub
************************************************
Session present: 0
Subscribing at QoS 2, packetId: 1
Publishing at QoS 0
Publishing at QoS 1, packetId: 2
Publishing at QoS 2, packetId: 3
************************************************
Subscribe acknowledged.
packetId: 1
qos: 2
Publish received.
topic: async-mqtt/Teensy41_QNEthernet_Pub
message: Teensy41_QNEthernet_Pub Test3
qos: 2
dup: 0
retain: 1
len: 29
index: 0
total: 29
Publish acknowledged.
packetId: 2
Publish received.
topic: async-mqtt/Teensy41_QNEthernet_Pub
message: Teensy41_QNEthernet_Pub Test1
qos: 0
dup: 0
retain: 0
len: 29
index: 0
total: 29
Publish received.
topic: async-mqtt/Teensy41_QNEthernet_Pub
message: Teensy41_QNEthernet_Pub Test2
qos: 1
dup: 0
retain: 0
len: 29
index: 0
total: 29
Publish received.
topic: async-mqtt/Teensy41_QNEthernet_Pub
message: Teensy41_QNEthernet_Pub Test3
qos: 2
dup: 0
retain: 0
len: 29
index: 0
total: 29
Publish acknowledged.
packetId: 3
Releases v1.5.0
Add support to ESP8266 W5x00 using lwIP_w5100 or lwIP_w5500 library
Add support to ESP8266 ENC28J60 using lwIP_enc28j60 library
Add example FullyFeatured_ESP8266_Ethernet
Update Packages' Patches
Debug Terminal Output
1. FullyFeatured_ESP8266_Ethernet on ESP8266_NODEMCU_ESP12E using ESP8266_ENC28J60 Ethernet
This is terminal debug output when running FullyFeatured_ESP8266_Ethernet on ESP8266_NODEMCU_ESP12E , using ENC28J60 Ethernet
with lwIP_enc28j60
Library, connecting to broker.emqx.io
MQTT server.
Starting FullyFeatured_ESP8266_Ethernet on ESP8266_NODEMCU_ESP12E using ESP8266_ENC28J60 Ethernet
AsyncMQTT_Generic v1.5.0 for ESP8266
Connecting to network : .....................................
Ethernet DHCP IP address: 192.168.2.187
Connecting to MQTT...
Connected to MQTT broker: broker.emqx.io, port: 1883
PubTopic: async-mqtt/ESP8266_Pub
************************************************
Session present: 0
Subscribing at QoS 2, packetId: 1
Publishing at QoS 0
Publishing at QoS 1, packetId: 2
Publishing at QoS 2, packetId: 3
************************************************
Subscribe acknowledged.
packetId: 1
qos: 2
Publish received.
topic: async-mqtt/ESP8266_Pub
message: ESP8266_Ethernet Test3
qos: 2
dup: 0
retain: 1
len: 22
index: 0
total: 22
Publish acknowledged.
packetId: 2
Publish received.
topic: async-mqtt/ESP8266_Pub
message: ESP8266_Ethernet Test1
qos: 0
dup: 0
retain: 0
len: 22
index: 0
total: 22
Publish received.
topic: async-mqtt/ESP8266_Pub
message: ESP8266_Ethernet Test2
qos: 1
dup: 0
retain: 0
len: 22
index: 0
total: 22
Publish received.
topic: async-mqtt/ESP8266_Pub
message: ESP8266_Ethernet Test3
qos: 2
dup: 0
retain: 0
len: 22
index: 0
total: 22
Publish acknowledged.
packetId: 3
2. FullyFeatured_ESP8266_Ethernet on ESP8266_NODEMCU_ESP12E using ESP8266_W5500 Ethernet
This is terminal debug output when running FullyFeatured_ESP8266_Ethernet on ESP8266_NODEMCU_ESP12E , using W5500 Ethernet
with lwIP_w5500
Library, connecting to broker.emqx.io
MQTT server.
Starting FullyFeatured_ESP8266_Ethernet on ESP8266_NODEMCU_ESP12E using ESP8266_W5500 Ethernet
AsyncMQTT_Generic v1.5.0 for ESP8266
Connecting to network : .
Ethernet DHCP IP address: 192.168.2.188
Connecting to MQTT...
Connected to MQTT broker: broker.emqx.io, port: 1883
PubTopic: async-mqtt/ESP8266_Pub
************************************************
Session present: 0
Subscribing at QoS 2, packetId: 1
Publishing at QoS 0
Publishing at QoS 1, packetId: 2
Publishing at QoS 2, packetId: 3
************************************************
Subscribe acknowledged.
packetId: 1
qos: 2
Publish received.
topic: async-mqtt/ESP8266_Pub
message: ESP8266_Ethernet Test3
qos: 2
dup: 0
retain: 1
len: 22
index: 0
total: 22
Publish acknowledged.
packetId: 2
Publish received.
topic: async-mqtt/ESP8266_Pub
message: ESP8266_Ethernet Test1
qos: 0
dup: 0
retain: 0
len: 22
index: 0
total: 22
Publish received.
topic: async-mqtt/ESP8266_Pub
message: ESP8266_Ethernet Test2
qos: 1
dup: 0
retain: 0
len: 22
index: 0
total: 22
Publish received.
topic: async-mqtt/ESP8266_Pub
message: ESP8266_Ethernet Test3
qos: 2
dup: 0
retain: 0
len: 22
index: 0
total: 22
Publish acknowledged.
packetId: 3
Releases v1.7.0
Fix ESP32 compile error. Check Missing default case in switch causes #10
Change to new Forked ESPAsyncTCP library for ESP8266 boards, using WiFi or LwIP Ethernet, with ESP8266 core v3.0.2+ or WiFi with ESP8266 core v2.7.4 to avoid compile errors
Releases v1.6.1
Workaround for RP2040W WiFi.status()
bug using ping()
to local gateway for example FullyFeatured_RP2040W
Use WiFi macAddress for RP2040W _clientId
Releases v1.6.0
Add support to RASPBERRY_PI_PICO_W with CYW43439 WiFi , using arduino-pico core v2.4.0+
Add example FullyFeatured_RP2040W
Update Packages' Patches
Debug Terminal Output
1. FullyFeature_RP2040W on RASPBERRY_PI_PICO_W
This is terminal debug output when running FullyFeature_RP2040W on RASPBERRY_PI_PICO_W , using CYW43439 WiFi
, connecting to broker.emqx.io
MQTT server.
Starting FullyFeature_RP2040W on RASPBERRY_PI_PICO_W
AsyncMQTT_Generic v1.7.0 for RP2040W CYW43439 WiFi
Connecting to SSID: HueNet2
Connected to SSID: HueNet2
Local IP Address: 192.168.2.180
Signal strength (RSSI):0 dBm
Connecting to MQTT...
Connected to MQTT broker: broker.emqx.io, port: 1883
PubTopic: async-mqtt/RP2040W_Pub
************************************************
Session present: 0
Subscribing at QoS 2, packetId: 1
Publishing at QoS 0
Publishing at QoS 1, packetId: 2
Publishing at QoS 2, packetId: 3
************************************************
Subscribe acknowledged.
packetId: 1
qos: 2
Publish received.
topic: async-mqtt/RP2040W_Pub
message: RP2040W Test3
qos: 2
dup: 0
retain: 1
len: 13
index: 0
total: 13
Publish acknowledged.
packetId: 2
Publish received.
topic: async-mqtt/RP2040W_Pub
message: RP2040W Test1
qos: 0
dup: 0
retain: 0
len: 13
index: 0
total: 13
Publish received.
topic: async-mqtt/RP2040W_Pub
message: RP2040W Test2
qos: 1
dup: 0
retain: 0
len: 13
index: 0
total: 13
Publish received.
topic: async-mqtt/RP2040W_Pub
message: RP2040W Test3
qos: 2
dup: 0
retain: 0
len: 13
index: 0
total: 13
Publish acknowledged.
packetId: 3
Using AsyncMQTT_Generic and Portenta_H7_AsyncWebServer libraries combined, makes Mbd Os Crash after muliple Web Server Calls.
See javos65/AsyncWebServer_plus_MQTT: Example Portenta MQTT plus Async Webserver (github.com)
Any one with a working MQTT + Webserver example working?
system
Closed
July 31, 2023, 7:06pm
10
This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.