Gentle reminder.
-
Welcome to B4X forum!
B4X is a set of simple and powerful cross platform RAD tools:
- B4A (free) - Android development
- B4J (free) - Desktop and Server development
- B4i - iOS development
- B4R (free) - Arduino, ESP8266 and ESP32 development
B4i Library MQTT - MQ Telemetry Transport for B4i
- Thread starter Alberto Iglesias
- Start date
Similar threads
B4i Library iMQTT - Official iOS MQTT clientB4A Tutorial [B4X] MQTT Chat Room
B4A Tutorial [B4X] MQTT - Connect & Reconnect
B4A Code Snippet [B4X] MQTT SSL and Self Signed Certificates
B4J Tutorial [example] [B4X] Control the desktop with your phone
Uhuuuuuu!!! I completely forgot! Sorry! Thanks for remember me!
This is the fix for this problem, please try with this new version
This is the fix for this problem, please try with this new version
Thank you, @Alberto Iglesias. Now setWill() is working!
However, these issues still remain:
1. onConnect() gets called only on connection success. There is no callback for connection failure. e.g. when broker is not available or if it is mis-typed.
2. After a successful connection, there is no connectionLost() event.
3. Topic is missing in Received() callback.
4. [Minor] Need APIs to set connection timeout and keep alive period.
Above functionality is needed to make error resilient MQTT app.
Thanks again for your support.
However, these issues still remain:
1. onConnect() gets called only on connection success. There is no callback for connection failure. e.g. when broker is not available or if it is mis-typed.
2. After a successful connection, there is no connectionLost() event.
3. Topic is missing in Received() callback.
4. [Minor] Need APIs to set connection timeout and keep alive period.
Above functionality is needed to make error resilient MQTT app.
Thanks again for your support.
Last edited:
Hi @Alberto Iglesias, please consider resolving above issues.